Picoreplayer directly play audio from usb/line-in

[RobbH]

I am not clear about to which cmd I should be adding the "-C 1" parameter. Could you please clarify?

You are using piCorePlayer, aren't you? If that is correct you can use the pCP interface to add this parameter to the Squeezelite startup command. Go to the Squeezelite Settings tab of the pCP web interface and scroll down about 2/3 of the page, until you find an input box labeled "Close output setting". You can enter the number you want (bpa suggests starting with 1) in that field and click the "Save" button a few lines below that.

[DerTeufel]

You are using piCorePlayer, aren't you? If that is correct you can use the pCP interface to add this parameter to the Squeezelite startup command. Go to the Squeezelite Settings tab of the pCP web interface and scroll down about 2/3 of the page, until you find an input box labeled "Close output setting". You can enter the number you want (bpa suggests starting with 1) in that field and click the "Save" button a few lines below that.

It's current value there is '5'.
Since I was confused by the error I got yesterday (device busy), I had added a sleep of 10 seconds to my script, before it was supposed to start alsaloop cmd. Shouldn't this had been enough to work already?

On the same page, there even is an option to use alsa control instead of software volume ("Use ALSA control for volume adjustment otherwise use software volume adjustment.").
I guess with this, I wouldn't even have needed to use "Event Trigger"? Anyway, tinkering around with this box and learing about it, is fun ... just wondering, whether there are any (dis)advantages in using that option.

[bpa]

It's current value there is '5'.

This may mean devices was still "is use" bysqueezelite when your script tried to run .

Since I was confused by the error I got yesterday (device busy), I had added a sleep of 10 seconds to my script, before it was supposed to start alsaloop cmd. Shouldn't this had been enough to work already?

"
"Device busy" means some other application has the device open. You need to do tests with squeezelite enabling debug logging ("-d outpput=debug") and manual/controlled alsaloop to confirm behaviour of "-C" and alsa device opens/closes .
Without looking at the squeezelite code, I don't know for sure.
The other possibility is that it is another application (perhaps accidentally) that is causing "device busy".

On the same page, there even is an option to use alsa control instead of software volume ("Use ALSA control for volume adjustment otherwise use software volume adjustment.").
I guess with this, I wouldn't even have needed to use "Event Trigger"? Anyway, tinkering around with this box and learing about it, is fun ... just wondering, whether there are any (dis)advantages in using that option.

squeezelite usually does volume control using s/w - amongst other things this ensure similar volume control curves across all output streams.
Tell squeezelite to use alsa control means any volume and gain setting will be passed to I think the open output alsa device. If the alsa device is open - then it could be "busy" for alsaloop - so I think it may not work. Again you'll need to test to confirm.

Some user like prefer the alsa volume control if their USB device has a volume control knob - it means there is only one volume control i.e. alsa control & manual control are the same.