Good NewsThe new GoldenHawk 3.8G library (in MJ8.0.206 and later) has solved a longtime problem I've had with
all MJ releases. That problem had to do with data CD burns and the physical order of the burns...now Goldenhawk burns the data tracks in filename order inside each sub-dir (a giant 'hurray' from me).
Now, new issues (bugs) to report:1. There's a new (pesky) popup dialog that displays when you add tracks to a data CD burn list and the filename contains more than 64 characters, with this message:
The following filenames are too long for writing to a CD. They will be truncated to 64 characters.
This popop message occurs when you initially add tracks to the burn list and when you reorganize (rename folders) in the burn list...annoying. Can we have an option to turn this message off if we don't want to see it everytime?
Now, something must have changed in MJ and what settings/format it uses to burn a data CD because in all releases prior to 206, 64 characters was not the limit. I've burned 40|PLS| backup data CDs using MJ and those CDs have filenames on them greater than 64 characters. So what changed? And, can we have an option in the CD burning options to choose the data CD format we want (Joliet, ISO 9660, XA, Joliet |PLS| ISO 9660, etc...I'm not an expert at formats). It seems the new MJ data burn format solved one problem for me, but has started another problem I can't accept for my data CD backup (I don't want to lose my original filenames and make restores a pain). I really, really want to use MJ for all my music-related burning tasks...I got my last issue fixed, but now my backups aren't acceptable. I'd really rather have the backup data CD burns work because everything is catologed in MJ and have the physical burn order problem remain (if I had a choice). Maybe a user-selectable burn format option will solve everything (I hope).
2. With a data CD burn list created and tracks added, the Update Order right-click menu option does not work...it does not retain the new order. It looks like it works, but leaving the Devices' node and returning show the order is lost. The Playlist.m3u file that MJ creates automatically on the CD during the burn also does not reflect the 'updated' order.
3. If you manually rename folders in a burn list (via the Org Tree nodes), the Playlist.m3u file MJ burns to the CD contains the old/original folder names. So, basically, MJ burns a CD with a .m3u file that is useless because it references folders on the disk that do not exist (if you renamed them manually). I did not verify what happens if you use the Rearrange CD Folders option (I'll leave that for you guys to test).
4. If MJ truncates a file's name to 64 characters, that truncacted name is not reflected in the Playlist.m3u file MJ creates on the burned CD. So, again the .m3u file is useless.
5. What will MJ do if the truncated to 64 character filenames create filename duplicates because the 1st 64 characters of two or more files are the same? I think that should be tested and fixed too (if a problem). I was doing some tests and noticed one set of album's MP3s I had were duplicated in the 1st 60 characters...just under what was needed to keep them unique for a successful burn!!
Thanks!!For everthing...someday we'll all be happy when MJ8.0 is released and
soooo stable.
Author
Topic: MJ 8.0.217 Beta Available... (Read 6908 times)