Ok, I’ve just put up a beta version of the 3.71 media player so everyone can check out the new CDDA stuff. It’d be great if you could all download it, test the digital cd playback and post back here if you have any problems. Here’s the url:

[url:3n0zzs83]http://www.fmod.org/files/fmod371.zip[/url:3n0zzs83]

The interface has changed a bit. Hit ‘Load CD’ to populate the playlist with the currently loaded CD’s tracks then just play them as usual. Notice that the CD output now appears in the scope and spectrum. 😀

The Options dialog is now accessible through the system menu in the top left of the main window. Choose your CD drive letter here and also choose digital or analog playback. There’s also a big “Device Info…” button that will report a bunch of details on the currently selected CD device.

If you have problems with CDDA, get the device info and mail it to me at andrew@fmod.org – don’t post it here or the thread will get too cluttered. Don’t forget to include a description of the problem you encountered. This is definitely still a BETA release so don’t expect it to work perfectly – I just want to get it out asap so I can start hitting the inevitable compatibility issues that are bound to turn up.

Yeah, I’ve used a few CDDA extraction programs, AudioCatalyst / Audiograbber (XING), and a few others in the past. They’ve all worked correctly and haven’t taken a lot of CPU time at all. Plus, I use Sonique 2 which also has CD ripping to do CDDA visuals and it works fine.

[quote="andrew":20kohdg2]Paranoid Android, does the CPU usage jump like that when you put effects on an mp3 or only for CD tracks? The effects are definitely not taking that much CPU time so it may be that I’m calculating the CPU usage incorrectly. If you check out the Windows performance monitor you’ll see that FMOD’s not taking much CPU time at all.[/quote:20kohdg2]

Well, I just tested it with an MP3 and I observed the same problem, when the song was playing without any DSP effects the cpu usage was around 1%, but when I turned effects on and then turned them back off the CPU usage started growing rapidly, it started around 2% and kept going up and eventually stopped at around 24%. Which isnt as bad as when playing a cd track where the cpu usage reached up to 100%. SO, Im not sure what the problem is, but without any DSP effects, both MP3 and CDA work perfectly with CPU usage at 1% – 1.5%.

Sorry, I didn’t know that there was a config dialog box, now I know what is the system menu 😆 … In the config dialog, no CD drive was selected so no CD was loading. I selected one, the G:, and know it works

Second:

It’s about the CPU usage, it starts at 1% and go up until 45% and then it stays there.

But there is a problem:
The first device, G: (DVD-Rom), works perfectly, but the second, H: (DVD±RW) isn’t recognized, I get the error message “ERROR: Couldn’t access CD/DVD device at H:” if I want a device report or if I want to load the CD.

Hopefully there is a good new, the CPU usage stays at about 7%, which is better but not necessarely exact.

You can now turn jitter correction on/off in the Options dialog. If you’re getting very high CPU usage, try turning jitter correction off and see what happens. If this doesn’t help, hit “Device info…” in the Options dialog and send me all the results.

Also the “amount” of jitter that’s being corrected is now displayed as the CD plays. If this doesn’t stay on or close to 0% then let me know what it gets to and what your CPU usage is and also send me your device info.

Thanks everyone!

Oh, and btw, J-F you’ll only be able to access your first CD device if you’re using ASPI. Sucks, I know, but that’s how it’s going to be for FMOD 3.xx. FMOD 4 won’t have this limitation.

[quote="andrew":1d90y64u]J-F, no that jitter correction % was just for beta testing.

Paranoid_Android, is the final release any better on the CPU time?[/quote:1d90y64u]

Definitely! I played a few CD tracks all the way through with the CPU usage being below 1%. Whatever you did it worked 😀 The only thing I noticed was when I clicked the Device info button all I got was the name of my CD device, not the extensive report that it gave before.

J-F can you give me some details on your system? What operating system are you running? How many CD/DVD devices do you have and how many hard drives? What are their drive letters meant to be? Are any of them SCSI devices?

As far as the extensive device info goes, we decided not to bloat the dll with all that code and text when most people won’t get any use out of it. We’ll still have a special build available on request that has all the info in there in case it’s needed for debugging purposes.