OK, I use burnatonce to make a data disc of MP3 files. It works OK for one folder of MP3 files, ripped with EAC and compressed with LAME. But another it burns the data MP3's not as MP3's at all and in another it burns 4 out of about 20 as MP3's the rest as non-MP3's

All the files play from the computer in fb2k; QuestionMan and Encspot say they are OK and MP3Ext shows them at the proper ripped rate. Whazzup!?

Are you sure you picked data mode? Try using another burning program. If you're not clear, we can't help.

Am I sure I picked data mode?? English has been my native tongue for 66 years. I read and write it pretty well. I even graduated from a good university in your city, in English. My French was not up to the challenge.

I have repeated the burn experiment with two drives and with CD-W and CR-RW discs. It happens not with all MP3 files but it does with these. The results are always the same regardless of the drive or the disc or the data. I can change the data, the drive and the disc and still get the same results.

fb2k, encspot and QuestionMan all see the MP3 files as OK, as does MP3Ext.

I am mystified by this.

I burn a data disc from a different directory and it works just fine. Tabernacle, eh!

From your description it is not clear what happens. What does "burns ... the rest as non-MP3's" mean? Do the files' extensions change once they are burned to the CD-R?

I get a file which responds to the MP3Ext tooltip software and tells me all about the file: artist, song, track, time, etc. It is not "seen" as an MP3, however. And it will not be played as an MP3. fb2k does not know what it is. No EXT I would guess.

What is weird is that this only happens with opera (so far). Blues, Rock, Jazz and whatever burn just fine. That is an aside, though. I am sure the genre has nothing to do with it. Too weird. I am stumped. I have never seen anything like it. For yuks I will uninstall burnatonce and try it with a fresh install.

BAO has some bugs in it however that has to be the strangest I've read about so far, and knock on wood I haven't had any troubles with it. If it can't be figured out using a solution from within the GUI I'd recommend posting it as a bug on the BAO forums.

• Have you customized the settings in:
  Mastering->Data CD...->ISO Settings
  The point I'm making is, have you enabled something you shouldn't have.
• Are the folder depths for the files too deep.
• Are the filenames too long.

Is it possible these are actully mpeg2 or mpeg2.5 files with an mp3 extension?

check the full file name perhaps?

bao balked at the file name lengths and I enabled "long joliet" to get past that.

I wish. They are all MP3's of my own CD's ripped with EAC and compressed with LAME V2. I checked them with Encspot, Questionman, MP3Ext and fb2k and they all show up as MP3's.

Folders and name lengths are OK. Lengths were too long and I enabled "long joliet" to get past that. This anomoloy just started. I have used bao for along time with no trouble. I wonder if Nero could be upsetting it somehow.

Also, I uninstalled bao 0.95 and installed bao 0.99b and now it burns the first track on each CD OK and the others are bogus. Does it hate Puccini? Just a thought.

FWIW, I just burned the MP3's to the CD-RW using Nero and it worked just fine. This means the bug is in using bao. It never happened before Nero was installed so it could be Nero is the rat or that bao just has suddenly (??!!) begun to fail, even on a fresh install.

Any ideas???

Definitely seems that it has to do with the filenaming. I just don't know if it is an erroneous configuration or a bug.

Nero 6.x and BOA 0.99b plus 0.995 coexisted peacefully on my system for years (WinXP)...

I never thought of Nero as an animal though

I doubt it is filenaming as Nero did the deed without a squawk. Also, some files in the same directory got written by bao and some did not. And while none did in bao 0.95 two did in the same directory in bao 0.99.5. How weird is this??

Well, if Nero is interfering with bao it is a rat. ;o) If it is not, it is a good pice of software.

My guess would be the iso settings, a screwed up SPTI, etc., but who knows for sure. You may need to look at your bao log file. In the screenshot below are the bao iso settings I've been using ever since I started using the program, and not once has it given me any problems.

I will set up bao as you have and give it a test. Right now I am ripping and burning DVD's so it will not be until later this afternoon. Thanks to you and all the other nice folks who have given me suggestions to shoot this bug.

I have set up bao as you have yours. I have burned a "data disc" of MP3's and gotten track 1 on CD1 and track 1 on CD2. The log is clean. I have included it:

SPTILOCK:1,1,0: LITE-ON DVDRW SOHW-812S Rev: US0J

Starting write at speed 4...
Turning BURN-Proof on
Using 16 byte P-Q sub-channel data mode.
Executing power calibration...
Power calibration successful.
Writing lead-in and gap...
Writing track 01 (mode MODE1/AUDIO )...

Wrote 90299 blocks. Buffer fill min 99%/max 100%.
Writing lead-out...

Flushing cache...
Writing finished successfully.

There are two MP3 files, two playlists and two files EAC generated during extraction as I added the whole directory. I ran a test earlier on got the same thing except track 1 on CD1 did not burn. Woohoo; must be beacuse it is a new moon.

You stated you wrote a data CD, however the quoted line above would suggest it resulted into an data/audio CD.? Huh? That's really strange!

Let me test writing an mp3 of my own and look at my log....
....I'd have to guess something is messed up with your install of BAO or the installed ASPI driver. If you aren't using Windows 2000 or XP, and are using Adaptec's ASPI driver make certain you are using the recommended version which is downloadable on the BAO mainpage which is v4.60.

A data disc should have this listed as the writing mode as shown from within the BAO log output.txt:
Writing track 01 (mode MODE1/MODE1 )...

After writting an audio CD this should be what's listed in the log:
Writing track 01 (mode AUDIO/AUDIO )...

I have no clue what's causing this.

OK, I am WXP, SP2 and up-to-date with all that M$ offers for updates. I run anti-virus software, anti-spy software and run a firewall. I run chkdsk and every three months now I am running SpinRite. I try to keep this machine clean and efficient. I am stumped, too.

As for bao: I did an uninsntall and then installed 0.99.5 and then the update so I should be current. I know it will be some little thing, but so far that "little thing" has eluded me. Reminds me of the days coding and having a production program fail and have about two or three days of crawling through code looking for the one bad line. Ah, computers!

What do you mean, "guess"? Can't you check it?
If there is no file extension, it means that BAO chops a part of the filename along with it. Wouldn't be surprised, considering how long classical title can get. The solution would be keep their lenght down, say, under 64 chars.

Good luck.

OK, I will check that. But, Nero burns the MP3 CD from the same folder no problem. I have long names and no folder limit enabled in bao so I am stumped, still. Sheesh, maybe I should just write them out longhand. ;o)

You mean, shorthand? Heh, that could be the solution!
Why not switch to DVDRs and UDF? Shrink the number of discs by 6X, less work burning, less work retrieving.

I am usually just putting an entire opera on a CD in MP3 format to play on the LR stereo or in the truck or at work on the computer there. It is a good way to squeeze an opera onto one disc. Sometimes I will just put a whole bunch of choral music and masses, or the SRV 79 - 80 tour taped off the soundboard of the gigs. Nero does it fine; bao chokes. bao 0.98, bao 0.99, bao 0.99.5. Hmmph. And it just started this weird behavior in the last few weeks. Must be that the moon is in the second house . . .

Ah, bao must not like opera music.

You know, I think you might be right. Just loves SRV, though. Stone kick-out-the-jams roadhouse rocker, fer sure.