[Nigel O’neill]

The built in multicam in Vegas is a bit limited. I use Vasst Ultimate S Pro Quadcam and it preserves all effects and transitions. The only catch is that when I need to close up or increase a gap, I need to remember to select the events and then select all the takes (markers) and realign them. On a big project with a couple of hundred or so takes (cuts to a different camera) this probably only takes me 5 minutes to do.

My system specs: Intel i7 7700k 4.20 GHz, GTX570, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 12 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

[Robert Maier] “‘Vegas stopped working”

I get this a lot, particularly when video acceleration is enabled. I also get it if I mix MOV files wth MP4 and MTS, so I simply convert MOV to MP4. The problem goes away.

Unfortunately Windows 10 is here to stay. I was forced to Windows 10 when my system died recently. I could not install Windows 7 again as it was an upgrade from Vista, and the technician was not about to do a dual install just to get me back to Windows 7. He simply installed an upgrade version of Windows 10 using my existing Windows 7 upgrade licence key.

I have avoided going to SVP14 as there is no pressing need for me. I alternate between SVP12 and 13 as the veg projects are both backwards and forwards compatible. I have noticed that video acceleration (for me) shows a preview on SVP12 but not on SVP13, but given the stability issues, I have disabled it, period, in both SVP versions.

My system specs: Intel i7 7700k 4.20 GHz, GTX570, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 12 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

I installed ffmpeg and QWinFF(a GUI front end to enable batch processing) to convert all the files in-situ and then replaced the MOV files with their MP4 equivalents on the timeline. All my files were iPhone 6S footage. It may not work with the iPhone 7 4K footage but is worth a try. The program simply re-wraps the MOV file into MP4.

Perhaps QWinFF may be all you need (I assumed it needed ffmpeg to be installed first as QWwinFF just appeared to be a GUI front end for ffmpeg).

My system specs: Intel i7 7700k 4.20 GHz, GTX570, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 12 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

I bit the bullet and used ffmpeg and QWinFF to convert all the files in-situ in batch and then replaced the MOV files with their MP4 equivalents on the timeline. Solved!

My system specs: Intel i7 7700k 4.20 GHz, GTX570, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 12 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Thanks. I just demuxed and then renamed the h264 file to mp4. Vegas accepted that file 🙂

My system specs: Intel i7 7700k 4.20 GHz, GTX570, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 12 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Just discovered that video acceleration works with Vegas 12 but not 13. Curious.

My system specs: Intel i7 7700k 4.20 GHz, GTX570, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 12 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Thanks Paul. It worked on Windows 7 so I am presuming that it is a Windows 10 issue

My system specs: Intel i7 7700k 4.20 GHz, GTX570, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 12 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

[Jay Mitchell] “When I connected the deck the driver installed in Windows Vista”

If John’s suggestions do not work, I do vaguely recall in Vista that you had to also force the OS to use the legacy driver:

• Click the Start Button, type devmgmt.msc in the “Start Search” box and press Enter.
• Expand the “IEEE 1394 Bus Host Controllers” node in the device tree on the right hand pane.
• Right click the host controller node select “Update driver software …”
• Select “Browse my computer for driver software”.
• Select “let me pick from a list of device driver on my computer …” and Check the box before “Show compatible hardware”.
• Choose the second option—1394 OHCI Com

pliant Host Controller (Legacy), and click next to update the driver.

My system specs: Intel i7 7700k 4.20 GHz, GTX570, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 12 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

With Vegas’ patchy history for CUDA support and general instability during editing/rendering since v11, I have disabled GPU support and recently bought the fastest CPU I could afford (6th Gen i7 3.4GhZ) and my previews are buttery smooth. Albeit my system did recently die after 7 years of heavy use, forcing the upgrade. I next intend to replace my mirrored drives with 2 SSD’s (currently only my boot drive is SSD) once the 2TB price point drops to under $500.

I know that there are Vegas users who have no issues with CUDA acceleration, but I have yet to find that holy grail on my system and multicam workflow any any version of Vegas or Windows 7/10 combination, even on a freshly built system. Maybe there is a problem with the GTX570 drivers, but I find that a faster CPU is of more direct benefit than a fast GPU.

My system specs: Intel i7 7700k 4.20 GHz, GTX570, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 12 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

[Colin Moxey] “I am using the built in audio with my Motherboard and I notice the driver is windows sound mapper with no other options to select.”

I edit using the on-board audio drivers BUT I use very good quality head phones to edit and monitor the audio. If I am editing a musical, I do have to vary the volume as follows: Select the event on the time line you want to adjust the audio for. Press V. A dark blue line appears. Double clicking on it creates a keyframe and by adding more than 1, you can drag the volume level up or down. You can use this technique to duck background audio for a music track whenever there is dialogue.

I also keep an overall eye on the master volume control to make sure the audio plays back at a similar level throughout the project.

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