Comments

Wolfgang S. wrote on 12/30/2007, 12:42 PM
Gearshift only uses existing render templates - and beside the templates "AVCHD for PAL/NTSC" there are no render templates in Vegas, that combines 5.1 audio with video (or whatever you use as proxy-file).

Either you combine the audio part with the new rendered video part manually (what can be a lot of work), or you use stereo only.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

InterceptPoint wrote on 1/1/2008, 8:19 AM
OK on the 5.1 issue but I'm still having problems getting Gearshift to work the way I would like: with Proxies only.

I don't want to create the Intermediaries since this takes a lot of time and, I think but could be wrong, the final render will use the Intermediaries instead of the original AVCHD files. I don't see any benefit to doing so although I have managed to make Gearshift work in that mode.

So I'm trying to run Gearshift in Proxy Only mode.

I have tried Source, Media Bin and Timeline modes. Source and Media Bin modes will allow me to create the GSP Proxy files but the swap from source to proxy or proxy to source just doesn't work. The replacement is not made. I get an error message every time. In the Timeline mode you cannot create a Proxy only render. It is not allowed by Gearshift.

So the question is:

Can you actually convert .m2ts AVCHD files to Gearshift Proxies and swap source to proxy and proxy to source (without creating the Intermediaries)? If so, how?
Wolfgang S. wrote on 1/1/2008, 9:24 AM
I have not tried - since I prefer the Intermediates, if I edit AVCHD at all (and use the Canopus HQ conversion tool here). So, I cannot say here more.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

JohnnyRoy wrote on 1/1/2008, 10:23 AM
> Source and Media Bin modes will allow me to create the GSP Proxy files but the swap from source to proxy or proxy to source just doesn't work.

Ooops! I just recreated this error (sorry) and fixed it this morning. There is a new release of GearShift 1.7.1 that fixes the problem with .m2ts files not swapping. Just download the latest GearShift from the VASST web site and install it over what you have now.

> Can you actually convert .m2ts AVCHD files to Gearshift Proxies and swap source to proxy and proxy to source (without creating the Intermediaries)? If so, how?

Yup. You were doing everything correctly. It was a bug in the program. This should work now. Sorry for any inconvenience this may have caused you.

~jr
InterceptPoint wrote on 1/1/2008, 11:40 AM
Thanks for the quick response but I still have a problem.

I installed 1.7.1 right over 1.7.0. 1.7.0 Uninstalled OK. 1.7.1 installed OK and shows up on the Vegas 8.0a taskbar just like it should. All looks OK installation-wise.

But I get the following message when I launch Gearshift:

"The located assembly's manifest definition does not match the assembly reference."

I can post the full error message if you want.

Any ideas?
Cliff Etzel wrote on 1/1/2008, 1:03 PM
I also get the same message so this appears to be a glitch in the latest build

The complete error message:

System.IO.FileLoadException: Could not load file or assembly 'Sony.Vegas, Version=8.0.0.179, Culture=neutral, PublicKeyToken=3cda94b1926e6fbc' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Reverting back to version 1.7.0 fixes the problem

Cliff Etzel - Solo Video Journalist
bluprojekt
JohnnyRoy wrote on 1/1/2008, 3:56 PM
Cliff,

Thanks that pinpointed the problem. I've uploaded a new build. Please download the 1.7.1 version again and see if that works. Under Vegas Pro 8 when you go into the GearShift About Box (i.e., click on the VASST logo) it should say:

Version: 1.7.1.33285

I have this working for me under Vegas 8.0a (Build 179)

~jr
InterceptPoint wrote on 1/1/2008, 4:20 PM
Sorry but I'm still getting the same error with the updated 1.7.1. I can't get to the logo but the time stamp on GearShiftV8.dll is 1/1/2008 3:29PM and the size is 1244 KB.

I am running version 176 of Vegas 8.0a.

Here is the complete error message.

System.IO.FileLoadException: Could not load file or assembly 'Sony.Vegas, Version=8.0.0.176, Culture=neutral, PublicKeyToken=3cda94b1926e6fbc' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Sony.Vegas, Version=8.0.0.176, Culture=neutral, PublicKeyToken=3cda94b1926e6fbc' ---> System.IO.FileLoadException: Could not load file or assembly 'Sony.Vegas, Version=8.0.0.179, Culture=neutral, PublicKeyToken=3cda94b1926e6fbc' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Sony.Vegas, Version=8.0.0.179, Culture=neutral, PublicKeyToken=3cda94b1926e6fbc'


at System.Signature._GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, IntPtr fieldHandle, IntPtr methodHandle, IntPtr declaringTypeHandle)
at System.Signature.GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, RuntimeFieldHandle fieldHandle, RuntimeMethodHandle methodHandle, RuntimeTypeHandle declaringTypeHandle)
at System.Signature..ctor(RuntimeMethodHandle methodHandle, RuntimeTypeHandle declaringTypeHandle)
at System.Reflection.RuntimeMethodInfo.get_Signature()
at System.Reflection.RuntimeMethodInfo.GetParametersNoCopy()
at System.RuntimeType.FilterApplyMethodBaseInfo(MethodBase methodBase, BindingFlags bindingFlags, CallingConventions callConv, Type[] argumentTypes)
at System.RuntimeType.GetMethodCandidates(String name, BindingFlags bindingAttr, CallingConventions callConv, Type[] types, Boolean allowPrefixLookup)
at System.RuntimeType.GetMethodImpl(String name, BindingFlags bindingAttr, Binder binder, CallingConventions callConv, Type[] types, ParameterModifier[] modifiers)
at System.Type.GetMethod(String name, BindingFlags bindingAttr, Binder binder, CallingConventions callConvention, Type[] types, ParameterModifier[] modifiers)
at Sony.Vegas.ScriptHost.ScriptManager.Run(Assembly asm, String className, String methodName)
at Sony.Vegas.ScriptHost.PrecompiledScriptManager.Run()
at Sony.Vegas.ScriptHost.RunScript(Boolean fCompileOnly)


JohnnyRoy wrote on 1/1/2008, 4:32 PM
> the time stamp on GearShiftV8.dll is 1/1/2008 3:29PM

You still have the old one. Make sure when you downlaod it you are not using a download manager or anything that will see that it's already been downloaded and give you the one that's in your cache.

The new GearShiftV8.dll will have a timestamp of 1/1/2008 6:29PM and the GearShiftInstaller-1.7.1.exe will have a timestamp of 1/1/2008 6:31PM.

~jr
InterceptPoint wrote on 1/1/2008, 5:15 PM
"You still have the old one. "

Nope. The installer timestamp is 6:31PM and my 3:29PM West Coast is probably your 6:29PM East Coast.

Still broke.
Should I upgrade Vegas from 176 to 179?
JohnnyRoy wrote on 1/1/2008, 5:32 PM
> Should I upgrade Vegas from 176 to 179?

Yes, this was compiled against Vegas Pro 8.0a Build 179. That should fix the problem.

~jr
InterceptPoint wrote on 1/1/2008, 6:31 PM
JohnnyRoy:

Thanks for all the hard work on a day when you should have been watching ball games and drinking beer.

The update to 179 did the trick.

Thanks again.

Jeff
MH_Stevens wrote on 1/2/2008, 9:31 AM
Johnny: To save starting a new thread I ask will Gearshift be working with the EX1 at 1990x1080 as an alternative to Cineform HD (as opposed to the 1440 version HDV)?