Good point Kit.

Need more hands-on-deck with this doobrie . . . .

G

> "actually, I haven't heard jr so bloomin' angry . ."

Angry? Me? YOU BET!!! :-D

Here is the out-of-the-box experience that my customers get with Production Assistant 2.0 under Windows 7:

(1). Install the program
(2). Click on the desktop icon
(3). The program opens

Here is the out-of-the-box experience that my customers get with Production Assistant 2.0 under Windows 8:

( 1). Install the program
( 2). Click on the desktop icon
( 3). Get prompted to download the Microsoft .Net Framework Runtime
( 4). Wait 20 minutes for a download that eventually fails
( 5). Click on the desktop icon again
( 6). Get prompted again to download the Microsoft .Net Framework Runtime
( 7). Wait another 20 minutes for a download that eventually fails
( 8). Post to the forums with your problem
( 9). Wait for an answer
(10). Get told it must be unique to your PC because it "work for me" ;-)
(11). Finally get an answer to download the stand-alone .Net Framework Runtime directly from Microsoft
(12). Manually download the stand-alone .Net Framework Runtime
(13). Manually install the stand-alone .Net Framework Runtime
(14). Get prompted to reboot your computer
(15). After the reboot, try and remember what it was that you were doing in the first place... Oh yea, I wanted to actually get some work done.
(16). Click on the desktop icon
(17). The program opens

Who gets blamed for this mess? I do because it's my application icon that they clicked on!

The same thing happened to Sony and the Media Manager. Sony finally had to relent and make the Media Manager a separate download because the Microsoft runtimes needed to run it kept failing when installing and failing when starting and customers were complaining. So Microsoft's inability to provide a seamless integration of their own runtimes gets blamed once again on the developers that use it.

Someone needs to gather up the development managers at Microsoft and beat them with the "Simple Stick!" ;-)

~jr

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

I've tried looking at systems specs from everyone experiencing problems with Extensions in SVP-13, unfortunately Sony doesn't display Windows version. I'm wondering if this is an environmental issue, like Win 7 vs Win 8.

WWAAG, what version of Windows are you running. Same for you Grazie and Bob.

Gary?!?? - Well there's a thing . . . .

I can't see my OS info from THIS side of the SONY WALL, but when I interrogate MY SYSTEM then it is there!

As if I haven't entered it - but I HAVE and I can see it's there too.

Here it is, ALL of it:-

System #1
Computer Brand/Model:
Operating System: Windows 7 64-bit
RAM: 16gb
Processor: Intel® Core™i7-2600k Quad Core 3.40GHz
Video Card: 2GB NVIDIA GEFORCE GTX 560 Ti - 2 DVI,HDMI,VGA - D
Sound Card: External PreSonus Audiobox
Video Capture: PanaDeckTHEN onto 1394; CF Card Reader
CD Burner: see below
DVD Burner: 12x BLU-RAY RE-WRITER DRIVE, 16x DVD ±R/±RW
Camera: Canon: XF300 (HD)
Add. Comments: Graphics Card Driver Install History:- 14 Mar 2013 - 314.22 14 Dec 2012 - 310.70 03 Dec 2012 - 9

It also had an SD camera that I no longer use. It would appear that SCS's DB is on the blink.

OS: Win7 64bit

Oh yeah, here's a SCREEN GRAB of my System Specs so I can SHOW you what both you and I can't see from THIS side of the fence. Until you check this out you'd not KNOW if you had had your SSpecs available to everybody.




Grazie

@Gary,

My OS is Windows 7/64 bit Home Premium Service Pack 1 (with ALL updates from MS)

Bob

WWAAG, what version of Windows are you running.

Same as Bob. Win 7/64 Home Premium with SP1.

wwaag

Hmmm ... ok, nothing spooky about this. If the problem was with Win 8 I'd be less surprised.

my .NET folders are exactly the same as wwaag, still no extensions show up

@grazie - oige works fine in 13, but no matter what i've tried, and where i've tried it i can't get event lenght to open.

i am so annoyed, i can't begin to describe what a pita it is after using it for so many years - here it is sitting very comfortably in 12:

@ushere

i put mine in the exact same place... ;)

@malowz -and by golly, is it noticeable when it's gone!!!!

@Kit >> Nice list. The same could be said of acid

Even though SCS will not admit to it, Acid is dead and no longer being maintained. The fact that it is still being sold is tantamount to fraud.

Dvda is the same. Sony software is faking it.

it's not showing up in 13!?

If you have problems with this extension.
Right click the show event length DLL and there is probably and "unblock" button in the file properties. Click that and you should be golden.

That fixed the problem for me. YMMV.

It seem .NET 4, which Vegas 13 uses, is looking at and honoring the Blocked flag which internet downloaded files typically get.

as i wrote in other thread -

norman, you've made me a very happy old man!!!!!!

yeap, works now. thanks norman ;)

Solved! Thanks Norman.

I achieved success with the same for the DOWNLOADED Open In Graphics Editor, which I pointed to a WEBSITE that mentioned that needing that UNBLOCK option.

Yup, needed to trace down the DLL to this PATH:

C:\Users\USER\AppData\Roaming\Sony\Vegas Pro\Application Extensions

That did it.

Grazie

@Ushere....How on earth do you get it to dock like that? Mine always goes to full length of the preview window (top to bottom) as soon as I drag it there. I normally have it floating free at top right corner - close to the shut down 'X'.

in 12 and 13 i simply drag and drop. in 12 it did it automatically*, in 13 it's drag and drop while holding ctl.

*i'm so happy that they made docking the reverse of what it was. i hated it when i'd simply move a window around and it would keep docking of it's own accord.

Yes, mine docks...but in a full length version. Not like yours! :-(

Arthur,
The "Multiple rows of docked windows" was added in Version 12. If you are running a version before that you cannot dock like ushere's screen capture.

That feature also made the docking when windows were moved around a real pain - hence the need for a change in the functioning of the ctrl key.

Willem.