Help Needed - Canopus AVIs & Vegas

rs170a wrote on 10/18/2005, 5:11 PM
I'm quickly losing my mind here.
I have 5 AVI files, edited on a Canopus Rex system (not by me!!), that I need to make into a DVD using DVDA 3.0
I rendered them out from Vegas (6.0c) as mpegs & ac3s but, when I brought them into DVDA (3.0c) , it said every file had to be re-compressed. When I did this, lip sync was off as well as what appears to be a field ordr problem.
The files are only 9 min. max. each.
I've done this numerous times before and NEVER had to go through this before.
Is this a Canopus (type 1 vs. type 2) AVI file issue? I've got the Canopus DV file converter but have never used it so I'm not sure which settings to choose.
Any help is gratefully appreciated.

Mike

edit: I did a test render using AVI files I created in Vegas so I know this works. It's the Canopus AVIs that are giving me grief :-(

Comments

rs170a wrote on 10/18/2005, 7:56 PM
bump.
ottowr wrote on 10/18/2005, 8:40 PM
This may or may not help, but when DVDA3 tells me it needs to re-render a file I *know* is ok, I save the project and re-open it. That usually fixes it. This issue has been around since v2.
rs170a wrote on 10/19/2005, 7:09 AM
In case anyone else runs into the same issue, I ended up using the Canopus DV File Converter and converted the Canopus AVI files to Microsoft DV (AVI 2) files. Brought them back into Vegas, rendered out to MPEG-2 & AC3, back into DVDA (where they had to recompressed) and made my DVD.

Mike
Marco. wrote on 10/19/2005, 11:35 AM
Vegas analyses and uses the Canopus AVIs coming from Rex not correctly. For Vegas them are Upper Field First though actually them are Lower Field First.

I had the same problem several times and Sony Support helped me by telling me how to modify the "Vegas profile.ini" file which is in the Vegas program folder:

--------------------------------------------------------------------------------------------------

Open the file "Vegas profiles.ini" within an editor. Search for this phrase:

"Key2=0, "None", 720, 576, 25.0, 0
Attributes2="Upper First", 1.0925925925, "Undefined", 1"

Modify this one to

"Key2=0, "None", 720, 576, 25.0, 0
Attributes2="Lower First", 1.0925925925, "Undefined", 1"

Save the file anew .

Be sure to have copied the original file with another name first to have a backup!

--------------------------------------------------------------------------------------------------

Now when you reopen Vegas it will analyse and use the Canopus AVI files correctly as Lower Field First.

Marco
farss wrote on 10/19/2005, 3:16 PM
If DVDA says it's going to recompress them then I'd say you've encoded them wronly out of Vegas in the first place. Go back and try again, encoding an already encoded file is not going to do much for the quality. What template did you use for the initial encode to mpeg-2?
Bob.
rs170a wrote on 10/20/2005, 3:35 PM
Marco wrote:
.how to modify the "Vegas profile.ini" file...

Thanks for the suggestion Marco. From the (limited) reading I've done, I think it's a field order issue of some kind as well. I even tried rendering the file out with the field order changed to upper but the problem remained.
I'll give your suggestion a try after this week is over. Too many 16 hr. days to think clearly right now :-)

farss wrote:
...you've encoded them wrongly out of Vegas...

I used the same template I've been using for a long time and that's a slightly modified version of the DVDA NTSC stream. All I've changed is to bump up the min. bitrate to 2M from 192K.

Mike
mark-woollard wrote on 10/20/2005, 5:13 PM
You said change it to

"Attributes2="Lower Field", 1.0925925925, "Undefined", 1"

Did you actually mean,
"Attributes2="Lower First", 1.0925925925, "Undefined", 1"
Marco. wrote on 10/21/2005, 12:24 AM
You are right, this was a bad typo.
Only change "Upper" to "Lower" so it should be "Lower First" in the end.

I edited my first posting to get it corrected. Thanks for this feedback.

Marco
rs170a wrote on 10/21/2005, 6:43 AM
What I wanted to ask you is "can I just leave the replacement value for key 2?"

I'd be very interested in knowing this as well. I have no problems changing the ini file but I'd like to know if I can leave it alone after I do this.

Mike
Marco. wrote on 10/21/2005, 7:15 AM
I can't tell for sure, but I modified that ini-file about 18 months ago after I had problems with certain Canopus DV files and anytime I got a Vegas update first thing I did was checking what happens when using such certain Canopus DV files and then I again modified the ini-file.
With that modified ini-file I never had a problem since.

Marco
rs170a wrote on 10/21/2005, 8:01 AM
Thanks Marco. One more long shoot to get through today and then I'll actually have a chance to try the mod.

Mike
Marco. wrote on 10/21/2005, 8:46 AM
I never worried about the modified ini-file but after you brought that topic up again I just did some further tests with it. What I found out:

The modified ini-file seems to be perfect for any dv stuff because dv must be lower field first and even if Vegas is confused by certain dv files like the Canopus ones it'll be perfect - lower field first.

But if you have a video input which fits 720x576 size and 25 fps but which is NOT dv then it does also change the field order to lower field first which might be not correct then.
So if you import or capture video which is Sony YUV it actually should have upper field first but with this modified ini-field it will be read as lower field first in Vegas.

This means you probably will not have any trouble with that kind of modified ini-file when using dv video. But you must reset the ini-file if you're going to use video which actually is upper field first.
If you have a project running with mixed stuff - both upper and lower field first - the modified ini-file is no help at all.

Marco
rs170a wrote on 10/21/2005, 3:38 PM
Marco, thank you VERY much. I just tried the ini mod and it worked perfectly.
I wish I had known about this before I started this project.
I'm also going to send an email to Customer support and strongly suggest that they add this fix to their knowledgebase.

Mike