I have a camera that takes H.264 and H.265 compressed video. With the 264 setting, my laptop seems to have no issues playing the videos back. With
the 265 setting, the video is choppy. I am running debian and did some searching. I do appear to have the libraries installed for 265. Do I also need to install the 'dev' libraries/packages to get the video to playback correctly? Are there any tips/tricks you all have re: playing H.265 video
on a linux machine?

Thanks!


* SLMR 2.1a * Aibohphobia, n. -- the fear of palindromes.
--- SBBSecho 3.12-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)

-={ 2021-06-12 22:48:47.304573427+00:00 }=-

Hey Mike!

Are there any tips/tricks you all have re: playing H.265 video
on a linux machine?

Make sure your player has H.265 capabilities.

$ ldd /usr/bin/mplayer | grep lib.26.
libx264.so.161 => /usr/lib/libx264.so.161 (0x00007fc80c9f2000)

$ ldd /usr/bin/ffmpeg | grep lib.26.
libx264.so.161 => /usr/lib/libx264.so.161 (0x00007fd9a99f9000)
libx265.so.192 => /usr/lib/libx265.so.192 (0x00007fd9a9471000)

As shown above mplayer is H.264 capable while ffmpeg can handle both. I believe mplayer can be built to use H.265 but so far that has been untested on any machine here. H.264 works great with everything I've thrown at it. Also I believe the end result is less bloated than H.265 and like you say your laptop has no issues with it.

Life is good,
Maurice

... Eþel byþ oferleof æghwylcum men.
Home is very dear to every man.
--- GNU bash, version 5.1.8(1)-release (x86_64-motorshed-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

-={ 2021-06-12 23:20:41.269312845+00:00 }=-

Hey Maurice!

Here is even a better way to find out what codecs mplayer supports'

$ mplayer -vc help

or -va for audio codecs. For this particular discussion try this;

$ mplayer -vc help | grep h26.
geoh264 vfw working GeoCodec h264 [GX264.dll]
ffh264 ffmpeg working FFmpeg H.264 [h264]
ffh264vdpau ffmpeg working FFmpeg H.264 (VDPAU) [h264]
ffh264crystalhd ffmpeg working FFmpeg H.264 (CrystalHD) [h264_crystalhd]
ffh264vda ffmpeg working FFmpeg H.264 (VDA) [h264_vda]
geoavc vfw working GeoCodec h264 AVC [GXAVC.dll]
ffi263 ffmpeg working FFmpeg I263 [h263i]
ffh263 ffmpeg working FFmpeg H.263+ [h263p]
ffzygo ffmpeg untested FFmpeg ZyGo [h263]
h263xa xanim crashing XAnim's CCITT H.263 [vid_h263.xa]
ffh261 ffmpeg working CCITT H.261 [h261]
h261xa xanim problems XAnim's CCITT H.261 [vid_h261.xa]
m261 vfw untested M261 [msh261.drv]
qth263 qtvideo crashing Win32/QuickTime H.263 [QuickTime.qts]
vssh264 dshow working VSS H.264 New [vsshdsd.dll]
vssh264old vfw working VSS H.264 Old [vssh264.dll]

No H.265 which we already knew but now extra confirmation as well as a bunch I've never even heard of.

Life is good,
Maurice

... Weorða ðe selfne godum dædum, ðenden ðin God recce.
Bring honour to yourself with good deeds, while God guides you.
--- GNU bash, version 5.1.8(1)-release (x86_64-motorshed-linux-gnu)
* Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)

-={ 2021-06-12 22:48:47.304573427+00:00 }=-

Make sure your player has H.265 capabilities.

$ ldd /usr/bin/mplayer | grep lib.26.
libx264.so.161 => /usr/lib/libx264.so.161 (0x00007fc80c9f2000)

$ ldd /usr/bin/ffmpeg | grep lib.26.
libx264.so.161 => /usr/lib/libx264.so.161 (0x00007fd9a99f9000)
libx265.so.192 => /usr/lib/libx265.so.192 (0x00007fd9a9471000)

My video player of choice is vlc. Issuing the ldd command above against its binary yields no results, but I know it will play back the 264 video. OTOH, running the above command against mpv yields results that would indicate that it does support 265 but it won't play the video back correctly, either.

As shown above mplayer is H.264 capable while ffmpeg can handle both. I believe mplayer can be built to use H.265 but so far that has been untested on any machine here. H.264 works great with everything I've thrown at it. Also I believe the end result is less bloated than H.265 and like you say your laptop has no issues with it.

I think you have that last bit re:bloat backwards. The same size video file that will hold nearly 20 minutes when H.265 is enabled will only hold 3 minutes of video if H.264 mode is used. That is why I am trying to use it. H.264 fills up a 64GB SD card in less than 3 hours. It takes well over 5 hours to fill it when using 265.

Those times are when shooting video at 1080p and 90fps.

Mike
#
--- SBBSecho 3.12-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)

Hello Mike!

13 Jun 2021 16:24, Mike Powell wrote to Maurice Kinal:

Those times are when shooting video at 1080p and 90fps.

Huawei P40 Pro, Huawei P30 Pro both have hardware 265, and both can play well in 60fps via usb type-c hdmi adaptor, i have one of them :)

no problem running in desktop mode either, just add bluetooth mouse & keyboard to get a real pc

anything over 60fps is real gamer, and battery drainer


Regards Benny

... too late to die young :)
--- Msged/LNX 6.1.2 (Linux/5.12.10-gentoo-dist (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)

-={ 2021-06-14 01:42:56.429351293+00:00 }=-

Hey Mike!

My video player of choice is vlc.

It does get around. I am unsure how to get vlc to report what codecs it has available to it but have heard that H.265 is possible. As of this writing I cannot say the same for mplayer which is what I am using here.

I think you have that last bit re:bloat backwards.

That is entirely possible. I am just going by a conversion I did once using ffmpeg comparing H.264 with H.265 output.

The same size video file that will hold nearly 20 minutes when
H.265 is enabled will only hold 3 minutes of video if H.264 mode
is used. That is why I am trying to use it.

I am guessing both were created by the camera.

For the record 'ffmpeg -codecs' reports this interesting line in it's output;
DEV.L. hevc H.265 / HEVC (High Efficiency Video Coding) (decoders: hevc hevc_v4l2m2m ) (encoders: libx265 hevc_v4l2m2m )

I believe libx265 is used by vlc as well.

Life is good,
Maurice

... Jag har ekorrar i mina byxor!
--- GNU bash, version 5.1.8(1)-release (x86_64-motorshed-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Huawei P40 Pro, Huawei P30 Pro both have hardware 265, and both can play well
60fps via usb type-c hdmi adaptor, i have one of them :)

no problem running in desktop mode either, just add bluetooth mouse & keyboard
o get a real pc

anything over 60fps is real gamer, and battery drainer

I will try lowering the fps and see if that makes a difference!

Mike


* SLMR 2.1a * Squirt guns don't soak people, People soak people.
--- SBBSecho 3.12-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)

For the record 'ffmpeg -codecs' reports this interesting line in it's output;
DEV.L. hevc H.265 / HEVC (High Efficiency Video Coding) (deco
rs: hevc hevc_v4l2m2m ) (encoders: libx265 hevc_v4l2m2m )

I believe libx265 is used by vlc as well.

It mentions DEV.L. In addition to lowering the fps to 60, I may also try installing the libx265 dev library and see if that changes anything.
Thanks!

Mike


* SLMR 2.1a * I am Drunk of Borg. Resistance is floor tile!
--- SBBSecho 3.12-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)

Hello Mike!

14 Jun 21, Mike Powell wrote to BENNY PEDERSEN:

anything over 60fps is real gamer, and battery drainer

I will try lowering the fps and see if that makes a difference!

Could you check the hardware specs fulfilling the h265 requirements?

Once i had a system without PAE that fails to run a newer operating system.

I would assume that a 7 times better compression ratio would require more calculating power for decompression. The bottleneck could be the hardware itself with no relation to the codecs/drivers.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)