-
DVDA 4 and Vegas 7 quirks! Anyone else?
Couple of little curly ones I have found so far. First one, DVDA 4.0 will not accept an m2v file from Procoder without having an error exception and closing. The same m2v files, all three hours plus, whip into DVDA 3.0 without a sweat. Why am I using Procoder you might ask. I find with long duration DVD’s its Mastering Quality, VBR, 2 pass to be a fair bit better than that from Vegas or DVDA.
Second one. I had to bring a TGA anim sequence of 150 frames into Vegas 7. These were 1024×576 for a widescreen PAL job. Click on the first one expecting the TGA to be seen but no luck. Dialogue box says unknown format or something to that effect. Same sequence in Vegas 6.0 is seen as soon as you click on the first TGA. Oddly though it sees the sequence as ‘Quicktime’, still alows you to bring all TGA’s in as a sequence. If they are 720×576 graphics both Vegas 6 and 7 recognize them as TGA’s. Quite odd! Anyone else seen these quirks yet? Sent the dump logs to Sony see if they can find the answers.
Chris Young
Sydney -
5 Replies
-
I’m having a similar problem with V7 reading images that V6 had no problem with. I have a lengthy project that contains many still images in JPG and TIF format. The project was created with Vegas 6.0d. Now when I open the project with version 7, it comes across every image file during startup and says that there was an error with each picture, and gives me the standard choices of leaving it offline, or ignoring all errors, etc. The path to the images in correct and says nothing about them being missing; just that there is an error opening them.. no more details.
🙁
andrew
-
Hmmm! Yes, a bit of a worry. Think we will be staying with V 6.0 and DVDA 3.0 until these quirks are sorted. The problem being that once you save a job in either program in versions 7 and 4 you can no longer open them in the earlier variants. Could be a nasty ‘gottcha’ if more anomalies show up. I actually tried a ‘copy paste’ from v6 to v7 and the graphic media on the timeline says ‘media offline’ so 7.0a is definitely not seeing some stuff.
Chris Young
Sydney -
Have you guys sent this to Sony’s tech support guys? They need to know so they can pass it on to the developers and get it fixed in the next version. If it’s not doing stuff that a previous version did just fine, that’s a big problem. They’ve been good about responding to my tech-support queries in the past (though it may take a day or two). Let them know so we can get a version of 7 that works the way it’s supposed to.
–the Fiddler
-
Oh yes! This has been done. Sony have got back to me with a request for examples of TGA files that V 7.0a won’t import. I have sent them some, will wait to see what transpires. The sad answer was on the DVDA 4.0 front. Whereas I have had no problems importing m2v files into DVDA 3.0, done dozens of them since it came out. With DVDA 4.0 it now appears that this is not possible. Sony support states that DVDA 4.0 will import MP2, M2P,MPG and MPEG but not a M2V file. If I rename the m2v file as any one of the above I can actually import the file… and even preview it. It even brings in the correspondingly named AC3 audio file. Click on the file though and ‘poof!’, back to the desktop. Why on earth have they decided to drop support for the import of m2v files? So many good steps forward in both V 7.0 and DVDA 4.0 but sadly some things that worked in the past got broken. I have no doubt that 7.0b will have a fix for the TGA issue but am seriously hoping that DVDA 4.0 gets back its m2v import capability. Stuck on v3.0 otherwise for jobs where clients supply m2v files or I have three hour plus DVD requirements which as I have said in the past work out better quality for us, and render quicker, if done in Canopus Procoder as m2v.
Chris Young
Sydney -
Just got a reply back from Sony support re the TGA import issue. This may help others out there with the same problem. Quote from the reply:
“All versions of Vegas have a bug where Targa files that have a pixel height or width that is divisible by 256 will not open. Your file is 1024 wide…divides by 256, so it won’t open.
This has been fixed as part of Vegas 7.0b (to be released within a few weeks). The workaround for now is to resize the file to 1025 x 576 or any other number that doesn’t divide by 256 and it’ll open right up.”
Interesting!
Chris Young
Sydney
Reply to this Discussion! Login or Sign Up