Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro The strangest thing with burning CDs

  • The strangest thing with burning CDs

    Posted by Ted Snow on November 10, 2011 at 6:13 pm

    Some of you may remember my post a while back about having problems burning CDs within Vegas 8.0c. Well, I thought I’d give it a try with ver. 11 and see how that went.

    I know that it must have something to do with my system and not Vegas, but just wanted to share my findings. At first I thought maybe it was my CD/DVD burner. I always keep at least one extra printer (for printing disc labels) and an extra DVD burner in my closet for emergencies. (Some of my projects have to be done overnight).

    So I proceed to install a new DVD burner, along with the present one in my system which is still working fine. Same thing happens when burning audio CDs with the new burner.

    When the first CD get done burning, the door ejects and the window pops up saying that the burn was successful and “do you want to burn another”. If I say NO…then proceed to insert another blank CD, go to the Tools menu and say “Burn Disc”…”Disc At Once Audio CD”, the disc will burn just fine and any subsequent discs after than “done the same way” will be OK.

    BUT…if when it says “do you want to burn another”…I say YES…the disc comes out muted. I say muted because the disc is not blank. You can see the burned portion of the disc and it will “play” each audio track in media player or on a CD player…counting off the minutes and seconds of each of the songs…but no sound.

    The first CD I burn is always fine, but any subsequent CDs are not…which is why I have to say “NO” to “burn another disc” and start over with the burn process for each disc.

    My previous “Vegas” system, which I still use for other things, is an E8400 Core 2 Duo system and it never failed to burn as many CDs as wanted to burn by clicking “YES” to “burn another?”. And although I have found a “work around” for this problem, it’s just annoying for something like this to happen and not be able to actually find the problem. It takes a few extra mouse clicks to burn multiple CDs which is not a big problem…just annoying.

    ————————————————
    ASUS P8P67 Deluxe MB
    EVGA GeForce GTX 560 Ti 1 GB DDR 5
    Intel i7 2600k 3.4 Ghz
    Corsair HX750 power supply
    Two Seagate Barracuda 500g SATA III drives
    16 Gig G.Skill Ripjaws DDR3 1600
    Canopus ACEDVio card
    Thermaltake V9 BlacX Edition case
    Xigmatek Dark Knight CPU Cooler
    Win 7 Pro
    VEGAS 8.0
    VEGAS 11.0 32 & 64 bit
    Sony VX2100
    Sony HVR-Z7U
    Sony HDR-CX130
    Alesis HD24

    Mike Thomas ii replied 14 years, 6 months ago 2 Members · 5 Replies
  • 5 Replies
  • Mike Thomas ii

    November 11, 2011 at 9:16 am

    If the ‘muted’ CDs are in fact burned, the only thing I can think of is that the subsequent ‘muted’ CDs are not being “closed” properly.

    Can you see the tracks using your file manager (right click on CD drive, then ‘Explore’)…does the file layout look the same as the first working CD?

    Have you tried disabling your Windows Autoplay? (before burning)

  • Ted Snow

    November 11, 2011 at 7:37 pm

    Hey Mike,
    I’m pretty sure the CD sessions are closed because they will in fact “play” on any CD player…in the fact that they will start counting off the time in the display…you just don’t hear anything. You can even click “next” and go to the next track and that track will start playing…but you hear nothing.

    I’ve done some pretty extensive experimenting trying to figure out what’s going on but the only thing that works is to start another burn for each CD instead of saying “yes” to “burn another disc”.

    It’s baffling for sure.

    ————————————————
    ASUS P8P67 Deluxe MB
    EVGA GeForce GTX 560 Ti 1 GB DDR 5
    Intel i7 2600k 3.4 Ghz
    Corsair HX750 power supply
    Two Seagate Barracuda 500g SATA III drives
    16 Gig G.Skill Ripjaws DDR3 1600
    Canopus ACEDVio card
    Thermaltake V9 BlacX Edition case
    Xigmatek Dark Knight CPU Cooler
    Win 7 Pro
    VEGAS 8.0
    VEGAS 11.0 32 & 64 bit
    Sony VX2100
    Sony HVR-Z7U
    Sony HDR-CX130
    Alesis HD24

  • Mike Thomas ii

    November 11, 2011 at 8:22 pm

    You got me scratching my head for sure.

    Have you tried using ‘Track-at-Once’ instead? And are these audio tracks DRM free?

    I use Sony Sound Forge Pro 10 for most of my audio work and save as uncompressed WAV, but I still use Nero ROM that supports multiple burners using DAO/96.

  • Ted Snow

    November 11, 2011 at 9:49 pm

    This has not happened on just one project. It happens on any project that I try to burn an audio disc with. And it’s always original music recorded here in my recording studio. I record my tracks on my Alesis HD24 and import the tracks to my VEGAS PC and do the mixing in Vegas…rendering them to 44.1 16 bit WAV files.

    I then create a new session in vegas…add the wav files as CD tracks in the order that I want them on the CD. I’ve done this numerous times on my previous Vegas computer and always worked fine. It’s just been with this new computer build that I’ve experienced this problem.

    And as I’ve said…I do have the work around by burning each disc as a new burn and NOT clicking “yes” to “do you want to burn another disc”. It’s just annoying not knowing why this would happen.

    ————————————————
    ASUS P8P67 Deluxe MB
    EVGA GeForce GTX 560 Ti 1 GB DDR 5
    Intel i7 2600k 3.4 Ghz
    Corsair HX750 power supply
    Two Seagate Barracuda 500g SATA III drives
    16 Gig G.Skill Ripjaws DDR3 1600
    Canopus ACEDVio card
    Thermaltake V9 BlacX Edition case
    Xigmatek Dark Knight CPU Cooler
    Win 7 Pro
    VEGAS 8.0
    VEGAS 11.0 32 & 64 bit
    Sony VX2100
    Sony HVR-Z7U
    Sony HDR-CX130
    Alesis HD24

  • Mike Thomas ii

    November 11, 2011 at 10:30 pm

    Totally bizarre.

    Just a though, but did you ever think of trying the Sound Forge demo for your studio?

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy