VP20 cannot open "Vimeo Record" downloaded videos

RedRob-CandlelightProdctns wrote on 1/29/2023, 8:50 PM

I've recorded a few screen recordings using Vimeo Record. Downloaded the original videos to my desktop and tried dragging to Vegas -- Vegas crashes. Tried enabling legacy AVC in file I/O, and then it won't even accept the drop on the timeline.

I realize I can re-encode, or tell Vimeo to download a different format.. but thought I should mention it here to see if it's an obvious bug or just unsupported CODEC?

Here's the dump from MediaInfo:

General
Complete name                            : I:\2023-LifeSights-Pitch\media\sample_--_scrolling_videos (Original).mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : iso5 (iso5/iso6/mp41)
File size                                : 1.57 MiB
Duration                                 : 29 s 384 ms
Overall bit rate                         : 447 kb/s
Writing application                      : Lavf59.27.100

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Baseline@L3.2
Format settings                          : 1 Ref Frames
Format settings, CABAC                   : No
Format settings, Reference frames        : 1 frame
Format settings, GOP                     : M=1, N=100
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 29 s 384 ms
Bit rate                                 : 445 kb/s
Width                                    : 604 pixels
Height                                   : 808 pixels
Display aspect ratio                     : 0.748
Frame rate mode                          : Variable
Frame rate                               : 15.076 FPS
Minimum frame rate                       : 0.978 FPS
Maximum frame rate                       : 1 000.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.061
Stream size                              : 1.56 MiB (100%)
Codec configuration box                  : avcC

Vegas 21.300

My PC (for finishing):

Cyperpower PC Intel Core i7-7700K CPU @ 4.2GHz, 64GB mem @ 2133MHz RAM, AMD Radeon RX470 (4GB dedicated) with driver recommended by Vegas Updater (reports as 30.0.15021.11005 dated 4/28/22), and Intel HD Graphics 630 driver version 31.0.101.2112 dated 7/21/22 w/16GB shared memory. Windows 10 Pro 64bit version 10.0.19045 Build 19045.

My main editing laptop:

Dell G15 Special Edition 5521, Bios 1.12 9/13/22, Windows 11 22H2 (10.0.22621)

12th Gen Intel Core i7-12700H (14 cores, 20 logical processors), 32 GB DDR5 4800MHz RAM, Intel Iris Xe Graphics, NVIDIA GeForce RTX 3070 Ti Laptop GPU w/8GB GDDR6 RAM, Realtek Audio

 

 

Comments

john_dennis wrote on 1/29/2023, 9:02 PM

@RedRob-CandlelightProdctns

Just about everything about the video looks like crap to me.

Bit rate                                 : 445 kb/s
Width                                    : 604 pixels
Height                                   : 808 pixels
Display aspect ratio                     : 0.748
Frame rate mode                          : Variable
Frame rate                               : 15.076 FPS
Minimum frame rate                       : 0.978 FPS
Maximum frame rate                       : 1 000.000 FPS

Even Shutter Encoder didn't like it.

VideoReDo Quick Stream Fix didn't like it, either.

RedRob-CandlelightProdctns wrote on 1/29/2023, 9:53 PM

@john_dennis I hear what you're saying -- on paper it doesn't look so good. But did you open it in Windows Media Player or VLC? Plays and looks fine in both of those.

Last changed by RedRob-CandlelightProdctns on 1/29/2023, 9:53 PM, changed a total of 1 times.

Vegas 21.300

My PC (for finishing):

Cyperpower PC Intel Core i7-7700K CPU @ 4.2GHz, 64GB mem @ 2133MHz RAM, AMD Radeon RX470 (4GB dedicated) with driver recommended by Vegas Updater (reports as 30.0.15021.11005 dated 4/28/22), and Intel HD Graphics 630 driver version 31.0.101.2112 dated 7/21/22 w/16GB shared memory. Windows 10 Pro 64bit version 10.0.19045 Build 19045.

My main editing laptop:

Dell G15 Special Edition 5521, Bios 1.12 9/13/22, Windows 11 22H2 (10.0.22621)

12th Gen Intel Core i7-12700H (14 cores, 20 logical processors), 32 GB DDR5 4800MHz RAM, Intel Iris Xe Graphics, NVIDIA GeForce RTX 3070 Ti Laptop GPU w/8GB GDDR6 RAM, Realtek Audio

 

 

john_dennis wrote on 1/29/2023, 10:23 PM

A plastic spoon will get ice cream into your mouth, but they're rarely used at State Dinners.

Former user wrote on 1/29/2023, 10:34 PM

@RedRob-CandlelightProdctns I checked Capcut, ClipChimp. Premiere and Resolve, they all load and play the video, so it mustn't be as unique/unusual as first seems. Windows video editor loads the video into it's media bin, but it can't play it

RogerS wrote on 1/29/2023, 10:48 PM

I'd find a different way to get higher-quality files that also work in Vegas if that's your preferred editor.

Howard-Vigorita wrote on 1/29/2023, 11:09 PM

Tried to run the so4 analyzer on that clip and it crashed With this error message:

File appears to not have a default sample duration

Not sure what that means but my guess is that there is a wrapper error made by an ffmpeg beta version. Maybe it put the duration in the metadata but forgot to write it into the header. Anyway, I created a new wrapper with the most recent official release of version 4.4.1 from gyan and now it's fine. Ffmpeg command I used is this:

ffmpeg -i original.mp4 -c:v copy -an sample2.mp4

The mediainfo is exactly like the original except for the ffmpeg version number that I used:

General
Complete name                            : C:\Users\hv\Downloads\sample2.mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/iso2/avc1/mp41)
File size                                : 1.57 MiB
Duration                                 : 29 s 384 ms
Overall bit rate                         : 447 kb/s
Writing application                      : Lavf58.76.100

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Baseline@L3.2
Format settings                          : 1 Ref Frames
Format settings, CABAC                   : No
Format settings, Reference frames        : 1 frame
Format settings, GOP                     : M=1, N=100
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 29 s 384 ms
Bit rate                                 : 445 kb/s
Width                                    : 604 pixels
Height                                   : 808 pixels
Display aspect ratio                     : 0.748
Frame rate mode                          : Variable
Frame rate                               : 15.077 FPS
Minimum frame rate                       : 0.978 FPS
Maximum frame rate                       : 90 000.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.061
Stream size                              : 1.56 MiB (100%)
Codec configuration box                  : avcC

If the Vimeo app that created this runs ffmpeg installed locally on your computer, just update ffmpeg with an official release version. If the Vimeo app embeds ffmpeg libs, try and get them to update it similarly. The problem may be that they used an early v5.1 which was known to be a little flaky.

RedRob-CandlelightProdctns wrote on 1/30/2023, 1:19 AM

@Howard-Vigorita Vimeo Record is a Web-based screen-capture/recording tool from Vimeo. I'm not sure how it works under the covers, but it upload the recorded video to Vimeo where we then have the option to "download original" or any variety of transcoded videos (including 720p). The 720p download worked fine in Vegas so I went with that... don't know why their "original file" version is as you say it is -- perhaps they indeed are using ffmpeg behind-the-scenes to generate the original?

Having worked with Vimeo support in the past, I think it'll be unlikely to get them to fix/change their encoding any time soon! Since the file does appear to work in several other NLEs and players, it does make me question if it's a Vegas issue or theirs though.

I have a suitable workaround for now (using the 720p download instead of original).. thanks for your efforts!

Vegas 21.300

My PC (for finishing):

Cyperpower PC Intel Core i7-7700K CPU @ 4.2GHz, 64GB mem @ 2133MHz RAM, AMD Radeon RX470 (4GB dedicated) with driver recommended by Vegas Updater (reports as 30.0.15021.11005 dated 4/28/22), and Intel HD Graphics 630 driver version 31.0.101.2112 dated 7/21/22 w/16GB shared memory. Windows 10 Pro 64bit version 10.0.19045 Build 19045.

My main editing laptop:

Dell G15 Special Edition 5521, Bios 1.12 9/13/22, Windows 11 22H2 (10.0.22621)

12th Gen Intel Core i7-12700H (14 cores, 20 logical processors), 32 GB DDR5 4800MHz RAM, Intel Iris Xe Graphics, NVIDIA GeForce RTX 3070 Ti Laptop GPU w/8GB GDDR6 RAM, Realtek Audio

 

 

Howard-Vigorita wrote on 1/30/2023, 3:56 AM

You could just rewrap any other the broken recordings like that. Ffmpeg is free and the rewrap stream-copy is as quick as it gets. I'm just surprised that Vimeo let a damaged clip go out. Wonder if it's just a one-time thing, maybe a corruption in the download or a power surge on their end.

Former user wrote on 1/30/2023, 6:22 AM

I'm just surprised that Vimeo let a damaged clip go out. Wonder if it's just a one-time thing, maybe a corruption in the download or a power surge on their end.

@Howard-Vigorita I think it's dash format, which Vegas cant' read. It does look stranger then the usual Vimeo Dash file, must be to do with the screen recorder app. Normally Vimeo files show the X264 encoding information when read with mediainfo.

Bottom line is, that even as a strange mpeg-dash file, the other NLE's read and play it fine. My searching skills not so good when looking for dates when implemented, I only find that Handbrake became compatible in 2017 and Adobe Premiere could edit Dash the same year, implementation unknown

This is a standard dash file if you want to compare https://www.dropbox.com/s/0v3h1nzwrkkbh7e/Sometimes%20I%20Wonder%20-%20Short%20Film-535511325.fdash-fastly_skyfire_sep-video-19d12ee4.mp4?dl=0

Does not play in my Vegas.

 

RedRob-CandlelightProdctns wrote on 1/30/2023, 10:37 AM

You could just rewrap any other the broken recordings like that. Ffmpeg is free and the rewrap stream-copy is as quick as it gets. I'm just surprised that Vimeo let a damaged clip go out. Wonder if it's just a one-time thing, maybe a corruption in the download or a power surge on their end.

Not a download corruption. 3 different (small) files all have same result. And it plays/opens in other tools.

Vegas 21.300

My PC (for finishing):

Cyperpower PC Intel Core i7-7700K CPU @ 4.2GHz, 64GB mem @ 2133MHz RAM, AMD Radeon RX470 (4GB dedicated) with driver recommended by Vegas Updater (reports as 30.0.15021.11005 dated 4/28/22), and Intel HD Graphics 630 driver version 31.0.101.2112 dated 7/21/22 w/16GB shared memory. Windows 10 Pro 64bit version 10.0.19045 Build 19045.

My main editing laptop:

Dell G15 Special Edition 5521, Bios 1.12 9/13/22, Windows 11 22H2 (10.0.22621)

12th Gen Intel Core i7-12700H (14 cores, 20 logical processors), 32 GB DDR5 4800MHz RAM, Intel Iris Xe Graphics, NVIDIA GeForce RTX 3070 Ti Laptop GPU w/8GB GDDR6 RAM, Realtek Audio

 

 

Howard-Vigorita wrote on 1/30/2023, 4:21 PM

@Former user Thanks. Never heard of MPEG-DASH before but apparently they're supposed to have an MPD file extension in which case Vegas would ignore them. It seems that the fix I discovered is 4 year-old news:

https://video.stackexchange.com/questions/24435/how-to-download-and-encode-a-video-from-a-mpd-manifest

I think at a minimum, Vegas should not crash when these things are renamed mp4 instead of re-wrapped. The file you linked generated the same analyzer error, crashed Vegas, and re-wrapping fixed it too so Vegas could read and play it. The maximum gop size for your clip turned out to be 73 and is not vfr, so shouldn't be too much of a Vegas edit problem. Not as bad as the Vimeo one which is vfr with a gop of 100 which cannot be made totally edit-friendly without a transcode.