Vegas Pro 15 frame rate anomaly

[Ole Kristiansen]

Hi Pete !

What is the spec of you computer ?

[George Dean]

Pete, you have probably checked this, but are your project properties set to match your source media?

Best Regards……George

[Pete Tombs]

Yes they are. When I imported the media I accepted the “set project properties to match media” option.

And I rechecked that it was so afterwards.

[Pete Tombs]

Windows 7 64 bit
Intel Xenon R CPU W3505 @2.35 ghz
12 gig Ram

[Pete Tombs]

and it’s one particular video stream that’s exhibiting this weird lag. The bit of video in the other video track responds fine. But that’s DNxHD. Maybe I should convert the other video to DNxHD too?

[George Dean]

Pete, is there anything weird in the source media specs? Does Mediainfo (text mode) reveal anything out of the ordinary? What kind of camera codec was used to record the ProRes?

Best Regards……George

[Pete Tombs]

all looks very standard to me. It was a scan from a 35mm print. 4k, downconverted to HD.

It plays fine in other players (like VLC) where I can move it forward frame by frame with no issues and it plays fine in Resolve etc. But I have a very complicated projec t in Veags that I’m loathe to recreate in Resolve so I’d really like to get it working in veags. I think this must be a Vegas problem. I’ve had no response as yet from their customer service helpline

General
Name: Wild_Pussycat_Restored.mov
Folder: E:
Type: MAGIX ProRes
Size: 37.56 GB (38,462,056,770 bytes)
Created: 16 August 2018, 12:23:42
Modified: 16 August 2018, 12:41:46
Accessed: 16 August 2018, 17:13:12
Attributes:

Streams
Video: 00:25:34.333, 24.000 fps progressive, 1920x1080x32, ProRes
Audio: 00:25:34.333, 48,000 Hz, Stereo, PCM

ACID information
ACID chunk: no
Stretch chunk: no
Stretch list: no
Stretch info2: no
Beat markers: no
Detected beats: no

Other metadata
Regions/markers: no
Command markers: no

Media manager
Media tags: no

Plug-In
Name: mxhevcplug.dll
Folder: C:\Program Files\VEGAS\VEGAS Pro 15.0\FileIO Plug-Ins\mxhevcplug
Format: MAGIX ProRes
Version: Version 1.0 (Build 8532)
Company: MAGIX Computer Products Intl. Co.

[Pete Tombs]

and here’s the mediainfo text:

General
Complete name : E:\Wild_Pussycat_Restored.mov
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 0000.00 (qt )
File size : 35.8 GiB
Duration : 25 min 34 s
Overall bit rate : 201 Mb/s
Encoded date : UTC 2018-08-16 11:23:42
Tagged date : UTC 2018-08-16 11:41:46
Writing library : Apple QuickTime

Video
ID : 1
Format : ProRes
Format version : Version 0
Format profile : 422 HQ
Codec ID : apch
Duration : 25 min 34 s
Bit rate mode : Constant
Bit rate : 198 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:2
Scan type : Progressive
Bits/(Pixel*Frame) : 3.982
Stream size : 35.4 GiB (99%)
Title : Core Media Video
Writing library : adv0
Encoded date : UTC 2018-08-16 11:23:42
Tagged date : UTC 2018-08-16 11:41:46
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio #1
ID : 3
Format : PCM
Format settings : Little / Signed
Codec ID : lpcm
Duration : 25 min 34 s
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 channel
Sampling rate : 48.0 kHz
Bit depth : 24 bits
Stream size : 211 MiB (1%)
Title : Core Media Audio
Encoded date : UTC 2018-08-16 11:23:42
Tagged date : UTC 2018-08-16 11:41:46

Audio #2
ID : 4
Format : PCM
Format settings : Little / Signed
Codec ID : lpcm
Duration : 25 min 34 s
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 channel
Sampling rate : 48.0 kHz
Bit depth : 24 bits
Stream size : 211 MiB (1%)
Title : Core Media Audio
Encoded date : UTC 2018-08-16 11:23:42
Tagged date : UTC 2018-08-16 11:41:46

Other
ID : 2
Type : Time code
Format : QuickTime TC
Duration : 25 min 34 s
Time code of first frame : 01:00:00:00
Time code, striped : Yes
Title : Core Media Time Code / master
Encoded date : UTC 2018-08-16 11:23:42
Tagged date : UTC 2018-08-16 11:41:46

[Pete Tombs]

I suspect it might be the mxhevcplug.dll plug in.

I believe there are ways of bypassing it, but I’m sure that adds other complexities to the process.

P

[George Dean]

Hi Pete,

I agree, nothing jumps out of the Mediainfo to imply there is something unusual about the source. And, the fact that it is fine in Resolve, I would tend to think it is Vegas having a problem.

Have you tried to start a fresh project in Vegas and add only this clip to see how it reacts? There may also be something in the cached application data that is confusing Vegas. Maybe a Full Reset would help. Keeping in mind a reset and deleting the cached application data will return Vegas to it’s original installation configuration.

It’s seem pretty weird, wish there was something I could put my finger on.

Best Regards……George