Posts by nonobio

    Hello :)


    I can't play some DVD-VIDEO : when i insert the disk, go to "disk" main menu and "play" : sometimes i can see the DVD menu then i can't start the title nothing happen. Sometimes LibreElec crash and reboot as soon i use the "play" action.


    All the no working DVD are "Live's music" DVD and i think it is something related to dvd region code because i tried and compared with movies disks :


    All my live's music DVD are "PAL all region code zone" and can't be played.

    My tested DVD movies working well are all with region zone code "2" (europe).


    I tried to change Settings\Player\DVD : force the use of zone "2" and/or "try to skip intro before menu : no changes.


    I checked the region code of my drive on Windows (live windows) : it is region "2" with 4 changes remaining.


    I'm on a PC with CPU AMD E1-1200 with integrated GPU AMD Radeon HD 7310.

    LibreElec version is 9.2.0


    Debug logs when trying to play a live music DVD with nothing happening after pressing "play" on the DVD menu :

    http://ix.io/23xn

    http://ix.io/23xp


    dmesg : http://ix.io/23xs


    Thanks

    Hi :)


    First i had no sound at all on Chrome. I'm using audio analog out and after setting custom audio in add-on : plughw:1,0 : sound is present...


    But, not on this site : justdancenow.com


    After clicking on this button :


    C1OQGaA.png


    I have sound on my Windows 10 PC with Chrome 77.0.3865.120 but on LE last beta version and Chrome add-on9.1.901.101 there isn't. Sometimes i can hear the beginning then it is muted after 1 second.


    Do you have any idea about this problem ?


    I can send you logs if needed.


    Thanks

    Hi chewiit :)


    With only my Xbox 360 Wireless Gaming Receiver for Windows plugged, working and with two xbox 360 controllers connected :

    dmesg | paste

    lsusb -v | paste


    With only my Xbox Wireless Adapter for Windows (v1. For connect Xbox one v1 and V2 controllers) plugged but not recognized :

    dmesg | paste

    lsusb -v | paste


    With only my Xbox Wireless Adapter for Windows 10 (v2. For connect Xbox one v1 and V2 controllers) plugged but not recognized :

    dmesg | paste

    lsusb -v | paste


    Hope you can do something :)

    Hi,


    There are 3 Xbox wireless adapter (receiver) for Windows :


    1- Xbox 360 Wireless Gaming Receiver for Windows (for connect Xbox 360 wireless controllers) : i have one and i confirm it works on Windows 7, Windows 10 and LibreElec 9. It should also work on Windows 8 and 8.1 but i didn't tried.

    3ig2AIw.jpg


    2- Xbox Wireless Adapter for Windows (v1. For connect Xbox one v1 and V2 controllers) : i have one but even if it is designed to work on Windows 7, 8.1 and 10, it doesn't work on Windows 7,it is broken after some updates. I tried it on LibreElec 9 and it isn't reconized.

    0VKAuN2.jpg


    3- Xbox Wireless Adapter for Windows 10 (v2. For connect Xbox one v1 and V2 controllers) : i have one and as its name says it work only on my Windows 10 PC. It doesnt' work on my Windows 7 PC (no driver available) and doesn't work also on LibreElec 9.

    hJ4TKBR.jpg


    My questions :


    • Is there a way to make Xbox Wireless Adapter for Windows (v1) or Xbox Wireless Adapter for Windows 10 (v2) works with LibreElec ?
    • Does the Xbox one controller (v2 with BlueTooth) works on LibreElec ? (if yes : with any Bluetooth Adapter ?)


    Thanks

    Ok, thanks, i stay with SMB ;)


    I found a way to display SMB version used on Windows, with this command on PowerShell : Get-SmbConnection


    As soon as i start playing a video on my windows client (Kodi 18), i can see the "dialect" used, and it show "2.1" :


    5JdqWOL.png


    I'm surprised, i thought it will be dialect "1" since i'm not "authentificated" (credential used and shown in powershell is the one from my PC client; which isn't the same on my WIndows 7 server) :

    The current complexity is caused by Microsoft not ourselves, but it's not particularly hard to configure things as long as you stick to a couple of basic principles. The main one is that all connections must be authenticated with a username/password.

    Should i understand that authentificated is a condition to use SMBv2 only on LE 9 client, not on Windows client ?

    Thanks for all your clear reply :)


    Is SMB the best choice for sharing sources on my Windows 7 PC or should i consider other sharing protocol instead ? I read a little about NFS; but i think it isn't native on Windows.

    Hi,


    Ok, i did it. I read a lot about wanna cry, smbv1, etc. I read that even if a device is patched for wannacry, it is recommended to disable SMBv1 in case of a new attack, because SMBv1 is very old.


    Beside my LE devices, i also updated Kodi on a Windows client. I thought it will have the same requirements that LE to access my SMB sources but no : it access it without prompt me to enter name and password. If i undesrtand : it means it is using SMBv1 (i didn't disabled SMBv1 on my Windows 7 server, not yet ;) ).


    My questions :

    1- Is there a way to display in kodi which smb version is used when i play a video from a smb share ?

    2- Since i updated LE to version 9, i have "buffer" issue : video is often paused somes seconds and then payed again (i never had this issue, or only sometimes before LE9) : can it be related to changes in SMB ? (something else ?)

    3- If i use SMBv2/3 instead of SMBv1 in Kodi : wil i really see an improved speed ? (access to sources, start to play faster, etc.)

    4- If i'm actually using SMBv1 on my windows client, will it use SMBv2 as soon as i will edit source to enter my name and password for the smb source ?


    Thanks

    Hi :)


    I just updated my kodi to 18 and LE to 9 and... "smb wasn't working". I had to force smb1 min/max in kodi setting and "legacy security" to make it work again.


    With this thread i undestand why now. Thanks Klojum and chewitt for your clear explanations :)

    The SMB client in LE 8.2 based releases defaults to SMB2 and SMB2 does not support browsing so this will always fail. If your server supports SMB2+ you can configure it manually - use an authenticated connection (use username/password). If it does not support SMB2 your only option is to force Kodi to use SMB1 .. set the SMB client to min and max SMB1. If it's really crap and ancient, you might need to set the legacy security option.

    I had to used this setting... ;)


    So to be more secure i should use SMB2 min, ok, but i have some questions :


    Apart for security, is there other benefits to use SMB2 instead of SMB1 ? I read about better speed; is it real ? Can i expect faster connexion when i watch a movie on my Kodi client connected to a smb share on my Windows 7 "server" ? I think i was in SMB 1 since a lot of years; all was working fine exept sometimes some "buffering".... Could it be thing from past with SMB 2 ?


    Which are really security risks using SMB 1 for a "LAN" use ? It's a "local" area network, isn't it ? So i think that if i don't share smb over internet (i never tried this) there isn't risks ? I used guest connexion to not have to enter credentials when i browse my lan shares.

    Am i wrong ? Could someone access to my SMB 1 shares (guest access) from internet ?!


    I want to be sure it is worth to use SMB2 (a little more effort to make things works...) instead of my actual SMB1 and legacy security (it is working right now ;) ).


    Thanks

    You will need to keep using a modified version as the official branch will update the legacy GPU driver causing it to freeze shortly after boot again (I think a few other people have uploaded modified builds to work with these older cards too).
    I will upload any new builds I make to my github releases page - you can probably expect them 3-4 days after a new public release of LibreELEC (well as long as my 8200 is still working that is ;) )


    To update to a newer version of my fork you will need to use the old manual update way of dragging and dropping my img.gz file into the update folder:


    HOW TO:Update LibreELEC - LibreELEC


    Ok, thanks :)