burning bad audio cd's

Comments

ChristoC wrote on 6/12/2012, 10:03 PM

>How do we make sure Sony is aware of this so that it can be straightened out somehow?

follow the "My Account" tab at the top of this page, navigate to "My Support" (log in as necessary) - then follow the "Ask a Question" link on that page - fill in your details and file a bug report....
MikeT1111 wrote on 6/13/2012, 12:06 PM
I submitted a tech support question today. Thank you for the answer. I have been a "Sonic Foundry" customer since the Mastering House Bundle days. (I still have my copy of those discs) I have never had to submit a question to the Sony techs. Usually the forums had the answer. Hopefully this will be addressed and corrected.
Brian_S wrote on 9/20/2012, 6:08 AM
I am having the same problem. Switched to Version 8 on another machine and burned the disk just fine
Madfrisbee wrote on 10/29/2012, 1:56 PM
Still dealing with this issue on the newer builds. Vegas 8 burns them perfectly every time!
Curt wrote on 3/8/2013, 10:30 PM
I produce a weekly radio program for a local church using Vegas 10 (Pentium Dual Core, 2GB RAM, Win XP-SP3). Each program is burned to CD.

I just found out today that since July over 15 of the programs were unairable due to the audio dropping out after a few minutes.

I did a quick experiment. I pulled up a recent session and did a timeline burn like I usually do. Watched the burn carefully. No problem. Put the CD in my outboard CD player and it played fine.

Did another burn. This time I went ahead and surfed the web while burning. Sure enough, after 8:43 the audio disappears although the disc still showed almost 40 minutes left of the program. Hmmm.....

I did it again, surfing as it burned. Same result, but at 9:15 into it.

Did a fourth burn, this time not touching anything. Just sat and watched. That burn played normally.

Thoughts?

Geoff_Wood wrote on 3/10/2013, 7:20 AM
Probably due to an antivirus surge while burning. Possibly at the point when BurnProof cuts in due to cpu load increasing or disk transfer rate being compromised. Burn at a max speed of 8x or 16x . And don't surf the net while burning.

geoff
Madfrisbee wrote on 6/25/2013, 11:14 AM
I've tried all that stuff, and saw randomly good and bad results multitasking/not multitasking, virus software enabled/disabled, lots of variables seemed to make very little change to my results. I used three different machines, with Win 7 Professional running with all the updates, or even a clean Win 7 install on one machine. None of that seems to make a difference.

Using Vegas 8, though, I could multitask all I wanted, use virus protection the whole time, etc. V8 always burns them flawlessly. I thought about 32-bit vs 64-bit, but I honestly have no idea at this point - everyone's results on here seem all over the map, and Sony's techs have never been able to duplicate the problem for anyone when we report the issue.
hbwerner wrote on 7/1/2013, 12:57 PM
I have two audio cuts on the time line, track markers are in place, but the disk-at-once CD moves the index and break for the second track into the first track a minute or so before the actual end. Then as a second track, the rest of the first plays and continues with the second track, which then concludes short of the end. I have Vegas Pro 12. For one scary moment I thought that Vegas was finally able to correctly burn CDs. Does anyone know of a competitive editing program that works right for CDs?
hbwerner wrote on 7/1/2013, 3:08 PM
New twist - I decided to render my two tracks, and the rendering came out with the ends cut off.
Geoff_Wood wrote on 7/1/2013, 5:43 PM
Did you have "Render Loop Region only" selected ?

geoff
hbwerner wrote on 7/1/2013, 10:23 PM
I did have it checked and tried it agian to be sure, and it cut off the last end.

I have a thought now - I changed the pitch of the recoriding and it might have lenghtened the actual play time not the time on the layout. I looked back at the fx and see there is a box to maintain time duration - which was unchecked. That was the problem. Lesson learned. The render goes by the time codes on the layout, not the actual play time.