Lee Doucet
Forum Replies Created
-
Downloads aren’t indicative of much, since you had to register to download updates as well. They only just added an in-product update system in Resolve 16b1…
Resolve is exceedingly popular by virtue of Windows’ market share vs. macOS; and the fact that it is also available on both macOS and Linux.
It probably already has more users than FCPX, at this point.
-
Probably not, as they have publicly stated that the standalone version will continue.
But, it’s certainly not a priority. It get little to no mid-release support. Last update for Fusion 9 was, what… almost 2 years ago?
The priority seems to be moving as much functionality into Resolve as humanly possible, as quickly as possible, so that they can get to a point where they can realistically end it and not have to focus on two tools 🙂
-
CS4 has no hardware decode support, and you didn’t say what the birtate of those MP4 files are. Is that footage from a smartphone or consumer camcorder (which maybe XAVC-S or AVCHD)? Those are low bitrate files. Even a Laptop HDD can handle that, frankly.
4th Gen i3 is quite low end, even for CS4, when using that type of footage.
You will get better performance transcoding that to a Digital Intermediate Format: ProRes, DNxHD/R, Cineform, Grass Valley (Canopus) HQ[X], etc… Maybe XAVC-Intra? Whichever CS4 supports, in that order.
CS4 is pretty old, and I always hesitate to tell people to upgrade – especially with Adobe apps, given the change in business model since then…
But those files would almost certainly work out of the box with a current version of Premiere Pro CC. I’ve personally never been satisfied with the way videos look after running them through Handbrake 🙁
-
1. In VEGAS Pro 14, GPU Encode Acceleration only works for Fermi cards (and maybe Maxwell). It won’t work with Pascal cards. You need to upgrade to VP15/16 for that.
2. VEGAS Pro 14 has broken support for GPU Graphics Acceleration on Nvidia Pascal Cards. It simply doesn’t work properly, if at all. You need to upgrade to VP15/16 to fix that. Everything is done with the CPU, with very little help from the GPU. When using the NLE, you probably should set it to the Intel iGPU, and not the Nvidia GPU.
Upgrading will also give you QSV Decode Acceleration for supported formats (which should work well on a 7th Gen i7-HQ CPU, up to 10-Bit HEVC).
-
Honestly, there isn’t much difference between Movie Studio Platinum and Pro. It’s just VEGAS Pro with some features and CODEC/Interchange formats disabled.
It is not at all comparable to the difference between Premiere Elements and Pro CC, or iMovie and Final Cut Pro X 😛
MSP 12 is 3 versions behind VP15, so it’s possible that the bug was introduced into VEGAS Pro (and possibly Movie Studio Platinum) after that version was released (i.e. v14, though the bug may be limited just to v15 of VP). MSP versions, these days, release months after VEGAS Pro, so it’s possible that it may dodge bugs that are in VEGAS Pro by virtue of them being fixed while it’s still in development, while VEGAS Pro simply has the bug ignored because they decide to backburner it and work on the new version instead.
-
Variable Bit Rate is 101% ignorable. That is not going to be the issue.
Variable Framerates can cause issues in some NLEs, but VEGAS Pro has – at least in my experience – handled that type of footage with ease; even while other NLEs (Avid, Premiere, Resolve, etc.) failed to do so (Premiere has been updated to better handle that type of media). Still, I’d look into that as a possible issue (I did not download the OP’s file, so I cannot say if the file even has this MediaInfo tag on it).
-
I think it has more to do with just reputation. I think Apple just didn’t focus on the things that make Avid strong for those types of productions. Currently, no one else really matches them there, though others (like Adobe, BMD, Grass Valley) are starting to pay a bit more attention to that area.