Try putting a backslash "\", in front of "(" and ")".
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this thread: http://forums.slimdevices.com/showthread.php?t=114828
A minor point but it might be a good idea to do a "tail -f" on the LMS
update log, as it is now there is a bit of a wait with no output and
then the whole lot at once when (I assume) the log file is closed.
coyrls's
sheeple wrote:
> I do not need a DAC at all, because the digital signal is going into a
> Hypex plate amp that has its own converters.
>
> I always thought Justboom products where produced by the same factory as
> the HiFiBerry SPIDF-boards, but the latter had bought the more
> sophisticated
kidstypike wrote:
> There was no AC adapter supplied with my Topping E30. :confused:
>
>
Same for me.
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this thread:
If you set the E30 to Coax or Optical input and then power up your Pi,
does the input on the E30 switch to USB? If not, the E30 is not
"seeing" anything on the USB input.
coyrls's Profile:
slartibartfast wrote:
> In my experience there is no issue with the sound quality using USB into
> an external DAC from a Pi3B. I am not using the ethernet port though.
>
> Sent from my Pixel 3a using Tapatalk
The pre Pi 4 criticism was something I have read about rather than
experienced
Labarum wrote:
> I presently have a Beresford DAC strapped to the back of the TV with its
> two optical inputs driven by
>
> 1.A Chromecast Audio dongle receiving via Castbridge
>
> 2. A TV which has a Chromecast Video Dongle attached - this dongle is
> also recognised by Castbridge and audio
FYI this one works well for me:
https://www.amazon.co.uk/gp/product/B07NYN9PL6/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8=1
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this thread:
1) Yes
2) Yes
(in my opinion)
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this thread: http://forums.slimdevices.com/showthread.php?t=114923
SlimChances wrote:
> 1979 must be a linux thing to default to. Funny there were no personal
> computers in 1979 but then neither in 1901;)
Unix time is the number of seconds since midnight 1st January 1970. Of
couse Unix wasn't written for personal computers.
kidstypike wrote:
> You'll have to connect them by ethernet first to enter the new
> SSID/password.
Or change the SSID/Key on the new router to be the same as the old
router.
coyrls's Profile:
The Bluetooth function on piCore Player is for connecting Bluetooth
speakers as output devices. It doesn't support receiving Bluetooth
inputs as far as I know.
coyrls's Profile:
I don't have this problem with 64 bit on a Pi 4:
Code:
11:43:20 up 30 days, 15:16
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this thread:
pgf wrote:
>
> What should really happen is a) squeezelite should fix the SIGTERM
> shutdown bug, and b) the init.d script should be scrubbed to eliminate
> some of its issues. Maybe I'll figure out how to submit a bug against
> squeezelite. If any of our dear readers know the answer, please
Very nice.
A minor point, I think your second comment should read: "# commands to
run when the device is unplugged go here".
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this thread:
chill wrote:
> That makes sense, thank you.
>
> So assuming that's the case, is there a way to override the default,
> such that 'kill' (specified without a path) will use the busybox version
> in /bin?
>
> It still seems possible that the start-stop-daemon is using the default
> external
I think the "default" kill will be the shell built in version.
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this thread: http://forums.slimdevices.com/showthread.php?t=113661
slartibartfast wrote:
> Turn it off and on again does fix a lot of issues. I can't remember this
> ever happening before though. It probably had been running for a long
> time. Is it recommended to have a scheduled reboot when pCP is only used
> as a player?
>
> Sent from my Pixel 3a using
To be clear, I don't think from what you've reported that pcp is
"crashing", it seems to be that Squeezelite is no longer functioning.
As has been suggested, if there is a fault with the DAC hardware or the
DAC driver, this could happen and it may require a reboot before the
fault can be
There is a possibility I think that there is some sort of timing issue
going on, as the DAC doesn't function at boot but will function if you
replug it. The odd thing is that the DAC is recognised but doesn't
function. Anyway, as an experiment, you could slow down the boot
process by setting
Pommes wrote:
>
>
> I edited vi the asound.state, now it is working!
> Thank you so much, you made my day again!!!
Great! You were ahead of me. Ignore my previous post then! Glad it's
working, that was a tricky one.
Please can you login as tc using ssh and type "cd" to make sure you are
in your home directory, then copy everything the the code section below
and paste into your ssh session at the $ prompt (make sure that you have
everything copied, including the "%" sign at the end):
Code:
Also, rather than vi the sound.state, can you also run "cat
sound.state", I want to see if vi is putting the escaped characters in
or if the escapes are in the file itself. The two errors are for
control #2 and #3 and those are the two with the special characters in
the name.
Pommes wrote:
>
> the file /proc/asound/cards exists, but is empty(i did vi cards, is
> there an easier way on mac?)
>
> Thanks
> regards
> Pommes
Sorry you can't vi that file. At the command ($) prompt just type cat
/proc/asound/cards
Pommes, please can you run:
Code:
sudo alsactl -d restore
-d is a debug option and may give us more information on the error
message.
Can you also post the contents of this file:
Code:
/proc/asound/cards
I've just checked and, yes, Explorer 2 is actually Explorer². I wonder
if this non ascii name is causing the problem with restore.
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this thread:
Paul Webster wrote:
> Please post the entire contents of your /var/lib/alsa/asound.state
> file.
> If too big then you can attach it to the forum post.
> If not too big then enclose with BBS tag [ code ] and [ /code ] but
> without the spaces.
>
>
>
> BBS tags -
Greg Erskine wrote:
> Did he generate and save a new asound.state?
>
This is where we are at:
Code:
tc@pCP:~$ sudo alsactl -R store
tc@pCP:~$ sudo alsactl restore
alsactl: set_control:1325: failed to obtain info for control #2 (No such file
or directory)
Pommes wrote:
> Could you explain, please?
> I would open pcp_startup.sh and modify by "removing the $CARDNAME
> argument to "alsactl init" at line 421 and "alsactl restore" at line
> 425"???
> I can not even find the pcp_startup.sh to try to modify it.
> Thank you
Sorry, this is not to do
Yes but this doesn't explain pommes' problem where he uses alsactl at
the command line and the save works but the restore fails.
I did post much earlier in this thread about the cardname USB preventing
the state from being restored and suggested the workaround of using
asctl restore as a user
Pommes wrote:
> When i run it in ssh on mac terminal? yes, before and after reboot the
> same error.
> There is no way to run this commands from picore webif, is there?
No you can't do this from the Web interface.
It's very odd because a store followed immediately by a restore, should
work.
After you run alsactl store, run alsactl restore (i.e. no reboot). Do
you still get the same error messages?
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this thread:
Pommes wrote:
> Yes i did that.
> It worked well with my Soundblaster DAC, but i swapped and wanted to use
> a Meridian Explorer Dac.
> With that one it is not working:-(
Maybe try "alsactl -R" to remove the old runstate file before you run
"alsactl save", perhaps your old entries for your
Pommes wrote:
> I just connected a Meridian Explorer usb dac to Raspberry 3 picore 7.01
> and unfortunately the headphones out is way to low.
> in alsamixer i can bring it up, but after reboot the volume is low
> again.
> I tried all tricks mentioned here, but it doesnt work.
> Is there a way
One possibility is that the USB probe on boot, although successful, is
somehow "locking up" the USB DAC, maybe because the probe is happening
before the DAC has completed its power up initialisation process. Is it
possible to check this by powering the DAC independently of your Pi and
making
I am a bit lost as to how an upgrade vs a fresh install will address the
problem. I think bigq started with 7.0.0, so it's not as if it was ever
working under 6.0.1.
My suggestions would be:
1) Check what is specified as the output under Squeezelite settings and
if it's not already
bigq wrote:
> Man in a van and coyrls, thanks for your advises.
> So I tried to save (sudo alsactl store), backup and then reboot.
> The same situation, only replugging helps after boot.
>
> As far as I can see the problem is in initializing 'USB' soundcard on
> boot. Fo
bigq wrote:
> As I can see, the problem is here:
>
> Waiting for soundcard USB to populate. Done (1).
> Waiting for network. Done (1).
> Starting ALSA configuration...alsactl: init:1787: Cannot find soundcard
> 'USB'...
> alsactl: load_state:1763: Cannot find soundcard 'USB'...
> .alsactl:
Try saving manually at the command line (su alsactl backup) and then
backing up (pcp bu), then rebooting with the "su alsactl restore" in
Tweaks.
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
As discussed in this thread:
https://forums.slimdevices.com/showthread.php?111540-Alsa-mixer-on-picore-cannot-save,
saved ALSA settings for a USB DAC are not restored successfully. A
workaround is to put "su alsactl restore" as a user command in the
Tweaks tab.
To address 2), or at least to not attempt to restore settings to a card
that hasn't been detected, the test at line 414 of pcp_startup.sh:
Code:
if [ "$ALSAlevelout" = "Custom" ]; then
would also have to include a check that the card has been
chill wrote:
> I've been looking into this. I have the same issue as described in
> 'this thread'
> (https://forums.slimdevices.com/showthread.php?111540-Alsa-mixer-on-picore-cannot-save)
> - in my boot log I see:
> >
Code:
> > Starting ALSA configuration...alsactl:
Going back to pcp_startup.sh, I would have thought that removing the
$CARDNAME argument to "alsactl init" at line 421 and "alsactl restore"
at line 425 would fix the problem. The effect would be to initialise
and restore settings for all ALSA cards but I can't see that would a
problem, as this
slartibartfast wrote:
> I bet yours cost more than £75 [emoji3]
>
> Sent from my Pixel 3a using Tapatalk
Still £75 is about £650 in today's money.
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
Man in a van wrote:
> :cool:
>
> I'm listening today, to mine, which was built in 2000 :)
>
> ronnie
What a coincidence! I was trying to find out what an A21 looked like in
2000 but without success but I am guessing not the same as 1975. I
remember going up to London (from Reading) to buy
I have looked at pcp_startup.sh. CARDNAME is set to USB, so the check
in line 358:
Code:
until aplay -l | grep '\[' | grep -q $CARDNAME 2>&1
is passed because on my system aplay -l returns:
Code:
card 0: E30 [E30],
paul- wrote:
> That boot log means the USB device is not found when trying to restore.
> pCP boot relies on everything being powered at boot. USB powered off
> and pluggable cause problems. The uneven rules floating around should
> make it easy to automate loading the Alsa state too.
As I
Greg Erskine wrote:
> The third field in [Squeezelite Settings] > "Upsample setting" is
> attenuation.
>
> I am using 4dB attenuation, I haven't tried larger but I assume it
> works.
>
> Why use ALSA for attenuation instead of using the Topping E30's PRE
> mode?
I didn't realise you could
I don't know much about electronics but the manual says the input
sensitivity is "100mV into 200 Kohm flat response" and I set alsamixer
dB gain to -18.00.
coyrls's Profile:
slartibartfast wrote:
> What is the amplifier? I must admit to adding 10dB attenuators between
> my DAC and my Audiolab 8000A to allow the volume control to operate well
> away from the minimum at night time listening levels.
>
> Sent from my Pixel 3a using Tapatalk
It's a Sugden A21
Greg Erskine wrote:
> Are you guys using the Card Control screen?
>
> 33271
>
> The [Save] button does the backup and sets ALSAlevelout="Custom" so the
> saved volume is restored after a reboot.
>
> Has this process broken? I haven't used it for many years. The only time
> is used it was
paul- wrote:
> What is in your boot log?
I should have looked before, here is what I think is the relevant
section:
Code:
Waiting for soundcard USB to populate. Done (1).
Waiting for network... Done (7).
Starting ALSA configuration...alsactl: init:1787:
slartibartfast wrote:
> If a USB DAC does support it what benefit does that give you?
>
> Sent from my Pixel 3a using Tapatalk
The default output level is too high for my amplifier, I have to set the
volume really low and tiny increments make a big difference to the
volume. I use alsamixer
paul- wrote:
> Make sure you backup after saving. Nothing is retained between reboots,
> unless you backup.
I definitely did a backup (pcp bu) after saving but it didn't retain the
setting.
coyrls's Profile:
Pommes wrote:
> I am running pcp 7 64bit on Raspberry 3 with a usb dac sound blaster
> play3.
> I had to increase the volume in alsamixer.
> I tried all described in this thread, but only putting alsactl restore
> into tweaks commands solved my problem
Same for me, the alsamixer level setting
Probably any SSD should be ok but it's worth checking power consumption
before buying as they differ more than you would expect. Some that are
labelled "green" use more power than others not making that claim. No
real need to worry about performance.
I have successfully used this caddy:
https://www.amazon.co.uk/gp/product/B07NYN9PL6/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8=1
and this SSD:
https://www.ebuyer.com/790252-kingston-a400-480gb-ssd-ebuyer-com-sa400s37-480g
with no external power and no issues. I chose the ssd because of its
low
Sorry for the multiple posts. Each time I post something it prompts me
to try something else. I really shouldn't be using the forum to aid my
thought process but it seems to work.
It seems that ffmpeg wants to convert embedded jpegs in wma files to
embedded pngs when converting from wma to
I think I have got to the bottom of the issue. It seems that the png
codec is required to deal with a jpg embedded in a wma file. If I run
the command
Code:
$ ffmpeg -codecs | grep png
with pcp, where the conversion doesn't work, I get:
Code:
I have tried the same ffmpeg conversion under Debian:
Code:
$ ffmpeg -i f.wma -f flac o.flac
and it works. The version of ffmpeg is reported as:
Code:
ffmpeg version 4.1.6-1~deb10u1 Copyright (c) 2000-2020 the FFmpeg
I have found a better option -vn "as an input option, blocks all video
streams of a file from being filtered or being automatically selected or
mapped for any output", I checked on the command line and it works. I
then edited the PlayWMA plugin's custom-convert.conf for wma to flac
to:
Code:
It does seem to be the embedded jpg that is causing the problem. If I
run the command:
Code:
$ ffmpeg -i f.wma -map 0:1 -f flac /tmp/o.flac
it works. The -map 0:1 tells ffmpeg to only deal with the second
stream, as it seems to think that the
Having thought about it, it looks like it is trying to convert the
embedded jpeg to flac, which obviously it can't do. I will investigate
ffmpeg options that will stop it trying to do this! The version of
ffmpeg with pcp 6.1 didn't have this issue.
ralphy wrote:
> Yes I was using the 64bit version of pcp7 and I too have the same
> disabled options, I just snipped them from my post as they are just
> noise.
Very strange, I did notice that in the options is says "--enable
static", does this mean no dynamic linked libraries? In the
ralphy wrote:
> What version of ffmpeg do you have installed?
>
>
I installed the pcp-ffmpeg extension from the pcp repository. Are you
running the 64 bit version of pcp?
The version seem to be the same as yours:
Code:
ffmpeg version 4.3.1 Copyright (c) 2000-2020
It does seem that the version of ffmpeg downloaded as an extension to
Pcp 7.0 64 bit is unable to convert wma to flac, meaning the Play
Windows Media LMS plugin wont work. The simple ffmpeg command:
Code:
$ ffmpeg -v 9 -i f1.wma f2.flac
Should
I have sorted out my problems with my LMS migration. In the end I
deleted the Cache directory contents but kept the preferences directory,
rescanned my library and reinstalled my plugins.
I am still having a problem with the Play Windows Media plugin. This
worked under Pcp 6.1 32 bit with
slartibartfast wrote:
> You could try copying your 6.1 card to another SD card and then do an
> in-situ update to 7. I know that works from 7 beta but don't know about
> 6.1.
>
> Sent from my Pixel 3a using Tapatalk
I wanted to move to 64 bit and so an in-situ upgrade wasn't an option.
I
OK, I have gone back to the original 6.1 SD and everything works and so
nothing has been changed on the USB drive that prevents my 6.1 SD from
working. I guess my question now should be how do I set up my 7.0
installation so that LMS will pick up the configuration from my 6.1 set
up? Are there
I think there must have been a flaw in my logic when I upgraded to 7.0
from 6.1. I chose to burn a new SD card with the 64 bit version of 7.0.
I switched cards and reapplied my settings. I installed LMS 8.1.2 (I
had already upgraded to LMS 8.1.2 under Pcp 6.1). My LMS cache files
were all on
Greg Erskine wrote:
> hi coyrls,
>
> This is fairly normal and can usually be ignored.
>
> What is happening is the "dirty" bit on the boot partition has been set.
> This is caused by pulling the power rather than shutting down which
> resets the "dirt
I have noticed the following messages from dmesg:
Code:
FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be
corrupt. Please run fsck.
If I manually mount and then unmount mmcblk0p1, I get the same message
on unmounting. If I
I have finally resolved my HiFi Berry forum sign up problem and have
posted in the thread there, asking about the release of the patch.
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this
paul- wrote:
> Hopefully its quick, and I can just upgrade the kernel before a full
> pCP7 release.
For various reasons, I haven't had a chance to check the full pCP7
release until now but I have found that the problem is still the same as
with the beta release (and 6.1): 24/192 files will not
psketch wrote:
> I found that you have to do a Manual update in pcp to get it to switch
> over to the new version. So, looking at the stable.xml, it showed
> 8.1.2, but checking for updates showed no new version, although I was on
> the last 8.1.1 nightly. Just doing a manual update in pcp
kidstypike wrote:
> Ah, sorry, on the LMS page click the "Update LMS" button, then on the
> next page click the "Manual Update" button.
>
OK, I'm still on 6.1.0 and I don't get that option. I guess I will need
to run the lms-update.sh command manually again to get to 8.1.2.
slartibartfast wrote:
> 8.1.1 is stable. On my Pi which is Raspbian I needed to install 8.1.2
> manually and from then on I get updates.
>
> Sent from my Pixel 3a using Tapatalk
As I understand it, 8.1.1 is now classified as the release version and
8.1.2 as the stable version.
I am not sure how this answers my question. I chose the stable release
but am still on 8.1.1, not 8.1.2.
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this thread:
I am confused about how LMS updates happen with pcp. I am on pcp 6.1 (I
will be updating to 7.0) and I have previously used the lms-update
script to select the stable branch of LMS with nightly updates:
Code:
sudo ./lms-update.sh --release stable -s -r -u
paul- wrote:
> No that wont work, as init runs long before a restore of your backup is
> done. You would need to create a new initrd archive with that file in
> it, then add it after the main initrd in config.txt
>
> Also, I believe piCore only operates in single user mode. If someone
>
Haaarald wrote:
> Pushing up again. Im searching for the same solution. As my multimedia
> is controlled via CEC over the TV, this is always running when playing
> music. Is it possible to get no video output? I have a OLED and these
> dont like static pixels.
>
> Thanks,
> Harald
Try
paul- wrote:
> Wma is being dropped from all squeezelite versions.
>
> I will update the release notes to make that clear.
It might also be worth mentioning in the release notes that in addition
to activating the "Play Windows Media" plugin, you also need to install
the piCorePlayer extension
seekasoul wrote:
> Hello, bit out of topic, sorry. Is the driver for this cool DAC Hat from
> OSA Electronics (Spain) be likely to be (ever) impemented in
> piCorePlayer?
>
> DACBERRY ONE+
>
> Some info there:
>
> https://www.osaelectronics.com/product/dacberry-one-plus/
>
>
paul- wrote:
> Hopefully its quick, and I can just upgrade the kernel before a full
> pCP7 release.
Thanks! I'll keep an eye on the HiFiBerrry forum and I will post here
when they say it's been released.
coyrls's
The latest update for this is:
> An experimental patch is ready and will be included in the next
> HiFiBerryOS release. If this runs stable, we'll also create a pull
> request for the official Raspberry Pi kernel.
Once the new driver makes it into the official Raspberry Pi kernel, what
is the
I thought this was a really good deal until I realised that a Raspberry
Pi was not included in the price!
coyrls's Profile: http://forums.slimdevices.com/member.php?userid=44253
View this thread:
I am still unable to get a login to post on the HiFiBerry forums but
HiFiBerry support have told me that they are "working on this" and that
they will post on the HiFiBerry forum when they know more.
coyrls's Profile:
Jeff07971 wrote:
> Not sure if this is any help but My HiFiBerry DAC Pro plays 24/192 fine
> using pCP 7.0.0b6 and RPi 2
>
Based on a previous report of the same problem, there seems to be some
evidence that the problem is RPi 4 specific, see
Man in a van wrote:
> Why not try an 'image from Max2Play.'
> (https://www.max2play.com/en/max2play-image/)
>
> They have an image based on Buster and a setup routine which allows the
> selection of a dac mfg. One just needs to add LMS if required. It's
> possible to install LMS v8.0.0.
>
>
OK, I have installed v7.0.0b6 64 bit and the issue is identical to the
one I described with 6.1.0. Upsampling everything to 192 sorts the
issue out again.
I guess from an audio point of view the upsampling solution is
satisfactory; my ears can tell the difference between sound and no sound
paul- wrote:
> Based on everything you mentioned, that would be in the driver. Can
> you check on pCP7.0.0 Beta6 which is open to the
> public.https://forums.slimdevices.com/showthread.php?113199-piCorePlayer-7-0-0-Public-Beta
>
> pCP7, uses the latest rpi 5.4.y kernel base, there have
paul- wrote:
> As a test setup squeezelite to upsample everything to 24/192. If that
> solves the problems. It at least confirms its the Dac/driverand
> then you may have to pick up everything or downsampling the 24/192.
>
I have tried upsampling everything to 24/192, I think! My
Here is the Squeezelite log (for silent playing of 24/192) at debug
level:
Code:
[13:58:41.144601] sendSTAT:189 STAT: STMc
[13:58:41.144656] process_strm:377 set fade mode: 0
[13:58:41.144719] process:521 audg
[13:58:41.144743] process_audg:433 audg gainL:
OK. After more investigation:
24/192 *will* reliably play if it is the first track played after a
reboot, restarting Squeezelite is not sufficient.
Playing anything other than 24/192 nearly always prevents subsequent
24/192 tracks from playing. Once a 24/192 track did play after a 24/96
track.
Another thought, if it's a timing issue, that may explain why it's been
seem on (faster) Pi4Bs but isn't seen on (slower) pi3bs, see:
https://forums.slimdevices.com/showthread.php?97046-Announce-Squeezelite-a-small-headless-squeezeplay-emulator-for-linux-(alsa-only)=974561=1#post974561
Unfortunately I am unable to create an account in the HiFiBerry
community; both Firefox and Edge tell me that hifiberry.zendesk.com is
refusing the connection.
coyrls's Profile:
OK I will rerun and post the results.
I have been doing some investigation and have the following thoughts:
Is it possible that HiFiBerry have changed the DAC that they use on
their boards? I say this because their datasheet for the DAC+ Pro
states the maximum rate supported is 192kHz/24bit,
I have set logging at info level, is that OK?
Here is the ouptut from playing the first 30 seconds or so:
Code:
[00:04:11.654185] stream_thread:247 headers: len: 541
HTTP/1.1 200 OK
Content-Type: audio/flac
Content-Length: 322760001
Connection: close
paul- wrote:
> The original Dac Pro should set just fine through the web interface.
> 100% is 0db. That is where you should start.
>
> Turn on logging for squeezelite on the squeezelite page. then try to
> play the file. Then go to Diagnostics|Logs and check out the log.
>
Man in a van wrote:
> What audio output have you selected in Squeezelite ?
hw:CARD=sndrpihifiberry
Man in a van wrote:
> Can you ssh into the pi and run
>
> >
Code:
> > alsamixer
> >
>
> then select the dac and check the volume level
I have
1 - 100 of 115 matches
Mail list logo
