It all depends what you want to achieve in the end. If one box is running 24/7, then you could also make use of UPnP, with all its pros and cons.
If you want something like "stopping the video in the living room and continue watching it from the same position in the bedroom", them Emby or a MySQL database might be the way to go
Emby should be available as a docker. If not then it can be easily installed as such.
Make sure the HDMI cable you are using is a HDMI 2.0 cable
If that's already the case, then I'm out of ideas.
I guess you won't have a real benefit of HDMI 2.1. We discussed the stuff which is supported by HDMI 2.1 and for the normal usage and by looking at your setup, I would say you don't need to wait for that. 35W would be nice, indeed.
HDMI 2.0b supports 4k60 and unless you need more resolution (where we currently have no content for) or higher fps (your eye is not capable of recognizing nearly anyything >100Hz, IIRC) I don't see the benefit.
The only interesting option is EARC if Netflix supports Atmos and you will use that with your TV app and would like to have that at your AVR.
But as your AVR isn't capable of atmos at all, I also don't see the benefit in buying something with HDMI 2.1
Did I miss something?
Yeah, and if you want to have all the benefit of bitstreaming, then I have to say that the RPi3 is not the correct dievice for you. For me it's not the correct device as well as I also like bitstreaming, hence I own something x86. The actual RPi4 should do bitstreaming of HD audio. But that's currently a pretty new product and many tests have to be done. So if you want something that "just works", I can't recommend that.
It's a long log, those lines are all I can find that has anything to do with the SMB.
I can't help much as I don't own a RPi4 yet. But...
- enable debug logging
- disable everything unneded (Live-TV, library update on startup if enabled and such)
- restart kodi / reboot LibreELEC
- reproduce your issue as fast as you can (don't do anything else)
- grab the log
Also please get us some additional outputs
- ip a | pastebinit
- and probably dmesg | pastebinit
I highly guess our devs might need that info if it's not a known issue.
Operation not permitted
is a pretty good indicator for probably a password error. Are you sure you have setup SMB2 shares on your Windows machine? Does the same work with a RPi3? Have you checked the sources or probably tried to re-adding using the "add network connection" option to see if you are able to connect to the shares.
are you sure that the RPi4 is on the same network? If it has static IPs are you also sure it's a different IP from what the RPi3 uses?
oh, then there must be something strange with your logfile if that only shows 2 lines.
I generally thought the log might have over a 1000 lines where we might see way more info than this useless stuff (j/k)
capable of all formats known nowadays
currently not Atmos capable. Just to mention the formats which are "known nowadays". And there won't be an update for it.
same for Dolby TrueHD. DTS HD Master shows up as DTS Sourround.
Yes, the RPi can't handle bitstreaming of HD audio formats. To have the benefit of DTS-HDMA you have to use PCM where Kodi will decode the audio and send it via 8ch-PCM (over HDMI) to the AVR. The AVR will then show "Multichannel". That's expected. Simply use that. I doubt that you will hear the difference anyway as there's none.
As you can read from the settings truehdpassthrough and dtshdpassthrough are set to false and it does not appear in the Settings tab
because the RPi is not capable of.
But then why is DTS HD MA recognized as DTS Sourround by the AVR and not as Multi Channel In (PCM) like the Dolby Formats?
If you play a track containing DTS-HDMA, Kodi will show that in its video OSD. But as the RPi isn't capable of bitstreaming HD audio you will only get the Core of those tracks.
Let's assume you play DTS-HDMA or DTS-HRA. The core of both is "DTS" and that's what you get. The same counts for DolbyTrueHD where you will only get DolbyDigital from your RPi.
If you want more, either get better hardware or use PCM.
The RPi is only capable of bitstreaming DolbyDigital and DTS. That might bring up the question to DD+ again, which I can't answer for sure. But others have already answered in your other thread and confirmed it working.
If you don't get any of them and only see "Multichannel" on your AVR, then simply disable "Sync Playback to display" as that will disable passthrough even if that's enabled in your settings.
The log will tell most
Is it possible to see the full guisettings.xml
If you click on that ^ you will be pointed to:
So, I have a question towards you....what is the bloody point of an error message if you refuse to read it properly
Regarding your initial question about the transition add-on and the settings-dialog:
Have you ever considered to simply configure the add-on to work properly. Why on earth would you think that the same add-on from another source would behave differently? If you would have hit "Yes" on the above dialog, you would have seen that:
Maybe you should learn how to read the messages Kodi shows you. But I even don't think that you will read this posting properly. So don't expect further help in here if you refuse to read.
You all should probably post a debuglog instead of a "me too" posting. We can't help without that log
Not really sure what you mean. None of the addons I installed have anything to do with piracy.
While that might be basically true, we have a clear stance on that:
See the : Piracy Policy
In the end, it's pretty simple. As long as any of those banned add-ons and repos are installed, you won't get any kind of support in here. That's what the rules say. Either deal with it or don't. I don't mind. But don't expect help while those are installed.
You won't blame Firefox as well, only because of its possibility to reach grey-zone media. So you can't also blame Kodi for it to be able to contain banned repos. Anyway, it's our forum and we decide what we support and what not. Please read the rules you accepted and stop attacking staff.
I'm using the same test videos you do and I can't see any problems with it.
Make sure you have
- "sync playback to display" disabled
- "adjust display refreshrate" is set on "star/stop"
- matching whitelist options are set. e. g. 1920*1080: 60, 59.94, 50, 30, 29.97, 25, 24, 23.976 (if available)
If enabled, you don't need the "sync playback to display" option at all. That option is for Kodi on screens which aren't capable of a matching fps (e. g. PC Monitors which tend to support only 60fps). If your TV supports all those fps, the "sync playback to display" option isn't needed anymore.
If you don't set "adjust display refreshrate" to "start/stop" and leave it on off, then Kodi will use the FPS which is generally set to. Means if you set Kodis GUI to use 60fps, every video will be played at that fps, which could also cause stuttering.