Timecode + Speed

big_guitar wrote on 8/8/2024, 1:03 PM

Hi,

Is there a way to use timecode where I increase the speed of parts of a video, and the timecode rate increases with it, or would I have to EXPORT a video with the timecode included, and then just import that in a separate project to adjust video speed of video portions so the stored timecode would coincide?

Comments

CubeAce wrote on 8/10/2024, 12:25 AM

@big_guitar

Hi.

Sorry for such a late reply but I still can't get my head around what you are trying to do or why.

The industry standard for timecode is known as SMPTE timecode (Society of Motion Picture and Television Engineers) and is typically represented in the format HH:MM:SS:FF (hours, minutes, seconds and frames) and the only form of timecode available to most video editing programs. I say most video editing programs as I have not tried all of them but of those I have tried none have ever used anything but SMPTE.

Video editing programs will only ever render files that consist of a constant frame rate so any video that has sped up sections will lose the additional frames of the slower (more frames per second used) by the use of predicted picture (P frames) and Bidirectional Predicted Picture (B frames) that will use other frame information and blend the results to produce new and most possibly fewer frames than the files in use within the program.

This is why video produced from game play, smart phone, screen capture programs and some webcams that use variable frame rate encoding is often impossible for a video editing program to successfully use or render.

So we really need to know what you are trying to do and achieve to help you further.

Ray.

Last changed by CubeAce on 8/10/2024, 12:29 AM, changed a total of 2 times.

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5011

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2130 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 21TB of 8 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 560.81 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

AAProds wrote on 8/10/2024, 1:39 AM

@big_guitar

I don't think so. While you can split the timecode object and apply the speed control to it, if you split it (so you can go back to normal speed, the rest of the timecode is in the wrong position.

You also can't use the object-stretch mouse mode effectively either: the timecode stops running before it gets to the end of the object.

Instead of exporting with the timecode embedded (which would be the "easiest" way for later speeding up or slowing down; you wouldn't have to worry about desynching your video and timecode as you set up the speed change), I'd be inclined to just make up a timecode file, then overlay that onto your video and group it. Then you can speed up the desired sections, simultaneously speeding up your timecode track.

That would save doing a re-encode on the actual video.

 

All my forum comments are based on or refer to my System 1.

My struggle is over! I built my (now) system 2 in 2011 when DV was king and MPEG 2 was just coming onto the scene and I needed a more powerful system to cope. Since then we've advanced to MP4 and to bigger and bigger resolutions. I was really suffering, not so much in editing (with proxies) but in encoding, which just took ages. A video, with Neat Video noise reduction applied, would encode at 12% of film speed. My new system 1 does the same job at 160% of film speed. Marvellous. I'm keeping my old system as a capture station for analogue video tapes and DV.

System 1

Windows 11 v23H2 severely modified by Openshell and ExplorerPatcher

Power supply: 850W Cooler Master (should have got modular)

CPU: Intel i7 13700K running at 3400mhz, cooled by a Kraken 2x140mm All In One liquid cooler.

RAM: 64gb (2x32gb sticks) G.Skill "Ripjaws" DDR4 3200Mhz

GPU 1: iGPU UHD 770

GPU 2: NVidia RTX 3060Ti Windforce 8gb

C drive: NVME 500gb

Various other SSD and HDDs.

Monitor: 27"/68cm Samsung, 2560 x 1440, 43 pixels/cm.

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

Magix Video Easy version 7.0.1.145

System 2

(Still in use for TV and videotape capture)

Windows 10 v22H2

CPU: i5-750 at 2670mhz with 12gb RAM

Onboard IEEE1394 (Firewire) port

GPU: ATI Radeon HD 4770 (512mb) which is ignored by MEP

Hard drives: C Drive 256gb SSD, various other HDDs.

Monitor: Dell 22"/56cm, 1680x1050, 35 pixels/cm

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

VPX 12

big_guitar wrote on 8/10/2024, 4:35 AM

@big_guitar

I don't think so. While you can split the timecode object and apply the speed control to it, if you split it (so you can go back to normal speed, the rest of the timecode is in the wrong position.

You also can't use the object-stretch mouse mode effectively either: the timecode stops running before it gets to the end of the object.

Instead of exporting with the timecode embedded (which would be the "easiest" way for later speeding up or slowing down; you wouldn't have to worry about desynching your video and timecode as you set up the speed change), I'd be inclined to just make up a timecode file, then overlay that onto your video and group it. Then you can speed up the desired sections, simultaneously speeding up your timecode track.

That would save doing a re-encode on the actual video.

 

Thank you for that follow up. So, I did experiment with export with timecode and then import, and that would certainly work for my needs. I wasn't looking for true SMPTE here at this time, which I used with my 4-track tape recorder decades again, I was just needing an up counter to show how much time passed instead of making the video twice as long as it needs to be to get the information presented. I also found some ways to embed time passing info at the recording source.

I am curious about your statement to make a timecode file and then group, so by that you mean to establish a generic up counter video file, add that to the project, and group the 2 videos together, which I could use in future projects, is that correct? I think that could be an ideal means to be covered for this type of scenario, thank you for that suggestion. If I'm mistaken about what you meant, let me know, thanks again!

AAProds wrote on 8/10/2024, 4:50 AM

@big_guitar

I am curious about your statement to make a timecode file and then group,

All I meant there was to "group", in Magix parlance, the video object and the timecode object so when you start chopping them up/splitting them (when you speed up sections), the timecode track doesn't get "out of line" with the video track. You group by highlighting and clicking he objects with the CTRL key, then hitting the unbroken chain link icon. Then you can drag them all around/cut as necessary and they'll stay together.

All my forum comments are based on or refer to my System 1.

My struggle is over! I built my (now) system 2 in 2011 when DV was king and MPEG 2 was just coming onto the scene and I needed a more powerful system to cope. Since then we've advanced to MP4 and to bigger and bigger resolutions. I was really suffering, not so much in editing (with proxies) but in encoding, which just took ages. A video, with Neat Video noise reduction applied, would encode at 12% of film speed. My new system 1 does the same job at 160% of film speed. Marvellous. I'm keeping my old system as a capture station for analogue video tapes and DV.

System 1

Windows 11 v23H2 severely modified by Openshell and ExplorerPatcher

Power supply: 850W Cooler Master (should have got modular)

CPU: Intel i7 13700K running at 3400mhz, cooled by a Kraken 2x140mm All In One liquid cooler.

RAM: 64gb (2x32gb sticks) G.Skill "Ripjaws" DDR4 3200Mhz

GPU 1: iGPU UHD 770

GPU 2: NVidia RTX 3060Ti Windforce 8gb

C drive: NVME 500gb

Various other SSD and HDDs.

Monitor: 27"/68cm Samsung, 2560 x 1440, 43 pixels/cm.

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

Magix Video Easy version 7.0.1.145

System 2

(Still in use for TV and videotape capture)

Windows 10 v22H2

CPU: i5-750 at 2670mhz with 12gb RAM

Onboard IEEE1394 (Firewire) port

GPU: ATI Radeon HD 4770 (512mb) which is ignored by MEP

Hard drives: C Drive 256gb SSD, various other HDDs.

Monitor: Dell 22"/56cm, 1680x1050, 35 pixels/cm

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

VPX 12

big_guitar wrote on 8/10/2024, 5:13 AM

All I meant there was to "group"

ok that sounds more like I was hoping to do originally, I just wasn't sure how it would impact the timing values, I will experiment further thank you.

big_guitar wrote on 8/10/2024, 2:31 PM

@AAProds, So, just grouping the tracks and then cutting doesn't really work as desired... It totally screws up the time values.

For example, after grouping the video + time track, just cutting out one segment in the middle (without changing any lengths), the first segment ends around 33 seconds, then the next segment immediately jumps to displaying 50 seconds (instead of 33+ seconds), but the time remains constant for the entire 2nd segment (timecode remains frozen for about 30 seconds or so), and then the last section of split video jumps in time to a 1:41, but the last segment does continue the up count, where the 2nd remained constant, which seems odd, but the bottom line is that this doesn't seem to work in an ideal fashion.

AAProds wrote on 8/10/2024, 10:40 PM

@big_guitar

Yes, there is something crazy going on there; the audio traditionally doesn't like being speed-changed a lot and that appears to be what is what is messing this up. If you delete the audio tracks for the image video and the timecode video, you can change the speed as desired and the timecode will change as well (provided it is linked to the image video).

If you need audio, It looks like laying the timecode on the image video, exporting it and then editing the exported video will be the way to go.

Last changed by AAProds on 8/10/2024, 10:45 PM, changed a total of 1 times.

All my forum comments are based on or refer to my System 1.

My struggle is over! I built my (now) system 2 in 2011 when DV was king and MPEG 2 was just coming onto the scene and I needed a more powerful system to cope. Since then we've advanced to MP4 and to bigger and bigger resolutions. I was really suffering, not so much in editing (with proxies) but in encoding, which just took ages. A video, with Neat Video noise reduction applied, would encode at 12% of film speed. My new system 1 does the same job at 160% of film speed. Marvellous. I'm keeping my old system as a capture station for analogue video tapes and DV.

System 1

Windows 11 v23H2 severely modified by Openshell and ExplorerPatcher

Power supply: 850W Cooler Master (should have got modular)

CPU: Intel i7 13700K running at 3400mhz, cooled by a Kraken 2x140mm All In One liquid cooler.

RAM: 64gb (2x32gb sticks) G.Skill "Ripjaws" DDR4 3200Mhz

GPU 1: iGPU UHD 770

GPU 2: NVidia RTX 3060Ti Windforce 8gb

C drive: NVME 500gb

Various other SSD and HDDs.

Monitor: 27"/68cm Samsung, 2560 x 1440, 43 pixels/cm.

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

Magix Video Easy version 7.0.1.145

System 2

(Still in use for TV and videotape capture)

Windows 10 v22H2

CPU: i5-750 at 2670mhz with 12gb RAM

Onboard IEEE1394 (Firewire) port

GPU: ATI Radeon HD 4770 (512mb) which is ignored by MEP

Hard drives: C Drive 256gb SSD, various other HDDs.

Monitor: Dell 22"/56cm, 1680x1050, 35 pixels/cm

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

VPX 12

AAProds wrote on 8/10/2024, 11:49 PM

@big_guitar

Here's a waffle-on about what you're after, I think.

All my forum comments are based on or refer to my System 1.

My struggle is over! I built my (now) system 2 in 2011 when DV was king and MPEG 2 was just coming onto the scene and I needed a more powerful system to cope. Since then we've advanced to MP4 and to bigger and bigger resolutions. I was really suffering, not so much in editing (with proxies) but in encoding, which just took ages. A video, with Neat Video noise reduction applied, would encode at 12% of film speed. My new system 1 does the same job at 160% of film speed. Marvellous. I'm keeping my old system as a capture station for analogue video tapes and DV.

System 1

Windows 11 v23H2 severely modified by Openshell and ExplorerPatcher

Power supply: 850W Cooler Master (should have got modular)

CPU: Intel i7 13700K running at 3400mhz, cooled by a Kraken 2x140mm All In One liquid cooler.

RAM: 64gb (2x32gb sticks) G.Skill "Ripjaws" DDR4 3200Mhz

GPU 1: iGPU UHD 770

GPU 2: NVidia RTX 3060Ti Windforce 8gb

C drive: NVME 500gb

Various other SSD and HDDs.

Monitor: 27"/68cm Samsung, 2560 x 1440, 43 pixels/cm.

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

Magix Video Easy version 7.0.1.145

System 2

(Still in use for TV and videotape capture)

Windows 10 v22H2

CPU: i5-750 at 2670mhz with 12gb RAM

Onboard IEEE1394 (Firewire) port

GPU: ATI Radeon HD 4770 (512mb) which is ignored by MEP

Hard drives: C Drive 256gb SSD, various other HDDs.

Monitor: Dell 22"/56cm, 1680x1050, 35 pixels/cm

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

VPX 12

big_guitar wrote on 8/11/2024, 6:03 AM

@AAProds,

Thanks for making the demo. At one point in testing, I did add a black jpg file in between (which I saw mentioned in another forum post), and added black chroma key to the time code track, and made the black semi transparent, lined that up to frame the code text, and did the export/import.

It's interesting about the audio track impact. That's something I can test with further. I did notice speeding a part 4x (max increase via slider) cut out the ability to hear audio altogether, although it only warns about that if you manually type a value in over 4. But I don't think it deleted the audio track at 4x, you just can't hear it at all. I did not have video/audio separation set at the time, I will go back and check that out.

In this specific case, I re-recorded the source video using OBS with a script (or perhaps local html, I tried multiple means) which provided the semi transparent overlay with the timer, as I found that was a little easier and quicker to manipulate, plus I changed the video slightly. But if I am unable to record the source in this manner, I think I now have multiple options, thanks again!

AAProds wrote on 8/11/2024, 6:49 AM

@big_guitar my pleasure.

All my forum comments are based on or refer to my System 1.

My struggle is over! I built my (now) system 2 in 2011 when DV was king and MPEG 2 was just coming onto the scene and I needed a more powerful system to cope. Since then we've advanced to MP4 and to bigger and bigger resolutions. I was really suffering, not so much in editing (with proxies) but in encoding, which just took ages. A video, with Neat Video noise reduction applied, would encode at 12% of film speed. My new system 1 does the same job at 160% of film speed. Marvellous. I'm keeping my old system as a capture station for analogue video tapes and DV.

System 1

Windows 11 v23H2 severely modified by Openshell and ExplorerPatcher

Power supply: 850W Cooler Master (should have got modular)

CPU: Intel i7 13700K running at 3400mhz, cooled by a Kraken 2x140mm All In One liquid cooler.

RAM: 64gb (2x32gb sticks) G.Skill "Ripjaws" DDR4 3200Mhz

GPU 1: iGPU UHD 770

GPU 2: NVidia RTX 3060Ti Windforce 8gb

C drive: NVME 500gb

Various other SSD and HDDs.

Monitor: 27"/68cm Samsung, 2560 x 1440, 43 pixels/cm.

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

Magix Video Easy version 7.0.1.145

System 2

(Still in use for TV and videotape capture)

Windows 10 v22H2

CPU: i5-750 at 2670mhz with 12gb RAM

Onboard IEEE1394 (Firewire) port

GPU: ATI Radeon HD 4770 (512mb) which is ignored by MEP

Hard drives: C Drive 256gb SSD, various other HDDs.

Monitor: Dell 22"/56cm, 1680x1050, 35 pixels/cm

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

VPX 12