CvH Thanks. Please do.
Also since I have already started down the road with learning how to do it, Would you mind sharing the patch that you used.
Thanks,
LongMan
CvH Thanks. Please do.
Also since I have already started down the road with learning how to do it, Would you mind sharing the patch that you used.
Thanks,
LongMan
Thanks for your guidance. You are right, it was relatiely straight forward to build LibreELEC. Thanks for that. I built a Ubuntu 20.04 server and followed the instructions here. I was able to build 9.2 branch and 9.8 (master). It has been a long learning curve not necessarily hard just long because it took nearly half a day when I tried to build different packages. But I have succeeded in building the branches I mentioned before.
My current problem is that when I search for package.mk, I am getting maybe hundreds of hits. Could you provide a bit more specific guidance as the where I need to make those two changes.
Thanks
LongMan
Thanks for taking the time to reply and suggest a solution. I will do a bit of research to see how it is done.
Cheers,
LongMan
I am asking a LibreELEC team member to do us a favour by running a Build of MediaImport Beta 2. Milhouse had previously done builds for us before but he has stopped doing builds. Hopefully one of you can help us.
Thanks,
LongMan
ssh into your pi
bluetoothctl - to start the bluetooth control program
power on - to enable bluetooth service.
Put your remote in discovery mode
scan on - scan for pairable devices. The address, <dev>, and device name will be listed. Use the address, <dev> to pair
pair <dev>
trust <dev> - if you or your device needs it.
Exit - Quit bluetoothctl
Exit - end ssh session
Still no Joy. The remotes are not being discovered now. Previously discovery occurred but no pairing.
Thanks. I will try the next few nightlies and report back.
I am not familiar with the enigma systems. However, multi in usually means that the audio signal is been decoded on the box and the discrete channels are sent to the AV Receiver. You are getting the discrete channels but you lose any specialized processing that your receiver does on Dolby Digital bitstream. Some people say there is no difference, others say there is. Believe your ears.
I just checked mine and noticed the same thing. I use TV Headend. It could be the way PVR livestreams are handled. I am not sure. However, PVR Recordings pass the Dolby Digital bitstream, so all is not lost. Maybe someone more knowledgeable can chime in. I only really watch news on live tv. For movies and shows I watched recorded or ripped, so it has not been a problem for me.
Sorry, but I cannot help some more.
Cheers,
LongMan
Neither my first gen nor alexa remote pairs with curren rpi4 9.8 nightlies. Both were pair with 9.26 before update.
QuoteThird and last question: How can I add pictures and information to the movie section
Adding video sources - Official Kodi Wiki
QuoteI connected the raspberry to an A/V - Receiver to have dolby digital
Settings>System>Audio
Audio Output (hdmi connected to your reciever)
Number of Channels (Your speaker config eg. 5.1)
Allow Pasthrough Enabled
Select the audio formats that your receiver supports
Settings>Player
Sync playback to display Disabled
You may also need LE 10
Not sure how to navigate in Aeon Nox, but Jellyfin Kodi should put Videos Nodes for each Jellyfin Library under videos.
amazon basics
Try removing the colon (:) after nas_hostname so
nas_hostname:/volume1/Data/Movies
becomes
nas_hostname/volume1/Data/Movies
The people behind Argon One M.2 and the Desk Pro are already making circuit boards. Maybe one of them could do it. Just modify the design of the I/O board to fit their case.
I think there was even a post here from Argon Forty about writing a LibreELEC plugin.
Doesn't OpenAuto include the OS in the same way LibreELEC does?
OpenAuto is based on raspbian, just install Kodi on OpenAuto. IIRC it comes with Kodi already installed.
Wait for Desk Pi Pro