[Ryan Mcrobb]

Did you intend to upload a video for us to see?
If so, I can’t see it.

For what it’s worth, I used a NewBlue plugin(the name escapes me) once to add a very slight blur using a mask, unto the checked shirt of an interviewee I once shot, which worked really well.

http://www.ryanmcrobb.com

Asus G73jh Notebook
Win7 64Bit
AMD ATI Radeon HD5870
12Gb RAM
Vegas Pro 13

[Ryan Mcrobb]

Thankyou John.

I am well aware of the issues with .MOV files that are played in Vegas using the qt7plugin.dll, however for some reason, these particular files seem completely immune to this.

Nonetheless, I discovered that my work had another editing machine that had a direct connection to the hard drive that contained these files, and when I used this machine(which runs Vegas Pro 10) it worked quite well.(with some bizarre issues with some of the audio files attached to some video files)

It actually really surprised just how well it dealt with these enormous files; I could playback a 162Gb file in full resolution on the timeline, and only needed to lower the preview quality when I added some crossfades and blended 3 tracks with opacity.

I am pretty sure the issues I faced were to do with the bandwidth available to the computer in relation to the files size.
I am annoyed that Vegas doesn’t have an error screen explaining this. Simply greying out the options of putting the file in Project Media or Trimmer doesn’t help the end user solve the problems they are facing.

Thanks for your help.

http://www.ryanmcrobb.com

Asus G73jh Notebook
Win7 64Bit
AMD ATI Radeon HD5870
12Gb RAM
Vegas Pro 13

[Ryan Mcrobb]

OMG Thank you!

http://www.ryanmcrobb.com

Asus G73jh Notebook
Win7 64Bit
AMD ATI Radeon HD5870
12Gb RAM
Vegas Pro 13

[Ryan Mcrobb]

I am interested to know if this will work.
When I used the Blackmagic card to capture with Vegas, we were just using a composite video input(with stereo audio) rather than a high resolution HDMI signal.
It doesn’t look like you’ll get an answer here, so maybe speak to the manufacturers directly.
Good luck

http://www.ryanmcrobb.com

Asus G73jh Notebook
Win7 64Bit
AMD ATI Radeon HD5870
12Gb RAM
Vegas Pro 13

[Ryan Mcrobb]

Thanks Andrew, that’s good to know. It’s a shame that a commercial Vegas template would use a file type that will cause problems during playback and rendering.
I think that if Vegas is calling the qt7plugin to play the files then you only have 1 gigabyte of memory to play with.
I know John Rofrano said on a previous post of mine about iPad footage that there was only 2gig of footage available, but I noticed that there is a process called “File I/O Surrogate” constantly running a marginally 1 Gig, but only during times when Vegas is glitching with .mov files that use the qt7plugin. I also just don’t think that I had 2 gig of footage in use when I was using this file type.
Which is pretty grim!

http://www.ryanmcrobb.com

Asus G73jh Notebook
Win7 64Bit
AMD ATI Radeon HD5870
12Gb RAM
Vegas Pro 13

[Ryan Mcrobb]

I have also used a Blackmagic Decklink to capture video live via USB3.

[Ryan Mcrobb]

Thanks for your responses Russ and Mike.

I have been curious why I have had issues with iPad .MOV files but not DSLR .MOV files.

I just checked the properties of both kinds of files within Vegas, and I found that the DSLR .MOV files use the “compound.dll” plugin but the iPad .MOV files use the “qt7plug.dll” plugin.
I am not sure why Vegas calls them “plugins” rather than codecs because I am pretty sure that is how they are functioning.

Vegas also uses the compound.dll plugin to play Vegas-created MP4 files, which gives me the impression that Canon DSLR .MOV files are not going to give me the same kind of headaches that the iPad footage did with the 2Gb maximum allowed memory from the Quicktime plugin.

If anyone else has any nuggets of wisdom, I’m keen to hear it, but otherwise I think I will plough onwards with my huge DSLR files on my timeline!

Thankyou

[Ryan Mcrobb]

I have used a USB3 Blackmagic Decklink to capture footage in to Vegas before, so I would think the device will work as expected. Ideally the device should come with a list of compatible NLE’s so you can sleep easier with your purchase.

[Ryan Mcrobb]

[John Rofrano] “Did you try just renaming the .MOV extension to .MP4? That might have worked as well.”

Nope. That might save me a lot of time in the future though!

[John Rofrano] “Because MOV files are processed by the 32-bit Quicktime run-time in Vegas Pro and MP4 files are handled natively with their own 64-bit driver.”

I don’t understand.I seem to be able to put numerous long DSLR .MOV files in Vegas’ timeline and it doesn’t flinch.
Are you saying that all .MOV files use the 32-bit Quicktime runtime, which means that only 4 gig of RAM can be assigned to the files?
Thankyou John

[Ryan Mcrobb]

I solved the issue by (rather painstakingly) encoding all the iPad .mov files to .mp4 files in Handbrake.

I have no idea why Vegas struggles with iPad footage, and why it only had problems after I had been working editing the video for over an hour.