I am new here. If this is not the right place to post this, apologies.
We have a new computer that can play 2160p@60fps video smoothly (nVidia GTX980M GPU).
We also have a ~7-year-old computer (GPU: ATI HD 6970M) that plays 1440p@60fps smoothly, it also plays 1080p@120fps on an 1080p 120Hz screen, but not 2160p@1fps.
With deactivated hardware acceleration, the old computer plays 2160p@30fps footage normally for half a second and then the video freezes while the audio keeps playing.
I am sure the old computer has more than 1/60 of the performance of the newer computer. How come it fails to play back 2160p at ONE frame per second (from a test video file)?
Both 2160p@30fps and 1080p@120fps have exactly 248832000 pixels per second. How come only the latter can be played by the older computer, despite the same number of pixels per second?
+ Reply to Thread
Results 1 to 23 of 23
There are many variables involved in playing video smoothly on any computer, new or old. I have a 12-year old computer that plays pretty much everything, with no problem. In my case, they key was finding the right software program.
Software video players are NOT all created equal.
So, what video player are you using?
Are you saying you have a 1 fps 2160p video that isn't playing on the old computer? Or are you saying you expect a 30 fps 2160p video to play at some lower frame rate but still show you all the frames?
As a side note: What format is you video in?
Often 2160p is HEVC (might even be HDR) while 1080p is H.264 and your graphics card will not be able to decode HEVC @ 2160p.users currently on my ignore list: deadrats, Stears555
Last edited by LG7; 29th Dec 2019 at 13:27. Reason: Correct number.
* With modern codecs the working set while decompressing video is typically several frames. But the issues still holds -- the 4x larger working size is going to result in less effective caching.
About the GPU: The GPU that the 7 year old computer has has a maximum display resolution of 1440p, while the new GPU certainly supports 2160p.
Also, the newer computer supports toggling between an CPU-integrated Intel GPU and a dedicated Nvidia GPU, while the old computer does not offer the option to use the integrated GPU, although the hardware (Intel Core i7-2630QM) is equipped with one.
The other thread thread is not the exact same subject as this one.
They overlap somewhat, but one thread asks about why two devices with the exact same GPU play videos differently, while the other is about why an old computer fails to play back a video at a higher resolution with proportionally decreased framerate.
It is, although somewhat similar, not exactly the same thing.
Vlc has a know limitation - can't play 1fps.
Most media players attempt to play back files in real time, dropping video frames and audio as needed to stay on time.
Try turning off any "drop frames" settings that are checked.
Don't have it, but you may need a program like VirtualDub to play back files frame-by-frame without dropping at non-real time playback.
I don't have the interest yet to write an explanation on why and how exactly, but this post should give you some ideas on the concept of modern codecs.
https://forum.videohelp.com/threads/393903 ("Further Off-Topic", "VLC")
Ok, thanks for clearing it up. I now understand DPB is the reason.
But is still something I don't understand:
How come the UleFone Armor 2 fails to play back 4K video smoothly, despite having appropriate hardware: Mediatek Helio P25 CPU and a Mali T880 GPU, both of which support 2160p video according to data sheet?
The DPB in this case is basically defined by the media player (or its underlying hardware acceleration method).
Also note: the VE is usually considered as an independent part on SoCs.
But the software used to play back the video (both VLC Mobile and Android Media Framework) play it back on a Galaxy S7 Edge (Snapdragon 820 CPU and Mali T880 GPU) smoothly.
So the only way this could happen is that the software is somehow incompatible with the Helio P25, although it shouldn't be, because both P25 and Snapdragon 820 the same processor architecture, ARMv8.
Highly dubious on this line.
The Helio P25 data sheet mentions 1080p display resolution, but 2160p video resolution.
Also, it plays 1080p@60fps and 1440p@30fps smoothly.
Last edited by LG7; 26th Jan 2020 at 04:08. Reason: Adding “ Highly dubious on this line.” quote.
MediaTek Helio P25 is a SoC instead of a CPU.
And it's extremely rare for a smartphone SoC to have multiple VE units integrated.
Note: the same for Qualcomm Snapdragon 820.
@gdgsdg123 Thanks for the information.
But I just noticed: That P25 data sheet ( https://www.mediatek.com/products/smartphones/mediatek-helio-p25) says “capture FPS: 24fps”.
I will now try playing a 2160p@24fps video on the UleFone Armor 2.
Note that video encoding needs much more ressources than decoding.
But in the meantime, here are some more observations and tests I made:
Using the app “Open Camera” (third party camera software for Android), I have access to frame rate modes (15, 24, 25, 30, 60, 96, 100, 120) that were not accessible through the precluded camera software that always uses VFR (variable frame rate) 10-30fps (depending on brightness conditions) at these resolutions: QCIF (176×144), CIF (352×288), D1 (720×480), HD 1280×720, FullHD 1920×1080.
According to my recording tests using the OpenCamera on the rear camera:
2160p@15fps: Fails to start recording.
1440p: OpenCamera has no 1440p mode, at least not the somewhat old version I use.
1080p@120fps mode: Skips many frames. Apparently, the effective framerate is ~30fps
1080p@60fps: Similar as 120fps, but less frequent stuttering. Sometimes records a few frames without skipping in succession. But average frame rate still appears like 30fps.
720p@120fps: Looks 90% smooth, ~10% skipped frames
720p@60fps: Looks 95% smooth, ~5% skipped frames (surprisingly).
864×480@120fps: Always smooth, no skipped frames.
Note that the Armor 2 uses a crappy image sensor (Samsung S5K3P3), which could also be the cause of the poor performance at 720p or higher.
I have not done much testing for the front camera (also max. 1080p@30fps), but I have made another interesting observation:
Selecting 480p@60fps for the front camera actually works in the viewfinder (the preview looks 60fps smooth), but when starting the video recording, the camera software (OpenCamera) freezes up and the front camera becomes inaccessible to any app until next reboot (even after forcibly taskkilling OpenCamera). Strange phenomenon.
The test files used for playback were not the same as the ones recorded on the Armor 2.
I tested a DCi 4K video (4096×2160@24fps) now.
Playback using VLC: Smooth for first second, then only the audio keeps playing.
Playback using stock media player: smooth.