Comments

jetdv wrote on 12/15/2025, 2:16 PM

And what format of video is inside this MOV file? I MOV file is like a paper sack - it can hold many different things. So you need to use something like MediaInfo to determine what is inside that file.

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

Szczepan-Wtorek wrote on 12/15/2025, 2:20 PM

Yes, already adding information.

 

 

john_dennis wrote on 12/15/2025, 3:31 PM

@Szczepan-Wtorek

Upload a sample file to a cloud share site, OneDrive, Google Drive, Dropbox, etc. Post the link here...


... and someone will try it for you.

Howard-Vigorita wrote on 12/15/2025, 4:48 PM

@Szczepan-Wtorek 10bit 4:2:2 Avc cannot be decoded by a gpu making it an impractical format for video editing, no matter what container it's in. Suggest you transcode existing footage to something your gpu can handle. And set your camera to record in that format in the future.

RogerS wrote on 12/15/2025, 7:17 PM

@Szczepan-Wtorek Can you tell us your GPU model?

Interesting that it's also 32-bit float audio. This is a very editing unfriendly combination you have (if the video worked I don't think the audio would be editable in VEGAS without transcoding it to wav).

Szczepan-Wtorek wrote on 2/4/2026, 12:20 PM

@RogerS

Sorry for no response from me.

I have this problem on my laptop, on my desktop computer I have no problem importing MOV files to V22

Laptop:

GPU - GTX 5060

CPU - Razen 7 260

 

Desktop:

GPU - RTX 2080

CPU - I9 9900k

Steve_Rhoden wrote on 2/4/2026, 12:25 PM

@Szczepan-Wtorek  Go into Preferences and under the File I/O tab change "Enable legacy AVC decoding and Enable legacy HEVC decoding, And see if things behave differently for you.

Szczepan-Wtorek wrote on 2/4/2026, 12:29 PM

@Steve_Rhoden Yes, I have it set up like that