NO SHOW EVENT LENGHT!!!!

Back to post

Comments

wwaag wrote on 4/19/2014, 4:29 PM
TimeLIne tools does not show up anywhere, neither extension locations nor scripting.

There are three extension locations under Edit, View, and Tools. Most of mine (including Timeline Tools, and Show Event Length) show up under the View|Extensions except Plural Eyes that shows up under Tools|Extensions.

wwaag

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

BobMoyer wrote on 4/19/2014, 4:36 PM
-wwaag-
You are correct, it does show up under the "View" menu/extensions. However, it still gives me the same error msgs. as listed above. Ultimate and VideoWall will launch properly.

Bob
wwaag wrote on 4/19/2014, 4:39 PM
You are correct, it does show up under the "Edit" menu/extensions.

Don't you mean View|Extensions?

wwaag

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

BobMoyer wrote on 4/19/2014, 4:46 PM
Yeah, that's what I meant...its been a long day for me....sorry for any confusion.

Bob
Gary James wrote on 4/19/2014, 4:55 PM
You are correct, it does show up under the "Edit" menu/extensions.
Don't you mean View|Extensions?
wwaag

Ok, now I'm more confused than ever. WWAAG, did you say that you are successfully running Timeline Tools with SVP-13?

TheHappyFriar wrote on 4/19/2014, 4:58 PM
Works for me too:
http://s1373.photobucket.com/user/the_happy_friar/media/works4me_zpsc403ef6f.jpg.html[IMG=http://i1373.photobucket.com/albums/ag400/the_happy_friar/works4me_zpsc403ef6f.jpg][/link]

User issues once again. As usual. :)
videoITguy wrote on 4/19/2014, 5:02 PM
Happy Friar - so do you want to explain to the rest of us mortals what are "user issues" as you have found them?
Grazie wrote on 4/19/2014, 5:02 PM
Gary, here are 2 error notices when I activate TT in VP13:-





Working fine and dandy in VP12 Build 770. I have .NET4 installed.

Cheers

Grazie



videoITguy wrote on 4/19/2014, 5:08 PM
Grazie's error is exactly the same reported error of Bob Moyer above in this thread.

The question would be what is common for their two installations and would it be something that other users are overlooking?
wwaag wrote on 4/19/2014, 5:35 PM
Ok, now I'm more confused than ever. WWAAG, did you say that you are successfully running Timeline Tools with SVP-13?

Yes. Both Timeline Tools and Show Event Length are working. I'll try the graphics editor script and report back.

wwaag

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

wwaag wrote on 4/19/2014, 5:47 PM
Just tried the Open in Graphics Editor script from Rosebud and it works perfectly. From the zip file, I extracted the 2 dll's and png file and copied them into the V13 Scripts Plug-ins Folder. I then ran the script specifying which graphics editor--Photoshop. I then imported an image, ran the script and the image opened in PS. I did a simple crop, saved, exited. Back in Vegas, the edited image was shown as a take.

wwaag

Here's the original.



And here's the cropped image shown as a take


AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Grazie wrote on 4/19/2014, 6:00 PM
Yup, wwaag I've done the exact same as you with out any luck. But what is the "V13 Scripts Plug-ins Folder"? I'm putting them in the Script Menu folder?

Thanks for reporting this.

Grazie

Grazie wrote on 4/19/2014, 6:02 PM
Here's my PATH:

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

Any different?

Grazie

wwaag wrote on 4/19/2014, 6:07 PM
But what is the "V13 Scripts Plug-ins Folder"? I'm putting them in the Script Menu folder?

My mistake. It IS the Script Menu folder that I used. But it does work as shown in the above photos. As an aside, this really will be a very useful script. Hopefully, someone can figure out why it works in some systems and does not in others.

wwaag

C:\Program Files\Sony\Vegas Pro 13.0\Script Menu
The same.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Grazie wrote on 4/19/2014, 6:12 PM
I've had this script working up to VP12, but not now with VP13.

G
ushere wrote on 4/19/2014, 7:10 PM
@wwaag - thanks for the pointers....

so now i'm getting the following error 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 my desktop:

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

either way it's obviously a no go, but working happily under 12 on both machines...

still furious. this is so unprofessional...
Steve Mann wrote on 4/19/2014, 11:33 PM
Note that .net versions are NOT hierarchical, that is, .net v3 does not replace v2 and v4 does not replace v3. (Oddly, v2 did replace .net v1).

NickHope wrote on 4/19/2014, 11:40 PM
Marc S wrote: "...I recently installed Sony Mo Studio Platinum for someone and it now includes show video length built into the program..."

How had they implemented it? i.e. What did it look like?
PeterDuke wrote on 4/20/2014, 2:21 AM
On the side topic of .NET, can anybody explain why each program that needs .NET seems to install its own release, so that I end up with several versions of .NET2, .NET3, etc.

I tried uninstalling them all and replacing with the latest release of each version from the MS site, so that I only had one release for each version. Nothing seemed to break.
JohnnyRoy wrote on 4/20/2014, 5:39 AM
> "On the side topic of .NET, can anybody explain why each program that needs .NET seems to install its own release, so that I end up with several versions of .NET2, .NET3, etc."

Because Microsoft is clueless on how to provide common runtimes and they force this upon the end user. .Net Framework releases are NOT backward compatible. You need to install old versions if you need that capability. It's the stupidest thing I've ever seen.

The applications are not requiring multiple copies of .Net. The application is totally unaware of this. Microsoft Windows is downloading multiple copies of .Net. I was shocked when I first tested Production Assistant 2.0 on Windows 8.1 and it installed just fine. Then the first time I ran the launcher, it prompted me to download and install .Net 3.5. Trust me, I did nothing to make this happen other then use the .Net Framework when I was developing.

So you can blame Microsoft for telling developers to use their .Net Framework, and then not having the common courtesy of shipping the runtimes with it's precious operating system (like it isn't bloated enough already). The .Net Framework is a mess and Microsoft continues to make their developers look bad in front of their customers.

~jr
Grazie wrote on 4/20/2014, 6:08 AM
SUCCESS with OIGE! - but not as we know it - JIM!

O...K... ( actually, I haven't heard jr so bloomin' angry . . be that as it may . .ahem . . . ) I believe I have success with the Open In Graphics Editor script.

Instead of copying/using the script from within the Script Menu, I had made an exploded ZIP Folder on my Desktop, and to copy from there.

1st attempt at least I had got the Setting to work, but was told that there was an error on USING the OIGE script . . O...K....

I then told a leap of faith and instead of using the OFFICIAL Sony Script Menu Folder, I used the Desktop Folder and that HAS worked.

Eh? - It works.

Now, maybe just maybe, the importance of copying to Script Folder has to be done FROM an already established MS folder? Not just an un-Zipped folder?

Is this .Net4 poking its nose in?

Now, all I need is some kind soul to figure-out this OFFICIAL<>DESKTOP Script Menu fan-dangle.

Leslie - hold tight.

Grazie

Grazie wrote on 4/20/2014, 7:37 AM
O..K....

I had to change the Permissions of the Official SONY Script Menu Folder to "match" those of the Working Desktop Folder of the OIGE Script and settings.

I can now activate it from the OFFICIAL SONY Script Menu Folder.

Lesson learnt here - was what? Not sure.

Anybody wanna shed light on this?

Grazie

ushere wrote on 4/20/2014, 7:53 AM
grazie, you're a wonder...

now, take a deep breath and walk me through what you did step by step, and i'll try event length with it instead.

NOT that we should have to be doing any of this in the first place ;-(
Kit wrote on 4/20/2014, 8:19 AM
I think the problem is that Sony are storing scripts where they shouldn't. They shouldn't be located in the Programs folder but in Users\UserName\AppData\Roaming etc. That's why you needed to change the permissions. You shouldn't need to do it again to install other scripts if you have given users full control over the folder. That's just a guess.