I'm looking at a Panasonic camcorder that records in MOV 4.2.0 & 4.2.2 10 bit.
It also has AVCHD as well but in 8 bit.
I was wondering if VP22 can handle the MOV 10-bit versions.
Is it HEVC? 10 bit media is supported in VEGAS but few GPUs decode 422 so consider staying with 420 for better performance.
Roger
Yes, it is HEVC
Not sure if my GPU would or not at this time.
Your GeForce RTX 4070 Ti Super can only decode 10-bit 420 HEVC.
Your CPU has a Intel UHD Graphics 770 which can decode 10-bit 422 HEVC. I have a similar iGPU but don't find the performance all that great in VEGAS.
My suggestion would be to find sample footage from this camera or a similar one online and test it before you buy the camera (or if in the store they let you shoot a sample onto your SD card do that).
OK, I'll check that out. Thanks.
Recently I started to use Panasonic X1500 and recording in 4K-60p 10bits (both mov & mp4):
Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main 10@L5.1@High Codec ID : hvc1 Codec ID/Info : High Efficiency Video Coding Duration : 13 s 13 ms Bit rate : 95.7 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 59.940 (60000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 10 bits Bits/(Pixel*Frame) : 0.193 Stream size : 148 MiB (100%) Language : English Encoded date : 2025-03-13 23:30:42 UTC Tagged date : 2025-03-13 23:30:42 UTC Color range : Limited Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Codec configuration box : hvcC
Editing the footage in VP 22 (encoding to 8bit), however on my system (see my specs) I cannot do it without proxy at all (preview framerate is just a few fps).
With proxy I can edit it with full framerate but only if using auto preview resolution :(
Going to upgrade my CPU/MB/RAM this weekend. Not expecting miracles as by reviews the new CPU it not much faster. So later I will most probably upgrade GPU as well.
Also, RAM usage is very high and I'm still having some random crashes (I found it much more stable when I disable GPU decoder) that I did not have when editing my 1080-60p footage from previous camcorder.
@ChasMc I found a good difference using VP21 using the Intel GPU set in I/O either ON or OFF.
However using VP22 b248 shows such improvement in playback with Intel GPU ON or OFF that my VP 22 test is redundant.
The sample I used to test was previously available here (user AVSupport) and would really try any PC. It's the Sony A7SIII Hevc 10 bit 422 with no P frames all B frames.
My computer specs are listed below. I shoot 4K 10 bit 4:2:2 150Mb/s MOV Panasonic, but AVC and HEVC. Some effects play back ok, others, I have to change the Preview to something has acceptable playback. I'll try effects, and if playback it really not great at all, I'll do that at the end of editing.
@ChasMc The reason why in using VP22 that there is good playback with Intel GPU not selected for decoding in I/O is that it IS being used as the Taskmanager displays in Video decode1. Not issue with this, VP is simply seeing the decoding capabilities of Intel GPU and using it although it's not selected in I/O.
there is good playback with Intel GPU not selected for decoding in I/O is that it IS being used as the Taskmanager displays in Video decode1. Not issue with this, VP is simply seeing the decoding capabilities of Intel GPU and using it although it's not selected in I/O.
It is possible you do not have decoder selected in dropdown, but option 'Enable QSV Encoding and Decoding (where available)" is ticked.
I think what Johnny says is right- for some formats VEGAS will just use the hardware decoder if it finds one, regardless of user preferences.
johnny-s, I tried your sample. On Best- full, it ran ok with a little jurky when moving. Tried a simple cut in it with a 1 sec. transition. The transition was poor. Tried preview - auto, wasn't very smooth when you were moving.
Similar to my experience using VP22 b248 at Best/Full. I only did playback. 1st. second or 2 less than 50 fps, full 50 fps after that.
Far less playback rate on previous to VP 22.
there is good playback with Intel GPU not selected for decoding in I/O is that it IS being used as the Taskmanager displays in Video decode1. Not issue with this, VP is simply seeing the decoding capabilities of Intel GPU and using it although it's not selected in I/O.
It is possible you do not have decoder selected in dropdown, but option 'Enable QSV Encoding and Decoding (where available)" is ticked.
I unchecked that first and it made no difference. I still had Intel decoding equivalent.
Then I ran Taskmanager with it still unchecked and I am getting Intel decode1 benefit.
Ok. I think the decode1 is odd. i.e. an anamoly in so far as it's giving a readout graph for Intel GPU when it's not selected for decoding. At the same time the "decode" (not "decode1") shows no decoding graph when Intel is not selected.
The simplest way to confirm is to physically disconnect the Intel GPU, I did that. I marked out the AVSupport clip in 1 - 6 second markers. Total duration is 26 seconds.
With the Intel GPU physically disconnected playback at Best/Full only hits 50 fps immediately after the 6 seconds marker.
With the Intel GPU in use and selected for decoding then playback at Best/Full hits 50 fps immediately after the 1 second marker.
I suspect that 'Enable QSV Encoding and Decoding (where available)" is only applicable to iGPU's.
I still get 50 fps just after the 1 second mark whether 'Enable QSV Encoding and Decoding (where available)" is checked or unchecked.
Meant to add that with Intel Gpu not selected for decoding in I/O playback at 50 fps takes place just after 4 seconds mark.
johnny-s, I tried your sample. On Best- full, it ran ok with a little jurky when moving. Tried a simple cut in it with a 1 sec. transition. The transition was poor. Tried preview - auto, wasn't very smooth when you were moving.
I'm thinking that your camcorder output may be not as difficult to play as this sample.