Posts by HiassofT

  • LE 9.0.2 freeze when ATI remote is used

    Thanks for reporting back, I'm glad it's working now and I'll add the fix (dropping the modprobe file) for the next release.

    And I agree with you, the driver shouldn't crash if mouse functionality is disabled.

    It'd be best if you sent a bug report by email to Mauro and Sean (the maintainers of the media and rc subsystems) and a CC to the linux-media list:

    Mauro Carvalho Chehab <[email protected]>

    Sean Young <[email protected]>

    [email protected]

    so long,

    Hias

  • MCE remote not working after upgrade from LibreELEC 8 to 9.0.2

    Make sure you haven't disabled eventlircd or have any other old configurations hanging around. If in doubt post the output of

    Code
    ls -la .config .config/udev.rules.d .config/system.d .config/rc_keymaps

    Also check with irw, ir-keytable -t and ir-ctl -r as described in the wiki.

    Edit: and please grab the latest log ZIP from the Logfiles samba share and attach it here.

    so long,

    Hias

  • cma_alloc failed on latest raspberry pi 9.0.2 image

    I'm unable to reproduce the issue here. Tried with a fresh 9.0.2 install on a RPi3B+ and checked both with disable_overscan enabled and commented out.

    Did you make any other changes to config.txt? If yes, please post your config.txt.

    Also please grab the latest log ZIP file from the Logfiles samba share and upload it here.

    so long,

    Hias

  • Beginners Problem with DACBerry One+

    Quote from DIno0815

    There is a quick start guide that explains everything you need to do a setup with any software available. You have the Volumio example, just need to follow the same instructions. Use Hifiberry DAC Plus profile, and will work.

    Since they mentioned the Hifiberry DAC Plus (which is different to the non-plus one), you could try the overlay for it

    Code
    dtoverlay=hifiberry-dacplus

    so long,

    Hias

  • Remote control advice

    I'd recommend using an MCE remote with an MCE USB IR receiver, these are very well supported in Linux and will work out of the box in LibreELEC.

    Make sure you get a "real" MCE remote (using the MCE IR protocol), eg a HP branded one like this (random ebay pick when searching for "HP MCE"): USB MCE RC6 Wireless Receiver HP TSGH-IR07 Windows Media Center remote NUC KODI | eBay - "MCE" has become a somewhat generic term nowadays and lots of IR and even RF remotes not using the RC6 MCE IR protocol are advertised with that term.

    If your HTPC / Kodi box has an IR receiver built in you won't even need the USB IR receiver, MCE remotes are supported in LibreELEC with the built-in IR receivers, too.

    RF remotes and airmice / wireless keyboards, especially the cheap ones from asia, are a hit-and-miss (some work very good, some very badly), so make sure you get the exact same model someone else has tested before - buying a random RF remote / airmouse and hoping it will work is like playing lottery :)

    so long,

    Hias

  • Raspberry composite output

    Without a HDMI cable connected the RPi defaults to analog/composite video and the only thing you need to configure is PAL/NTSC mode via the sdtv_mode option in config.txt.

    If you get some noise make sure you use the correct cable (there are several different standards for TRRS-to-RCA cables so double-check you got one that's compatible with the RPi) and that the TRRS plug is fully plugged in on the RPi.

    so long,

    Hias

  • Configuring my TV IR remote for Kodi

    As the RPi is a 3.3V-only device you have to connect the IR receiver's VCC pin to 3.3V (the receivers typically work between somewhere below 3V and somewhat above 5V).

    What TV remote are you using? Some TVs use rather odd IR protocols that may not be supported by in-kernel decoding.

    If your TV has been built in the last ~10 years chances are very good that it support's CEC. If that's the case it's a lot easier to just use that (you don't need an IR receiver as well).

    If you don't have CEC support in your TV then you may need to create a lircd.conf file with irrecord - which can be tricky.

    It may be easier to just use a different remote then, eg an MCE remote, which is supported by in-kernel decoding.

    so long,

    Hias

  • JustBoomAmpHat issue in latest Libreelec 9

    A small heatsink in combination with a case probably doesn't result in enough cooling as cases usually block airflow. You could try without the case, turning the RPi by 90° so that the GPIO connector is on the bottom can also help improving airflow (some time ago I did some tests and got 1-2°C lower temps with this setup).

    I don't think the RPi audio cards will work on the tinkerboard as it's missing the drivers for it.

    I'm using plain Kodi to play audio, in combination with Yatse on an android phone or tablet - this allows for easy remote control without having to turn on the TV.

    I can't complain with audio quality when using Kodi, I'm mainly using FLACs and audio output from Kodi is bit-perfect. IIRC most reports of Volumio or other audio distros sounding "better" boiled down to them having configured a higher output volume - compare the with amixer values, this should give you a hint if that's the case.

    AFAIK there are not "equalizer" addons for kodi, some time ago Kodi supported DSP addons but that was dropped as it wasn't working properly IIRC.

    so long,

    Hias

  • support for Allo Digione ?

    I don't have an Allo Digione card myself but it should work fine with current LibreELEC versions.

    The main difference to the Hifiberry DAC is that it'll allow you to use AC3/DTS passthrough if you connect it to a surround receiver.

    The Allo card doesn't seem to have an optical (Toslink) output though. This can be very helpful for fixing ground loop issues - the Hifiberry Digi cards (which are also significantly cheaper than the Allo card) and several others have this feature.

    With S/PDIF digital output audio quality will be mainly determined by your receiver / DAC. As this eliminates the analog connection to your receiver / amp and the probably more noisy power supply on the RPi audio quality should be a bit better. As you seem to have been happy with your Hifiberry DAC I wouldn't expect a significant improvement though.

    so long,

    Hias

  • MCEUSB IR blasting in Libreelec

    What box are you using?

    On PCs power on by USB or CIR usually has to be enabled in the BIOS.

    On AML boxes this is would be handled by u-boot, the vendor u-boot version might be tied to the remote that came with the box, not sure if power on by USB is supported. Not really my area :)

    so long,

    Hias

  • The adventures of LibreElec and a really old IR remote..

    Thanks a lot for testing!

    I've sent my changes to the driver author and the Linux kernel IR maintainer to get some more feedback and testing media: rc: xbox_remote: add protocol and set timeout - Patchwork and I'll later push a PR so it'll be added to future LibreELEC releases.

    I'm not sure if there's anything we can do about the performance of quickly repeated button presses. The current parameters (64ms period plus 10ms timeout) are rather similar to the ones of the lirc_xbox driver (which used a default of 100ms to distinguish between repeated button presses and new ones) so I'd expect to be performance to be about the same.

    Other remotes / protocols like eg rc-6 (used on MCE remotes) contain a "toggle bit" to distinguish between held down buttons and new button presses which helps a lot to improve the performance on quickly repeated button presses. The xbox remote driver doesn't seem to set that bit, could well be that the IR protocol or IR receiver don't support that.

    so long,

    Hias

  • The adventures of LibreElec and a really old IR remote..

    Thanks a lot for the tests!

    The MCE USB dongle could receive something but unfortunately it doesn't look like valid IR signals so we can't use it to get the details of the Xbox remote protocol. It was worth a try, though.

    I managed to deduce parameters from the ir-keytable -t output though and had a shot at using them in the xbox remote driver. Can you please test with this image (for RPi2/3)?
    libreelec-rpi2.arm-9.0-devel-20190323102559-d446ddb.tar

    When you test with this image please keep an eye on "double-action" button presses (i.e. if a short button click results in 2 or more movements). I've added a bit of headroom to the parameters but if they are too strict they could (occasionally) happen and we'd need to increase the headroom.

    so long,

    Hias