The 2160p file is good because is showed well if I connect the disk to a USB
input of my TV, a SONY BRAVIA, but I prefer the functionalities
of VLC player rather that those of TV interface.
Here the captured screen of VLC 'Settings' and 'Statistic':
https://www.dropbox.com/s/7c3hcru9zwi70le/Codec.png?dl=0
Hi,
I have some problems playing files with 4k resolution with VLC (or also Kaffeine) with a Raspberri pi4.
The audio works well, but the video is always all black.
At the beginning I had setting the screen resolution to 1920 x 1080. Afterwards I have changed screen resolution to 3960 x 2160, the pi4 show
well
the desktop and icons but not 2160p files.
When I try to play a HEVC x265 2160p file with any resolution, VLC show always a
black screen, while with a Full HD 1080p file it show well the footage.
The 2160p file is good because is showed well if I connect the disk to a
USB
input of my TV, a SONY BRAVIA, but I prefer the functionalities
of VLC player rather that those of TV interface.
Here the captured screen of VLC 'Settings' and 'Statistic':
https://www.dropbox.com/s/7c3hcru9zwi70le/Codec.png?dl=0
https://www.dropbox.com/s/in0j7au6rmoa0p0/Statistics.png?dl=0
Note that the number in the red frame always increases.
Can anyone help me?
On Sun, 05 Sep 2021 16:44:57 +0200, SB <stNOOObenevSPAM@tin.it> declaimed
the following:
The 2160p file is good because is showed well if I connect the disk to a USB
Actual spinning disk? Or are you using "disk" for a flash drive?
input of my TV, a SONY BRAVIA, but I prefer the functionalities
of VLC player rather that those of TV interface.
Is there anything else using the USB ports of the R-Pi. Are you using
USB2 or USB3 port? Is the device even rated for USB3 speeds? {At least the
4B has a real Ethernet, not a hidden Ethernet<>USB chip}
What else is running on the R-Pi?
That is NOT showing a "2160p" file... If anything, it is a 1600p30 (if
not 1600i30; suspect p30 as it says "frame rate" not "field rate") -- the >term "2160p" refers specifically to a video with a pixel height of 2160 >lines, regardless of width.
I also noticed that with 3960 x 2160 screen during the remote connection with Anydesk the mouse is slow and the percentage of CPU is over 60-70% with only the
desktop active.
SB wrote on 06-09-2021 at 10:26:
I also noticed that with 3960 x 2160 screen during the remote connection with
Anydesk the mouse is slow and the percentage of CPU is over 60-70% with only the
desktop active.
Normal 4k resolution is 3840x2160 (not 3960!), that shouldn't be a
problem for a Pi 4. You can even enable 4k @ 60 fps mode, if your
monitor/tv supports it. Look at the configuration program in the menu or
in the Terminal: sudo raspi-config. Best leave it at 30 fps for
compatibility and a little more performance headroom, though. Also, only
one of the hdmi ports can do 60 fps.
The ssd should be able to handle this easily. There have been reports of
slow external ssd's, depending on the chipset of the interface
apparently. I don't know details, have a look at the forums on the rpi >website. My Samsung T5 works well.
VLC on the Pi doesn't have hardware acceleration, that's probably the >limiting factor. Try playing the file with omxplayer from the command
line (Terminal), that's the only player with hardware accel. as far as I >know.
Also, the HW accel. is only for h.265 encoded video, I think? Not h.264.
But the Pi 4 should be fast enough to do that in software. Maybe not in
4k, though? I don't know.
After some search it seems that VLC don't use hardware acceleration with the GPU
and hardware for HEVC x265 decoding.
https://www.raspberrypi.org/forums/viewtopic.php?t=253359 https://www.raspberrypi.org/forums/viewtopic.php?f=38&t=246837
It seems that the solution can be Libreelec with Kodi, but Libreelec is a media
player dedicated os, I'd rather stay on Raspbian os.
SB <stNOOObenevSPAM@tin.it> wrote:
After some search it seems that VLC don't use hardware acceleration with the GPU
and hardware for HEVC x265 decoding.
Yes, that's what I said. Not for anything.
https://www.raspberrypi.org/forums/viewtopic.php?t=253359
https://www.raspberrypi.org/forums/viewtopic.php?f=38&t=246837
It seems that the solution can be Libreelec with Kodi, but Libreelec is a media
player dedicated os, I'd rather stay on Raspbian os.
Yes, that's because behind the scenes it uses the only hardware accelerated >video player on the Pi, which I also mentioned: omxplayer.
So you already
have the solution, you just need to use the terminal. Or write your own >GUI/web interface around it, if you don't like Libreelec.
Well, it seems I was behind the times (I never play videos with my
Pi's). From https://github.com/popcornmix/omxplayer :
"Note: omxplayer is being deprecated and resources are directed at
improving vlc.
This is due to: omxplayer uses openvg for OSD and subtitles which isn't supported on Pi4. omxplayer uses openmax which has been deprecated for a
long time and isn't supported with 64-bit kernels. omxplayer does not
support software decode omxplayer does not support advanced subtitles omxplayer does not support playback from ISO files. omxplayer does not integrate with the X desktop
Please try using vlc. If there are features of omxplayer that vlc does
not handle then try reporting here."
So, VLC is the official way forward. If it doesn't work, ask in the
official forums, I guess.
A. Dumas wrote on 07-09-2021 at 09:36:
Well, it seems I was behind the times (I never play videos with my
Pi's). From https://github.com/popcornmix/omxplayer :
"Note: omxplayer is being deprecated and resources are directed at
improving vlc.
This is due to: omxplayer uses openvg for OSD and subtitles which isn't
supported on Pi4. omxplayer uses openmax which has been deprecated for a
long time and isn't supported with 64-bit kernels. omxplayer does not
support software decode omxplayer does not support advanced subtitles
omxplayer does not support playback from ISO files. omxplayer does not
integrate with the X desktop
Please try using vlc. If there are features of omxplayer that vlc does
not handle then try reporting here."
So, VLC is the official way forward. If it doesn't work, ask in the
official forums, I guess.
BUT! The developer(s?) seem to be stuck. No hardware helpeing at 4k,
yet. See https://github.com/RPi-Distro/vlc/issues/47
(*) Shame that when analog TV in the USA was disbanded, a decision wasn't >taken to make the digital version exactly 30 fps (or 24 fps for 3:2 pulldown >film), and that the color NTSC "fix" of changing 30 to 29.97 persists ;-)
In article <sh2uej$d5m$1@dont-email.me>, NY <me@privacy.invalid> wrote:
(*) Shame that when analog TV in the USA was disbanded, a decision wasn't >>taken to make the digital version exactly 30 fps (or 24 fps for 3:2 >>pulldown
film), and that the color NTSC "fix" of changing 30 to 29.97 persists ;-)
I suspect that would've made those cheap (free in some cases?) converter boxes to bring analog-only TVs into the digital era not-so-cheap, as they would've needed some way to convert 30-fps input to 30000/1001-fps output.
Was 625/25 lucky, or was the ratio of CSC to line frequency chosen
carefully to avoid a collision with sound, given NTSC's problems?
On 11/09/2021 17:48, NY wrote:
Was 625/25 lucky, or was the ratio of CSC to line frequency chosen
carefully to avoid a collision with sound, given NTSC's problems?
The urban legend has it that coming as it did about the time that
digital electronics and computing were coming into TV that it was
chosen because 405 in decimal becomes 625 when converted to octal.
On Sat, 11 Sep 2021 19:22:34 +0100
gareth evans <headstone255@yahoo.com> wrote:
On 11/09/2021 17:48, NY wrote:
Was 625/25 lucky, or was the ratio of CSC to line frequency chosen
carefully to avoid a collision with sound, given NTSC's problems?
The urban legend has it that coming as it did about the time that
digital electronics and computing were coming into TV that it was
chosen because 405 in decimal becomes 625 when converted to octal.
Ummm. Nope.
625 line TV started in the early 1960s. As a TV repairman, I was watching
the
BBC2 trade tests in the mid 1960s. I didn't come across any digitisation
till
the 1970s, by which time the TV rental business was collapsing.
The PAL system did learn a lot from the NTSC mistakes. The real killer was swapping the phase of the colour sub carrier on alternate lines. The
result was
that any phase shift giving a drift towards red on one line, would be
towards
green on the next line, and your brain averages these out so you don't
notice
anything wrong :)
I believe that some TVs displayed the lines as they were received (one with
a positive hue error and the next with a negative hue error of the same >value) and relied on the brain to average it. Other more elaborate ones used >a one-line delay and electronically averaged the two lines so the same
colour info (with no hue error) was output on both lines.
I have downloaded Libreelec and I will try it on a dedicated SD,
Il giorno Tue, 07 Sep 2021 18:51:16 +0200, SB ha scritto:
I have downloaded Libreelec and I will try it on a dedicated SD,
After a week of usage, I can say that 4K footages are played perfectly on Kodi
on LibreElec os.
Moreover my SONY TV remote control is easily integrated with Librelec, probably
using the I2C interface present in HDMI cable.
There are a world of plugins, and is pretty usable, afterall a good acquisition.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 371 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 37:33:34 |
| Calls: | 7,932 |
| Calls today: | 2 |
| Files: | 12,998 |
| Messages: | 5,805,631 |
