Burning takes too much time with CD Architect 5.2

Jack from Multiview Inc. wrote on 3/25/2005, 1:35 PM
Hey people,

I'm new here. I've been using SF6 for 2 years now for work. Love it. I just got the 8.0 version. Seems to be ok for what I need it for but I had to do some initial settings before using it (unlike SF6).

Anyways, I really like CD Architect 5.2. Very easy to use. However, it takes close to 10 minutes to burn an audio CD at max speed (48X)!! It looks like my cache goes down real fast. Why is that?? When I burn with Nero, it takes about 3 minutes. Now when I bring my burning speed down to 16X, it takes about 5 minutes to burn but still a little slow for me. i would like to burn at full speed without that cache going down. Remember, it does not happen with Nero or even Easy CD Creator. Anyone know why this is happening?? In the field I am in, it's very important to burn my master CDs ASAP.

Thanks for your help!



Geoff_Wood wrote on 3/25/2005, 2:37 PM
If your cache is dropping fast, then your drive is buffer under-running all the time, and the extra time taken for the burn is the BURn-Proof recovery time.

But you should never be buring audio CDs at 48x anyway. 12x is really max for reliable transportable discs, and 8x or less for 'master' CDs - if quality is a factor in what you are doing ....

CDM wrote on 3/25/2005, 3:47 PM
I used to burn at 8x only for masters and stopped a while ago. Now I burn them at 24x and haven't had a single problem and I make glass master from these all the time. But I agree, that CD Architect 5.2 is very inconsistent with burn times. One machine will burn at 24x while another with the exact same drive burns at like 5x
Chienworks wrote on 3/25/2005, 6:40 PM
Not that this helps you at all, but i've noticed weird behavior like that when burning with SIREN, which i assume uses a similar buring routine. I've had the cache drop to zero for long enough for the drive to power down! It's always resumed and finished burning the disc, which then appears playable. It does seem like SONY's burning has some problems from time to time.

On the other hand, i never have this problem burning in Vegas. *shrug*
Jack from Multiview Inc. wrote on 10/16/2005, 1:28 PM
Guys, sorry for not answering sooner. Forgot about that post!

Anyways, I don't have a problem at all when burning at 48X for my masters and I use them for high speed CD duplication.

But it's not normal too take so much time to burn. Again, Nero burns my CDs in 3 minutes and they are perfect. What's the damn problem??

Geoff_Wood wrote on 10/16/2005, 2:34 PM
Are you doing any processing on the source meia - in master bus or event plugins, and what spec source files. SRC, bit-depth conversion, and effects/processing is done in realtime (unless told otherwise) and the burn will be paced to accomdate that wrt CPU resources.

Jack from Multiview Inc. wrote on 10/25/2005, 7:11 AM
Hey Geoff,

Thanks for helping. I'm not sure if there is any processing done while burning but basically all I want is to burn the file the way it already saved as without any processing/effects, SRC and conversions. How do I tell the program to disable all that?

Geoff_Wood wrote on 10/26/2005, 5:01 PM
If you have nothing specified it won't do anything, except fot the src and bitdepth conversions if you have anything other than 16/44k1/s source files (and you can't get around that if you want an audio CD).

Does the buffering meter keep running down ? If so, you are asking too much of you PC, and are incurring any additional delay at BurnProof (or whatever) recovers between 'bursts'.

doctorfish wrote on 11/4/2005, 3:24 AM
I experienced a similar thing yesterday. Went to burn some audio cds (not for master just for a friend) and had the burn speed set to max with no processing. Well the first disc started going and lo and behold the estimated burntime was 98 minutes! I let it go for a while since the cd drive was active and to make sure it wasn't just a display problem, but 10 minutes later the burn was only 3% complete so I canceled it. After checking the disc I could see that yes the burner had been working but oh well .. coaster anyone?

I closed CD-Architect and tried again with all the same settings and this one burned in just a few minutes as it should have. Thinking it was just a glitch I decided to burn another (different tracks but same burner settings) but guess what? Same thing happend. 90 minute burn time, canceled, eject coaster, close and reopen CD-A, burn disc sussessful again.

This happened 4 times. Needless to say I wasn't happy. These are actiually the first discs I've burned with CD-A 5.2. Never had burn speed issues with 5.0, but occasionally the progress meter wouldn't update unless the cursor was placed over it. Still though all burns with 5.0 went as fast or slow as I had set in the settings.

These issues could be related to 5.2. Did anyone here wtth burn speed issues have the same problems with 5.0?

drbam wrote on 11/5/2005, 6:08 AM
"These issues could be related to 5.2. Did anyone here wtth burn speed issues have the same problems with 5.0?"

Never had any burn speed issues with CDA 5.0. Although I have 5.2, I haven't even installed it because of these kinds of continuing reports. I'm disappointed in Sony's handling of the current releases and simply haven't wanted to put myself through the trouble shooting hassle. I'll just continue to use Vegas 3 & 5, SF 7, and CDA 5 until I find something else that serves my needs.

doctorfish wrote on 11/6/2005, 5:25 AM
Yeah I hear ya drbam.

After my 5.2 experience, I may reinstall 5.0. I'd wanted the CD text feature though so I'm first going to try an uninstall/reinstall to see if that works. In fact I think I may just download a new copy from this site and do a fresh install with that. If that doesn't work it's back to 5.0 for me.

Geoff_Wood wrote on 11/6/2005, 1:59 PM
Let's recap.

- Your files are already 16/44k1/s ? If not CDA is converting these on the fly.

- You have no effects processing on the events or the master. If any processing this reduces the rate at which CDA can 'feed' the write buffer.

-You have no other processing running that are utilising significant amounts of CPU.

- You have the latest firmware in your writer.

- Most of us do have 5.2 working flawlessly, though few here would remotely consider burning an audio CD at anything more than 12 or 16x, so how that works is a bit cloudy. Will try one tonight, then stick it thru PlextoolsPro and a range of players to remind myself why I'm not keen on 'fastest' ....
doctorfish wrote on 11/7/2005, 7:00 PM
Good tip Geoff. I'll have to burn a few at slower speeds and see how it goes. For studio work I never burn audio discs at such high speed but was running low on time to burn a few things for a friend and well decided to go the high speed route. The thing that really got me was the inconsistancy. It would burn REALLY slow. But then after canceling and restarting CD-A it would burn at max speed no problem. And then the next burn would be REALLY slow again and so on.

As far as the projects specs go, I do have the latest firmware for my cd-burner and there's was no processing. Well, out of 5 different projects one track in the first project had the event volume envelope dragged down to -3db but that's it. The files were all Sony .pca files which I believe are 16bit/44.1k but I'll have to check on that. Again if the pca files are to blame the inconsistancy is wierd.

Anyway, I'll be reinstalling a fresh copy today and burning a few tests to see what happens.

Geoff_Wood wrote on 11/8/2005, 6:30 PM
If they are PCA then maybe they are being uncompressed on-the-fly. What did choosing pre-render do wrt the actual burn time ?