[Nigel O’neill]

If you have a choice of export formats, I would use .MXF

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

[Nigel O’neill]

1. Lock the audio track or event that you want to preserve

5. You can simply enter the duration for the text event. You might need to drag out the event to see it in full as I don’t believe it dynamically resizes the length

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

[Nigel O’neill]

Eric

Thanks for your message of support. I think Sony’s silence was beginning to have damaging effect and I know of a few editors who have already jumped ship. Hopefully your message hemorrhages any further defections.

As a semi-pro editor, feature-wise I would like to know if Magix and the creator of many Vaast products, John Rofrano, will continue to support the plugin’s, particularly the Ultimate S Pro tool set which I swear by for multicam editing.

Secondly, does Magix’s support for the Vegas Pro extend to DVD Architect or will that be re-engineered? It has some great capabilities but also a few shortcomings, the main one which is lack of multi-threaded support. Authoring takes a-g-e-s.

I had a dabble in Resolve and Catalyst, but they just don’t cut the mustard when it comes to multicam editing. Hideous a.k.a Edius just makes hard work of simple edits. I’ve been using Vegas since version 8, tasted a bit of Avid, Pinnacle Studio and Premiere and just couldn’t get any stability out of them, albeit that was in the days of XP/Vista. Vegas has been a solid performer for me since 2006 and has never let me down.

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

[Nigel O’neill]

Hopefully they don’t dumb Vegas down too much, plus it would be tragic (for me at least) if my Vasst plugins no longer work.

[Nigel O’neill]

It was files from Sony cameras. I like it that Vegas just about imports anything. No messing about or anything.

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

[Nigel O’neill]

I had a play. It couldn’t recognise footage from one of my two cameras. Identical models. Go figure. It then recognised some footage, and then later, couldn’t see it. I can’t see myself using Resolve. Stuff that is so easy to do is clunky in Resolve.

Vegas 13 with Ultimate S Pro for my multicam editing is working fine for me. I have no compelling reason to use Resolve, even if it is free.

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

[Nigel O’neill]

Personally, I would rename my external data drives further down the alphabet. I use P for Projects, O for output and R for Removable (my disc caddy). If you are using USB drives, simply disconnect at the drive rather than unplugging from the socket as suggested later on, because Windoze assumes a drive plugged into a different USB is a new one and gives it a new drive letter.

I also use RAID technology behind these drives, so whilst P and O appear to be 1 disk each, they are in fact 4: RAID 1 (mirror) for P so that I have a backup copy in real time and RAID 0 (striping) for drive O because I want performance (but with no redundancy).

I use C for my main drive, and D, E, F and G for disc burners.

Corporate networks also recognise this need and start their network drive mapping from H for Home and then go down the alphabet.

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

[Nigel O’neill]

My Windows 10 upgrade was a nightmare. I discovered hardware older than 2012 seemed to have driver issues. They often did work but were extremely unstable or performed extremely poorly.

My theory is that if you want Windows 10, get it with new hardware for maximum sociability and compatibility.

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

[Nigel O’neill]

You are welcome

[Nigel O’neill]

There is a setting in power management you can try that forces the fan to stay on all the time, rather than respond to CPU load before kicking in:

Control Panel > Power Options
Note the plan you are using and select Change Plan Settings
Click on Change Advanced Power Settings

When the Advanced Power Settings window appears, locate
Processor Power Management
Expand it to expose the System Cooling Policy
Change On Battery to Active
Change Plugged in to Active
Click on Apply

All this does is that it forces the CPU to be cooled constantly. The downside is that when running on battery, your battery life gets a bit hammered.

If this does not make a difference, you problem could lie elsewhere:

Is this CPU being overclocked? The BIOS may have been set to allow it and the system cannot cope. The only reason I can see a why a CPU would slow down would be to protect itself. This is something you generally cannot override and is built into the architecture of the CPU.

You could have a faulty CPU or one with poor thermal contact i.e. CPU grease has been applied incorrectly, or there is a manufacturing fault.

I bought a high end Dell XPS laptop a few years ago that had a faulty video GPU that would throttle the laptop after 11 months of purchase. It was replaced under warranty but died again a month later and Dell refused to replace it. There was a class action against Dell, but I could not be bothered.

Editing generally would not put any decent sustained load on the CPU and is not a good indicator of CPU performance. You might be running at 3.2 Ghz, but at 10% load. You would be hard pressed to see it being stressed beyond 10-20% for bursts at a time, but rendering definitely places a sustained load for extended periods of time.

In closing, gaming laptops don’t make great editing systems. I have a i7 laptop and an i7 desktop, and the desktop wins hands down. It is built for performance. laptops are built for so-so performance and portability.

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