Just simple cuts and connecting clips. I have that clicked already, but I think the issue is they are LOG from iphone black magic camera app h.265 2160 x 3840 so read vegas doesnt do well with this and its a bit confusing. Do you have any ideas?

Can you share the settings you used in the app? Or MediaInfo? Avoid 10 bit 422 as most GPUs can't decode it.

Can you share the settings you used in the app? Or MediaInfo? Avoid 10 bit 422 as most GPUs can't decode it.

Thanks for responding! Is this what you need? I tried to create proxy and that made the whole program lag now.... One problem at a time, let me know if this is the right info, super frustrating ahaha.

Hi @Boting-Mo this is helpful and confirms it is 10 bit 30fps HEVC. I really could use more detail from MediaInfo or a sample file. https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

A proxy file only works if you change your preview quality to preview/full or lower. Did you do that?

What is your GPU model? It's cut off at top (RTX could be 20XX through 50XX).

Are the settings in options/preferences/ file io on the defaults (experimental HEVC decoding unchecked?)

Can you share the settings you used in the app? Or MediaInfo? Avoid 10 bit 422 as most GPUs can't decode it.

Thanks for responding! Is this what you need? I tried to create proxy and that made the whole program lag now.... One problem at a time, let me know if this is the right info, super frustrating ahaha.

would you Try moving the file to another location. Not OneDrive.

+1.

Also, HEVC is a more demanding file format to work with. You listed "generic" computer specs, and not specific ones like the ones listed in my Signature below. Also, which Build of VP23 are you using?

Hi @Boting-Mo this is helpful and confirms it is 10 bit 30fps HEVC. I really could use more detail from MediaInfo or a sample file. https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

A proxy file only works if you change your preview quality to preview/full or lower. Did you do that?

What is your GPU model? It's cut off at top (RTX could be 20XX through 50XX).

Are the settings in options/preferences/ file io on the defaults (experimental HEVC decoding unchecked?)

General
Complete name                            : C:\Users\thewu\OneDrive\Desktop\LOG FILES ORIGINAL BUSZHIKE\Fight Scene Start Tracking Rig.mov
Format                                   : MPEG-4
Format profile                           : QuickTime
Codec ID                                 : qt   0000.00 (qt  )
File size                                : 238 MiB
Duration                                 : 41 s 598 ms
Overall bit rate                         : 47.9 Mb/s
Frame rate                               : 30.000 FPS
Recorded date                            : 2025-11-30 11:58:28-06:00
Encoded date                             : 2025-11-30 17:58:28 UTC
Tagged date                              : 2025-11-30 17:59:11 UTC
Recorded location                        : 41.43413°N 87.51705°W
Writing application                      : Blackmagic Cam 3.2.000045
Writing library                          : Apple QuickTime
Writing hardware                         : Apple iPhone 16 Pro 24mm
com.apple.quicktime.full-frame-rate-play : 1
com.apple.proapps.manufacturer           : Apple Inc.
com.apple.proapps.clipID                 : A001_11301158_C097
com.apple.proapps.reel                   : 1
com.apple.proapps.scene                  : 1
com.apple.proapps.shot                   : 1
com.apple.proapps.isGood                 : 0
com.apple.proapps.logNote                : Good take
com.blackmagic-design.camera.dayNight    : Day
com.blackmagic-design.camera.environment : Interior
com.blackmagic-design.camera.dateRecorde : 2025-11-30T11:58:28-0600
com.blackmagic-design.shutterMode        : Speed
com.blackmagic-design.shutterSpeed       : 1/60
com.blackmagic-design.camera.iso         : 200
com.blackmagic-design.camera.whiteBalanc : 5000
com.blackmagic-design.camera.whiteBalanc : 20
com.blackmagic-design.camera.aperture    : f1.8
com.blackmagic-design.camera.lensType    : iPhone 16 Pro 24mm
com.blackmagic-design.sensorFPS          : 30
com.apple.proapps.cameraName             : A

Video
ID                                       : 1
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Format Range@L5@Main
Codec ID                                 : hvc1
Codec ID/Info                            : High Efficiency Video Coding
Duration                                 : 41 s 598 ms
Bit rate                                 : 47.2 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Rotation                                 : 90°
Frame rate mode                          : Variable
Frame rate                               : 30.000 FPS
Minimum frame rate                       : 28.571 FPS
Maximum frame rate                       : 31.579 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:2
Bit depth                                : 10 bits
Bits/(Pixel*Frame)                       : 0.190
Stream size                              : 234 MiB (98%)
Title                                    : Core Media Video
Writing library                          : HEVC
Encoded date                             : 2025-11-30 17:58:28 UTC
Tagged date                              : 2025-11-30 17:59:11 UTC
Color range                              : Limited
Color primaries                          : BT.2020
Matrix coefficients                      : BT.2020 non-constant
Codec configuration box                  : hvcC

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Little / Signed
Codec ID                                 : lpcm
Duration                                 : 41 s 578 ms
Bit rate mode                            : Constant
Bit rate                                 : 768 kb/s
Channel(s)                               : 1 channel
Sampling rate                            : 48.0 kHz
Bit depth                                : 16 bits
Stream size                              : 3.81 MiB (2%)
Title                                    : Core Media Audio
Encoded date                             : 2025-11-30 17:58:28 UTC
Tagged date                              : 2025-11-30 17:59:11 UTC

Other
ID                                       : 3
Type                                     : Time code
Format                                   : QuickTime TC
Duration                                 : 32 ms
Frame rate                               : 30.000 FPS
Time code of first frame                 : 11:58:28:00
Time code of last frame                  : 11:58:28:00
Time code, stripped                      : Yes
Title                                    : Core Media Time Code
Encoded date                             : 2025-11-30 17:58:28 UTC
Tagged date                              : 2025-11-30 17:59:11 UTC

Hi @Boting-Mo this is helpful and confirms it is 10 bit 30fps HEVC. I really could use more detail from MediaInfo or a sample file. https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

A proxy file only works if you change your preview quality to preview/full or lower. Did you do that?

What is your GPU model? It's cut off at top (RTX could be 20XX through 50XX).

Are the settings in options/preferences/ file io on the defaults (experimental HEVC decoding unchecked?)

Hi @Boting-Mo this is helpful and confirms it is 10 bit 30fps HEVC. I really could use more detail from MediaInfo or a sample file. https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

A proxy file only works if you change your preview quality to preview/full or lower. Did you do that?

What is your GPU model? It's cut off at top (RTX could be 20XX through 50XX).

Are the settings in options/preferences/ file io on the defaults (experimental HEVC decoding unchecked?)

Hi @Boting-Mo this is helpful and confirms it is 10 bit 30fps HEVC. I really could use more detail from MediaInfo or a sample file. https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

A proxy file only works if you change your preview quality to preview/full or lower. Did you do that?

What is your GPU model? It's cut off at top (RTX could be 20XX through 50XX).

Are the settings in options/preferences/ file io on the defaults (experimental HEVC decoding unchecked?)

Hi Roger, Again thanks for taking the time to help! I did follow the tutorial links you sent, I believe I correctly sent in the media info and file op settings. I also included my computer specs, however, I didn't quite understand the RTX cut off could be 20xx through 50xx. Let me now if I did anything erroneously or need to update more information. Today, I also set my preview quality to lower and will see how it plays out. Thanks!!

+1.

Also, HEVC is a more demanding file format to work with. You listed "generic" computer specs, and not specific ones like the ones listed in my Signature below. Also, which Build of VP23 are you using?

Hi Ray,

Can you share the settings you used in the app? Or MediaInfo? Avoid 10 bit 422 as most GPUs can't decode it.

Thanks for responding! Is this what you need? I tried to create proxy and that made the whole program lag now.... One problem at a time, let me know if this is the right info, super frustrating ahaha.

would you Try moving the file to another location. Not OneDrive.

My One drive syncs my desktop although I have it shut off when I am editing. Strange, I downloaded these from google drive directly to my desktop and used those files. I will try a different location and see what happens.

@Boting-Mo thanks for the laptop specifications. Trying to edit HEVC 4K 4:2:2 10bit on your computer will cause lag in the Preview window. Your hardware (still not GPU specs) can not decode it in real time. In addition, there will be the heat issues as you edit and the hardware tries to keep up. Is there a specific reason for shooting 10bit 422? Also, and this is just a guess, you are using a cellphone for the video, hence the slight variable frame rate per your MediaInfo. Video cameras shoot at a constant frame rate.

Frame rate mode                          : Variable
Frame rate                               : 30.000 FPS
Minimum frame rate                       : 28.571 FPS
Maximum frame rate                       : 31.579 FPS

Those media specs are very helpful. The issue is that it's 10-bit 422 HEVC and that isn't a format your RTX 3050 is capable of decoding. A proxy file would work if you set the preview quality to preview/full or less but my recommendation would be to capture to an easy to edit format. If your app allows 10-bit 420 as an option that would work well. A phone isn't really capable of putting out pristine 422 data anyway as far as I'm aware.

@Boting-Mo thanks for the laptop specifications. Trying to edit HEVC 4K 4:2:2 10bit on your computer will cause lag in the Preview window. Your hardware (still not GPU specs) can not decode it in real time. In addition, there will be the heat issues as you edit and the hardware tries to keep up. Is there a specific reason for shooting 10bit 422? Also, and this is just a guess, you are using a cellphone for the video, hence the slight variable frame rate per your MediaInfo. Video cameras shoot at a constant frame rate.

Frame rate mode                          : Variable
Frame rate                               : 30.000 FPS
Minimum frame rate                       : 28.571 FPS
Maximum frame rate                       : 31.579 FPS

Hmmm, It was able to playback recently for whatever reason. I didn't change anything and its generally not skipping for right now. The only thing was creating proxy and preview quality, but it was already set that way. Considering what you said, does that make Vegas a less than optimal solution if I choose to use the Iphone 16 on certain projects versus a camera, granted, that I want to edit, color grade, etc?

Those media specs are very helpful. The issue is that it's 10-bit 422 HEVC and that isn't a format your RTX 3050 is capable of decoding. A proxy file would work if you set the preview quality to preview/full or less but my recommendation would be to capture to an easy to edit format. If your app allows 10-bit 420 as an option that would work well. A phone isn't really capable of putting out pristine 422 data anyway as far as I'm aware.

Hmmm, It was able to playback recently for whatever reason. I didn't change anything and its generally not skipping for right now. The only thing was creating proxy and preview quality, but it was already set that way prior to looking for help. So basically phones are a no go if you want to proceed into editing material professional? I honestly wanted to use it just to edit the video timeline, speed, etc, then send the project out to a 3rd party for most editing needs in proper format.

No, I am not saying the Vegas is a "less than optimal" solution. With cellphones, they record at a variable frame rate. Video editing software, while can handle small frame rate differences (VFR, or variable frame rate), they prefer to edit with CFR (constant frame rate). HEVC requires more computing power to "unpack" the more highly compressed (smaller) file than say, the same scene recorded in H264. To get a more "constant frame rate" from your cellphone, lighting conditions has to be perfect. Otherwise, the frame rate can be all over the place.

Here is something that you can do to test. Record the same video with HEVC and then with H264 8bit. Then see which one plays back smoother.

And while cellphones can work, again, everything has to be perfect for them to. Video cameras will always be constant frame rate, and have better low light capabilities than a cellphone. If you plan to shoot professionally, you really do not see people shooting with cellphones. Also, the better quality the video you shoot, the less post production issues someone will have.

Your biggest issue is the unnecessarily high quality (422 color depth), not the mildly variable franerate though neither are great for editing.

The camera's native app would be easier for editing as I'm pretty sure it's not 422.

As an alternative to a proxy workflow you could add a conversion step to say ProRes 422 using a program like Shutter Encoder. It will make it constant frame rate as part of the conversion and preserve whatever quality is in the original file. File sizes will be large.

No, I am not saying the Vegas is a "less than optimal" solution. With cellphones, they record at a variable frame rate. Video editing software, while can handle small frame rate differences (VFR, or variable frame rate), they prefer to edit with CFR (constant frame rate). HEVC requires more computing power to "unpack" the more highly compressed (smaller) file than say, the same scene recorded in H264. To get a more "constant frame rate" from your cellphone, lighting conditions has to be perfect. Otherwise, the frame rate can be all over the place.

Here is something that you can do to test. Record the same video with HEVC and then with H264 8bit. Then see which one plays back smoother.

And while cellphones can work, again, everything has to be perfect for them to. Video cameras will always be constant frame rate, and have better low light capabilities than a cellphone. If you plan to shoot professionally, you really do not see people shooting with cellphones. Also, the better quality the video you shoot, the less post production issues someone will have.

 

Ah, that makes sense. It is my first time using the phone and lighting was hell. I will test that out, thanks for the info.

Your biggest issue is the unnecessarily high quality (422 color depth), not the mildly variable franerate though neither are great for editing.

The camera's native app would be easier for editing as I'm pretty sure it's not 422.

As an alternative to a proxy workflow you could add a conversion step to say ProRes 422 using a program like Shutter Encoder. It will make it constant frame rate as part of the conversion and preserve whatever quality is in the original file. File sizes will be large.

Hmm, yes, but the size of file is huge if I use the native app, thus the blackmagic camera app, motion blur, set white balance, etc etc. I tried an encoder but some of the files wouldn't "encode" lol. If I use a phone again will alter work flow. First time self producing this short film trying out the phone, it has been an experience, but at least with all the advice I can create proxy lower view quality and then render to check it out, or send it off to someone to edit. Appreciate you help!

Yes, proxies seem to be what you need for your use case. To be clear on how the proxy system works, when you right click on a media file in the project media pool and select "create video proxy", you will see a progress bar pop up in the bottom left corner. When it fills, your proxy is ready. To enable your proxy file, select either "preview" or "draft" preview quality in the preview window. This will use the proxy file during playback, which should result in smoother timeline performance, but it will ignore the proxy and use the original full resolution file when you go to render. If you need to see the full resolution file at any time, simply set the quality to either "Good" or "best" in the preview window.

You could try using ffmepg inside your command prompt. I used ChatGPT told it my issues and it wrote the line of code. Just make sure to detail the source information from your phone and tell it you want it to run in 4k60 or 4k30 in sony vegas and it will run the program and make it a constant bit rate and format it so vegas likes it. I've done it countless time for videos off my phone and for when my old webcam had to use the Logitech capture software. Was a life saver.