@Former user Nick seems to have removed the link to the script from section 10 in his update 10/17/2017.
@vkmast Maybe an oversight? Or maybe theres a commercial angle. i.e. Pure speculation here on my part ... Magix probably pays per licence activation, so if everyone used the script then Magix would pay more than is necessary as without the script some users might never use some of the codecs.
@vkmast - Totally confused now.
Really🤣. I could ask Magix to lay on an extra server, but then, we’re only at page 3, maybe wait a while.
@Grazie Yes, they get activated on a per use need case. Not sure that if you were offline and the codec wasn’t yet activated that you couldn’t use it, but probably yes.
Just sharing my vp17 upgrade experience as it sounds similar to the original post on this thread, but I do now have it stable and working well.
On initial install v17 took ages to load complex v16 projects and crashed before I could do much. I have Rysen 1700, Nvidia 1060ti 6gb and 32gb system RAM. I film with Sony A7 cameras, so all my files are XAVC-S, mixture of 4k@24fps and 1080@60fps.
Here's what I did to get it under control:
It's great to edit with now. Still crashes about once per hour, but that's similar to V16.
And the smooth playback of 4k clips is great. My dream of a budget self build PC that can edit 4k video without having to transcode clips is finally working. Yay, vegas!
I also use vegas on another PC that only has a 1050ti 2tb GPU, and that won't cope with NVDEC playback. So I'd guess a 1060ti 6GB is the best budget GPU to get that working.
Grazie, have you disabled hover scrubbing? That may help your project media issue.
Just sharing my vp17 upgrade experience as it sounds similar to the original post on this thread, but I do now have it stable and working well.
On initial install v17 took ages to load complex v16 projects and crashed before I could do much. I have Rysen 1700, Nvidia 1060ti 6gb and 32gb system RAM. I film with Sony A7 cameras, so all my files are XAVC-S, mixture of 4k@24fps and 1080@60fps.
Here's what I did to get it under control:
- Turned off thumbnails (that made the biggest difference)
- Switched File IO to NVDEC (that allows me to play 4k files in preview with no lag for the first time!)
- Installed latest studio driver for the GPU (1060ti 6gb)
- Reduced Dynamic RAM to 300 (down from 1600). Essential to get stable playback.
- I tried disabling so4.dll but that made playback slightly worse (didn't test overall stability) so I've kept it enabled.
- When I first opened a v16 project in v17 it did take a long time to settle - I think that was mostly the thumbnail issue, but possibly there's some other file checking going on in the background (that's only a guess).
It's great to edit with now. Still crashes about once per hour, but that's similar to V16.
And the smooth playback of 4k clips is great. My dream of a budget self build PC that can edit 4k video without having to transcode clips is finally working. Yay, vegas!
I also use vegas on another PC that only has a 1050ti 2tb GPU, and that won't cope with NVDEC playback. So I'd guess a 1060ti 6GB is the best budget GPU to get that working.
When I use so4compoundplug it takes just over 3min to load my project with compoundplug it tales 1min 15 sec.