Posts by jazzlpunk

    Dear All,

    I´ve noticed that with librespot under libreelec on rpi4b, the sound is by default compressed. I´m not talking about compression as in mp3 or such, but when using a compressor for decreasing the dynamics of the file in order to increase its loudness.

    On some stuff, especially music from before the 90´s, this can have horrible consequences. How do I disable this?

    Please note that the latest available version from the libreelec repository is 9.0.115, and this could be something that has been made optional in later releases. I wouldn´t know how to install newer versions though, so if this is a solution, please advise. I assume that none of the settings in the settings.xml file has any impact on this...
    And, I should add that libreelecs spotify service (which fails to impress in any other way compared to librespot) does NOT add this compression, so it´s not like a thing spotify always does that can´t be turned off.

    Example: spotify:track:5BSkUsTWQWfctzP5EF8XnK - that´s really not how that song should sound!

    I´m playing it now through tuneblade, a decent alternative to play all pc audio through kodi, and this sounds how it should. I think I do recall though that it has some bugs with suddenly stopping to work, so I´d prefer librespot to not use compression.

    Also, tuneblade makes it impossible for me to have a chat over my headset while listening to spotify, since what I´m using here in my living room is a raspberry that´s RDPing into my PC on the 2nd floor, and that solution only allows one audio device, meaning that I´d get the party I´m calling talking through the libreelec raspberry.

    If someone ever comes across this old topic, I´d like to add something that people may not have realized.. It´s in the putty gui´s host field where you want to type root@ip. Then it will prompt for password next. So don´t simply put the ip address in the host field, where you then will be prompted for both login and password. Should you wish to do it that way, then ONLY type root in the loginname field - not the @ip part.

    Code
            <source>
                <name>MEDIA</name>
                <path pathversion="1">smb://user:pass@NAS/MEDIA/</path>
                <allowsharing>true</allowsharing>
            </source>

    I edit /storage/.kodi/userdata/sources.xml directly (not via the GUI) as I find it easier/faster than spelling stuff on a remote with no keyboard and the format is pretty simple to follow ^

    If you're sharing from a machine that uses DHCP make sure you use the hostname (NAS in the example above) else the DB will break when the host changes IP address.

    Cheers, good idea! But since this is a symlink from the raspberry to a shared folder on my windows computer, where login and password is already set, I assume that its the symlink I will be sharing to and this is where I will need a bit of advise. The raspberrys ip on the network is 192.168.178.18, and its hostname is libreelec.

    So am I right that I should not set login and pw since theyre already in the mount, and should I indicate the storage folder or not, and should I use 192.168.178.18, 127.0.0.1 or libreelec (the hostname) in the xml file?

    EDIT: Nevermind, I found out what had to be done: Instead of trying to add the mount the way I previously attempted, I needed to click on "Home folder" and there storage was visible, inside which was the subfolder representing the symlink. Bingo!

    For anyone interested, this looks as follows in the sources.xml file:

    Code
    <source>
                <name>film</name>
                <path pathversion="1">/storage/film6/</path>
                <allowsharing>true</allowsharing>
            </source>

    Not even mentioning smb nor credentials because it´s already setup in the mount file, and neither the raspberrys hostname nor ip are mentioned because of the mount scripts local installation.

    .. and using this technique is even better than NFS with regards to buffering - its not even showing any buffering taking place in the 1st minute as I experienced it with NFS! I guess the buffer settings in my first post helps with that though, not sure what it would be like with the defaults.

    I think I got it right now. Somehow I had done alterations to a copy of the file that I put in the storage folder, so anything I had changed, such as the password was not changed in the mount file that the system uses.

    So I confirmed this to work by in SSH typing ls and it let me view the shares content.

    But I am unsure still of how to add it in kodi. If I set it up as smb://192.168.178.18/storage/film it tells me still that the share does not exist - also if I remove the /storage part.

    Previously, my raspberry pi 3 was running xbian which never had any hiccups (buffering issues) when playing files with a high bitrate via LAN over SMB (like an hour = 6 GB), but with libreelec installed instead on the same raspberry and connected in the same way, I get buffering issues once a minute or more.

    I tried playing the files over NFS which made the buffering less, but certainly still happening. Then I added advancedsettings.xml using the 4th example at HOW-TO:Modify the video cache - Official Kodi Wiki, and bingo: Buffering only occurs in the beginning!

    SMB buffering still is as bad as before though, and I would like to also be able to watch videos with no glitches using this protocol.

    So in this thread (where I have also reported my progress, but thread seems so old that nobody reads it) Advance settings for expanding cache not working.. I saw an advise about using system mounts instead. Not a big operation I thought:

    Code
    # The share we want mount
    What=//192.168.178.10/Film6
    # Where we want mount this share
    Where=/storage/film

    I amended the login and password as well, but I get this when checking status after enabling the mount:

    And I´m also wondering exactly how to make the share pop up in the Kodi menu.. If I add it manually from Kodi like smb://192.168.178.18/storage/film or smb://192.168.178.18/film it tells me that share is not available. What am I doing wrong? I also tried browsing from the server, where under WORKGROUP there´s libreelec which is then the same as 192.168.178.18, but it does not show me the storage folder.

    I played around with advancedsettings.xml extensively and wasn't able to solve the buffering issues at all. I then stumbled across a thread that suggested using system mounts rather than what Kodi uses (which I think is libsmb). This has fixed the problem! No buffering at all.

    To set this up, SSH into your box and make a copy of /storage/.config/system.d/cifs.mount.sample (in the same directory) and then follow the instructions contained within it.

    cifs.mount.sample

    Sorry to hijack such an old thread, but I am trying to do what is being suggested here. Amending the sample file was pretty straight forward so I have:

    Code
    # The share we want mount
    What=//192.168.178.10/Film6
    
    # Where we want mount this share
    Where=/storage/film

    I also set the loginname and password for the windows smb share.

    Then I named the file storage-film.mount, and put it in the storage directory, then ran enable storage-film.mount which it said was succesful.
    But how do I then make it visible in Kodi? It does not show up when I go to add a location, and I actually also tried there to add an SMB share there by enterting the pi´s network IP address and then the folder named film, but it does not manage to connect to it..

    I never had issues with buffering on xbian, so theres either a larger buffer there or they mount in the background in the way I´ve just done it, dunno. It plays fine from a USB stick and the pi is on cable to my router where it gets a 100 mbit speed.
    I should also add that its not all content giving me this problem. Stuff where an hour is 2 GB works fine, but a movie I just wanted to watch which is 100 mins long and 9 GB in size would stop and buffer every 10 secs..

    Edit: I checked the status of the mount and got the following. Maybe someone can provide an explanation based on that:

    EDIT (again): Went off to try doing this via NFS instead. This seems a bit more stable, less buffering occurs but is still there..

    Another edit: I did as suggested in the beginning although I was under the impression that it would not work and took the 4th example from:

    HOW-TO:Modify the video cache - Official Kodi Wiki

    That didnt do nothing for SMB indeed, but seems to now have cured the buffering under NFS!

    Still would like to know how to get things working with SMB though.

    Hi, I can only recommend (if you have an Android Phone) to buy the app HiFy. Works perfectly with Libreelec! With Librespot I had only problems.

    Thanks, but I can see it only supports premium which I´m still not set up for - going through some crazy steps for setting up a bank account with a debet card in my home country, where I do not live in order to unlock all music from there. I thought libreelec would support spotify free also, but if thats not the case, this could be the reason why it doesnt want to establish a connection?

    Dear All,

    I installed this on my raspberry with latest libreelec, and my android phones spotify indeed does see librespot. However, it keeps staying on "connecting" and then falls back after a while to the device that it was using - it does manage to connect to the raspberry.

    Could this have something to do with that the raspberry runs over LAN while the android phone is on my wifi - both are running via the same router though?