Proper stream could not be found in the media file

David-R wrote on 4/7/2022, 1:33 AM

Pro 18 Build 527


" Warning:  Error occurred while loading the project file...
The proper stream could not be found in the media file."


When I open "Details" it lists some files as...

"...has changed enough that the media stream properties from the project file could not be applied. Default media stream properties were used."


The project loads, but now about of half of the MP4 clips (out of dozens) wont play video.  This project loaded fine many times in the past.  All the MP4 clips were created from the same app.  Now, some play video, and some dont.  The audio portion of all clips still play.  The problem clips also play fine in other apps, so they are not corrupt. 

Comments

Dexcon wrote on 4/7/2022, 1:43 AM

A search of the forum for that warning came up with the following post which seems similar:

https://www.vegascreativesoftware.info/us/forum/sony-mts-file-loads-in-vegas-17-as-video-but-in-vegas-18-as-audio--124104/

Have a look at the last 2 comments, the second last being tagged as the soklution.

So try resetting your Vegas Pro 18 back to its factory settings, the way to do this is decribed here:

https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

... but do make sure that the cache is chosen to be cleared.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

David-R wrote on 4/13/2022, 4:11 AM

Thanks for reply! But those suggestions wont work for me.

Yeah, I had seen and tried resetting Vegas by starting it with CTRL+SHIFT depressed, but Vegas wont start when I do that (?).

And the suggested folder to delete in "Users" does not exist on my computer(?).

Dexcon wrote on 4/13/2022, 6:44 AM

And the folder to delete in "Users" does not exist on my computer(?)

@David-R ... make sure in Windows Explorer that Hidden Files is checked under the View menu. If it is already checked and 'C:\Users\USERNAME\AppData\Local\VEGAS Pro\18.0' does not exist, that will be most unusual.

Other than that, use the forum's search function with the warning message that you get, but not very much results from that search as I found.

Also, perhaps upload a detailed MediaInfo report (a free app) of one of the media that is not displaying video in Vegas Pro 18. More information about MediaInfo here: https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/ Others on the forum may then possibly identify any issue with the media versus Vegas Pro 18.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

David-R wrote on 4/19/2022, 2:46 AM

Thanks so much!!

Properties in Vegas reveals that the problem files are missing a "Video Stream" line, that is present in the working files. Otherwise, problem-files data matches working-files.

MediaInfo reveals that the problem files are missing a "Frame rate Mode: Constant" that is present in the working files.  Otherwise, the data matches. Perhaps a variable frame rate issue?


So the question remains, how to fix?   I doubt that random files suddenly changed on their own.  I imagine that a Vegas update decided it would no longer read these files.

VEGASHeman wrote on 4/19/2022, 11:55 AM

@David-R: Can you specify which File I/O plugin is used to read the problem file in b527? You can find this information by right clicking on the video event for the file in the timeline, selecting "Properties" and navigating to the General tab. The plugin used should be listed at the bottom.

Also, if possible, could you upload one of these files? On the surface, the frame rate mode should not affect the behavior to this extent (i.e. the entire video stream is excluded).

David-R wrote on 9/9/2022, 3:45 PM

Very late reply, but the video track portion of the problem clips does not display any data, and there is no General tab under Properties. But the audio track portion shows "compoundplug.dll", same as the video clips that do work. Here is an example of a problem MP4 that will not play video in b527 (248mb) - https://app.box.com/shared/static/5eir5s49v2nwyk37rape42sz3gct90xt.mp4

 

john_dennis wrote on 9/9/2022, 4:58 PM

@David-R

A quick and simple rewrap of the file in Shutter Encoder enabled Vegas 19-643 to read the problem file properly. My installation of Vegas 18-527 (on another boot image) was able to read to problem file with no intervention. A lot can happen to screen captures. I'd just use Shutter Encoder to rewrap and clean up issues and move on with my life.

While you're at it, you might consider changing that funky variable frame rate. I suspect your original file was mis-characterized as constant frame rate.

Conforming the frame rate in Shutter Encoder...

... rather quickly produced this...

General
Complete name                            : E:\OBS Captures\Action 12-27-2020 2-49-02 AM_H.264.mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/iso2/avc1/mp41)
File size                                : 492 MiB
Duration                                 : 1 min 43 s
Overall bit rate mode                    : Variable
Overall bit rate                         : 40.0 Mb/s
Encoded date                             : UTC 2022-09-09 22:14:41
Tagged date                              : UTC 2022-09-09 22:14:41
Writing application                      : Lavf59.24.100

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L5.1
Format settings                          : CABAC / 4 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 4 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 1 min 43 s
Bit rate                                 : 40.0 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 29.970 (29970/1000) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.644
Stream size                              : 489 MiB (99%)
Writing library                          : x264 core 164 r3095 baee400
Encoding settings                        : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=18 / lookahead_threads=3 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=abr / mbtree=1 / bitrate=40000 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Encoded date                             : UTC 2022-09-09 22:14:41
Tagged date                              : UTC 2022-09-09 22:14:41
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 1 min 43 s
Source duration                          : 1 min 43 s
Source_Duration_LastFrame                : -13 ms
Bit rate mode                            : Variable
Bit rate                                 : 301 kb/s
Maximum bit rate                         : 320 kb/s / 320 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 3.70 MiB (1%)
Source stream size                       : 3.71 MiB (1%)
Title                                    : Mirillis Sound Media Hand
Language                                 : English
Default                                  : Yes
Alternate group                          : 1
Encoded date                             : UTC 2022-09-09 22:14:41
Tagged date                              : UTC 2022-09-09 22:14:41

Happy Otter Scripts also has a means of converting variable frame rate video to constant by rewriting the PTS.

Yelandkeil wrote on 9/9/2022, 5:30 PM

I also got the same warning recently, the source files are yet from Sony's earlier 3D-camcorder.

After hitting/closing the warning, timeline plays back well without any impact.

-- Hard&Software for 5.1RealHDR10 --

ASUS TUF Gaming B550plus BIOS3202: 
*Thermaltake TOUGHPOWER GF1 850W 
*ADATA XPG GAMMIX S11PRO; 512GB/sys, 2TB/data 
*G.SKILL F4-3200C16Q-64GFX 
*AMD Ryzen9 5950x + LiquidFreezer II-240 
*XFX Speedster-MERC319-RX6900XT <-AdrenalinEdition 24.12.1
Windows11Pro: 24H2-26100.3915; Direct3D: 9.17.11.0272

Samsung 2xLU28R55 HDR10 (300CD/m², 1499Nits/peak) ->2xDPort
ROCCAT Kave 5.1Headset/Mic ->Analog (AAFOptimusPack 6.0.9403.1)
LG DSP7 Surround 5.1Soundbar ->TOSLINK

DC-GH6/H-FS12060E_HLG4k120p: WB=manual, Shutter=125, ISO=auto/manual
HERO5_ProtuneFlat2.7k60pLinear: WB=4800K, Shutter=auto, ISO=800

VEGASPro22 + XMediaRecode/Handbrake + DVDArchi7 
AcidPro10 + SoundForgePro14.0.065 + SpectraLayersPro7 
K-LitecodecPack17.8.0 (MPC Video Renderer for HDR10-Videoplayback on PC) 

David-R wrote on 9/9/2022, 5:34 PM

Thanks! Do you know if Shutter Encoder can batch hundreds of files? I dont see that offhand.

The frame rate varies with game capture. Thats why I suggested Vegas has some issue with that. But those clips all played fine in Vegas for over a year, then suddenly stopped working.

Vegas is also working with hundreds of more recent variable rate captures from the same capture app.

john_dennis wrote on 9/9/2022, 6:20 PM

@David-R

"Do you know if Shutter Encoder can batch hundreds of files?"

Yes. Just select them when you Browse.

Former user wrote on 9/9/2022, 7:27 PM

The frame rate varies with game capture. Thats why I suggested Vegas has some issue with that. But those clips all played fine in Vegas for over a year, then suddenly stopped working.

Vegas is also working with hundreds of more recent variable rate captures from the same capture app.

I had a look at your file, plays the file with default AVC decode, but does not play with Legacy AVC decode. Make sure legacy decode is not set. If this is actually the case, and you choose Legacy AVC decode to avoid the terrible GPU decoder and instability it causes you can change 'hardware decoder to use' to off

I tested with VP18 527, and VP19 643

john_dennis wrote on 9/9/2022, 9:09 PM

I don't know how the Vegas developers feel, but I'm getting weary with the expectation that an application targeted toward "Professionals" should be able to decode and function with every frankenfile* that anyone creates in the privacy of their own home without regard to any standards.

Shutter Encoder Conform to 29.97 FPS takes three seconds for the one minute forty-seven second sample file, the output of which plays smoothly on an i7-3770(k) on Vegas Pro 14.

Folks, let's find something else to worry about.

* Credit to @Musicvid

David-R wrote on 9/13/2022, 11:23 PM

 

...your file, plays the file with default AVC decode...

 

That fixed it! Thanks todd-b!!

john dennis, I am glad to know about Encoder, but adding more steps/apps in a pipeline is not ideal, especially where hundreds of clips need to be checked, processed and re-checked regularly.

I am a VFX pro of 26 years, and every app on my workstations played these game captures, except Vegas. I dont see anything that odd about them. But compatibility issues are the biggest plague of computers, as dozens of interdependent components must continuously upgrade among varying vendors and rates.

john_dennis wrote on 9/14/2022, 12:54 AM

@David-R

"...every app on my workstations played these game captures, except Vegas."

I'm not unsympathetic. The Windows 10 Video Editor was able to injest your video on my oldest machine. The machine once had Vegas Pro 9-13 on it, but now just has Microsoft Office. It actually made good use of the hardware resources. If you call Q9450/GTS450 resources.

@VEGASHeman