Recording time doesn't work in MEP2021 Plus

MovieEditorr wrote on 4/3/2025, 9:47 AM

Im using MAGIX Movie Edit Pro 2021 Plus Steam Edition (Version 20.0.1.80).

I tried add "Rec. date & time" timecode template to my video. The time displays only in first frame:



I think there is some kind of bug?

Comments

AAProds wrote on 4/3/2025, 10:19 AM

@MovieEditorr

My understanding is the "Recording Date and Time" is only for DV-AVI, where the actual date+time is inserted into the tape as it is being recorded (a characteristic of the DV format). At any point in the recording, you can use that title template to extract the actual date+time, not the start date+time. That timecode isn't inserted into MP4-type video so it's probably just displaying the time when the file was created.

Last changed by AAProds on 4/3/2025, 10:21 AM, 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

Bluray Burner: Pioneer BDR-212D

Various other SSD and HDDs.

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

MEP 2021 version 20.0.1.80

Movie Studio 2025

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

johnebaker wrote on 4/3/2025, 12:01 PM

@MovieEditorr, @AAProds

Hi

From the testing I have done with a video clip that has a time code channel, in MMS 2025 I do not have 2021 installed, the time code types work as follows:

Date: the current date.

Movie time and Movie time transparent: the timeline cursor position in the Movie Studio project window, this is dynamic.

Date + Movie time: - current date + the timeline cursor position - dynamic

Recording date: The date the video was recorded, is a static value only available if the video has a Time-code channel - see note below

Recording time: the time the video was recorded, unable to determine is a static or dynamic value, only available if the video has a Time-code channel - see note below, - see note below

Recording date/time: The date and time when the footage was recorded, unable to determine is a static or dynamic value, only available if the video has a Time-code channel - see note below.

Note these time codes, displayed the appropriate information for a few seconds, then crashed MMS 2025 repeatedly.

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

MovieEditorr wrote on 4/3/2025, 12:24 PM

My suggestion for MAGIX: If the file is not in DV-AVI format, MAGIX could calculate the time from the creation time in the file metadata, which usually starts from the time the recording started (in this case it started 2025:04:03 17:35:57).

[QuickTime]     Create Date                     : 2025:04:03 17:35:57
[Track1]        Track Create Date               : 2025:04:03 17:35:57

Or make manually possibly set time.

johnebaker wrote on 4/3/2025, 2:50 PM

@MovieEditorr

Hi

. . . . If the file is not in DV-AVI format . . . .

I did not make it clear in my post above, this applies to any video file format that supports a time code channel.

The file I tested with was a MOV, FullHD 1920x1080 px, JPEG encoded video clip with embedded Time code channel.

. . . . MAGIX could calculate the time from the creation time in the file metadata, . . . .

The problem with this is a copying process from camera to computer or folder to folder 'issue':

Copying a file from camera to PC or to another folder etc, when the destination file is opened the Date/time created is set and, as the file contents have not be modified during the transfer the Modified date/time metadata copied to the new file, this results in 'out of sync' metadata, eg:

In theory, the 'creation time' can be calculated from the Date/time modified and the video length metadata if it is present, however if the video is modified through processing before editing, eg the video equivalent of processing a RAW image to a real colour space for the editor, then the Date modified can also get changed.

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.