I have checked and all my HDCD-decoded files seems to be 24bit and play
well. What tool did you use to convert your HDCD audio to 20bit?
*Living Room:* RPI2+HifiBerry DAC+ Pro & piCorePlayer
*Attic:* RPI2+HifiBerry DAC+ RCA & piCorePlayer
*Other rooms:* 6x SB Radio
*LMS*: Version 8.3.0 on
DreadfulSupervision wrote:
> I'm having trouble playing 20-bit flacs with piCorePlayer 8.2.0 running
> on a raspberry pi 3 with a HiFiBerry DIGI2 Pro hooked up to a Cambridge
> Audio CX80 with optical toslink. I also had the same issue with a
> different HiFiBerry Digi.
>
> As a test, I tried
Honey wrote:
> Yes, understood Qobuz doesnt use MQA except in rare cases. My question
> is when Tidal is used via LMS, its no first unfold possible?
Indeed. Long story short: MQA is a lossy, proprietary technology which
is not supported by LMS. To say that MQA is controversial is an
audiomike wrote:
>
>
> I suspect this was the cause of my corruption. If you happen to recall
> how to turn this logging off (ideally via the command line), you'll save
> me some time. I've tried searching a bit.
>
> Best
I am afraid I don't know.
*Living Room:* RPI2+HifiBerry DAC+ Pro
audiomike wrote:
> I was able to successfully copy the files over to a new SD card and it
> seems to be working. The main challenge was getting confused with some
> permission issues for the PCP_BOOT partition until I remembered it was
> VFAT rather than ext4. I look forward to trying the
rgdawson wrote:
> I'm afraid I have nothing more to offer, but I have never heard this
> with SLX myself and I don't have any Ogg/Vorbis local files, but Spotify
> uses Ogg and I don't have an issue there. pCP v5 apparently used
> squeezelite version 1.9.2-1158. And looking at raplhy's github
rgdawson wrote:
> Prior to your post I had never noticed this issue. But today, believe
> it or not, I was trying out an old R-Pi 1. I installed piCorePlayer on
> it and running audio over hdmi, just to see if it worked. Well sure
> enough, I noticed very audible distortion at the end of a
rgdawson wrote:
> As far as Squeezelite-X is concerned, it should be exactly the same as
> running squeezelite by itself, since that is all SLX is doing. SLX runs
> the latest version of squeezelite, currently v1.9.9-1392. Have you
> tested various output device settings, and in your testing
A few months ago I discovered that gapless playback of Ogg/Vorbis files
was not working flawlessly in piCorePlayer. The playback is gapless, but
during the transition to the new track a small glitch is audible. I
started a separate thread about it on this forum, but that remained
silent
paul- wrote:
> feel free to change the ip address that your system uses on the tweaks
> page.
I know that you can change it manually and will do, but like I said: IMO
a better default for pCP should be considered instead of changing all my
devices by hand each time after doing a full install.
edwin2006 wrote:
> Ahum, totally blocked 8.8.8.8 and 8.8.4.4 in the firewall of the router
> to force android phones to use the dns server (pi-hole) the router
> supplies.
> I guess I have to pay attention when running updates of pcp.
>
> Verstuurd vanaf mijn SM-G960F met Tapatalk
Same here,
I am running 2x RPI2b + HifiBerry with the latest piCorePlayer on it for
years now. Works flawlessly.
I don't use LMS on it however, never tried it.
*Living Room:* RPI2+HifiBerry DAC+ Pro & piCorePlayer
*Attic:* RPI2+HifiBerry DAC+ RCA & piCorePlayer
*Other rooms:* 6x SB Radio
*LMS*: Version
A final post ons this subject for reference purposes: since LMS version
8.2.0 a systemd service file for logitechmediaserver was introduced
which solves this issue in an elegant way. The /etc/rc.local workaound
is not needed anymore.
My own attempts to create such a file where useless, so many
Apesbrain wrote:
> On the DAC front, HiFiBerry and IQaudIO offer basic boards for well
> under $30 that snap onto the RPi. Current versions of pCP include
> drivers for both.
>
> https://www.pishop.us/product/hifiberry-dac-light/
> https://www.pishop.us/product/iqaudio-dac/
I can endorse
spt58 wrote:
> For anyone interested I was able to get this working
>
> alsa-utils needs installing in the docker container (apt install
> alsa-utils)
>
> I am using a Behringer UFO202 usb audio card (with phono preamp built
> in)
>
> Device */dev/snd* needs passing through to the docker
mherger wrote:
> > I am sort of an 'oldskool guy' which prefer a separate stable (aka
> > 8.0.x) and developent (8.x) branch available, but I understand this
> > impacts available resources of people.
>
> There are tags for "latest" (8.0.1 nightly) or "stable" (8.0.0)
> available:
>
>
In the light of the LMS 8.0.0 release: what is the preferred way of
working with the official docker image in the opinion of the members
here?
I am sort of an 'oldskool guy' which prefer a separate stable (aka
8.0.x) and developent (8.x) branch available, but I understand this
impacts available
lordvader wrote:
> I've been using the snoopy86 container. Reckon I'll be able to switch
> over to one of these containers using my existing volumes - obviously
> pointing to the correct equivalent paths?
>
> Sent from my Redmi Note 8T using Tapatalk
There must be several LMS images 'out
adhawkins wrote:
> Just out of interest, anyone spinning up the containers using
> docker-compose rather than straight 'docker'? When I was trying to do
> that, I couldn't get around the LMS security settings where it looked
> like the client web accesses were in a different network, so it
zordaz wrote:
> Well, I can confirm x64 7.9.3 starts fine and is able to scan a local
> music library. I will test with several plugins enabled later.
> I have used my docker-compose file as mentioned earlier in this thread,
> albeit on a different host (Win10pro instead of Xubuntu
dasos wrote:
> So I don't use Windows, but I do see many people struggling with
> permissions. Why not use a volume? It's generally not recommended to
> persist data using a bind mount (but I know it is super common). Anyway,
> try something like this. You can add port mappings if you prefer.
Necromancyr wrote:
> Can you post your compose.yml that's working on Windows 10? I'm trying
> to run under Windows 2019 w/Docker in a Linux container and it's just
> not working.
>
I am using Docker via WSL2 & Windows, and also have Docker on several
linux systems.
On Win10 my current
dasos wrote:
> I mentioned it above - use host based networking. That's when you attach
> the container directly to the hosts network stack. You could in theory
> communicate with Docker from inside the container and have it map extra
> ports using the API, but that is even more hacky.
>
> Let
DOliana wrote:
> Nothing from my side - if it starts it should be as good as the old
> image.
Well, I can confirm 7.9.3 starts fine and is able to scan a local musc
library. I will test with several plugins enabled later.
I have used the same docker-compose file as earlier mentioned in this
DOliana wrote:
> While at it I changed the build process to use plattform specific
> packages. I was able to test the arm versions, but I currently do not
> have the possibility to test the x64 version (I definitely have to work
> on that). Could anyone try and see if the images
>
mherger wrote:
> > I know, my reaction was from Docker perspective however.
> > As 7.9.3 is released now, let's optimize the Docker image for it. So
> no
> > 'Docker' effort in a LMS 7.9.4 image as long as there is no released
> > version.
>
> Sounds good to me.
>
> One challenge I've never
mherger wrote:
> > I know, and I don't think it is necessary to keep/maintain a nightly
> > 7.9.4 (and 7.7.x) image. Let's focus on 7.9.3 and 8.0.
>
> There's no more work done on 7.9.3, as it has been released. Any further
>
> work will be 8.x or 7.9.4 (or later).
>
> --
>
> Michael
I
reinholdk wrote:
> 7.9.3 is a released version now and there's a new nightly branch 7.9.4.
I know, and I don't think it is necessary to keep/maintain a nightly
7.9.4 (and 7.7.x) image. Let's focus on 7.9.3 and 8.0.
*Living Room:* HifiBerry DAC+ Pro & piCorePlayer
*Attic:* HifiBerry DAC+ RCA
I'm back from a long vacation ;-) and will do the extra testing within a
few days.
In the light of the new LMS releases I will focus on 7.9.3 and 8.0 only.
I don't think it is necessary to keep the other versions anymore.
*Living Room:* HifiBerry DAC+ Pro & piCorePlayer
*Attic:* HifiBerry
DOliana wrote:
> Sounds reasonable - I created images as I wrote above. Did anybody get
> into testing the images? I have been running them successfully on ARMv7
> and they also all started on x64. If nobody objects, I will release them
> to the wild :-)
I will do some additional testing of
d6jg wrote:
> I thought 7.9.3 and 8.0.0 are both development branches.
> 7.9.3 builds upon 7.9.2 with fixes and new features.
> 8.0.0 includes Online Music Library integration on top of fixes and new
> stuff in 7.9.3
> Both are pretty stable but can be subject to accidental breakages on
>
I have done my first testing with x64 via docker-compose.
I was successfully able to pull the 7.9.2 and 8.0 images, both 7.7.6 and
7.9.3 gave a 'manifest unknown' error. This must me something with the
image-syntax/label in my compose file.
The following tests on the 7.9.2 and 8.0 containers
DOliana wrote:
> For anybody interested in testing: I created the images as described
> (until we agree on the required versions). There are now the following
> images:
>
> > > >
- latest-SetProperVersions-7.7.6
- latest-SetProperVersions-7.9.2
- latest-SetProperVersions-7.9.3
-
Viragored wrote:
> Hi all. I've just installed piCoreplayer on a Raspberry Pi 3, pretty
> much aiming just to prove the concept for when the day comes that my
> slowly dying Squeezebox Duet finally dies and has to be replaced.
> Frankly, I'm astonished that the team who run this project have
teebee wrote:
>
> Anything else you need to know?
Yes, have you installed Squeezelite via the Ubuntu repositories or
manually via a download?
In both cases: which Squeezelite version are you running?
I expect some basic start/stop scripts will do in your setup, this info
is just to be sure
This is indeed possible, but on a regular Ubuntu/Debian installation you
might run into hassles with the ownership of the sound device when
running Squeezelite, especially when more users are active on the
system. Even the Pulseaudio version of Squeezelite is in that use case
not always straight
teebee wrote:
> Yea ment the root drive. So that means i have most of the files on other
> disk (var/log/lib). My sb radios disconnect sometimes so thought of
> maybe reinstalling lms. I have a huge collection so think that's the
> issue. Since I have a old kubuntu I'm not sure what I can
This is of course possible, but requires some basic linux skills.
My first question is: what do you mean by 'boot disk'? Is this the disk
where your entire linux system is installed?
And is LMS installed via a deb-package?
The basic installation of LMS is not that big, but the database +
This thread does remind me of comparable issues I am having for years
(in fact: since Debian / Ubuntu changed to Upstart and Systemd):
https://forums.slimdevices.com/showthread.php?102220-Xubuntu-14-04-amp-startup-sequence-of-LMS/page2
My current system is Xubuntu 18.04 and LMS 7.9 (Nightly).
I
paul- wrote:
> Yes, previously reported issue, just make sure to be in Beta mode for
> now.
Assuming it is indeed the same issue as I reported last week:
After saving the configuration, the right DAC will only by visible in
Beta mode. All other modes will say 'Analog', even If you have chosen
paul- wrote:
> Just switch to Beta mode and it will show all of the cards. For those
> that the card is not showing, please go to the Diagnostics Page, then
> select "Raspberry Pi"
>
> Please tell us what is in the revision field.
>
> Also, please tell us what browser is being used.
Tested
carsten_h wrote:
> I also did a fresh install last week and the Hifiberry DAC+ (and Pro)
> are directly available. I used the Advanced Tab.
Strange, I've tests it on more than one computer in several browsers.
Hifiberry DAC+ etc. is only available in the Beta Tab. I the mean time a
did a fresh
Just did a fresh install of version 5.0.0 on one of my two standard
HifiBerry DAC+ players.
It took me a while to find my HifiBerry card in de drop down menu
however.
Is it intentional that you need to enter the GUI beta mode to be able to
select the appropriate HifiBerry card?
IMHO this is
TomS wrote:
> I have an old box running Ubuntu 14.04 LTS and what seems like
> Squeezebox Server 7.8.1 (despite the fact that the web interface says
> there is a new version 7.8.1 available). The info page says 7.8.1
> though.
>
> Anyway, I am thinking I should at some point push this to SBS
Fiddling with links in /etc/rc?.d doesn't work, already tried that long
ago. I will look into LSB tags and systemd unit files when I have some
spare time for it, but that route feels like a manual workaround.
I still think this should be solved within the default config and
packaging of LMS. I
drmatt wrote:
> The correct solution is to tell systemd that LMS requires network. It
> will then start it after it starts the network successfully.
>
> Presumably you have the init script linked into the wrong rc?.d
> directory.
>
> -Transcoded from Matt's brain by Tapatalk-
The problem also
Mnyb wrote:
> Btw Triodes spotify plugin is dead and so is the oficial spotify app .
>
> Remove thoose and start using spotty.
Yeah I know that, Spotty is running fine here since the very beginning.
*Living Room:* HifiBerry DAC+ Pro & piCorePlayer
*Attic:* HifiBerry DAC+ RCA & piCorePlayer
Yes, this is an old one but...
Today I decided to test if it was possible to remove the Q
/etc/rc.local workaround command, because I am running Ubuntu 16.04 now
with systemd and LMS 7.9.x
The test was unsuccessful, the /etc/rc.local workaround is still needed
when running LMS on a system
The latest FFmpeg version (3.1) has a HDCD filter built in, which is
based on the on the Foobar2000 HDCD component code:
http://wiki.hydrogenaud.io/index.php?title=High_Definition_Compatible_Digital
Is there any chance this FFmpeg version will end up in Ralphy's FFmpeg
version of Squeezelite
Julf wrote:
> You mean checking against accurip database (as rubyripper does multiple
> reads and verifies they are the same)? Have you tried morituri?
I know Morituri, but the last time I checked it it was a CLI tool and
that is not what I prefer for ripping.
*Living Room:* HifiBerry DAC+
I use Exact Audio Copy via Wine for ripping and Easytag and Kid3-qt for
tagging.
In the past I used Rubyripper and and good old grip/cdparanoia
sometimes, but I really miss the secure rip functions of EAC in those
programs.
*Living Room:* HifiBerry DAC+ Pro & piCorePlayer
*Attic:* HifiBerry
stereoptic wrote:
>
> Any suggestions as to why I couldn't use the 'advanced' (or any other
> selection)? I can stay on v. 1.19. Thanks for the great product and
> the continuing support!
Are you using plugins like Adblock or Ghostery?
After a few months of experience with the solution above, I have to
resurrect this post :p
In the end the boot sequence tweak only solved part of the problem:
Internet Radio indeed worked fine this way, but Triode's Spotify plugin
didn't. After a regular reboot or startup of the system Logitech
Tnx. Fiddling around with the Boot Up Manager did the trick; I changed
the start / stop priority of LMS to 98.
It seems to work, although the network itself is managed by Upstart and
cannot be configured via this tool.
I am running LMS 7.8.0 on a Xubuntu 14.04 server installation and am I
having an issue with the startup sequence of the network and LMS.
LMS, by default on my system, starts before the network interfaces.
Therefore LMS is not able to log into mysqueezebox.com automatically.
This means that I am
55 matches
Mail list logo
