Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Cannot burn ISO image rendered by DVD Architect, contains videos/audio files rendered in Sony Vegas

  • Cannot burn ISO image rendered by DVD Architect, contains videos/audio files rendered in Sony Vegas

    Posted by Jason Reinhardt on February 28, 2014 at 2:39 am

    Hello All,

    Having a very strange issue suddenly with Sony DVD Architect Pro 5.0b.

    I create a lot of projects that I normally burn to blu-ray and haven’t had any issues at all until today. Normally, I render my video portion using Sony Vegas Pro 10.0 using the AVCHD 1920 x 1080 60i format, and my audio using AC-3 Pro, Stereo DVD setting. I drag n’ drop the video into Architect and the audio always automatically follows, as it is always in the same directory with the video file. Architect renders the project into an ISO image and burns it onto my usual Verbatim BD-R discs, either single-layer 25GB or double-layer 50GB depending on the size of the project.

    Tonight I am doing a simple upscale job for a client. Fed the footage in from VHS and upscaled accordingly via Sony Vegas as I’ve done many times in the past. Rendered both audio and video files in Vegas and imported into DVD Architect and went to render/burn the project after building the disc menus, etc. ISO image seems to render fine at a final size of roughly 12GB’s. But, when it goes to burn the image to disc, it stalls out at burning the lead-in. The blue light on my blu-ray burner flashes as normal and I hear the disc speed up as if it’s going to be written to, and then, suddenly the light goes out and the disc slows down and stops. Meanwhile, “burning lead-in” is still present on my Architect software with the time counting up as normal. This goes on for about 15 mins (the time it would normally take to burn an ISO image of that size) then says burning complete and asks if I want to make another copy as it normally does. However, when I take the disc out nothing has been written to it and the disc has become a coaster and cannot be attempted to be used again.

    So far, I have taken the troubleshooting steps of trying to burn another ISO image from a previously successful project to a disc using the same burner via Architect, and all is well. It worked no problem. Then, I downloaded the ImgBurn software to try using it to burn the problematic ISO to disc. It too fails with the same scenario happening. Thinking the ISO image is corrupt I loaded it up using MagicISO and it was fine. I can go into the file and play the video/audio files rendered within just fine. I am lost. This was supposed to be a quick and easy project and everything went completely smooth as usual with no weird issues along the way. But now, this lone ISO file refuses to be written to disc. I’ve previewed the disc in Architect looking for anything that doesn’t belong and all seems well. I can navigate all menus, all chapter markers are fine, and the video/audio on each selection plays fine. I rendered a second and third ISO image from this project and all do the same thing when I try to burn them. I don’t understand where the problem might lie.

    If anyone has any info or suggestions I have not tried it would be greatly appreciated.

    Thank you.

    Jason Reinhardt replied 12 years, 6 months ago 4 Members · 13 Replies
  • 13 Replies
  • Stephen Mann

    February 28, 2014 at 2:12 pm

    Wow, that’s interesting. Do you still have the VHS tapes? Try starting over with a few minutes of video from the tapes, all the way to burn on a BD-R disc. Try making a short DVD to see if it has the same problem.

    Are the VHS tapes possibly protected by Macrovision? Vegas should have caught that, but it’s a thought.

    Steve Mann
    MannMade Digital Video
    http://www.mmdv.com

  • Steve Rhoden

    February 28, 2014 at 2:18 pm

    Its probably something went corrupt in that particular iso file.
    Try creating that iso from scratch again and make sure no other
    program is opened during the process.

    Steve Rhoden
    (Cow Leader)
    Film Editor & Compositor.
    Filmex Creative Media.
    https://www.facebook.com/FilmexCreativeMedia
    1-876-461-9019

  • Jason Reinhardt

    February 28, 2014 at 5:38 pm

    The VHS tape is something that was produced locally about 25 years ago. I fed it into my editing machine using the Dazzle DVD recorder USB capture device since my HD-PVR doesn’t reading anything with an output below 480i. I’ve used this method on several other VHS upscale conversions and not had any problems until now. Normally if something goes screwy with the initial feed in, Vegas will normally not open the video file at all and crash. When this happens I always have to feed the source video in again. Usually, when Vegas opens it up I’m golden from there. No strange occurrences happened with this process all the way up to the point where the ISO is about to be written to disc. Never seen anything like it. I’ve checked over the project in DVD Architect a hundred times and nothing is out of the ordinary. No symptoms or signs of trouble anywhere as would normally be the case.

    One last T/S step I’m going to try before doing the whole project over as Steve suggested: I’m going to move the ISO file to another machine and try to burn it from there. Something tells me I’m wasting my time but I’m willing to give it a shot before starting over from scratch.

  • Stephen Mann

    February 28, 2014 at 5:47 pm

    ” I’m going to move the ISO file to another machine and try to burn it from there. ”

    No, you aren’t wasting your time, you are eliminating variables.

    Steve Mann
    MannMade Digital Video
    http://www.mmdv.com

  • Jason Reinhardt

    March 1, 2014 at 10:18 pm

    I started the project all over from the beginning. Fed the source video into the editing machine again. Edited and rendered in Sony Vegas. All went well. Built the disc in DVD Architect again. All previews were flawless.

    I go to render/burn the final product to disc again — and SAME THING.

    I am absolutely bewildered.

  • Stephen Mann

    March 2, 2014 at 3:02 am

    What happened when you tried the burn on a different machine?

    Steve Mann
    MannMade Digital Video
    http://www.mmdv.com

  • Jason Reinhardt

    March 2, 2014 at 8:55 am

    I was just about to hop on here and post the results of that for anyone who may be following this thread, or have this problem in the future.

    But, it worked when I moved the ISO image to another machine. I have no idea why or what the deal is. I did the entire project over from scratch on my high-end machine and still the same thing happened. Different files went into the project all the way around and still the same result. But, moving the ISO to another machine caused the burn to behave normally. I double-checked the finished product and not a flaw anywhere.

    What in the world? I wish I had some understanding of what the issue is on the high end machine, and why it’s only isolated to this one project. I’m happy the project is done and my client will be satisfied, but mentally I am very frustrated at the overall issue. I guess I won’t really know more until my next project and if it happens again.

  • Stephen Mann

    March 2, 2014 at 11:56 pm

    If you really want to know what happened, you might try physically swapping the BD burner hardware, or buy a new one for your first PC. The lasers in them *do* wear out.

    Steve Mann
    MannMade Digital Video
    http://www.mmdv.com

  • Stephen Crye

    March 2, 2014 at 11:58 pm

    In DVDA 5.0b, under Preferences, Burning Tab, what is the setting for “use Legacy Disk Drivers?” compared to the machine where it worked?

    Steve

    Win7 Pro X64 on Dell T7500, MultiTB SATA, 12GB RAM, nVidia Quadro 2000, Vegas 12, 11, 10, 9 DVDA 6.0 & 5.2(build 135) Sony HDR-CX550V, Panasonic GH3 with LUMIX G X VARIO 12-35mm / F2.8 ASPH, LUMIX G X VARIO 35-100mm / F2.8

  • Jason Reinhardt

    March 3, 2014 at 12:08 am

    I was tempted to do that until I tried burning an ISO from a previous project and everything went fine. Only the current project was problematic.

Page 1 of 2

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