Jivelite for piCorePlayer

[Jeff07971]

I hope so. I always test HDMI audio to my TV.

What was missing here was Jivelite output to screen. I only tested jivelite to 7" screen and 3.5" screen, I must not have tested jivelite to TV during pCP8 development

Hi Greg,

I'm sorry to say I don't think it does work.

My system is now not clean installed but it does not appear there is an output device.

I added "dtoverlay=vc4-kms-v3d,noaudio" to config.txt in order to get the Video output working, which it did.

To test for you I removed the ",noaudio" from config.txt and rebooted

I then set SL to use HDMI via Web Gui and rebooted

after reboot SL was not running.

I SSH'd in :-



Not sure how the HDMI should show up (I've never used or been interested in it) but I don't think its here

Jeff

[Eyerex]

Having the same problem one thing i did see when booting it says something about "waiting for sound card to populate.........fail"

[Paul Webster]

The IEC958 device worked best for me when I used kms rather than fkms.
Try all of the ones with hdmi in their name.

[paul-]

Here is the skinny

By default when you select HDMI on the squeezelite page, pCP is going to prepopulate the "output" field with the device "b1"

There are many cases where the default choice of B1 is not going to work, just manually select one of the others

-RPI4 has "b1" and "b2" ports due to dual HDMI
-When you load the vc4 driver with audio, the output "B1" and "B2" will get disabled, and your outputs are now going to be vc4hdmi

Just manually pick the output on the squeezelite page and press save. IEC958:CARD=vc4hdmi is likely the best choice.

[Greg Erskine]

Hi Greg,

I'm sorry to say I don't think it does work.

My system is now not clean installed but it does not appear there is an output device.

I added "dtoverlay=vc4-kms-v3d,noaudio" to config.txt in order to get the Video output working, which it did.

To test for you I removed the ",noaudio" from config.txt and rebooted

I then set SL to use HDMI via Web Gui and rebooted

after reboot SL was not running.

I SSH'd in :-

[ATTACH]35226[/ATTACH]

Not sure how the HDMI should show up (I've never used or been interested in it) but I don't think its here

Jeff

Hi Jeff,

On a clean pCP install (no dtoverlay=vc4-kms-v3d) the HDMI interface appears when you plug in a HDMI device and boot. Well it does using my HDMI port on my TV. In the past this has been an adequate test.

We have defaulted to "b1".

Now come the complications:

If you unplug your HDMI device it disappears from ALSA. Makes sense but I think this behaviour changed going from pCP6 to pCP7.
Some RPi's now have 2 HDMI ports, named "HDMI0" and "HDMI1". In ALSA these line up with "b1 - HDMI1" and "b2 - HDMI2". Notice 0 becomes 1 and 1 becomes 2, clever.
I have found some dual RPi HDMI ports don't work.
The default MMAP settings broke the audio output in some circumstances (for Headphones too) in pCP7. Should be fixed in pCP8.
Then yesterday we found the separation of audio and visual. In the past if audio worked, jivelite worked. We might have just been lucky for the past 6 or 7 years with this assumption.

We are just gradually working through these issues in pCP7 and pCP8.

regards
Greg

[Howard Passman]

Odd behavior between LMS 8 and Jivelite

piCorePlayer | piCorePlayer v7.0.0 | www v00011 | linux 5.4.83-pcpCore-v7l | piCore v12.0pCP | Squeezelite v1.9.9-1386-pCP

Loaded the above on a new RPI 4 with the exception I loaded LMS 8.0. Loaded Jivelite and then went to set the Language and Joggler interface. When I set the interface the pi locked up. Tried this a few times and went back to LMS 7. Everything worked fine.

Then I did an insitu update to 8.0 and things were fine with the exception of I could not sync players. Everything would play along fine for about 30 seconds and then stop. The Transporter would say buffering so I fooled around with the sync settings in LMS to no avail. I found that as long as I only sync'd two players together it worked fine. The 3rd one seemed to be the issue. But then I reset Jivelite and found once again on LMS 8 I could not set the Joggler interface. Went back to LMS 7.0 and everything, including multiple sync'd players works fine.

No idea what this all means, but thought I'd report it.

Howard

[mr-b]

Hi

My VU meters have all disappeared after I switched to wifi from ethernet.
I checked jivelite was pointing to the correct new player (same name) and music plays fine but there are just no VU meters at all when you switch views.
I tried switching VU meters and saved, then restarted PCP but still nothing.

Any ideas?

[Howard Passman]

Uninstall Jivelite and reinstall with the interface that you will be using. ie: Ethernet or wifi. It's how Jivelite works unfortunately. VU meters will be back fter you do that.

Bests,

Howard

Hi

My VU meters have all disappeared after I switched to wifi from ethernet.
I checked jivelite was pointing to the correct new player (same name) and music plays fine but there are just no VU meters at all when you switch views.
I tried switching VU meters and saved, then restarted PCP but still nothing.

Any ideas?

[Howard Passman]

Also, as I stated previously, there seems to be a hang up when using LMS 8.0 and Jivelite. If you are using LMS 8.0 I would recommend going back to LMS 7.0.

Howard

Uninstall Jivelite and reinstall with the interface that you will be using. ie: Ethernet or wifi. It's how Jivelite works unfortunately. VU meters will be back fter you do that.

Bests,

Howard

[mr-b]

Uninstall Jivelite and reinstall with the interface that you will be using. ie: Ethernet or wifi. It's how Jivelite works unfortunately. VU meters will be back fter you do that.

That's great - thanks! VU meters are working again (well after I've figured out which skin to use on my 7" display - it's not very forgiving of the wrong setting and I had no clue which to use!).

FWIW I'm running LMS 8.0 (but on another rPi) and have not seen any jivelite issues so far apart from this one.

[paul-]

Hi

My VU meters have all disappeared after I switched to wifi from ethernet.
I checked jivelite was pointing to the correct new player (same name) and music plays fine but there are just no VU meters at all when you switch views.
I tried switching VU meters and saved, then restarted PCP but still nothing.

Any ideas?

After changing the interface, you have to reset something in jivelite. There is a reset button in the pCP interface. You will have to setup jivelite from scratch.

[Howard Passman]

The only issue I saw with Jivelite and LMS 8.0 was if you reset Jivelite you will not be able to select a skin. At least every time I did it locked up. I could load everything with pCP 7.0 and then insitu update to pCP 8.0 fine. But if I reset Jivelite I had to go back to pCP 7.0 and start over.

Pretty much the only real choice with a 7" screen is Joggler.

It might be handy if there was an information bit where you load Jivelite about using the right interface if you want to use the VU's

Glad all is well. I don;t know much, but I know this bit.

Howard

That's great - thanks! VU meters are working again (well after I've figured out which skin to use on my 7" display - it's not very forgiving of the wrong setting and I had no clue which to use!).

FWIW I'm running LMS 8.0 (but on another rPi) and have not seen any jivelite issues so far apart from this one.

[Howard Passman]

After changing the interface, you have to reset something in jivelite. There is a reset button in the pCP interface. You will have to setup jivelite from scratch.

Hi Paul. I didn't find reset to work in order to get the VU's working again. Only uninstall and reinstall using the interface to be used to connect.

Howard

[mr-b]

Justboom DAC clicks

I have a Justboom DAC HAT and am trying out some monitor speakers which are showing up clicks/glitches whenever I change volume or pause playback. I'd not noticed these before but I was connected to a basic AV amp, and via ethernet (now wifi) - so maybe the monitors are just more sensitive. How does one solve clicks in the Jivelite settings?
I also noticed high pitched whine sounds through the speakers when the pcP boots with the Touch screen attached.

The output setting is hw:CARD=sndrpijustboomd. ALSA is 80 4 _ 1 _.
The Alsa mixer and Card control show an amazing arrangement of settings - are there any docs or guidance on where to start?

[Man in a van]

I

The output setting is hw:CARD=sndrpijustboomd. ALSA is 80 4 _ 1 _.

try changing the first value from 80 to 160 or 240

ronnie