[Nigel O’neill]

I had no problems with the actual matching when I followed the instructions, but it just did not work for me above SVP 10c. I didn’t have the patience and time to work through it.

I don’t think fbmn anticipated it would be used with Ultimate S. It works at the event level in the multicam screens, but when creating the master track, things went haywire colorwise. John suggested I try to apply the color match FX at the track or media level (media bin?), but I never did.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Vegas does not support mkv files.

Those converters are a bit of a crap shoot, and I suspect the converter you are using is creating a proprietary mp4 file format that Vegas does not understand. You may have to try and find another converter to use, or try exporting a small file to AVI with the tool you are using, and see if Vegas accepts that.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

David

Those glitches look like drop outs, or if you are recording to card, possibly a break in the join between clips.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Gilles

I successfully used fbmn’s software color matching plugin with Vasst Ultimate S Pro for a multicam edit with SVP 10c. I was able to colour match events on the timeline with much success. When I went to 10e, the plugin started misbehaving and giving me very strange psychedelic coloured output. Both John Rofrano (developer for Vasst) and Frederic Baumann (developer for Color Match) looked into it, but were unable to come to a successful solution. We concluded that Sony developers had changed their OFX implementation. Whilst Quadcam and Color Match worked great together up until 10c, they don’t after SVP 10c.

I have to admit I got a bit frustrated with not being able to find a solution quickly and didn’t give Frederic my source and project files. Given that the problem was complicated with another 3rd party plugin (Ultimate S), I left at that. I have remained in SVP10c to this day. I do have a CUDA video card which has turned out to be a dud because SVP11 is more stable with GPU acceleration disabled. What a joke.

fbmn software has since rewritten his code to be optimised for CUDA, but I have not purchased it nor trialled it. I suggest you trial and see if it works.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

My last BSOD was a related to a second video card driver I had updated (one of my systems had a PCI and USB video). I rolled it back and the problem did not recur.

I am wondering if rendering to a USB memory stick can be the result of driver issues, because when you plug in a device, Windows typically installs drivers for that USB device.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Sony’s tech support response does make some sense, and is the closest thing you can get to a clean install without reinstalling the o/s. Given that your registry bloats over time, you are in effect starting with a clean user profile. It also means that by installing SVP last, any other software that may have overwritten some registry entries or associations SVP depends on, are reinstated.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

I was going to suggest reporting the issue to NeatVideo as it could be an OFX implementation issue, but I see it is happening to the standard FX as well.

For me, something changed since v10c where unexpected results with FX crept in with multicam edits. I have a 3rd party colour matching plugin that badly misbehaves in any version of SVP above 10c. I reported it to the developer who blamed Sony for changing the OFX specifications.

For this reason I am still on 10c. I did want to move to SVP11 with the promise of GPU acceleration, and even forked out $$ for a GT570. That amounted to nought as you have to disable it to get any measure of stability during rendering. Kinda defeats the purpose.

In short, you might need to report this OFX issue to Sony.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Sam, you could always create your own custom render template and save it with the save markers unchecked and use that whenever you want to render… .

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Check out my response to a similar issue in this post:

https://forums.creativecow.net/thread/24/949080#949151

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Hanh

You need to use the software that came with the camera to stitch the video back together. In the case of Sony cameras, you need to use Picture Motion Browser.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6