09:52 <k-man> how can i remotely control the ui so i can type a host, login and pw for my jellyfin plugin?

09:52 <k-man> ideally from my computer

11:37 <BillTorvalds> I recently bought an RPI 4 and ende dup installing LibreELEC on it. I tested it briefly on a HDMI TV and it works. Now I've finally received the special cable specifically made for RPI 4 to output composite, hooked up to my 1989 PAL TV. I read the comment in config.txt and followed it exactly: I told config.txt to use distconfig-composite.txt, as well as added the PAL row in cmdline.txt, exactly according to the instructions. In spite of

11:37 <BillTorvalds> this, all I see on the screen is four repeated LibreELEC logos flickering away in black-and-white, with nothing ever happening such as the UI loading up. Doesn't seem to respond to keyboard/gamepad input either. Just stuck like that. What could possibly be wrong?

11:37 <BillTorvalds> s/ende dup/ended up/

11:38 <BillTorvalds> The fact that it's black and white and repeated like that hints to me that it's actually outputting NTSC in spite of me using the right line?

11:39 <BillTorvalds> (But that's just a guess from me based on what NTSC Nintendo 64 games look like on the same TV.)

12:33 <LEBot> [slack] <chewitt> What is “the right line” that you used?

13:52 <BillTorvalds> chewitt: video=Composite-1:720x576@50ie

13:53 <BillTorvalds> Undearneath the "boot=blablabla" line.

13:54 <BillTorvalds> And in config.txt: #include distroconfig.txt

13:54 <BillTorvalds> include distroconfig-composite.txt

14:09 <BillTorvalds> What could be wrong?

14:09 <BillTorvalds> Shouldn't that logo just display briefly anyway, to be replaced by the actual UI, no matter how messed up it looks in this state?

14:09 <BillTorvalds> Why does it just linger on the boot screen?

14:09 <BillTorvalds> It didn't seem to take long to boot up when I tried it on the HDMI TV.

14:55 <LEBot> [slack] <chewitt> All boot params need to be on the same line. If you split them anything after the first line is ignored.

15:00 <BillTorvalds> Well, that certainly was NOT mentioned in the instructions.

15:01 <BillTorvalds> "# For PAL add: video=Composite-1:720x576@50ie"

15:01 <BillTorvalds> That, to me, reads like: "add this line"

15:07 <BillTorvalds> Well, that did the trick. Now it at least starts up and has colour.

15:08 <BillTorvalds> Unfortunately, the resolution is so high and it's "off-center" to the point where I can't navigate around in the UI and get to the resolution settings. :(

15:12 <LEBot> [slack] <chewitt> I’ve no experience with composite output since 2016 (and not ever on Pi hardware) so can’t offer any guidance.

15:13 <LEBot> [slack] <chewitt> I do know that modern Kodi is designed for a minimum 720p screen so anything smaller will be challenged in places.

15:14 <LEBot> [slack] <chewitt> You might be better off with Raspberry Pi OS

15:48 <BillTorvalds> I started with Raspberry Pi OS.

15:48 <BillTorvalds> It was inexplicably ultra-sluggish to the point of being unusable.

15:48 <BillTorvalds> Making me think there was something wrong with the hardware, but apparently not, since LibreElec/Kodi runs on a modern TV and seems to perform well.

17:24 <BillTorvalds> I can't get it to output any sound. I've double-checked everything. It works with the same setup with other sources, but not the RPI4...

17:24 <BillTorvalds> In the audio settings in Kodi/LibreELEC, it only allows me to set the volume to -99 dB to 0 dB.

17:24 <BillTorvalds> What's up with that?

17:25 <BillTorvalds> Why isn't that from 0 to 99 dB or something?

17:25 <BillTorvalds> I've looked through every damn menu and thing.

17:26 <BillTorvalds> It's so infuriating that it defaults to 0 dB and doesn't allow me to go any higher in the slider.

17:26 <BillTorvalds> I know for a fact that the videos I'm trying to play have audio.

17:26 <BillTorvalds> What could possibly be causing this?

17:55 <BillTorvalds> Any ideas?

19:24 <mack> I can't comment on hardware/config issues you're describing, but the -99 to 0 db scale is correct for describing the digital audio volume full scale. 0 is the reference point of max value. Moral of the story: dB is dumb for describing most things audio people use it for.

19:26 <BillTorvalds> This is just... absurd. Why is it muted when the guisettings.xml says: <audio>

19:26 <BillTorvalds> <fvolumelevel>1.000000</fvolumelevel>

19:26 <BillTorvalds> <mute>false</mute>

19:26 <BillTorvalds> </audio>

19:30 <BillTorvalds> This is ridiculous. I can't believe the problems I've had with this thing. How does something like this happen to begin with?

19:38 <Ommand> probably because you're an extreme edge case that was never tested for?

19:38 <BillTorvalds> Yeah, it's so extreme to output audio? :/

19:38 <Ommand> over composite to a tv from 1989? are you serious?

19:39 <BillTorvalds> There is nothing wrong with the TV, as I said. It outputs audio from everything else.

19:39 <BillTorvalds> But not from the RPI. It seems clear that there is something with LibreELEC/Kodi that is up.

19:39 <Ommand> see my first

19:39 <BillTorvalds> ?

19:40 <BillTorvalds> Why does the audio setting inside the video player not let me set the volume to over 0 dB?

19:40 <Ommand> mack already explained that to you

19:40 <BillTorvalds> No, he didn't.

19:40 <Ommand> ok good luck bud

19:40 <BillTorvalds> You had no intention of helping. I can tell by the aggressive, hostile tone of your texts.

19:41 <Ommand> aggressive and hostile you say

19:59 <BillTorvalds> I finally got it working, by switching the audio setting in System. I looked there before, but then it only had one option. Now it had three. However, while the two others produce sound, the audio keeps cutting off constantly when playing known-good video files!!

19:59 <BillTorvalds> This convinces me that there is just something wrong with the hardware on my RPI4.

20:00 <BillTorvalds> The video plays without stutter, but the audio does.

20:00 <BillTorvalds> (Does stutter.)