No DV options at all.
Dovi ko is located in configfiles folder .
Where is storage? If I open coreelec from my PC a dont see any folder called storage.
1 Like
FYI I didn’t get a chance to pull this change.
/storage/dovi.ko Will work
But these two won’t
/storage/.config/dovi.ko
/flash/dovi.ko
So what should I do to put Dovi ko in storage?
Playing movies with your build is mostly normal, some are not, but when you stop playing, it’s normal to play again. Great improvement
My TV is sony 95h and only supports LLDV
1 Like
Thank you for the tip. It works now
Can do this as well:
Edit samba.conf in config and add this:
[Storage]
path = /storage
available = yes
browsable = yes
public = yes
writable = yes
root preexec = mkdir -p /storage
I think most of the issues with DV material mainly comes form the way it was encoded. Looks like if Handbreak (>v1.7.2) is invovlved in the process, making most of the nuisance, at least here for me.
Tried with Dune Part 1, transcoded using makeMKV, started started alomost instantly. But then it pauses for few seconds in every minute or so, with this error:
error <general>: CAMLCodec::GetPicture: time elapsed since last frame: 5319ms (11:Resource temporarily unavailable)
Amuyone experiencing the same thing?
https://paste.coreelec.org/iZ0vb0
-S
I get some oddity on Framestor’s “Special Edition” of the Abyss.
Things could be playing well for 5-10 min, but then some weird glitch where video glitches but audio keeps going then video “catches up” by playing in double time while audio just continues. Similar to MEL glitch before, but much more intermittent (wait minutes before an issue happens).
EDIT: I do see this error in my logs which is the same as above
2024-03-17 10:13:36.848 T:4977 error <general>: CAMLCodec::GetPicture: time elapsed since last frame: 6777ms (11:Resource temporarily unavailable)
and the below errors which look more severe:
2024-03-17 10:26:15.504 T:6521 error <general>: _________________________________________________________________________________
2024-03-17 10:26:15.504 T:6521 error <general>: script.plex: ERROR:
2024-03-17 10:26:15.504 T:6521 error <general>: Traceback (most recent call last):
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.urllib3/lib/urllib3/connectionpool.py", line 536, in _make_request
2024-03-17 10:26:15.504 T:6521 error <general>: response = conn.getresponse()
2024-03-17 10:26:15.504 T:6521 error <general>: ^^^^^^^^^^^^^^^^^^
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.urllib3/lib/urllib3/connection.py", line 461, in getresponse
2024-03-17 10:26:15.504 T:6521 error <general>: httplib_response = super().getresponse()
2024-03-17 10:26:15.504 T:6521 error <general>: ^^^^^^^^^^^^^^^^^^^^^
2024-03-17 10:26:15.504 T:6521 error <general>: File "/usr/lib/python3.11/http/client.py", line 1374, in getresponse
2024-03-17 10:26:15.504 T:6521 error <general>: File "/usr/lib/python3.11/http/client.py", line 318, in begin
2024-03-17 10:26:15.504 T:6521 error <general>: File "/usr/lib/python3.11/http/client.py", line 279, in _read_status
2024-03-17 10:26:15.504 T:6521 error <general>: File "/usr/lib/python3.11/socket.py", line 706, in readinto
2024-03-17 10:26:15.504 T:6521 error <general>: File "/usr/lib/python3.11/ssl.py", line 1278, in recv_into
2024-03-17 10:26:15.504 T:6521 error <general>: File "/usr/lib/python3.11/ssl.py", line 1134, in read
2024-03-17 10:26:15.504 T:6521 error <general>: TimeoutError: The read operation timed out
2024-03-17 10:26:15.504 T:6521 error <general>:
2024-03-17 10:26:15.504 T:6521 error <general>: The above exception was the direct cause of the following exception:
2024-03-17 10:26:15.504 T:6521 error <general>:
2024-03-17 10:26:15.504 T:6521 error <general>: Traceback (most recent call last):
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.requests/lib/requests/adapters.py", line 486, in send
2024-03-17 10:26:15.504 T:6521 error <general>: resp = conn.urlopen(
2024-03-17 10:26:15.504 T:6521 error <general>: ^^^^^^^^^^^^^
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.urllib3/lib/urllib3/connectionpool.py", line 844, in urlopen
2024-03-17 10:26:15.504 T:6521 error <general>: retries = retries.increment(
2024-03-17 10:26:15.504 T:6521 error <general>: ^^^^^^^^^^^^^^^^^^
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.urllib3/lib/urllib3/util/retry.py", line 470, in increment
2024-03-17 10:26:15.504 T:6521 error <general>: raise reraise(type(error), error, _stacktrace)
2024-03-17 10:26:15.504 T:6521 error <general>: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.urllib3/lib/urllib3/util/util.py", line 39, in reraise
2024-03-17 10:26:15.504 T:6521 error <general>: raise value
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.urllib3/lib/urllib3/connectionpool.py", line 790, in urlopen
2024-03-17 10:26:15.504 T:6521 error <general>: response = self._make_request(
2024-03-17 10:26:15.504 T:6521 error <general>: ^^^^^^^^^^^^^^^^^^^
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.urllib3/lib/urllib3/connectionpool.py", line 538, in _make_request
2024-03-17 10:26:15.504 T:6521 error <general>: self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.urllib3/lib/urllib3/connectionpool.py", line 370, in _raise_timeout
2024-03-17 10:26:15.504 T:6521 error <general>: raise ReadTimeoutError(
2024-03-17 10:26:15.504 T:6521 error <general>: urllib3.exceptions.ReadTimeoutError: AsyncHTTPSConnectionPool(host='192-168-4-21.0ea8e66afe034a52b8064484ae0ea8b6.plex.direct', port=32400): Read timed out. (read timeout=5.0(5.0))
2024-03-17 10:26:15.504 T:6521 error <general>:
2024-03-17 10:26:15.504 T:6521 error <general>: During handling of the above exception, another exception occurred:
2024-03-17 10:26:15.504 T:6521 error <general>:
2024-03-17 10:26:15.504 T:6521 error <general>: Traceback (most recent call last):
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.plexmod/lib/_included_packages/plexnet/http.py", line 131, in _startAsync
2024-03-17 10:26:15.504 T:6521 error <general>: res = self.session.get(self.url, timeout=timeout, stream=True)
2024-03-17 10:26:15.504 T:6521 error <general>: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.requests/lib/requests/sessions.py", line 602, in get
2024-03-17 10:26:15.504 T:6521 error <general>: return self.request("GET", url, **kwargs)
2024-03-17 10:26:15.504 T:6521 error <general>: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.requests/lib/requests/sessions.py", line 589, in request
2024-03-17 10:26:15.504 T:6521 error <general>: resp = self.send(prep, **send_kwargs)
2024-03-17 10:26:15.504 T:6521 error <general>: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.requests/lib/requests/sessions.py", line 703, in send
2024-03-17 10:26:15.504 T:6521 error <general>: r = adapter.send(request, **kwargs)
2024-03-17 10:26:15.504 T:6521 error <general>: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-03-17 10:26:15.504 T:6521 error <general>: File "/storage/.kodi/addons/script.module.requests/lib/requests/adapters.py", line 532, in send
2024-03-17 10:26:15.504 T:6521 error <general>: raise ReadTimeout(e, request=request)
2024-03-17 10:26:15.504 T:6521 error <general>: requests.exceptions.ReadTimeout: AsyncHTTPSConnectionPool(host='192-168-4-21.0ea8e66afe034a52b8064484ae0ea8b6.plex.direct', port=32400): Read timed out. (read timeout=5.0(5.0))
2024-03-17 10:26:15.504 T:6521 error <general>: _________________________________________________________________________________
2024-03-17 10:26:15.504 T:6521 error <general>: `
2024-03-17 10:26:20.608 T:6389 info <general>: CVideoPlayerAudio::Process - stream stalled
2024-03-17 10:26:30.497 T:3844 warning <general>: ActiveAE - large audio sync error: -9671.264773
2024-03-17 10:26:30.498 T:3844 warning <general>: ActiveAE - large audio sync error: -9671.470148
2024-03-17 10:26:30.498 T:3844 warning <general>: ActiveAE - large audio sync error: -9543.668481
...
I can’t say for sure this timestamp corresponded to exactly when I experienced the playback issue, but think it is 10:26 one.
I see exactly the same pattern - audio keeps rolling whilst video gets paused. Abyss is the next in my list to try.
Can someone tell me what version of CoreELEC I have? I think I uploaded this version at the beginning.
CoreELEC-Amlogic-ne.aarch64-21.0-Omega_nightly_20231116-Generic.img
I would like to have x64 versions with DV support.
I read that there are versions “ne, ng and ng-dv”.
Looking at the file I uploaded, it seems that I have the ne version, but after execution
cat /etc/*-release
I think I have ng
CoreELEC:~ # cat /etc/*-release
NAME="CoreELEC"
VERSION="21.0-Omega_nightly_20240316"
ID="coreelec"
VERSION_ID="21.0"
PRETTY_NAME="CoreELEC (official): 21.0-Omega_nightly_20240316"
HOME_URL="https://coreelec.org"
BUG_REPORT_URL="https://github.com/CoreELEC/CoreELEC"
BUILD_ID="714e3fe0ee55ce1490d634a764908222523538bf"
LIBREELEC_ARCH="Amlogic-ng.arm"
LIBREELEC_BUILD="official"
LIBREELEC_PROJECT="Amlogic-ce"
COREELEC_ARCH="Amlogic-ng.arm"
COREELEC_BUILD="official"
COREELEC_PROJECT="Amlogic-ce"
COREELEC_DEVICE="Amlogic-ng"
BUILDER_NAME="TheCoolest"
On the Player-LED DV front, it seems a bit jumpy. Changes, but no picture with cd/cs set to auto. Playing the same DV file as previous. Changing resolution after changing settings to apply.
First boot after applying the patch, it seemed to run at 12-bit 4:4:4. It did not like that, no picture. https://paste.coreelec.org/Z8y5vu
Went back to forced 4:2:2, and picture returned. I then went back to auto cd/cs, and ever since it now goes back to 10-bit 4:2:2 (which is the same as previous to patch). I rebooted to try and make sure nothing was stuck, but same results. https://paste.coreelec.org/dB3TCF
Edit: That original DV test file was Dune, and like others have said, maybe that’s an outlier. Gave one of Framestor’s Incredibles 2 DV files a try, auto cd/cs, and that worked no problem. Even had less to 0 delay at the start: https://paste.coreelec.org/CupPnV (MediaInfo: Imgur: The magic of the Internet)
With a very small handful of exceptions , Disney does not master animated films (or dang near any full Disney film) in DV on disc. Including Incredibles 2. So if if this is a hybrid remux of any sort I strongly suggest that everyone takes a grain of salt on the playability of any of these titles.
Tbf for anything coming from originally disc we really should only be focusing on playability for MEL or FEL titles. And not these bizarre Frankensteined DV hybrid files I’m seeing more and more of, recently. Either a true profile 5, 7 or 8 title and not one stitched together from multiple different profiles.
Also, a screenshot of mediainfo that includes the software and versions used to create the file would also be helpful.
2 Likes
It looks like you are experiencing NFS protocol errors:
https://www.ietf.org/rfc/rfc1813.txt
NFS3ERR_NOENT
No such file or directory. The file or directory name
specified does not exist
Possibly permissions issues.
Makes total sense. The more I’m on here the more I see how nuanced DV is even just a bit under the covers. Will try to keep that in mind for any future feedback. For completeness, the upper part of those screenshots 
The problematic Dune file: Imgur: The magic of the Internet
Incredibles 2 file: Imgur: The magic of the Internet
Yeah Dune is a title that is seemingly a one off. I think everyone has issues with it in some form or another. I personally think the UHD master has some sort of formatting error/glitch at the beginning.
With wait delay of 24, and especially at the beginning of the file, the DV mode setting won’t even settle down until the WB studio animation kicks in. It also triggers at least 3 cs/cd changes. It skips about 20-24 frames before it settles down (ctrl-shift o) to see). However the moment the WB Animation plays it’s smooth after that. Oddly enough that title is more consistently playable resumed than from the beginning lol.
A hybrid is simply P8 DV, nothing wrong with it and vast majority of cases superior to the vanilla disk with no DV. Star Wars, HP, etc. Saying we shouldn’t test hybrids is basically saying to ignore real-world P8 use cases. If there are no problems playing the film on Shield Pro/Zidoo, then CE should also have no problems playing it.
As far as quality goes, I believe Framestor has remuxed every single UHD disk in existence (~1300). Their hybrids are technically sound, no question about that. In some cases they shouldn’t have made the hybrid, but even those are still technically correct.
Besides, the majority of films (60%) with HYBRID tags aren’t even DV hybrids; they’re audio hybrids since UHD disks frequently have more compressed audio vs other sources. So even judging by the filename isn’t accurate:
That said Abyss is just a regular film.
2 Likes
Is it possible to get a standalone apk of this with CMv4.0 to test on android? Thanks
Btw dmesg log output would be preferred.
with dmesg filtered, these are the pertinent things you should see:
dmesg| grep 'colour\|line\|tunnel_mode\|!!!\|forced\|auto\|cd\|sdr\|VSIF\|hdr10\|tunnel\|vsif'
[ 7429.286875@1]- hdmitx: fs = 7, cd = 6, tmds_clk = 594000
[ 7429.463490@4]- hdmitx: hdmitx: display colour subsampling is auto set to YUV444 (VIC: 93)
[ 7429.463492@4]- hdmitx: hdmitx: display colourdepth is auto set to 12 bits (VIC: 93)
[ 7429.535269@0]- hdmitx: hw: config hdmitx IP vic = 93 cd:6 cs: 2
[ 7429.545404@0]- hdmitx: fs = 7, cd = 6, tmds_clk = 296703
[ 7429.615973@0]- hdmitx: hdmitx_set_hdr10plus_pkt: null vsif
[ 7430.759486@0]- hdmitx: hdmitx: display colour subsampling is auto set to YUV444 (VIC: 93)
[ 7430.759489@0]- hdmitx: hdmitx: display colourdepth is auto set to 12 bits (VIC: 93)
[ 7430.831306@0]- hdmitx: hw: config hdmitx IP vic = 93 cd:6 cs: 2
[ 7430.841459@0]- hdmitx: fs = 7, cd = 6, tmds_clk = 296703
[ 7430.841519@0]- hdmitx: fs = 7, cd = 6, tmds_clk = 296703
[ 7433.720312@0]h hdmitx: hdmitx_set_vsif_pkt: type=5, tunnel_mode=0, signal_sdr=0
[ 7433.786189@1]- hdmitx: hdmitx: display colour subsampling is forced to YUV422 by Dolby Vision tunneling
[ 7433.786191@1]- hdmitx: hdmitx: display colour subsampling is auto set to YUV422 (VIC: 93)
[ 7433.786193@1]- hdmitx: hdmitx: display colourdepth is forced to 12 bits because of Dolby Vision sink capability
[ 7433.786195@1]- hdmitx: hdmitx: display colourdepth is auto set to 12 bits (VIC: 93)
[ 7433.855293@1]- hdmitx: hw: config hdmitx IP vic = 93 cd:6 cs: 1
[ 7433.865503@1]- hdmitx: fs = 7, cd = 4, tmds_clk = 296703
[ 7434.787122@0]h hdmitx: hdmitx_set_hdr10plus_pkt: null vsif
[ 7434.788314@0]h hdmitx: hdmitx_set_vsif_pkt: type=4, tunnel_mode=0, signal_sdr=0
[ 7436.327292@0]h hdmitx: hdmitx_set_vsif_pkt: type=0, tunnel_mode=0, signal_sdr=0
[ 7436.327300@0]h hdmitx: hdmitx: Dolby VSIF, VEN_DB2[3]) = 0
[ 7436.535774@0]h hdmitx: hdmitx_set_vsif_pkt: type=0, tunnel_mode=0, signal_sdr=1
[ 7436.535781@0]h hdmitx: hdmitx: Dolby VSIF, VEN_DB2[3]) = 0
[ 7436.535790@0]h hdmitx: hdmitx: Dolby VSIF, switching signal to SDR
[ 7436.535799@0]h hdmitx: vic:93, cd:4, cs:2, cr:1
[ 7444.710666@0]h hdmitx: hdmitx_set_vsif_pkt: type=5, tunnel_mode=0, signal_sdr=0
[ 7445.714241@0]h hdmitx: hdmitx_set_hdr10plus_pkt: null vsif
[ 7445.715337@0]h hdmitx: hdmitx_set_vsif_pkt: type=4, tunnel_mode=0, signal_sdr=0
It sets it on the initial YUV444 12-bit (not correct for LLDV) because for the first two switches (IIRC one for the overall mode, and then the refresh rate switch) Kodi has not yet set the DV flags, so it treats it like any other video. Not until a few seconds later it switches correctly to 4:2:2 12-bit for LLDV. Right about when the WB animation plays. You may have seen another DV logo pop-up on your TV (LG TV definitely have this) right when the animation plays. From what I can tell this is related. Also in LLDV, you may actually notice distorted colors, for the first few seconds. I only noticed this, just this evening because my receiver popped up an OSD over the other black intro screen. That initial setting is close enough to the proper TV-led mode setting so you don’t notice the distorted colors.
Similar behavior happens with TV-led, albeit a third switch to YUV444 8-bit (btw this is intentional–RGB444 for some reason causes only black screens to show and my TV and HDFury correctly report RGB with this YUV444 mode is set).
I noticed that too but it dorsn’t make much sense to me. I’m running this NFS server for over 4 yrs. now and my other CE, running v9.2.8 on U9-H, runs without any error using the very same server. Alos, if it was a permission error, it wouldn’t start playing in the first place, right?
I wonder, if anything changrd in CE, the part of the code that deals with NFS share. Tried to look into the code but couldn’t figure out.