-
solution to Canopus AVI problem
Thanks go to user MarcoB on the Sony forum for providing this fix.
I can verify that it works perfectly 🙂
I’ve added a follow-up comment from him as well.————————————————————————————————–
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.
————————————————————————————————–Follow-up:
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 720×576 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. -
4 Replies
-
Mike ~
Read my post from September:
https://forums.creativecow.net/cgi-bin/new_read_post.cgi?forumid=24&postid=857282&pview=t#head
I got no replies to this post about the weird Canopus/Vegas field dominance question back then but this may shed some light on the subject. The problem we have is that one Vegas 6.0c box sees Canopus files as lower field and the other, also 6.0c sees them as upper field!! Go figure. I have found that there is no problem working with the Canopus files with upper field dominance if you change the field order in the clip properties. ‘Cos if you don’t the renders are just plain sadness over the wasted time, horrible major field tearing. Thanks for the info though as I will now have a look to see why the two Vegas boxes are seeing Canopus files differently as I would imagine the .ini files are the same on both boxes as we haven’t modified them.
Chris Young
CYV Productions
Sydney -
Hi Chris. I just read your post. Very weird!!
Glad to see I wasn’t alone on this 🙁As mentioned here (and on other forums), my biggest complaint was that DVDA always wanted to re-render everything. I did try changing the field order on the imported clips. No difference. I changed the field order and re-rendered them as AVIs and brought them back in. Still no difference. Then Marco made that post, I did it and success!!
I have no idea why Canopus files cause this much grief but am happy I was able to solve my problem. I’ve sent an email to Sony asking them to please put the solution into their knowledgebase for anyone else.Let me know if this fix solves your problem.
Mike
-
Mike ~
Yes I will check it out and post back. In the meantime I have got around the problem by using Scenalyzer v4.0 Beta using the Canopus Edius drivers and in v4.0 it allows you to check the import as Vegas AVI2 type files which have been coming in with the correct lower field dominance. Much prefer to use Scenalyzer because I find it a far better capture app than the Vegas one plus Scenalyzer v4.0 is much improved over the earlier v2.0 if anyone is interested.
Chris Young
CYV Productions
Sydney -
Scenalyzer is by far superior to Vegas capture. Now, if only you could drag from Scenalyzer directly into Vegas after being able to so quickly identify the shot you need…
I use Scenalzyer all the time especially for it’s additional features, such as archiving, and also file splitting and joining.
The only time I use Vegas capture is when entering advanced capture info for batch capture lists. If you ever want to re-capture anything in Vegas, you MUST use ADVANCED capture, because crash capturing does not capture with correct time code (it is 16 frames off). This means that every shot you might “re-capture” will be 16 frames off.
You can, however, recapture any Vegas projects that were originally captured with Scenalyzer.
td
Reply to this Discussion! Login or Sign Up