INTERACT FORUM
More => Old Versions => Media Center 11 (Development Ended) => Topic started by: Markeau on November 29, 2002, 11:08:23 am
-
Before burning with cdr's I have been trying cdrw's on my Yamaha CRW2200E which worked fine with MJ8. The first try was successful, except no crossfade, with these options:
Use internal ASPI layer
Decode files directly to CD
Write CD-Text
Apply current playback settings to the CD
Then to try to get crossfade I tried every combination of the available options but no tracks ever get written to the cdrw even though the dialogs say the burning was successful. I then reset the options to the above and can successfully burn, but no crossfade. If I try to playback the newly burned audio cd nothing is played and the little speaker icon just cycles thru each track, and if I exit and restart MC then click on the first track of the new cdrw MC hangs and has to be killed in Task Manager .
Also, the max speed for the 2200E is 20x but the max available in the CD Writer options dialog is 4x.
-
you might want to try the external burner driver, there is an option for it under options\writer
play with the options using it under "test" to save disks
-
I fixed it. During a cdrw format I got a XPpro bluescreen referencing the IDE driver. I had been using the Intel Application Accelerator 2.3 (includes tweaked IDE driver) successfully for about a month but became suspicous of it since the previous IAA 2.2 gave a similar error (during a defrag).
So the short of it is that after removing IAA 2.3 and installing the XPpro native IDE driver *all* of the burning options work correctly including crossfade!
And the max speed option is now back up to 20x where it should be.
At some time I would hope that MC would properly work with IAA 2.3, but it's not a show stopper and the workaround is easy - just revert back to the native XP IDE driver. For those that don't know, the IAA is for most of the later Intel mobo's like my 850EMV2.
-
maybe you should talk to the people who make IAA 2.3 and tell them your problem so maybe they can maybe make a fix
-
But all worked fine in MJ8 ...