When we filled out the questionnaire a while back I suggested to SCS that they look at some of the scripts (like show event length and lock and unlock track) and use them as a basis for some new features. My constant refrain is "usability". Instead of that it looks like they have inadvertently stopped some of the scripts from functioning

maybe something to do with .net4?

i really don't know, but this is a real deal breaker for me - i might just ask for a refund.

i mean really, people have been asking for this for YEARS, it's not rocket science, it's a very basic necessity in editing knowing how long an 'event' is, and showing how much i extend or contract it, though useful, still isn't any alternative to giving me the actual event lenght!

come scs, DO NOT screw up what others have done for us UNLESS you can replace it!!!!...

I know Vegasaur had to be updated to work with Vegas 13, so it seems something must have changed for at least some types of extensions.

I assume the developer will have to update this extension so it can work in 13.

what shows up great is the watermark on the trial version,,,,they have that working perfectly :)
sorry...but another beta release...and another bunch of issues same old same old....but hey you can use your ipad!
sorry for you issues,, this release is a no upgrade here for sure

I am really surprised that so many of you jump in so early. You're very brave! This coward is waiting until a day before the 31st May deadline at the very earliest.

Lack of support for the Show Event Length script would be a dealbreaker for me (as would Frameserver etc.). Maybe we can persuade Rosebud (and Satish) to update his scripts.

If any developers are reading and wondering what we're talking about, Show Event Length is discussed here. In the future I would love to see this functionality neatly implemented like this:

[IMG=http://dl.dropboxusercontent.com/u/21489814/would-like.jpg]

If any developers are reading and wondering what we're talking about,

It's not like it would take any amount of code to implement this.

They already have code in Vegas that paints tiny boxed numbers like Nik showed. The video prefs item for, "Show source frame numbers on event thumbnails as" writes stuff exactly like that.

So just a simple check box preference in the same place as "source source frame numbers", for a new "show event length". Then reuse the existing code for painting the boxed numbers, only it just needs to be centered in the event frame and not on the thumbnail.

look, this is really a necessity for me in any number of situations....

i'd be quite happy to pay for this script / extension alone!

i am so p*ssed off with scs and this pathetic release i'm seriously thinking that this will be my last upgrade EVER...

btw @ nck - i wouldn't have bothered if it wasn't for my well complained about 'render as' problem - which doesn't appear in 13. now, whatever was causing it doesn't seem to affect 13, so in that regard i can now at least render without first having to do a workaround. that alone was probably worth $150 in time saved by my forgetting to use the workaround ;-)

i will wait for a new build to fix this stuff... or else, will be the first time i stay with a older version.. EVER..... and i use Vegas since "the first" version...

few useful enhancements for me + new bugs = no go

Don't hold your breath that this will be fixed. There were 2 similar very annoying issues with V12, which were never fixed (see threads below) despite SCS acknowledging them, and promising a fix on the "next release". Having only recently got a reliable working version of V12, there's no way I'm jumping into V13 based on what I've seen and read so far. And that's really SCS's fault. Professional editors should be literally CHOMPING at the bit to use the new version. Instead we get 'editing on an ipad'. Yaaaaaaaay.

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=849313

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=865674

it's my thread so i can rant if i want to ;-P

i've spent the day working on a large, though not too complicated project...

it feels like i'm going backwards, honestly.

i have no idea who or how this release was assessed or beta tested, but i get the distinct feeling:

a. scs is a group of programmers who happen to be involved with an nle software project (as opposed to a paint program, animation program, etc.,). they certainly AREN'T editors.

b. scs believes in moving forward, a good thing if they'd take a moment or two to look back occasionally and repair what is obviously broken, and some of these bugs date back YEARS

c. scs DON'T listen to their core users. in fact they probably have to listen to marketing, but that shouldn't stop them repairing what's broken.

d. throwing gimmicks at pros is pointless, we don't need them, what we need is, as has been said countless times over a number of years; is a reliable, stable, robust nle.

e. whatever beta testing program is now in place is a failure if it doesn't catch NEW problems, such as breaking scripts, gopro, etc., let alone resolve old ones.

f. scs should sort out gpu once and for all. it's nothing more than a bad joke as it stands at present. no, it's not a bad joke, it's embarrassing especially when compared to the competition.

g. colour levels... need i say more?

it's such a great pity that what was once software head and shoulders above the competition, and punching even beyond that has been brought down to such a derisory level.

it's very unlikely i'll ever spend any money on vegas again, and i'll certainly not be recommending it either. edius, even given it's clunky interface, limited toolset, etc., at least has the backing of grass valley, a company that knows it's market and caters directly to it - no gimmicks, just solid, reliable, BORING software.

it's going to take a LOT to get me back on board the fanboi train....

Vegas Pro 13... Nothing to see here, ladies and gentlemen. Move along please.

I'm left wondering what is the point of VP13 other than to generate more revenue for SCS?

(I'm delighted for those of you who have found a reason to upgrade, and I'm reading your posts with interest... you may come up with a reason for me to upgrade. Who knows.)

Nice list. The same could be said of acid

For whatever reason, Show Event Length works on my system. Also Timeline Tools works. I have a suspicion that the problem involves the various Microsoft .Net's that are installed on one's system. Perhaps Gary James, the author of Timeline Tools could shed some light on the problem.

wwaag

wwaag, what .net frameworks you got installed on your system?

you can find in the "programs and features" on control panel

Check on your C Drive how many folders and what numbers are those labeled NetFrame:


Subject: RE: Vegas Crashing when I use othe applications
Reply by: videoITguy
Date: 4/17/2014 9:12:38 AM

Most importantly what OS and version are you running.

The VegasPro13 installation could sufficiently change your prior NetFrame structure for the base OS - that will need to be followed up on. How many root folders do you have on your C-Drive that are labeled NetFrame and what numbers are they?
Message last edited on 4/17/2014 9:14:34 AM, by videoITguy.

Most importantly what OS and version are you running.
Win 7 64 bit Home Premium with SP1.

Here is a screenshot of the dotnet installations on my system--lots. This is from the Windows folder.



I believe that the last, V4.0...., was installed by VP-13.

wwaag

Added. Here is a screenshot.

What I find really strange is that I recently installed Sony Movie Studio Platinum for someone and it now includes show video length built into the program. I expected it to be in Vegas 13 but saw at NAB that it was not. When I asked the Sony staff about it they did not seem to know about it being in Movie Studio.

"Also Timeline Tools works. I have a suspicion that the problem involves the various Microsoft .Net's that are installed on one's system. Perhaps Gary James, the author of Timeline Tools could shed some light on the problem"

I've been out of the loop on this entire SVP-13 discussion, since I have no immediate plans to upgrade. I've been told by some that SVP-13 intentionally was preventing compiled DLL Scripts, and Vegas Extensions not compiled to Microsoft's .Net 4.0 Framework from working. (SVP-13 was designed with .Net 4.0). But if I'm reading this correctly, you're saying that TLT and other Extensions are working in SVP-13?

Let me try to explain what the .Net Framework is. .Net - pronounced DOT NET is a comprehensive library of programming utility functions that software engineers can use to write programs. .Net was a revolutionary advancement in programming support code. And since it's inception, it has been updated with new and more advanced capabilities every few years. You can think of the huge numbers of support functions that .Net provides as a set of pins in an electrical connector. Collectively these are called the Application Programming Interface or more commonly, just API. .Net 2.0 had it's set of "pins". When Microsoft released .Net 3.0, what they did was add a new connector with an additional set of "pins" that included all the new .Net 3.0 features. The same was true for the 3.5 and 4.0 releases. Each of these releases added new connectors. The truly clever thing about this design is that any program that was written for an older version of .Net, will still plug into the .Net 2.0 connector of the newer, wider, multiple connector version of the later .Net API. And most programs will use features ("pins") from all the "connectors" available in the version of .Net used in their design.

Timeline Tools was written using .Net 2.0. I did this intentionally because that allows TLT to be used with any newer version of Vegas that is designed using a newer version of the .Net Framework. This prevented me from taking advantage of the newer and more advanced capabilities in the newer versions of .Net, but that was offset with the ability to support all versions of Vegas back to v8.0 when Extensions were introduced. Vegas would have to intentionally prevent older Scripts and Extensions from working with SVP-13, because there's nothing inherent in .Net itself that would prevent them from working.

So, can anyone else provide any feedback on SVP-13's ability to run older compiled Scripts and Extensions?

Gary ...

I tried the show event length extension talked about in this thread and it did not work for me in 13.
Vegasaur needed an update to work with Vegas 13.

Leslie,

This may be stating the obvious, but you did copy subject script from the Vegas 12 Scirpt Menu folder to Vegas 13, didn't you? "C:\Program Files\Sony\Vegas Pro 12.0\Script Menu"

For the past several upgrades, I've eliminated this problem by putting my custom scripts in "%username%\Documents\Vegas Script Menu" (it needs to be manually created.) By doing this, custom scripts will be available to all upgrades without having to go thru the copy process.

...Jerry

FYI, Timeline Tools installs into the C:\...\Documents\Vegas Script Menu folder for the reason you just cited.

- Gary - TimeLine tools:
TimeLIne tools does not show up anywhere, neither extension locations nor scripting. However, the icon shows up in the "Customize toolbar" option of VegasPro 13. When added to the toolbar, I get 3 different dialog msgs:

First: Unexpected Error Initializing Timeline Tools: step 1

Could not load file or assemble 'RicherTextBox, Version=1.0.3.0,
Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

Second: TimelineToolsModule::OnLoaded

Object reference not set to an instance of an object.

Third: TimelineToolsModule::OnClosing

Object reference not set to an instance of an object.

Hope this helps.
Bob