Posts by VLouis

Quote from frugirune

In essence, it doesn't work as intended because the goal was to change audio output automatically depending on the chosen medium to play.

Hi, you should take a look at the "Audio Profiles" settings "Auto Switch" section... I'm using that to auto change the sound output for video (profile1 - HDMI) and music (profile2 - HifiBerry-DAC)... If do you use a remote controller, you can change the audio output by assigning a remote button to popup the "Audio profiles window". Create a "remote.xml" file in ...../.kodi/userdata/keymaps/ to use the remote's "blue" button for this:

<keymap>
<global>
<remote>
<blue>RunScript(script.audio.profiles,popup)</blue>
</remote>
</global>
</keymap>

Hi, theoretically the "default" (after boot) audio output you can change in the kodi settings (system/audio...). About the Audio Profiles Addon... it's well documented here: https://kodi.wiki/view/Add-on:Audio_Profiles and https://forum.kodi.tv/showthread.php?tid=353852.

Quote from frugirune

Cycling through profiles has no impact (on any of my RPis) on which audio port is active - it is not overriding/changing system settings - what do I do wrong?

First you need to link in the addon settings the "phisical" audio port to an addon "profile" (it's 10 profiles are available). Each profile can be labeled with a name (like the "digital" or "analog"), I'm using as the label "HDMI" for profile 1 linked to the HDMI output (ALSA:Default...hdmi), and "HIFI" linked to the I2S (ALSA:...Hifiberry-DAC). To link... prepair the profiles (add/change name, enable....etc), go to the settings/system/audio, change the output (verify if working - have sound at that output), then go to settings/addons... Audio Profiles, select "Run" and assign one enabled profile to the active sound output. It's not an "plug and play" addon, need some work in the settings, but isn't a "rocket science" to make it to work.

Quote from gaspin

I have read in this forum that if you try to connect by ssh and you put the command getedid create would be fixed,

Hi, That command is useful in the case when sometimes the RPi (LE - at startup) doesn't detect the display (ex. some displays in stand-by mode doesn't provide EDID information trough HDMI). You are sure don't have any hardware issue? Try with another HDMI cable, another HDMI output/input, another display... I'm using RPi4B with LE too, and I don't have HDMI/Display problem (I have set a cronjob for LE to reboot it every night and I used that getedid command to ensure the display is "detected" even if in StBy).

Quote from genaker

I wasnt' able to get the logs, I checked the instructions but I couldn't do it...

To solve that needs information, and the "TP-Link wifi usb adapter for my rpi2 and Libreelec doesnt decognize" doesn't to much. So you need to provide a log and could be usefull some "extended" information about wifi adapter model, LE version...

I had maybe a similar experience last week when tried to update (RPi3B, LE12 nightly) and found two "surprise", my preferate skin and the wifi usb adapter (cheap, RTL8192EU chipset) not worked. Tried the latest LE12 nightly today (seen in changelog "iwlwifi-firmware package updates"), and the usb-wifi working again...

Quote from LybsterKodi

I going to convert my 6TB HDD to EXT4 as soon as I free up a PC to install Linux on that's fast enough to transfer everything from backup to the reformatted disk.

You don't need to install linux for that. You could use a "Live linux" from USB stick. Tip: search for "Ventoy" (booting ISO directly from USB stick) and "Xubuntu". Just be carefull, "playing" with partitions could lead to data lost...

Quote from retropie boy

i just got it a sundisk last year. everything been work I had retropie along with kodi on it. I have a portable hard drive aka DV drive connected to the raspberry pi 4. All the Videos are in MP4 and i had no problem. during the summer this year that same error popped up and a few days ago, it appear again

That "error" looks like an SD-Card issue... so get an another SD-card, install the LE, and try it... The fact "that device worked well before" not means is working now too... And an SD-card isn't something expensive or hard to find.

That "portable hard drive aka DV drive" have own power supply or draw the power from the USB connector? If powered from USB, could be a power source issue (if without that hard drive always booting fine). For external HDD never recommended to be powered from USB.

Quote from retropie boy

how to solve that problem

SD-card problem? Maybe try with another card.

Quote from insulator

I noticed that the USB WLAN comes up with wlan2, the internal wlan with wlan0.

You can disable the internal wifi if you add this to config.txt dtoverlay=disable-wifi

Hi, when I had exactly the same issue (wasn't with LE12 - but now I'm using Rpi3B + USB-Wifi + LE12 and no issues), was because of the power source...

Hi, in the past I had some similar HDMI issues (RPi3B LE), always because of display recognition (HDMI cable, TV in StBy when the RPi booted). Basically if the LE don't "see" the diplay at the end of the HDMI cable... no picture at all. Did you tried with another display? Always power up first the display than the RPi to be able to "read" the display capabilities. Also you can try some settings in the config.txt related to the HDMI output (force HDMI, preset resolution... search for the config.txt documentation). In the case of the LE11/12, I think the display resolution settings are moved to the "cmdline.txt". Also you could try it with another OS (Raspberry Pi OS?). It's not impossible to be an RPi3 hardware issue, but in most of the cases is something else, don't give up so easy.

Quote from barry

I am using the analog output on the Pi, to a dumb stereo with no surround sound, etc.

Hi,

Do you have audio-video synchronization issue between the HDMI video and the analog audio output? I tried to use same thing in the past with my RPi3B, and had that issue. Don't know is in the case of RPi4B is same situation. Also the analog audio output had poor sound quality. I switched to use the GPIO digital sound output (I2S). I'm using now this, it's cheap but need some wireing to be connected, or you can use an HifiBerry-Hat built with RPi GPIO comaptible connector. I think that analog audio is on the RPi just to have a minimal sound output, mostly when is used without display. Even for a "dumb stereo with no surround sound" should be used something better when you want to listening some music.

Hi, maybe take a look here.

Another device, another issue... I'm using LE with RPi, in the case when the RPi restart, when the TV is in standby, had EDID issue, so I made an EDID dump with "getedid create" command. Something similar you can try... If you can save your TV's edid data with another device and put it in the right place in your Wetek?

Quote from sindbad6

So my board seems to work at all and is not broken as I thought before. What I don't understand, that it is rcognized as "HifiBerry DAC" not as Digi2-Pro. And of cause, why it doesn't work with LE.

Did you tried to add to the LE config.txt the "dtoverlay=hifiberry-dac" line?

It's interesting why the HifiberryOS detected your boards chip as "pcm5102a". Can post here a picture with your Hifiberrry board, and another one with the chip used on the board?

Quote from frankvw

Update: several hours of testing have shown some progress: I set the WiFi router to use only IEEE802.11b/g and moved the RPi closer to the router (right next to it, in fact). Suddenly the problem disappeared.

Then I moved the RPi away from the router again (to the point where the WiFi signal was barely enough to be useable) and LE now complains again with the "invalid-key" error and requests that I enter the "correct" key.

So off-hand this does seem to be related to WiFi protocol implementations in some routers and/or signal strength/quality.

Yeah, the tiny RPi onboard wifi antenna... probably a case again where the size is matter

I'm doesn't had the "invald-key" problem, only the weak signal and unstable connection... so I disabled the the onboard wifi (config.txt) and I'm using an USB wifi dongle with external antenna. Far better wifi connection. If you have an USB wifi dongle or can borrow one for testing, try it...

Quote from cappsie

Looks like it was already commented out

Code

# uncomment to enable infrared remote receiver connected to GPIO 18
#dtoverlay=gpio-ir,gpio_pin=18 

#dtoverlay=gpio-ir,gpio_pin=18 - That is for IR remote receiver what can be connected to the GPIO port!!!

Read again what I wrote before...

Disable the onboard wifi... by adding to the config.txt the "dtoverlay=disable-wifi" line

I'm using an unusual solution for this. Because I had too many issues with HDMI-CEC, I connected an IR receiver and an IR LED to the RPi's GPIO. Now I'm using an MCE IR remote to control the LE, with modified function of the remote "power" button, when is pressed, first send a "Stop" command to the Kodi, then send few times the propper "power" signal to the TV thru IR LED. I'm using same button to switch on the TV, just need to be pressed twice (first to wake up the Kodi).

Hi,

I had something similar with my RPi3B. Bored to the weak onboard wifi and tried to use a better wifi dongle (with external antenna).

I disabled the onboard wifi by adding to the config.txt the "dtoverlay=disable-wifi" line.

Hi,

A good starting point could be to take a look at the CEC settings:

Settings -> System -> Input -> Peripherals -> CEC Adapter.

It's a posibility your RPi have random reboots, and thru HDMI-CEC to "grab" the TV input when the LE starting.

If you don't use the CEC (control the Kodi with the TV remote), better to disable it completelly.

Another thing is why your RPi have random reboots (if have it...)...