Proxy playback - please fix!

Comments

RuedigerW wrote on 10/3/2017, 6:09 PM

@altarvic: I would love to use your script in Vegas Pro 12 as I made the same observation richardbushell did: Proxy files could look better.

Unfortunately your links do no longer work (I guess after the switch to Magix, error message is "*** Link corrupt ***"). Is there any chance you could make your scripts public again?That would be really helpful!

Greetings from Germany,

Rüdiger W.

@altarvic

altarvic wrote on 10/4/2017, 5:09 AM

I don't know what made the links "corrupted" here (they were always public), but I fixed them. Don't forget to change

using ScriptPortal.Vegas;

to

using Sony.Vegas;

if you want them to work in Vegas Pro 12

andyrpsmith wrote on 10/4/2017, 2:44 PM

Tried this and proxy replaces full res clips on time line. However if you use fxmedia such as stabilise then this is not applied to clip when rendered as far as I can see?

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

RuedigerW wrote on 10/4/2017, 3:51 PM

Hello altarvic! Thnx for fixing the link problem! I downloaded the scripts, changed the "using Sony.Vegas" part but as soon as I call the scripts within Vegas Pro 12 I get the following error:

C:\Program Files\Sony\Vegas Pro 12.0\Script Menu\Add Proxies as Takes.cs(27) : Type- or Namespacename var could not be found. (Missing using-directive or Assembly link?)

(That's a translation of the error message because I have a german version installed!)

Unfortunately I'm no JS/C# programer, do you have any idea what's going wrong?

altarvic wrote on 10/4/2017, 4:17 PM

I believe, because of the old .NET Framework in Vegas 12.

I replaced incompatible code, you can re-download and try again.

RuedigerW wrote on 10/4/2017, 5:07 PM

Thnx for your quick reply. Yes, it's working now but a quick test with a large clip cuted into pieces and doing some zoom in (4k source material with default Vegas Pro proxy files) lead to wrong zooming and after switching back to original/original proxy, the IN and out OUT points also changed. Strange. But thnx anyway, I'll have a closer look at it with my next project.

Regards,
  Rüdiger

altarvic wrote on 10/4/2017, 5:16 PM

These scripts were created for @richardbushell. Maybe his specific proxy workflow is not for everyone (and he uses Vegasaur to create custom .sfvp0 proxies).