Importing video from Galaxy 22 to VPX11

1940 wrote on 8/23/2023, 11:07 PM

Hi,

I have a 36 min MP4 video captured on a Samsung Galaxy 22 Ultra

It took a while to convert but now it's in, there is sound but no vision.

What have I not done or done incorrectly?

I am not sure what data will help to get an answer but this is what I see.

Frame Width 3840
Height 2160
Data 41966
Total bit 422222
Frame 56.46

The project video settings
PAL HDV1 720p 16:9 (1280x720;25fps)

Auto Create Proxy files.

The object properties as it sites in the timeline. are..

Resolution 3840x2160 pix
Radio 16:9
MPEG
Frame 56.46
Color depth 8bit
Color Sample 4.2.0
Intermediate image processing Auto Interlace, Interpolate intermediate images.

When I play in VLC I see this as the Codec.

Codec: MPEG-H Part2/HEVC (H.265) (hvc1)
Video resolution: 3840x2160
Frame rate: 56.456647
Decoded format: Planar 4:2:0 YUV

Comments

Reyfox wrote on 8/24/2023, 6:45 AM

Convert it with what?

1940 wrote on 8/24/2023, 7:10 AM

When I imported it into VPX it said it was converting it. That process took a long time.

When that has happened before. I have always been able to see the vision and use the file, but not this time. Audio us okay but file is all yellow with no frames showing.

I also tried to convert with VLC but that also didn't work and only played audio. Win10 Media does play it all however.

Are tge monent I have Prism Video Converter on it, but it too is exremely slow.

My lesson so far. is not to record on the phone in UltraHD.

Reyfox wrote on 8/24/2023, 7:16 AM

You have always been able to do this with files from this phone with the same video settings to record?

Former user wrote on 8/24/2023, 9:36 AM

@1940 Hi, the VLC codec H265 shows your video is HEVC, this is becoming a more acceptable format but still causes some issues, & only one of your PC's 'Nvidia Quadro FX 5800' has the 4GB Magix recommended min specs but it was launched November 11th, 2008. .

Try turning off the High bitrate option on your phone, this will produce an AVC format rather than HEVC,

You might also try recording at 30fps rather than 60fps, even on my PC i notice the difference between the two in Magix's performance,

Former user wrote on 8/24/2023, 9:43 AM

@1940 There's an App called MediaInfo, download it, it's free & a fast download with no added adverts or any of that rubbish. https://mediaarea.net/en/MediaInfo, this will give much better info about your media.

After downloading, right click on the media file in your Windows folder, open MediaInfo, choose Text from the options at the top, Copy & paste the information in a new comment on here 👍

Like this

1940 wrote on 8/24/2023, 4:28 PM

Many thanks guys.

In Prism I converted to 1280 still 60 fps and it worked fine in timeline however when I zoomed it was grainy so I an now converting the orig to 1920 at 30fps to see if that is okay when I zoom in..

I will change the phone setting too as you suggest.

Thank you for the MediaInfo tip. What a program !

Here is the info.

General
Complete name                            : \\DELL-9020-VIDEO\RedA-4TB-3TB Data\2023 Aug 22 Galaxy Interview v 3\20230822_125559.mp4
Format                                   : MPEG-4
Format profile                           : Base Media / Version 2
Codec ID                                 : mp42 (isom/mp42)
File size                                : 10.7 GiB
Duration                                 : 36 min 11 s
Overall bit rate                         : 42.2 Mb/s
Frame rate                               : 56.457 FPS
Performer                                : Samsung SM-S908E
Encoded date                             : 2023-08-22 03:32:13 UTC
Tagged date                              : 2023-08-22 03:32:13 UTC
xyz                                      : -33.7949+150.7051/
com.android.version                      : 13

Video
ID                                       : 1
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main@L5.1@High
Codec ID                                 : hvc1
Codec ID/Info                            : High Efficiency Video Coding
Duration                                 : 36 min 11 s
Bit rate                                 : 42.0 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Rotation                                 : 180°
Frame rate mode                          : Variable
Frame rate                               : 56.457 FPS
Minimum frame rate                       : 20.000 FPS
Maximum frame rate                       : 60.040 FPS
Real frame rate                          : 60.000 FPS
Standard                                 : PAL
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Bits/(Pixel*Frame)                       : 0.090
Stream size                              : 10.6 GiB (99%)
Title                                    : VideoHandle
Language                                 : English
Encoded date                             : 2023-08-22 03:32:13 UTC
Tagged date                              : 2023-08-22 03:32:13 UTC
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
mdhd_Duration                            : 2171826
Codec configuration box                  : hvcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 36 min 11 s
Source duration                          : 36 min 11 s
Bit rate mode                            : Constant
Bit rate                                 : 256 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                              : 66.3 MiB (1%)
Source stream size                       : 66.3 MiB (1%)
Title                                    : SoundHandle
Language                                 : English
Encoded date                             : 2023-08-22 03:32:13 UTC
Tagged date                              : 2023-08-22 03:32:13 UTC
mdhd_Duration                            : 2171769

CubeAce wrote on 8/24/2023, 8:10 PM

@1940

Hi.

A variable frame rate difference of 40 frames per second could throw out a lot of computer systems when trying to render to a constant frame rate. The base frame rate of 56.457 FPS is also not a standard video frame rate. Phone manufacturers do this mainly to save storage space on the phone but it causes headaches when trying to edit the footage.

Others here may be able to suggest good free programs to convert those file to a better constant frame rate for editing so not all is lost for this project.

Ray.

johnebaker wrote on 8/25/2023, 2:27 AM

@1940

In addition to @CubeAce comment, and assuming your signature is up to date, none of the PC's listed in your support hardware acceleration (HWA) for HEVC video.

Conversion of the video the h.264/AVC encoded video and Constant Framerate would ease the load on the PC's, this can be done using a converter such as Handbrake or AviDemux.

The Intel based system HD4600 integrated GPU supports HWA of h.264/AVC video however only up to 1920 x 1080 resolution.

HTH

John EB

Former user wrote on 9/4/2023, 10:14 AM

Those GPUs likely don't decode HEVC, so if he's using "High Efficiency" that is asking for issues.

If you are using High Efficiency, the first thing you need to do is try disabling HDR10+ (and High Bitrate - both together and in isolation) to see if that will allow the PC/Software to decode the video properly. Blank video points to an issue with the Video CODEC not being supported, but the Audio (usually AAC) being supported.

On that hardware platform, I would suggest never recording HEVC - only H.264, since a PC with that GPU/iGPU likely has a weaker CPU and software decoding High Bitrate HDR10+ HEVC is just going to bottleneck your performance (likely quite heavily). Without a GPU to offload video decoding to, it is not worth it. I would also posit that that machine simply isn't useful for UHD recording no matter the CODEC< unless you have gobs of RAM and fast storage and transcode everything to an uncompressed or [at least] Intermediate CODEC (ProRes, DNxHR, Grass Valley, etc.)

IMO, the easiest way to eliminate issues with this footage is to buy a cheap AMD RX400/500 (Polaris) GPU and upgrade to VPX12+ (needed to AMD GPUs). This will give you the UHD H.264/HEVC Decoders you need to handle that footage and eliminate most of the CPU bottleneck, as well as well as a faster GPU for FX Processing. Not sure about HDR10+. Maybe you'll need an RX 5000-series (Navi) card for that - you'll certainly want Navi if you encode HEVC, as the encoder in Polaris is not great (Decoder should be fine, though).

I reckon a GTX 1050Ti or 1060 (2060 if you can find a really cheap one) would work, as well.

VFR Smartphone Footage has been a solved problem for half a decade, at this point. I don't think this is an issue. It wasn't an issue when I was on am i7-7700HQ/GTX1050 Laptop, and none of my newer machines even sniffle at that kind of footage no matter what NLE I load them in. Most NLEs made adjustments to factor that in back in 2018/2019 ("Pro NLEs" trailing the consumer packages by 1-2 years).

You can convert the footage, but I think performance will be poor on a machine that old if you try to edit UHD timelines regardless of what CODEC you use - unless your timelines are really simple. Layered video, effects, transitions, color grading, etc. are still going to bottleneck the CPU and likely the GPU as well. OP will not get GPU Decode unless they downscale and downsample all of their footage to 4:2:0 1080p/HD.

@1940 Hi, the VLC codec H265 shows your video is HEVC, this is becoming a more acceptable format but still causes some issues, & only one of your PC's 'Nvidia Quadro FX 5800' has the 4GB Magix recommended min specs but it was launched November 11th, 2008. .

Try turning off the High bitrate option on your phone, this will produce an AVC format rather than HEVC,

You might also try recording at 30fps rather than 60fps, even on my PC i notice the difference between the two in Magix's performance,

If you toggle off High Bitrate but High Efficiency or HDR10+ are still toggled on, it will still record HEVC.

High Bitrate requires High Efficiency, but the opposite is not true - it's an option in that case.

In order to record H.264, you have to toggle off High Efficiency and both options under it.

If either or both of those other two options are toggled on, it will force the phone to record videos in HEVC CODEC.

You cannot record HDR10+ or High Bitrate video using the H.246 CODEC on those phones.

Also, OP should check whether or not certain combinations of Resolution and Framerate force HEVC encoding. Some phones will force HEVC encoding for UHD/4K if the framerate is > 30FPS due to file sizes being too massive when you record this footage using H.264. 8K recording on a Samsung phone is something I cannot imaging they would ever allow you to record using H.264. That is almost certainly HEVC no matter what settings you have enabled in the camera app.

Smartphone Storage isn't even as fast as a SATA3 SSD, so devices may not be able to write data fast enough to keep up with the recording. It's also why most Samsung phones (that I've used) force you to record UHD footage to the internal storage (doesn't allow recording that to an SD Card). It's also why certain combinations are Raster/Framerate are only recorded using HEVC, which results in smaller files to write (generally 40-50% smaller than H.264).

30p will perform better than 60p because there are - generally speaking (VFR is an obvious factor) - twice as many frames to process and decode. CODECs like H.246 and HEVC do not encode entire frames. They record Frames and then sequences of changes in between them. This is why they can be so small. So, the files are computationally intensive to decode, which is why hardware decoding is such a boon.

Without hardware decoding, even H.264 UHD30 footage is going to bottleneck an old CPU - especially once other factors are bought into the picture (Layered Video, Effects, Transitions, Color Grading, Image Stabilization, Re-Timing, etc.).