hi Russell.
regards
If you set the MAC address to the same on multiple players. LMS uses MAC address to uniquly identify players, or, general network problems. If you are using wifi things like the microwave and cause dropouts.
There seems to be some action regarding alsaequal. Some guys have it wokring on piCore. No promises though.
Thanks. It is good fun working with Steen and the other guys on this project.
regards
hi sckramer,
We haven't included tvservice in piCorePlayer by default, but if you install the piCore extension rpi-vc.tcz it is in there.
I haven't tested it.
regards
Slick extension system, didn't know about that...
It did seem to work:
tc@piCorePlayerZERO:/usr/local/bin$ sudo /usr/local/bin/tvservice -o
Powering off HDMI
tc@piCorePlayerZERO:/usr/local/bin$ sudo /usr/local/bin/tvservice -p
Powering on HDMI with preferred settings
tc@piCorePlayerZERO:/usr/local/bin$ sudo /usr/local/bin/tvservice -o
Powering off HDMI
It did seem to work:
tc@piCorePlayerZERO:/usr/local/bin$ sudo /usr/local/bin/tvservice -o
Powering off HDMI
tc@piCorePlayerZERO:/usr/local/bin$ sudo /usr/local/bin/tvservice -p
Powering on HDMI with preferred settings
tc@piCorePlayerZERO:/usr/local/bin$ sudo /usr/local/bin/tvservice -o
Powering off HDMI
hi sckramer,
Thanks for reporting back.
A word of caution about adding piCore extensions. piCorePlayer is a very small image, about 70MB, so you can quickly fill up the free space. This free space is also used by insitu-upgrade. So you will need to increase the size of the partition at some time.
Also, when you do an upgrade, you will need to reinstall your extensions.
regards
hi bambadoo,
I just did the change to the ffmpeg squeezelite here and of course it worked properly.
Did squeezelite complete the download?
Did you run out of space?
Do you have jivelite loaded?
Did you do a FS resize?
A df at the Linux command prompt will tell all.
regards
Thanks BTW
Did a FS resize and voila - it worked
Great news.
We will have to add more help info and checks for free space as we are finding more people wanting to add some extras and running out of space.
regards
I did expand the filesystem, for the upgrade to 1.22-- plenty of space.
Tested the command with a monitor attached: sudo /usr/local/bin/tvservice -o
It turns it off immediately.
I added it to the Tweaks --> user commands, it works great & turns off the HDMI at startup.
I'll add the extension info to my upgrade notes.
Thanks!
Last edited:
hi sckramer,
Is the only reason you are doing this is save power?
Are there any other reasons to turn off your HDMI?
I am just trying to work out if it is worth the effort to add this as an option to piCorePlayer.
regards
Squeezelite does not launch with IQAudioDAC+
Hello,
I have a Raspberry B+ with two additional boards: IQAudioDAC+ and AMP+. The configuration is powered with the recommended Power Supply from IQAudio.
It worked very well with PicorePlayer 1.18b when I assembled my kit a few months ago, and then I stopped for a while to use it.
Since a few days, I have tried several times to power it up. After I upgraded to PicorePlayer 1.22, I always get "Squeezelite is not running" (and the associated "red dot" on the main page) when the IQAudioDAC+ is selected. When I select "onboard audio", Squeezelite runs ok and the green dot is displayed.
I have tried several things without success:
- resize FS
- go back to 1.18b doing a clean install on the SD card
- try 1.19 or 1.21
No success, I cannot listen to music with the IQAudioDAC+ selected.
Can you help ?
Kind regards,
Emmanuel
Hello,
I have a Raspberry B+ with two additional boards: IQAudioDAC+ and AMP+. The configuration is powered with the recommended Power Supply from IQAudio.
It worked very well with PicorePlayer 1.18b when I assembled my kit a few months ago, and then I stopped for a while to use it.
Since a few days, I have tried several times to power it up. After I upgraded to PicorePlayer 1.22, I always get "Squeezelite is not running" (and the associated "red dot" on the main page) when the IQAudioDAC+ is selected. When I select "onboard audio", Squeezelite runs ok and the green dot is displayed.
I have tried several things without success:
- resize FS
- go back to 1.18b doing a clean install on the SD card
- try 1.19 or 1.21
No success, I cannot listen to music with the IQAudioDAC+ selected.
Can you help ?
Kind regards,
Emmanuel
Hi Emmanuel,
I am sorry about your issues.
I assume when you go back to 1.18b everything works OK and you have rebooted your RPi when requested.
What do you see on the Squeezelite Settings page > Output setting > More > Squeezelite found these output devices: ?
If you go into [Beta] mode, and select [Diagnostics] > [Sound] what is in the "Loaded sound modules" and "PLAYBACK Hardware Devices".
regards
I am sorry about your issues.
I assume when you go back to 1.18b everything works OK and you have rebooted your RPi when requested.
What do you see on the Squeezelite Settings page > Output setting > More > Squeezelite found these output devices: ?
If you go into [Beta] mode, and select [Diagnostics] > [Sound] what is in the "Loaded sound modules" and "PLAYBACK Hardware Devices".
regards
Hi Greg,
Thank you for your reply.
Actually, when I go back to 1.18b, it does not work either after reboot.
I replied to your questions using 1.22.
In the Squeezelite settings, I see;
Squeezelite found these output devices:
- null
- sysdefault:CARD=ALSA
From the diagnosis page, the loaded sound modules are:
====================> Start <====================
snd_soc_pcm512x_i2c 2570 0
snd_soc_pcm512x 18073 1 snd_soc_pcm512x_i2c
snd_soc_bcm2708_i2s 7654 0
snd_soc_iqaudio_dac 3003 0
snd_soc_core 167857 3 snd_soc_pcm512x,snd_soc_bcm2708_i2s,snd_soc_iqaudio_dac
regmap_i2c 3346 1 snd_soc_pcm512x_i2c
regmap_mmio 3556 1 snd_soc_bcm2708_i2s
snd_bcm2835 22487 0
snd_pcm_dmaengine 5794 1 snd_soc_core
snd_compress 8857 1 snd_soc_core
snd_pcm 93005 5 snd_soc_pcm512x,snd_soc_iqaudio_dac,snd_soc_core,snd_bcm2835,snd_pcm_dmaengine
snd_timer 23410 1 snd_pcm
snd 68783 5 snd_soc_core,snd_bcm2835,snd_compress,snd_pcm,snd_timer
=====================> End <=====================
The Playback harware Devices are:
====================> Start <====================
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
=====================> End <=====================
It looks like my IQaudioDAC+ card is not detected anymore ??
Kind regards,
Emmanuel
Hi Emmanuel,
First off, can you try a second reboot of pCP1.22
Funny how it is not detected even though snd_soc_iqaudio_dac is loaded?
Did you do a clean install of pCP1.18b?
Please confirm that it did work originally on pCP1.18b but now doesn't?
I assume the DAC board is correctly seated on the GPIO pins.
Please be aware, the newer versions of pCP use device trees, so require a reboot to activate the firmware. The older versions like pCP1.18b tried to do this dynamically.
I have asked Steen to have a look at your post, as I think he has these DACs.
regards
First off, can you try a second reboot of pCP1.22
Funny how it is not detected even though snd_soc_iqaudio_dac is loaded?
Did you do a clean install of pCP1.18b?
Please confirm that it did work originally on pCP1.18b but now doesn't?
I assume the DAC board is correctly seated on the GPIO pins.
Please be aware, the newer versions of pCP use device trees, so require a reboot to activate the firmware. The older versions like pCP1.18b tried to do this dynamically.
I have asked Steen to have a look at your post, as I think he has these DACs.
regards
Hi Greg,
Thank you for your time.
No change after second and third reboot.
Yes I do confirm it worked with 1.18b when I assembled my kit about one year ago.
It is fixed with the spacers provided by IQAudio, the whole config being in one of their cases.
Thank you very much.
Kind regards,
Emmanuel
Thank you for your time.
No change after second and third reboot.
Yes I do confirm it worked with 1.18b when I assembled my kit about one year ago.
It is fixed with the spacers provided by IQAudio, the whole config being in one of their cases.
Thank you very much.
Kind regards,
Emmanuel
Squeezelite does not launch with IQAudioDAC+ (update)
Hi Greg,
I think I have found the problem...
As wifi is not good in the room where my RPI is installed, I bought myself a wifi dongle based on Ralink RT5572 as there were reports that it was compatible with PicorePlayer, providing 5Ghz connectivity to a AC router.
Looking at PicorePlayer diagnosis pages, It seems to be very good from the network point of view, connecting on 5ghz frequency and providing a stable 6 Mbits throughput (not much, but should be enough for 96khz music).
But... that's when the RT5572 dongle is plugged in, that it is impossible to launch squeezelite with IQAudio output.
If I plug back my original Edimax dongle, Squeezelite can be launched ok, but I have a lot of network drops...
For information, I have tried with Max2Play and Squeezelite extension and encountered the same issue.
The following trio has compatibility issues :
- I2S IQAudio
- RT5572 driver
- Squeezelite
Any idea how to fix this ?
Kind regards,
Emmanuel
Hi Greg,
I think I have found the problem...
As wifi is not good in the room where my RPI is installed, I bought myself a wifi dongle based on Ralink RT5572 as there were reports that it was compatible with PicorePlayer, providing 5Ghz connectivity to a AC router.
Looking at PicorePlayer diagnosis pages, It seems to be very good from the network point of view, connecting on 5ghz frequency and providing a stable 6 Mbits throughput (not much, but should be enough for 96khz music).
But... that's when the RT5572 dongle is plugged in, that it is impossible to launch squeezelite with IQAudio output.
If I plug back my original Edimax dongle, Squeezelite can be launched ok, but I have a lot of network drops...
For information, I have tried with Max2Play and Squeezelite extension and encountered the same issue.
The following trio has compatibility issues :
- I2S IQAudio
- RT5572 driver
- Squeezelite
Any idea how to fix this ?
Kind regards,
Emmanuel
hi Emmanuel,
Good news, you are making progress!
I don't think you really need 5GHz wifi adaptor, they actually have less range than 2.4GHz but the quality of the adaptor and aerial also come into play.
Don't worry too much about dropped packets, as long as the number is not extreme. I usually have about 10% dropped. Signal quality seems to be a more important indicator.
Wifi adaptor seem to fall into 3 categories: No driver support, drivers available but are so bad not worth using, good driver support.
Wifi adaptor manufacturer don't always have driver support for Linux initially. It eventually gets there. Do you know if the adaptor is supported by Raspbian? Once it gets there, it will find its way to piCore then piCorePlayer.
If your really keen, there is a guy on the Raspbian forum that gives instructions of loading drivers that are not supported.
regards
Good news, you are making progress!
I don't think you really need 5GHz wifi adaptor, they actually have less range than 2.4GHz but the quality of the adaptor and aerial also come into play.
Don't worry too much about dropped packets, as long as the number is not extreme. I usually have about 10% dropped. Signal quality seems to be a more important indicator.
Wifi adaptor seem to fall into 3 categories: No driver support, drivers available but are so bad not worth using, good driver support.
Wifi adaptor manufacturer don't always have driver support for Linux initially. It eventually gets there. Do you know if the adaptor is supported by Raspbian? Once it gets there, it will find its way to piCore then piCorePlayer.
If your really keen, there is a guy on the Raspbian forum that gives instructions of loading drivers that are not supported.
regards
Hi Emmanuel.
Greg notified me about your problem.
After reading your post I suspect that it could be a power problem. Some wifi adaptors use more power than others, and it might be the case here.
Is it possible for you to test it with the problematic wifi dongle plugged in a external powered USB hub?
Regards
Steen