Posts by petediscrete

Quote from Da Flex

I'm using a Behringer UMC22 with my RPi3B+. Works out-of-the-box.

And I’m using a Cambridge Audio Dac Magic 100 which in fact works better out of the box in LE than it does in most other Linux distros as it recognises both USB modes, USB 1 (48khz) and USB2 (192khz).

Again these different modes are selectable via a switch on the DAC but other distros seem to ignore this and default to USB 1 no matter what you try.

Appears to be a Pulse Audio issue in most cases although I haven’t as of yet tried its supposed successor PipeWire in Ubuntu to see if anything has changed on that front.

I’m happy enough that the Bose Companion 5 is now working albeit a little unpredictable with LE11. I always thought that the USB feature as supplied by Bose was an afterthought at the time.

Of course Bose always suggested at the time that you connect analog via the Bose controller if you were experiencing difficulties with USB.

Best piece of advice from my experience is to minimise the amount of writes to the SD cards by using external drives where possible.

I reversed out that quirks change as it appeared to do nothing.

I remember getting it to work many moons ago in Ubuntu (9 or 10 not sure which) long before the RPI arrived on the scene. Just looking back at some of the so called solutions, or workarounds which would be a better description and very few of them look credible looking back now.

I've had the Bose Companion 5 running all evening and just managed to loose sound once. What I did to fix that was power down the RPI and remove power from the Bose unit. Once I plugged back in the Bose unit and powered up the RPI everything was fine. Another workaround you could say but an acceptable one.

I'm convinced the problem lies with the fact that when the Bose is not playing sound it automatically goes into mute mode and is not being woken up by LE. Even toggling the sound on the Bose controller does not change that. Maybe the author of the original driver never took that into account when writing the driver, who knows. I don't see anyone in any rush to revisit the Bose driver for a piece of equipment 17 years old now although quite a few of those units were sold at the time.

Once again guys. thanks for having a look. It's kinda working now via USB and there's always the analogue route to fall back on if needed.

Thanks guys.

No joy. The quirk was corrtectly applied as can be seen below, reboot but still no sound via Bose USB audio.

Quote

[ 776.957481] usb 1-1.1.2: new full-speed USB device number 9 using dwc_otg

[ 777.113019] usb 1-1.1.2: New USB device found, idVendor=05a7, idProduct=1020, bcdDevice= 1.00

[ 777.113086] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[ 777.113105] usb 1-1.1.2: Product: Bose USB Audio

[ 777.113122] usb 1-1.1.2: Manufacturer: Bose Corporation

[ 777.115589] usb 1-1.1.2: device (05a7:1020): applying quirk alias 047f:02f7

[ 777.495213] hid-generic 0003:05A7:1020.0004: hiddev96,hidraw0: USB HID v1.10 Device [Bose Corporation Bose USB Audio] on usb-3f980000.usb-1.1.2/input2

Display More

This guy seemed confident he had the issue resolved but didn't mention what model RPI he was using. Both the RPI3b+ and the Bose Companion 5 are USB2.00 devices. This really is a curious one. https://forums.raspberrypi.com/viewtopic.php?t=15872

Quote from mglae

It is your decision with which additional parameters you boot your kernel .

With snd-usb-audio being a kernel module in LE you even can put the parameter into a file in /storage/.config/modprobe.d

Ok so by editing the /storage/.config/modprobe.d and adding

snd-usb-audio.quirk_alias=05a71020:047f02f7

to the file this should resolve the issue.

Just reviving an old thread as I dug out the old Bose Companion 5 for the kid’s bedroom. Working perfectly and was immediately recognised on the RPI3+ as per expectation. Problem is and was noted elsewhere on the forum it just stops working for no reason.

A little digging outside the forum unearthed “quirks”. If I’m reading this right Linux is identifying the vendor ID incorrectly and as a result is using the incorrect driver. https://forums.raspberrypi.com/viewtopic.php?t=15872

Would this solution be a major task to implement in LE11

Skip the “enter predefined muxes” section in the Wizard by pressing the Esc key. Go to the Muxes tab and manually enter a known mux from Lyngsat for 28.2. Make sure you mark this as active. You will then be presented with a list of active transponders and the scan process will start.

During the scan process click the Status tab and watch the progress of each transponder as it’s scanning. You will then be able to identify if any transponder is causing your system to freeze up.

The predefined muxes list for 28.2 is way out of date and can cause issues during the scan process.

What satellite are you scanning. Are you running the Wizard. If so when you get stuck just save and continue. You can always do a full scan later. Personally I just add one single mux and set scan for new muxes only. That way you’ll only have active transponders included.

Quote from SamJ

I was offered 4.2 or 4.3 on initial installation. The 4.3 option has disappeared now. Disabling 4.2 doesn't change that. What can I do to make it reappear?

In LE11 they are both there. Just restart LE

Quote from SamJ

No other instance of TVH running and no duplicate muxes. I scanned the muxes and didn't map any results as I don't want any channels other than those in two bouquets I made. The advice I found for creating one's own bouquets was to do the mapping per bouquet.

Now looking to see how I can try TVHeadend 4.3 but I can't see how to uninstall 4.2

No need to uninstall 4.2. Just disable it and add 4.3 add on.

The best judge of that is yourself. A spare SD card, burn the image, pop it into the RPI3+, boot it up and you’re good to go. Nothing ventured, nothing gained.

Are you showing any sign of duplicate muxes. Is there any other instance of TVH running. Have your tried scanning the muxes without creating bouquets and mapped the results.

If it is a memory issue as stated you’re wasting your time. Try one of the other SBCs on sale at the moment.

Are your muxes DVBS/DVBT or something else. Have you tried TVH 4.3 Alpha. A little bit more information would help. What hardware are you running this on.

I strongly suggest you post logs so your problem can be investigated.

Not sure if this was already posted. Comprehensive and very informative for anyone dropping in on this topic https://forums.raspberrypi.com/viewtopic.php?f=28&t=58151

No idea. All I can say is you’ve encountered a problem, I haven’t. Maybe others who come across this topic and have similar setups could give an LE11 installation from fresh a whirl and report back.

Obviously if digging down further a whole host of equipment comparisons would need to be done. Good cables v bad cables, good PSUs v bad PSUs etc. That’s something you could probably do yourself at very little extra cost if you really are that determined to get LE11 up and running on a 256gb SD card. It certainly wouldn’t be a priority of mine.

I will say that reporting it as a bug with one negative experience may not find much traction. Again you just need to find others willing to try an install along you lines and see what the outcome is.

I will say I was mildly surprised at the performance of the RPI3+ using Live TV and even more surprised using it wireless as all my setups run wired.

Quote from tim50stroud

ok... can see why I thought windows was a step forward from Dos

I'll have play tomorrow and see if my 73 year old brain cells can cope. ..... seem to remember I SSH'd once before. Thanks!

Ensure you have SSH enabled in LibreELEC. In PuTTY on your remote computer enter the IP address of your LibreElec box, select Connect Once and username =root and password=libreelec if you haven’t changed it during the LibreELEC installation. It really is that simple.