How to find out (edited) clip length

Comments

Red Prince wrote on 2/18/2017, 2:29 PM

2000 was the first year of this century, 2001 the second.

That would be logical, alas 2000 was the last year of the 20th Century, 2001 was the first year of the 21st Century. This is because there was no year 0, so the 1st Century started with the year 1 and ended with the year 100, the Second Century started at 100 and ended 200, etc (and the 1st century BCE started with the year 100 BCE and ended with the year 1 BCE).

As for the time code, it makes perfect sense it starts at 00:00:00:00 because it tells how much time has already passed since the beginning of the video/audio/clip. Just as it would make sense for a century to start at xx00, except the ancient European astronomers (or astrologers, actually) had no concept of zero until sometime in the Middle Ages (while the rest of the world had that concept long before, the Greeks insisted that nothing could not be something), so they started each century at xx01 and we continue to do so to stay backwards compatible.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Former user wrote on 2/18/2017, 3:04 PM

2001 was the first year of the 21st century. 2000 was the end of the 20th Century. Timecode starts at zero, if you don't understand why then realize that the timecode of 1:00:00 is the first frame of the 1minute timecode. 1 hour starts at 1:00:00:00. 00:00:00 is the first frame of timecode starting at 0.

If you really want to be confused, learn about drop-frame vs. non-drop frame timecode.

3POINT wrote on 2/18/2017, 3:12 PM

The main reason I am still using SVP13 is the "ShowEvenfLength" extension that someone developed a while ago; I wish that same someone would make it available for VP14 or somebody else would make a new one. It provides a dock able window that show the event length of an event the cursor is sitting on and is continuously updated when one changes the event length.


Where can I find/download that script?

Last changed by 3POINT on 2/18/2017, 3:13 PM, changed a total of 1 times.

3POINT, Theo Houben, Vegasuser since version 5 and co-founder and moderator of the Dutch Vegasforum https://www.vegas-videoforum.nl/index.php

Recware: DJI Osmo Pocket/Mavic Mini, GoproHero7Black, PanasonicFZ300/HCX909.

Software: Vegaspro365+Vegasaur, PowerDirector365, Davinci Resolve 20

Hardware: i910900k, 32GB, GTX2080super, 2x1920x1200 display

Playware: Samsung Qled QE65Q6FN

Marco. wrote on 2/18/2017, 3:18 PM

"2001 was the first year of the 21st century."

You are right, of course. This was a bad example of mine.

"So why is than that the extensions are showing it differently?"

They don't. In the screenshot you're showing further above both extensions show a length of 4:04. What differs it the timecode value of the Event and this is because it is not a length, but the number of that frame while first frame had frame number 0.

Red Prince wrote on 2/18/2017, 3:28 PM

"2001 was the first year of the 21st century."

You are right, of course. This was a bad example of mine.

A good example would be one’s age. Someone born in 2000 turned one in 2001.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Peter_P wrote on 2/19/2017, 4:19 AM

You can find the Show Event Length for Vp14 now here.

bitman wrote on 2/19/2017, 7:21 AM

You can find the Show Event Length for Vp14 now here.

Thanks a lot for this great tool, works fine. Just one remark I had to place it on another location than you have indicated in your pdf on my windows 10.

I had to place it in: C:\Users\<your username>\AppData\Local\VEGAS Pro\Application Extensions

you may want to unhide AppData folder (if not already done).

Also reboot your pc  and/or close/start up vegas a couple of times if it does not appear in your extension selection (I suppose it depends how much and/or what of Vegas is currently cashed in your pc's memory).

 

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

Peter_P wrote on 2/19/2017, 7:35 AM

Sorry, um fortunately I also left the wrong path in the *.pdf for Show Event Lenght.

It should be : C:\ProgramData\VEGAS Pro\Application Extensions\

But it may also work on other locations.

OldSmoke wrote on 2/19/2017, 10:37 AM

"2001 was the first year of the 21st century."

You are right, of course. This was a bad example of mine.

A good example would be one’s age. Someone born in 2000 turned one in 2001.

I don't think there is any good example. You not only age by years but also by seconds and even smaller units. As such, to call the first frame of a one second event 0 is where I am not in agreement, I do accept it however. The conclusion would then be that timecode differs from event length by one frame?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Marco. wrote on 2/19/2017, 10:45 AM

Length is counting the frames. Timecode is labelling the frames.

Marco. wrote on 2/19/2017, 11:19 AM

Or according to the screenshot shown below - the length of the three timeline events are 3:00 each. Now look at the timecode label.

OldSmoke wrote on 2/19/2017, 11:34 AM

Timecode is labelling the frames.

I think my confusion came from the fact that when I set Vegas to show "timecode" on the clip in the picture, I didn't zoom in sufficiently and assumed the label shown at the end is the end of the clip, but it isn't. The label at the end is at the beginning of the last frame hence the difference to what the extension shows. 

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Steve wrote on 2/20/2017, 8:26 AM

There are no clips on the timeline. Everything on the timeline is an event.

OldSmoke wrote on 2/20/2017, 8:41 AM

There are no clips on the timeline. Everything on the timeline is an event.

Wow! Aren't you smart!

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

NickHope wrote on 2/25/2017, 3:42 AM

also, if it is something you need to monitor , you can open VIEW> EDIT DETAILS and select EVENTS. Set your columns to see IN OUT and DURATION. This screen updates the events as you edit. It is bit busy, but keeps all of that information available instantly.

And you can show the length column. Before the ShowEventLength extension was created, I used to have this above my timeline:

It would be handy, when while shortening an event, that you have an option to show the new event length above the cursor instead of showing now the time that the event is shortened.

I'd like to see both. The event length reading could be shown above the middle of the event, or even on the event itself, like this:

This type of functionality has been asked for so many times over the years and it's probably not difficult to introduce.