Reply by: Gary James - author of Timeline Tools and Playlist
Date: 4/20/2014 7:13:26 AM
" My Timeline Tools and Rosebud's Show Event Length are working."

and
Reply by: wwaag Date: 4/19/2014 3:47:10 PM
"The Open in Graphics Editor script from Rosebud works perfectly"
Location of script files verified as :C:\Program Files\Sony\Vegas Pro 13.0\Script Menu

notes:
Reply by: BobMoyer Date: 4/20/2014 10:39:28 AM
My OS is Windows 7/64 bit Home Premium Service Pack 1 (with ALL updates from MS)
and
Reply by: wwaag Date: 4/20/2014 11:33:40 AM
Same as BobMoyer. Win 7/64 Home Premium with SP1.

Subject: RE: NO SHOW EVENT LENGHT!!!! Reply by: malowz
Date: 4/20/2014 3:49:58 PM
my .NET folders show Net4 installed, yet no extensions show up

Member JV1 this FROM Subject: RE: Render speed seems a little slower in Ver13 vs V11 --- Reply by: JV1 on the Date of: 4/21/2014 12:58:19 PM
" I tried a much shorter clip (7 seconds) and added various FX to it ...looks like the "demo logo" could be the culprit slowing down the VegasPro13. Thanx VidMus for the idea.

I had called SONY a few times and suggested they add to V13 a simple "note-pad" to put Word docs and the like in (I do a lot of scripted narrations) I did install TimeLine Tools in VegasPro12 (?) a few months ago and that has a really nice notepad ."
and furthe Reply by: JV1 of Date: 4/21/2014 3:18:44 PM

Actually, I just tried opening Timeline Tools in the demo of V13 and it gives me an error even though the icon appears (View/Extensions/Timeline Tools). It still opens in V11 (I don't have V12). It's hard to believe they disabled this but maybe it's only disabled in the demo? Seems like a big step backwards.

FYI - The version is 1.0.53 - 64 bit mode, 2011 - 2013.

Update - I was just on the Timeline Tools website and it says V13 is not playing nice with TT but maybe there will be an update soon. I think I'll hold off on upgrading until TT works.

John, are you at liberty to describe what was "changed" to be compatible with SVP-13. There are probably hundreds of amateur and semi-pro Script and Extension authors out there that could benefit form some sage advice from you pro's; myself included.

1) Name the successful script ?
All of Vassts and Edwards.
"Rosebud" Open In Graphic Editor

2) Your OS ?

Win7 64bit

3) Are your running User Accounts control?

What is that?

4) Name any scripts that are unsuccessful if any that you have tried?

Event Length
Gary James (Gary's runs fine in VP12 - eh?)

5) what is the location of your VegasPro13 scripts containing folder?

C:\Program Files\Sony\Vegas Pro 13.0\Script Menu

> "John, are you at liberty to describe what was "changed" to be compatible with SVP-13."

I didn't change anything in my code. I just tested them to make sure that they worked. I had to change the installers to look for Vegas Pro 13.0 but that was just an installer tweak for people who only have Vegas Pro 13.0 installed.

What changed is they are now being called from .Net 4.0 so if .Net 4.0 changed something that affects your script then it might break your code. I'm not a Windows programmer so I didn't get too fancy with the .Net Framework. Perhaps people who took more advantage of it were affected more by it changing.

~jr

I think we should differentiate between scripts and extensions.
There is a very real difference.

1) Name the successful script ?
Vegasaur. An extension. (it was updated for V13 compatibility)

Antares preview levels. An extension. I am using the same version that worked under VP12. I changed nothing and it just showed up and worked in VP13.
http://vegasvideo.de/extension-previewlevels-en.html

2) Your OS ?

Win7 64bit

3) Are your running User Accounts control?

Yes

4) Name any scripts that are unsuccessful if any that you have tried?

Event Length (an extension)

5) what is the location of your VegasPro13 scripts containing folder?

Antares Preview levels is installed in
"My Documents"\Vegas Application Extensions
No installer. It is a ZIP file. I just copied the DLL here.

this is where I tried to use the Event Levels extension.

Vegasaur is installed in.
C:\ProgramData\Sony\VegasPro\Application Extensions
Vegasaur has an installer which uses this location.

> "to be very clear - you are suggesting that a tweak to the installer had to be made for users who have no other concurrent installation of versions of VegasPro prior to release 13 - because-"

None of those reasons.

To be very clear, my VASST installers look for all of the versions of Vegas that they support. Each installer is different. Some extensions require a certain level of Vegas Pro like Caption Assistant requires at least Vegas Pro 9.0e which is when closed captions were introduced. This helps customers to not install something that isn't going to work with their version of Vegas Pro or Movie Studio. That means that every time a new version of Vegas Pro or Movie Studio comes out, I have to add it to the list as a check in our installer. This is nothing specific to Vegas Pro 13.0 or .Net 4.0 or anything like that. I did this for Vegas Pro 12, 11, 10, etc. It's just a check for the existence of supported versions of Vegas; nothing more.

~jr

Are all the script problems with Vegas 13 caused by compiled code executed as .dlls ?

If so, here's a real shot in the dark... could it be that the script's .NET build must now reference the Sony.Vegas.dll shipped with Vegas 13?

...Jerry (who has no plans for a V13 upgrade at this time)

> "... could it be that the script's .NET build must now reference the Sony.Vegas.dll shipped with Vegas 13?"

Good guess but some of our VASST extensions are compiled against Vegas Pro 8.0 for maximum compatibility and they work fine in Vegas Pro 13.0.

~jr

"I think we should differentiate between scripts and extensions. There is a very real difference"

NormanPCN, when I'm talking about Scripts and Extensions, I'm referring to compiled Script DLLs, not stand-alone text files with .JS or .CS extensions. Compiled scripts are compiled to a specific version of .Net and the SonyVegas.DLL that they, like Extensions communicate with.

"I didn't change anything in my code. I just tested them to make sure that they worked. I had to change the installers to look for Vegas Pro 13.0"

John, do your installers require any specific security privilege level to operate. For example Administrator, or Power user, etc?

Timeline Tools does go outside the .Net Framework for some of its functionality. But this is nothing more than direct calls to the underlying Windows SDK which is Windows itself, and not related to .Net in any way.

This is very puzzling. The error messages reported by Grazie and Bob seem to indicate that Timeline Tools can't find the RicherTextBox Custom Control that I created and install right next to it in the same Vegas Script Menu folder. That is very bizarre.

> "John, do your installers require any specific security privilege level to operate. For example Administrator, or Power user, etc?"

The installer requests "highest" which is just below "administrator". I don't know if that's power user or not. You need to have elevated privileges to write to the HKLM registry hive.

~jr

And at the same time, Gary, TT is working in VP12. Shouldn't TT not work for BOTH 12 and 13, if it doesn't work for 13? Is that a clue?

Grazie

You are exactly right. And that's what's so puzzling. There's nothing obviously different from what SVP-12 and SVP-13 sees in the Vegas Script Menu folder. That's why I asked about privilege level in the installer. It's possible that SVP-13 requires a higher access level than 12 when installing Scripts and Extensions.

Grazie, when you installed TLT, where you logged in as an Administrator, or as a extra account owner?

JohnnyRoy,

I'm using Ultimate S Pro and when VegasPro 13 installed, I can found the extension already loaded? (Installed since VegasPro 10...). Am I missing something ?

I'm the Administrator. I'm the only one using this PC. Now, where do I confirm this?

Grazie

event length not loading in 13, working happily in 12

win7/64bit

and here's the error messages:

on the laptop:

System.IO.FileLoadException: Could not load file or assembly 'file:///C:\Program Files\Sony\Vegas Pro 13.0\Script Menu\CC_ShowEventLength.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)

and on desktop:

System.ApplicationException: Failed to create instance of main class: 'EntryPoint'.

> "I'm using Ultimate S Pro and when VegasPro 13 installed, I can found the extension already loaded? (Installed since VegasPro 10...). Am I missing something ?"

Nope you're not missing anything. This is what I've been trying to say all along. I didn't have to do anything to get the VASST Extensions to work. They just work as they always did. I tested them on Windows 7 and Windows 8.1. No issues that I could find.

~jr

VITG: "Gary ---When Grazie was asked by me if he had User Account control on - he did not know how to respond...he also implied that he had fiddled with permissions over folders (but perhaps not files) .

User Account Control is ON and was set to the DEFAULT for WINDOWS. I've NOW adjusted it to the HIGHEST option that is to inform me that ANY Program wishing to make changes I will be the first to know.

I AM the Administrator. I was prior and still am. Period.

Now my adjustments of security and the rights thereof were restricted to purely the working of the Open In Graphics Editor AND the options for the Event Length Script, which I'd read up about here on the Forums; seeking/sourcing further advise via email in the last 4 days, from the Author, Gilles, where he had advised me to re-read the already posted advise and then the well documented feedback concerning the security settings regarding .Net 4 . If anybody wishes to add any further ADVISE then I am all ears.

Is that clear enough?

And, BTW, if I then didn't know how to respond, VITGuy, why not inform me how to do it? I can and do follow instructions pretty well.

Cheers

Grazie

VITGuy, here are the additional sources I read and researched on. There are 2, with convergent lines of description which may indicate a solution:

No.1 : Blocked DLL from another computer: "An attempt was made to load an assembly from a network location"

No.2 : ".net local assembly load failed with CAS policy"

Cheers

Grazie

Gary: "Grazie, when you installed TLT, where you logged in as an Administrator, or as a extra account owner?

I was, and still remain logged in as the Administrator. I've rechecked this morning, after my cuppa coffee, so I am truly alert and responsive.

Both VP12 and VP13 are set with my same Admin Rights - that's me.

I just removed TLT from my PC and reinstalled TLT. It's working in VP12 and still not working in VP13.

Presently I cannot see any differences between VP12 and VP13, other than VP13 requires and uses .NET4 .

We are needing some logical convergence of User experience to nail this. Leslie has got TLT working in BOTH VP12 and VP13, but he can't get Event Length to work in VP13, but DOES work in VP12. He also has Gilles OIGE script working - as do I. But I can't get TLT to working in VP13.

There is something not tweaked.

Cheers

Grazie

hold on there gazie old chap - i never said i had tlt* running in 13 did i?

in fact, i don't even have tlt installed this time round.

*we are talking about 'time line tools', aren't we?

My apologies.

It is purely you have Event Length working in VP12 but NOT in VP13. Got it.

Grazie