Posts by HiassofT

  • Allo Digione

    The log lines you quoted are fine, this is when the audio device is opened for GUI sounds and you'll get the same messages for almost every device (float is rarely supported, usually only 16/24/32 bit).

    The relevant lines are a bit down in the log.

    These lines indicate DTS was detected and passthrough using 2-channel S16LE was properly activated:

    A bit further down, when you switched to the AC3 stream, it looks fine as well:

    It's rather puzzling, currently I have only 2 more ideas:

    Maybe your receiver got "confused" because you played a DTS track before? Have you tried playing a audio or video file with just an AC3 track?

    The allo digione driver doesn't handle the IEC/AES bits which, amongst other things, set the SPDIF channel status bits to indicate if it's a PCM audio or a compressed data stream. But then, IIRC, this channel status bit is mainly relevant to ancient DACs that only support PCM audio so they can mute the output if one (accidentally) tries to feed them AC3/DTS/... Modern stereo DACs and receivers that support AC3/... just look at the data stream as compressed data can be identified by unique headers in the stream. So it's puzzling why your receiver would detect a DTS stream flagged as audio in the status bits but not an AC3 stream.

    It could well be that I'm missing something, so maybe someone else can chime in with more things to check.

    so long,

    Hias

  • Xbox original remote on Kodi Leia -> problems to create keytable/ no events

    Thanks for the status update and fingers crossed things work out with the TSOP34138. Please keep us posted about the progress, I'd be interested in knowing if you can get the old Xbox remote to work.

    Concerning lirc_xbox: it can still work be made to work with kernel 4.14 but in LibreELEC we ship (optional in LE9) newer DVB drivers which also update the code for IR remotes to very bleeding edge kernel level - and lirc_xbox does no longer work with that.

    Therefore we made the decision to drop lirc_xbox completely in LE9. It would have been rather confusing to users to have lirc_xbox support in the base installation but not when you enable one of the optional DVB drivers.

    so long,

    Hias

  • Allo Digione

    The log looks OK to me.

    Which AVR receiver are you using? Does it have some buttons to select the mode or configuration you could change?

    It looks to me like the AC3 stream is sent correctly but for some reason your receiver doesn't detect it as AC3 and instead tries to output the compressed data as 2 channel PCM - which usually results in "terrible noise".

    so long,

    Hias

  • Allo Digione

    Quote from calabuig

    I must activate debug logging, start the playing, stop it and upload the log, right?

    Yes, please enable debug logging, reboot, then play a file, then upload the log.

    It's important to have debug information of kodi startup as well, therefore the need to reboot.

    so long,

    Hias

  • Xbox original remote on Kodi Leia -> problems to create keytable/ no events

    Which IR receiver (exact part number) are you using?

    There's nothing you can do in software to influence pulse/space detection, this is performed inside the IR receiver.

    Basically there are 2 key parameters for choosing an IR receiver, one is the carrier frequency of the IR signal (usually 36-40kHz), the other is the remote protocol a receiver has been optimized for and/or how well it can deal with external IR interference (eg sun shining directly on the receiver, nearby CCFL lamps etc).

    Usually using a 38kHz (which is used eg for NEC proto)l receiver will work fine, 36kHz (used eg for rc-5 and rc-6) and 40kHz (eg sony) are near enough to work fine.

    As for protocol optimization have a look at the last page of this document on the Vishay website: dataform.pdf - more detailled info are in the specific datasheets of the receivers.

    AGC1 is the most universal AGC implementation, AGC4 (which is optimized for eg NEC and RC5/6) doesn't work well with a bunch of protocols.

    So, my recommendation would be to try a TSOP34138 (1 is the AGC version, 38 the frequency). TSOP34438 (AGC4) could be problematic.

    Some IR protocols have a rather large pulse/space at the beginning (eg NEC starts with a ~9000 pulse and ~4500 space) and you'll also see a large space (or a timeout) between button repeats. But the other pulse/space values within an IR message are usually in the 400-2000 range.

    I searched a bit and the original Xbox remote indeed seems to use a non-standard protocol. So in-kernel decoding won't work, but you could be able to create a lircd.conf with irrecord (you might have to use irrecord raw mode if normal mode doesn't work) - but first you have to sort out the IR reception (pulse/space) issues.

    As for the old lirc_xbox driver: well, that never made it into the official Linux kernel, OpenELEC/LibreELEC included it as long as possible (it needed a bit of tweaking now and then, but not too dramatic), but it's time had ended and we had to drop it. All IR receiver drivers in the kernel got moved to a new code base (which allows IR decoding in the kernel) and the old code lirc_xbox was built around got dropped.

    so long,

    Hias

  • Xbox original remote on Kodi Leia -> problems to create keytable/ no events

    The mode 2 output looks very odd - the space values are oddly large. So I'm not 100% sure if there might be some problem with IR reception - or maybe the batteries of the remote are flat and it's not working properly?

    I'm not familiar with the original xbox remote, but if ir-keytable configuration doesn't work you could try the lircd.conf files from here: lirc-remotes / Code / [395780] /remotes/microsoft

    This one looks like it could work: xbox.lircd.conf?format=raw

    Download the file and copy it to /storage/.config/lircd.conf, then reboot (LE9.0 preview builds will automatically pick the file up and run lirc, in LE 8.2 you have to enable Lirc in LE settings).

    But before doing that I'd check into the mode2 output, the pulse/space values should usually be about 400-2000.

    so long,

    Hias

  • [SOLVED] Crashes with new Raspberry 3B+

    Please upload a kodi debug log. Without logs it's hard to tell what's happening - it could be anything (some addon, some custom configuration you made, a faulty SD card etc).

    Testing with a fresh installation on a known good SD card without any addons installed would be a good idea.

    Also: when the RPi locks up can you still ssh in?

    so long,

    Hias

  • [SOLVED] Crashes with new Raspberry 3B+

    A few RPi3B+s seem to be suffering from stability issues, the RPi folks are busy working on a solution for that - see this thread on the RPi forum: Raspberry Pi 3 B+ lockups - Raspberry Pi Forums

    To make checking for that issue easier we included memtester in LE 8.2.5. Please run the following commands and let memtester run for a coupe of hours

    Code
    systemctl stop kodi
memtester 512M

    If memtester reports an error it could be worth trying one of the suggestions from the RPi forum thread. One suggestion is to add the following 2 lines to /flash/config.txt

    Code
    arm_freq=1200
sdram_freq=450

    Then reboot and check with memtester again.

    Edit: most importantly, even when using a recommended power supply, it's always good to check if it performs as expected. Run the following command:

    Code
    vcgencmd get_throttled

    If you get anything else than 0x0 you have either a power or temperature issue.

    so long,

    Hias

  • 8.2.5 break IR remote

    Yes, you are absolutely right, the "slice" DT overlay seems to be broken. I'll ping the

    To get back IR on the Slice the following line in /flash/config.txt should work

    Code
    dtoverlay=gpio-ir,gpio_pin=37

    This will use the more modern gpio-rc-recv driver which means you'll also be able to disable Lirc in LE settings.

    so long,

    Hias

  • 8.2.5 break IR remote

    Interesting, it looks like the lirc_rpi driver isn't loading.

    Could you try to add the following line to /flash/config.txt

    Code
    dtdebug=1

    Then reboot and post the output of the following command:

    Code
    vcdbg log msg 2>&1 | paste

    so long,

    Hias

  • Wiki: Infrared Remotes for RPi

    Starting with LE 8.2 gpio-ir is the preferred/officially supported way to handle IR remotes on RPi. lirc-rpi is included as a legacy alternative while people migrate to gpio-ir. LE9.0 doesn't include lirc-rpi anymore.

    gpio-ir has been included in LE for a while, but in LE 8.0 and before the easy userspace configuration (via rc_maps.cfg) didn't exist yet (overriding the keymap eg via .config/rc_keymaps/rc6_mce did work though).

    Which LE version are you using and how does your setup look like? i.e. which dtoverlay lines did you use, do you have Lirc enabled or disabled in LE settings, do you have a custom lircd.conf file, did you add something lirc related to autostart.sh or add other custom configurations?

    If you do a fresh installation of LE 8.2 and just add "dtoverlay=gpio-ir" to config.txt your harmony remote should work out of the box if you configure it as a Microsoft MCE remote.

    so long,

    Hias

  • Xbox One Remote LibreELEC 8

    I'm not an expert with Amlogic devices but IIRC with 8.2.x builds you'll have to go the amremote remote.conf route. Creating a /storage/.config/lircd.conf file and enabling Lirc in LE settings could also work.

    Proper ir-keytable configuration for Amlogic devices was added very recently to the 9.0 LE development branch, so the documentation in the wiki does not apply to 8.2 AML builds.

    "LibreELEC-S912.arm-8.2.4-Subtitles-ff" suggests you are using some community build, so you probably have to ask the creator of this build for details.

    so long,

    Hias

  • Another remote double keypress (RPi 3B + TSOP4838 + Avermedia RM-HV remote)

    Yes, this setup will work.

    One thing to keep in mind is that the IR receiver of your DVB dongle will still be setup with the kernel driver's default config (in most cases to decode the manufacturer's remote, eg hauppauge remotes on hauppauge dongles - ir-keytable will tell you which table is active). If that causes issues (eg when you also use such a remote in the same room) you'll still need aluminium tape or blacklist the IR receiver driver module.

    The only case when you might want to run "ir-keytable -a ..." manually is when testing a new setup, to check if it works and eg find out if you have typos in your files. This is why I mentioned it in the wiki Infrared Remotes [LibreELEC.wiki]. If you are sure everything's correct you could also just reboot so the config is automatically applied.

    so long,

    Hias