Time to get off the fence?

Cliff Etzel wrote on 11/21/2014, 1:01 PM

Been quietly lurking off and on the past few months to see how stable VP13 has been and it seems 13 is a lucky number.

Given that Windows 10 will be released sometime next year, and that I refuse to pay Adobe a monthly ransom, no matter how big or small the amount is, (I currently edit with CS6 apps) and there's no guarantee that they will work with Windows 10, I'm now looking at Vegas to become my primary post production tool along with Sound Forge.

Having said that, I'll more than likely be looking at building a new editing machine next year but I'm uncertain as to whether to stick with Intel CPU's or consider AMD given the postings I've read about how well Vegas works with AMD GPU's. I'm considering a small form factor editing machine due to my new office having less space than I had previously and I'm wanting to pare down the size of the machine in preparation of the next iteration of Windows.

I don't do ANY gaming, this will be my workhorse computer and I'm not even sure if a workstation class AIO from HP should be considered.

Any advice on my posting?

Comments

OldSmoke wrote on 11/21/2014, 1:11 PM

AMD GPU yes, CPU no.

Cliff Etzel wrote on 11/21/2014, 1:23 PM

@OldSmoke - my current machine is running on an x58MoBo with Xeon processor and 18GB of RAM and an nVidia GTX-550ti card. I've read all the postings about how well AMD 6950/6970 cards perform with Vegas Pro 13. I'm not doing any heavy lifting video editing at the present time as I'm mainly producing no longer than 5 minute videos for my clients. I shoot DSLR video footage running Magic Lantern with a custom flat profile.

Having said that, any reason to upgrade my current hardware outside of the graphics card?

Thanks for your response

Cliff

videoITguy wrote on 11/21/2014, 3:12 PM

I am producing DSLR source content with great outcomes on machines half as powerful. Don't use Magic Lantern. VegasPro13 is fine.

Cliff Etzel wrote on 11/21/2014, 5:03 PM

@videoITguy - can you elaborate as to why one shouldn't use Magic Lantern?

OldSmoke wrote on 11/21/2014, 5:53 PM

It all depends on what you are working with now or in the future, 4K files playback at Best/Full with FX and transitions may actually require a dual Xeon setup, 5960X isn't strong enough either.

If can, get a R9 290 off eBay; should be around $220.

videoITguy wrote on 11/21/2014, 5:59 PM

Cliff, several things here, I really have no use of Magic Lantern, and even though I may be tempted to play with it - in my serious work, I use the DSLR as second or third unit companion to high-end camera production. I have heard anecdotally that Magic Lantern is a problematic app - and the least favorite thing in my bag is trying to add complexity.

As far as DSLR files produced in .mov containers I would never expose them directly to a VegasPro timeline. Instead they are all fully transcoded to digital intermediates of the Cineform codec and then safely used elablorately I may say on the timeline. One more thing transcoding is done outside of the Vegas app to keep full color and gamma.

Cliff Etzel wrote on 11/22/2014, 11:04 AM

@VideoITguy - I've yet to experience anything you mentioned with Magic Lantern being problematic. Albeit, my production tools are all DSLR ad as such needed to have the additional features that the firmware provides (Focus peaking, native ISO's not locked out, HDR, etc)

I've debated back and forth on transcoding to Cineform and had been for some self generated documentary work but much of the work I shoot has a quick turnaround and doesn't pay well enough to spend the extra time transcoding as it's being used for the web.

Are you using the GoPro app to transcode the DSLR footage to maintain full color and gamma?

I digress as my concern is preparing for what I get a sense of that I will be left with Premiere PRO CS6 apps not functioning correctly in the the future release of Windows 10 and it seems VP13 for the most part has become reliable.

As a side note, my go to app for post on the audio end of things has been Adobe Audition as their noise removal tool is quick and does a great job. I use it extensively to remove A/C and refrigerator noise when on location. Can this be done in Vegas Pro or do I need to look at Sound Forge Pro?

Thoughts?

videoITguy wrote on 11/22/2014, 11:09 AM

Transcoding is done for specific purpose - for example long form production, turnaround of 4 months for a project, complex compositing, keeping original color and gamma - release to Blu-ray disc. I use legacy Cineform, not the GoPro acquisition.

Now if you are quick and web release, many of these issues go away, and you may be back to transcoding of a different level - for example Sony MXF or other...

rraud wrote on 11/22/2014, 12:49 PM

Noise Reduction 2 audio restoration suite is bungled w/ SF-11 Pro among others including the iZotope Nectar Elements and the Mastering Suite. Sound Forge Pro is a must-have companion app for audio post IMO.

Cliff Etzel wrote on 11/22/2014, 2:14 PM

The #1 use I have for my working in audio is removing ambient hum from A/C, Refrigerators and other sources of low hum like marginal mics and such.

I currently have Sound Forge 10 and not sure if I should make the upgrade to SF 11 given what I use audio editing for when doing video post production.

Any thoughts?

rraud wrote on 11/22/2014, 4:20 PM

SF-10 Pro came with the NR-2 suite as well as the iZotope mastering suite.. not Nectar though as I recall. Unless you need or want something specific that Pro 11 has, there's no reason to upgrade IMO. In addition, SCS made changes to Pro 11's recording and effects chainer that many (including me) find counter-intuitive the slows down work flow.

VideoFreq wrote on 11/22/2014, 10:23 PM

Sorry for this aside... Does anyone know where to get the legacy Cineform? I have looked. Actually, I have it but it was a trial version and when I went to purchase the key code, GoPro said no, I need to update. I don't want to update.

Serena Steuart wrote on 11/22/2014, 11:23 PM

Why not update? You didn't actually buy the version you have.