Announce: piCorePlayer 8.0.0

[P Nelson]

Remember the old (true) saying: It is not a question of if your hard drive will fail, but when. And the corollary to this is when it fails it will be the worst possible time.

In every computer there is a sensor that detects when you are under stress or the importance of a task. When the sensor detects one of those conditions, the computer or program will fail, get hung up, require rebooting, or something else to make your life miserable.

[Narcos]

Excellent!

Having said that, your drive seem ancient, pokey, and mostly uncooperative . Please consider Gary's suggestion to replace the drive. If nothing else, have everything backed up for when it does fail. Remember what I said about operating "in the fringe" of working/not.

Not trying to sound like your/my father

Jim

Well noted Jim, ill definitely look into replacing the drive asap. Thanks for the heads up

[Man in a van]

In every computer there is a sensor that detects when you are under stress or the importance of a task. When the sensor detects one of those conditions, the computer or program will fail, get hung up, require rebooting, or something else to make your life miserable.

Sounds like time for a D.I.V.O.R.C.E.

ronnie


imo

[Narcos]

Gents,
Ronnie, Jim, GaryM, Slartibarfast, Kidstypike, Paul & Greg.


Now, I have renewed confidence for setting up the second RPI4 as a client. Don't wanna rest too long or I'll get lazy. So Lets see what needs to be done;

Lets Name the RPI's, RPIServer (RPI1) & RPIClient (RPI2)

RPI1 being the Server I plan to attach it to my router via ethernet (currently using it as a server+player via wifi, so will have to shut off wifi on this one and revert to wired connection (ethernet).

RPI2 being the Client will be attached to the DAC (which sits 15mtrs across diagonally from the RPI1). This pi2, I'd like to run via wifi.

Questions;

1. I believe both the pi's have to communicate with each other (handshake) or else how will the pi2 send commands (music selection, play, pause, stop etc)? Currently, using Material skin on iPhone to select & play music.

2. Since Pi1 is a server there's no need for Squeezelite player, correct? should it be "disabled"?

3. Since Pi2 is a player only (client) attached to the dac there's no need for installing LMS, am I right?

Best Regards

P.S. MOD's, not sure if this is the right thread, I can post it in another thread appropriately upon your confirmation.

[kidstypike]

Gents,
Ronnie, Jim, GaryM, Slartibarfast, Kidstypike, Paul & Greg.


Now, I have renewed confidence for setting up the second RPI4 as a client. Don't wanna rest too long or I'll get lazy. So Lets see what needs to be done;

Lets Name the RPI's, RPIServer (RPI1) & RPIClient (RPI2)

RPI1 being the Server I plan to attach it to my router via ethernet (currently using it as a server+player via wifi, so will have to shut off wifi on this one and revert to wired connection (ethernet).

RPI2 being the Client will be attached to the DAC (which sits 15mtrs across diagonally from the RPI1). This pi2, I'd like to run via wifi.

Questions;

1. I believe both the pi's have to communicate with each other (handshake) or else how will the pi2 send commands (music selection, play, pause, stop etc)? Currently, using Material skin on iPhone to select & play music.

2. Since Pi1 is a server there's no need for Squeezelite player, correct? should it be "disabled"?

3. Since Pi2 is a player only (client) attached to the dac there's no need for installing LMS, am I right?

Best Regards

P.S. MOD's, not sure if this is the right thread, I can post it in another thread appropriately upon your confirmation.

I. Any client will automatically appear as a player in Material skin on your iPhone..

2. Yes, set to disabled.

3. Yes, no need to install LMS.

[kidstypike]

Burn piCorePlayer to an SD card, insert in Pi, boot up with ethernet cable attached. Without doing anything else you should see a player named piCorePlayer in your iPhone Material app.

[garym]

1. I believe both the pi's have to communicate with each other (handshake) or else how will the pi2 send commands (music selection, play, pause, stop etc)? Currently, using Material skin on iPhone to select & play music.

To clarify, the rPi units don't exactly communicate DIRECTLY with each other. Both rPi units communicate with your ROUTER, and that's how these and any other squeezebox devices on your network (or smart devices, or other computers) communicate with LMS and the various players. But as noted, just connect both rPi's to your network in some way, give them different names for clarity, and everything will just work.

[TerryS]

Have to reset Jivelite when switching between WiFi and ethernet?

I built a player and server in one using a rPi CM4 and piCorePlayer 8.2.0. It uses a DSI touch screen display (using Jivelite).
Everything works fine until I switch from an ethernet connection to WiFi (or back again). First, I often get two players listed (same name) but only one of them connects when I select it from the Choose Player menu. But then, even though it plays, the Spectrum Analyzer and Oval Meter displays are missing.
I found that I have to do a "Reset Jivelite" from the web page to get things working again.
Is this expected behavior?

Terry

[garym]

I built a player and server in one using a rPi CM4 and piCorePlayer 8.2.0. It uses a DSI touch screen display (using Jivelite).
Everything works fine until I switch from an ethernet connection to WiFi (or back again). First, I often get two players listed (same name) but only one of them connects when I select it from the Choose Player menu. But then, even though it plays, the Spectrum Analyzer and Oval Meter displays are missing.
I found that I have to do a "Reset Jivelite" from the web page to get things working again.
Is this expected behavior?

Terry

I believe that the rPi reports as a different device when on WIFI vs ethernet (i.e, it is seen as two different devices (players or servers). Just curious, why would you need to switch back and forth from WIFI to ethernet?

[TerryS]

I believe that the rPi reports as a different device when on WIFI vs ethernet (i.e, it is seen as two different devices (players or servers). Just curious, why would you need to switch back and forth from WIFI to ethernet?

I don’t usually switch back and forth but I built the system in my lab that doesn’t have an Ethernet port. So I built it on WiFi. Then I moved it to my music room and switched to Ethernet. It wouldn’t have been a big deal but I didn’t realize what was going on. The two players, one of which wouldn’t connect really threw me. I messed with it quite a while, rebooting and such and then gave up and reformatted the sd card and started over only to get to the same place. I wasted a few hours before I tried re-initializing the jivelite. So I made it a bigger deal than it should have been.

[garym]

I don’t usually switch back and forth but I built the system in my lab that doesn’t have an Ethernet port. So I built it on WiFi. Then I moved it to my music room and switched to Ethernet. It wouldn’t have been a big deal but I didn’t realize what was going on. The two players, one of which wouldn’t connect really threw me. I messed with it quite a while, rebooting and such and then gave up and reformatted the sd card and started over only to get to the same place. I wasted a few hours before I tried re-initializing the jivelite. So I made it a bigger deal than it should have been.

got it!

[Narcos]

To clarify, the rPi units don't exactly communicate DIRECTLY with each other. Both rPi units communicate with your ROUTER, and that's how these and any other squeezebox devices on your network (or smart devices, or other computers) communicate with LMS and the various players. But as noted, just connect both rPi's to your network in some way, give them different names for clarity, and everything will just work.

Pardon me if this sounds stupid, but if Pi1 is Server connected to (HDD+router) & Pi2 being just a Player connected to (DAC). Which Pi will be connected to Material skin & will play the music, coz Pi1 is not a player & Pi2 is not a server holding any music. Im confused

[garym]

One is always controlling LMS and LMS then sends instructions to the players. So Material Skin will be talking to the LMS (on one of the rPi). Then LMS will send commands via your network to the other rPi serving as a player. Keep in mind that one could have a dozen players. But they are all talking to the single LMS in your network (and you only need to control that single LMS to control all the players)

[kidstypike]

Pardon me if this sounds stupid, but if Pi1 is Server connected to (HDD+router) & Pi2 being just a Player connected to (DAC). Which Pi will be connected to Material skin & will play the music, coz Pi1 is not a player & Pi2 is not a server holding any music. Im confused

The Pi that has LMS installed is your server. The other Pi is just a player and can be selected from the players list in material, material will list all players connected to your network.

[Greg Erskine]

I built a player and server in one using a rPi CM4 and piCorePlayer 8.2.0. It uses a DSI touch screen display (using Jivelite).
Everything works fine until I switch from an ethernet connection to WiFi (or back again). First, I often get two players listed (same name) but only one of them connects when I select it from the Choose Player menu. But then, even though it plays, the Spectrum Analyzer and Oval Meter displays are missing.
I found that I have to do a "Reset Jivelite" from the web page to get things working again.
Is this expected behavior?

Terry

Buried in the documentation "Setup Wifi", step 8.