Hitfilm pro.
The Madison team for Vegas has to re-code every year as well - both for the Hitfilm and Vegas POST pipes (remember they're different pipes).
Hitfilm pro. install#
With Vegas integration you both know you have to install Vegas FIRST, because it's code in the Vegas installer that sets up the pipeline - installing Hitfilm first means you don't even get the option of setting up integration. Pro users are under 5% of the user base, and not every Pro user installs AE plug ins.Īnother thing to take into account with both Vegas integration and Ae plug ins is BOTH TEAMS have to code.
Again, I don't have exact numbers, but I know over 90% of Hitfilm users are on Express and never buy add ons, beyond, maybe, their initial pay what you will.
You still have Vegas Post as an option, you still have rendering from Hitfilm as an option. Besides the product delineation, it still just removes a lot of dev-hours that can be used for other features.Īs far as "losing users," is concerned, yes, a small portion will be annoyed, but, it's not like you can shift to Ae or Resolve and get Vegas integration. They ARE different pipes - Hitfilm projects read the EDITOR Timeline to Vegas as a media clip while Vegas EFFECTS reads a designated Comp Shot. I have been told by the devs the Vegas POST integration was faster than the Hitfilm integration.
Hitfilm pro. update#
As well as marrying the update cycle, where the entire Vegas POST updates through the same installer rather than staggering different Installers for Vegas, Hitfilm and Imerge.
Hitfilm pro. serial#
As assen pointed out, Vegas POST is an option, and that also ties users serial codes to the same account through a single vendor (in this case Magix/Vegas handling the licenses) instead of through two sites/vendors. I think we can assume FXhome discovered the percentage of users using both was really small and determined dev time was better spent on features and improvements that would benefit more users.įinally from a business standpoint it helps delineate Hitfilm from Vegas POST. There's less value in the integration than one would think.Įvery year changes in both Vegas and Hitfilm require the pipeline to be rebuilt - surely you're both used to the new version of Vegas releasing and waiting for the next Hitfilm update to re-enable integration?įXhome also - you may recall - did user surveys over the summer. Rendering from Hitfilm and loading the media was faster every time. I used to run timing tests of integration vs just rendering from Hitfilm and moving the media to Vegas. My workflow just became rendering from Hitfilm and actually being able to edit other sections in Vegas in the background at the same time rather than being unable to edit in Vegas while the cache built. For something minor - maybe a color correction - this might not take too long, but, at least for the types of complex animations I would do I'd have a lot of time waiting for Vegas to cache. Of course when loading a Hitfilm project and/or sending media to Hitfilm from Vegas Vegas has to build the cache files. I happen to be one of those users and here's some of my personal experience.įirst - Vegas does not read Hitfilm's Pre-renders. Don't have exact numbers, but, Vegas integration is only useful for the small subset of users who have both Vegas Pro and Hitfilm.