So I got a new version of DVDitPro HD (V6.4) in the hopes that the new version takes care of the problems I had with V6.3 such as frequent corruption of project files. I spent much of today trying to author a BD-R disk with it that I hoped to deliver today. In the end, I wasted hours of my time and some of my money burning a BD-R coaster.
I encode all of my video using Canopus' Procoder V3.05, which has presets for DVDitPro HD. I used those same presets in the past, but DVDitPro HD V6.4 crashes with a Runtime Error every time I try to drag a 96KHz PCM WAV audio file to one of the audio tracks. Mind you, the file is already in the format that the program wants for a Blu-Ray project.
Since this behavior was new and I really needed to deliver my project today, I decided to try something different. Instead of outputting separate .M2V and .WAV elementary files, I started over and had Procoder output a .M2P Program Stream file -- nothing about the audio format itself changed, just the container format. I brought the .M2P into DVDitPro HD, dragged the file from the Media list to a Title, and low and behold, the bloody thing didn't crash. The audio track shows up, the Properties confirm that it's 96KHz PCM audio, and everything seemed normal. I previewed the title, and the audio and video played fine.
The next step in my workflow would have been to output an disk image file, burn that to a BD-RE for testing, and if it played correctly and met my expectations, burn the same image to BD-R media. I tell DVDitPro HD to output a disk image, but when I'm done, I can't find the ISO file. I thought maybe it placed it in a weird location, so I use Windows' Search feature to look for ISO files created today. There are none? I go back into the program and start the process again, but this time I hit the Browse button to see what location the program defaults to, figuring I might find the ISO there. To my surprise I find that the program doesn't write ISO files anymore, instead it writes .GI (Global Image) files. Great. Something new and incompatible to disrupt my workflow. But this did clue me in to the fact that Burn -> Burn Disk (which defaults to looking for ISO files that the program no longer outputs), might actually be able to use the .GI files, and it can!
Of course now the problem is that the files it created are said to be incompatible with the BD-RE media that I want to use for testing. I remembered having to choose between BD-R and BD-RE when I created the disk image, something that was new and unexpected. I selected BD-R because that's what I ultimately wanted to create, but now I can't use eraseable media for testing anymore? Lame!
At this stage I'm starting to run out of time, I want to have the disk burned and ready to show at 4PM, so I decide to bite the bullet and output on a Verbatim BD-R disk. After much disk activity and a roughly 20 minute wait, I get a dialog saying the disk was burned successfully!
I eject the disk, exit DVDitPro HD, and play the disk in CyberLink PowerDVD. The image looks great (Procoder produces wonderful output), but THERE IS NO SOUND! According to PowerDVD, the disk contains 2-channel stereo, but there is no freaking audio! Cranking up the volume just yields a constant hiss. At this point I've got about ten minutes before I need to head out, but I don't have a disk I can show, and I'm out of options to try anything else or even burn a simple DVD.
Today's fiasco was just the latest in a long series, this program has given me endless grief with both V6.3 and now V6.4. What was supposed to be an improvement over the previous version is utterly unusable. Unfortunately it is much too late for me to ask for my money back, but God knows that if I could charge Roxio for the time I wasted trying to get their software to work and recreating lost work, not only would I be getting my money back, they'd owe me money.
Question
THoff
So I got a new version of DVDitPro HD (V6.4) in the hopes that the new version takes care of the problems I had with V6.3 such as frequent corruption of project files. I spent much of today trying to author a BD-R disk with it that I hoped to deliver today. In the end, I wasted hours of my time and some of my money burning a BD-R coaster.
I encode all of my video using Canopus' Procoder V3.05, which has presets for DVDitPro HD. I used those same presets in the past, but DVDitPro HD V6.4 crashes with a Runtime Error every time I try to drag a 96KHz PCM WAV audio file to one of the audio tracks. Mind you, the file is already in the format that the program wants for a Blu-Ray project.
Since this behavior was new and I really needed to deliver my project today, I decided to try something different. Instead of outputting separate .M2V and .WAV elementary files, I started over and had Procoder output a .M2P Program Stream file -- nothing about the audio format itself changed, just the container format. I brought the .M2P into DVDitPro HD, dragged the file from the Media list to a Title, and low and behold, the bloody thing didn't crash. The audio track shows up, the Properties confirm that it's 96KHz PCM audio, and everything seemed normal. I previewed the title, and the audio and video played fine.
The next step in my workflow would have been to output an disk image file, burn that to a BD-RE for testing, and if it played correctly and met my expectations, burn the same image to BD-R media. I tell DVDitPro HD to output a disk image, but when I'm done, I can't find the ISO file. I thought maybe it placed it in a weird location, so I use Windows' Search feature to look for ISO files created today. There are none? I go back into the program and start the process again, but this time I hit the Browse button to see what location the program defaults to, figuring I might find the ISO there. To my surprise I find that the program doesn't write ISO files anymore, instead it writes .GI (Global Image) files. Great. Something new and incompatible to disrupt my workflow. But this did clue me in to the fact that Burn -> Burn Disk (which defaults to looking for ISO files that the program no longer outputs), might actually be able to use the .GI files, and it can!
Of course now the problem is that the files it created are said to be incompatible with the BD-RE media that I want to use for testing. I remembered having to choose between BD-R and BD-RE when I created the disk image, something that was new and unexpected. I selected BD-R because that's what I ultimately wanted to create, but now I can't use eraseable media for testing anymore? Lame!
At this stage I'm starting to run out of time, I want to have the disk burned and ready to show at 4PM, so I decide to bite the bullet and output on a Verbatim BD-R disk. After much disk activity and a roughly 20 minute wait, I get a dialog saying the disk was burned successfully!
I eject the disk, exit DVDitPro HD, and play the disk in CyberLink PowerDVD. The image looks great (Procoder produces wonderful output), but THERE IS NO SOUND! According to PowerDVD, the disk contains 2-channel stereo, but there is no freaking audio! Cranking up the volume just yields a constant hiss. At this point I've got about ten minutes before I need to head out, but I don't have a disk I can show, and I'm out of options to try anything else or even burn a simple DVD.
Today's fiasco was just the latest in a long series, this program has given me endless grief with both V6.3 and now V6.4. What was supposed to be an improvement over the previous version is utterly unusable. Unfortunately it is much too late for me to ask for my money back, but God knows that if I could charge Roxio for the time I wasted trying to get their software to work and recreating lost work, not only would I be getting my money back, they'd owe me money.
Link to comment
Share on other sites
11 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.