Damn good that you tell me that, every time I start a video it kills my Beamer, and I did not know why I had to deactivate that to watch again, but now all works as far as I can tell atm. thanks. Thanks for the hint.
I just updated a Raspberry Pi 2 to this release (it was on 19.1.0-14 before), and thereâs now quite a bit of stuttering, enough that itâs unwatchable. I tried to roll back to the previous package versions, but these donât seem to be available under Index of /osmc/osmc/apt anymore. Is there somewhere else I can get the previous packages?
i have the same issue , hdmi connected Panasonic AE6000 projector.
After plugging power in vero4k, red light stays for cca 2 seconds and then turns off. vero4k is not available neither on network, PJ have no signal.
Unplugging power and HDMI, replugging back just power and after some time HDMI allows vero4k to boot normally.
No HDMI switch/receiver used just straight cable to PJ.
I am investigating this. We might need to bisect some commits - do you know how to use SSH?
What/who is this in reply to?
1 Like
in my case yes, i use ssh daily
Canât SSH in, itâs really not starting. (first thing I tried)
Using SSH is no problem here too.
It was to @tomas1.
Iâd suggest a new post with logs regarding your situation. Alternatively you can downgrade via Download - OSMC.
Sam
Thanks for the continued releases and updates, however this one seems to have introduced playback issues with certain 4K/HEVC MKV titles with embedded DV FEL.
These file used to play fine previously as regular HDR10 content but now it only plays the audio and the video only show frames every 10 seconds or so.
OSD debug shows the VQ at 0%, 0Mbps, quickly spiking up to 99%, ~200+Mbps in a continuous cycle.
An sample of the mediainfo for the troublesome video:
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 41 min
Bit rate : 68.9 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.347
Stream size : 48.7 GiB (94%)
Language : English
Default : No
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0010 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Level : 214 cd/m2
Original source medium : Blu-ray
Another similar HDR10 w/embedded DV FEL file plays fine but has similar mediainfo:
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 16 min
Bit rate : 82.6 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.415
Stream size : 78.9 GiB (97%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Anyone able to test and confirm if this is not specific to my setup?
Same problem here 
Connected to Sony Bravia KD-65XF9005 via receiver Sony STR-DH590
I think I hit the same thing and found where to look for the reason (and, in my case, a workaround). It seems to have to do with the HDMI output detection.
Hartmut
the problem is that when projector is plugged into vero, the vero wonât boot (nothing on screen (no signal), not even available on network, so i do not know how i would provide logs/debug output when vero is in this state.
I have just found out that vero wonât boot even if PJ is in standby. When i turn off PJ completely, vero can boot normally and turning on the PJ after vero boots works fine.
This is what I can see in dmesg after plugging in the PJ when vero is already booted:
Nov 27 12:26:56 vero kernel: hdmitx: system: irq 80000002 0
Nov 27 12:26:56 vero kernel: hdmitx: hw: HDMI hpd locked
I have now also tried workaround by forcing resolution mentioned by Hartmut, but it did not help:
sudo fw_setenv hdmimode 1080p60hzforce
sudo fw_setenv outputmode 1080p60hzforce
reboot
thx
The force option doesnât seem to be working. I thought Sam had fixed it but it needs another look. So reboot without HDMI attached and
sudo fw_setenv hdmimode 1080p60hz
I may be wrong but I think outputmode refers only to composite output so should be left as
sudo fw_setenv outputmode 576cvbs
Setting it to 1080p60hz fixes my problem, though it was set to this before the update. It reboots normally now.
Unfortunately we donât support playback of DV at this time.
Kodi has a newer version of ffmpeg, which could introduce some regressions. If this is the case I am sure it will be identified promptly.
Correct.
When will it be available for download in the OSMC-Installer?
Player settings - > disable âonly allow acceleration for HEVCâ
3 Likes
You can already download and update. Disk images will come later in a few days.