Man in a van wrote:
> If you can spare the time, I am interested to learn about your power
> arrangement for the PI2AES (is it an early version).
>
> I only know of a couple this side of the "pond".
>
> It's a bit expensive to try on a whim :(
>
> Thanks
>
> ronnieI use a Meanwell PSU to
Man in a van wrote:
> you're very welcome :rolleyes:
>
> ronnieAn update on PI2AES. The ALLO Digione driver sounds better to me, so is
a keeper. It did not stop the drop outs but the GUSTARD kept its lock,
although I still needed to reboot. Removing underclocking didn't help,
the RPI4 just
Man in a van wrote:
> are you using the Allo digione setting for Squeezelite ?
>
> why bother underclocking ? run the pi at default and see if the same
> thing happens
>
> ronnieI am using the Hifiberry Digi Pro+ setting, recommended for the PI2AES.
I had not tried the Allo Digione, but just
I have recently upgraded my DAC from Topping D90 to a Gustard x26 Pro.
I am running v8.0 on an underclocked 8GB RPI4 with a PI2AES providing
outputs via coax, optical, AES and IIS. All sound great but after a
while the sound cuts and the Gustard appears to lose lock. This can be
30 mins or
paul- wrote:
> As my USB DACs work just fine.
>
> I would run alsamixer from an ssh session to see what mixer is getting
> reset.
Thanks, I'll give that a go when I get a chance.
fsger's Profile:
fsger wrote:
> Before trying with BT again, I cloned my SD-CARD so I would not have to
> reinstall everything. I then reinstalled BT (but did not have USB
> playing). It connected fine to my BT headphones but then USB sound was
> again very low. Thinking I would go back to the cl
paul- wrote:
> There is no link between playing a bluetooth speaker and hardware
> connected to the player. Infact you can play both at the same time.
> (I'm doing that now) Bluetooth speakers and USB DAC. You can even sync
> them together. The only possible link I can think of is that
paul- wrote:
> There is no link between playing a bluetooth speaker and hardware
> connected to the player. Infact you can play both at the same time.
> (I'm doing that now) Bluetooth speakers and USB DAC. You can even sync
> them together. The only possible link I can think of is that
Hi,
I have been using PCP 6.0.0 for a while and am very pleased with it -
well done! Yesterday I thought I would try out BT with a BT speaker.
I was very happy that is was easy to install, discover my BT speaker and
get working (once I'd figured-out that the speaker becomes another
player).
I would just like to say thanks guys. Great job! I installed Beta 6 on
my RPI4 and it runs perfectly. I am using an aluminium heat-sink case
and it runs at around 46C, although I am under-clocking it.
fsger's Profile:
I recently upgraded to v5.0.0 and all went very smoothly, or so I
thought... The 4.1.0 audio version had been rock-steady but then every
minute or two when playing Radio Paradise v5.0.0 dropped-out, but when
streaming from my NAS it seems stable. I changed to the standard
version to see if
huxmut wrote:
> I've said it before, you guys should rename the RT Audio version to the
> "dont use this" or the "your pi will die" version...
:-) The RT Version has been excellent on my RPI3B and RPI3B+, the only
issue I have had is with the Wifi (which after installing the normal
kernel I
Greg Erskine wrote:
> hi fsger,
>
> You should only be using one network interface at a time.
>
> regards
> Greg
Thanks, Greg, I use Ethernet to configure the wifi settings, start a
reboot, disconnect the cable and then nothing... no wireless connection
and it cannot be
paul- wrote:
> We've had some issues with Static wifiits really best to setup your
> DHCP server to give the device the same address all the time.
Thanks Paul, Both interfaces have static IP addresses anyway in my
router. With the DHCP setting it does not even pick-up an IP address
(the
paul- wrote:
> Btw, you did not need to manually install crda with 4.1.0, I doubt that
> caused any problems though?
>
> Can you hookup a display and keyboard to see the boot process when only
> WiFi is connected?
I did this it all looks OK. Rgearding wifi is says
"
Starting wifi...
paul- wrote:
> Make sure you are booting the system with WiFi only. Booting with
> Ethernet connected, then removing the cable will not work, as there is
> no network manager.
Thanks Paul. I have tried that including powering down and rebooting.
I cannot ping the PCP and it cannot be seen
I am running PCP 4.1.0 with the experimental real-time kernel.
Soundwise it is great but I'd like to connect via WiFi (I have noted the
warnings it may not work) rather than Ethernet. When I configure the
WiFi it gets an IP address (defined statically)and I can connect via
that IP address to
I took the opportunity to install 4.0 B6 real-time kernel on a new,
faster, SD-card. So far, works perfectly with RPi 3+ and Digione and
running LMS too (despite the dire warnings). As a bonus, it now seems
to synch properly with my Squeezebox Radio (3.5.0 would drop-out every
10-15 secs).
sbp wrote:
> Hi.
> I wouldn't use the audio version for a LMS setup - and I suggest only to
> use it for your squeezelite clients.
> So as the normal 3.5.0 version is working with your LMS installed I
> would stick to that. Personally, I use a RPi3 for my LMS server, with a
> 1 TB USB HDD
I had been running 3.22 Audio without any problems and expected an easy
upgrade to 3.5.0 Audio. Unfortunately, I spent number of fruitless
evenings trying to get a version of 3.5.0 Audio & LMS to run stably (in
most cases at some point in the set-up it - usually after LMS was
installed - it just
It looks like my previously reported issues were due to the power
supply. 3.5.0 must have tipped it over the edge. Powering it from a
battery I did a fresh install without any issues, including Samba.
Thanks for the great work.
Thanks guys for the update it looks like you have made some great
improvements but I am struggling to get it to work on my RPI3.
Previously I was running PCP 3.22 Audio with an Allo Digione, LMS with a
USB SSD mounted and SAMBA to allow me to synch the SSD with my NAS.
The in-situ update from
ralphy wrote:
> Just checked and this flac file plays on my Digi+ Pro on a rpi2 using
> pcp 3.11, standard kernel and I can play a standard 44.1K flac right
> afterward using coax.
>
> Are you using the audio kernel?
Thanks for doing that. Good to know the files are OK. I have tried
96KHz
huxmut wrote:
> can you upload a sample file (one that doesnt play for you) to a dropbox
> or similar.
> just to rule out the file type/encode
This is a free sampler 24/96 track from HDTracks
https://www.dropbox.com/s/sd2isn7jiis5pu4/03-American%20Culture%20X.flac?dl=0
I have converted
Man in a van wrote:
> I have used hifiberry digi+ and digi+pro with pCP up to and including
> v3.1. without any problems, not yet tried the new beta version.
>
> (The board that has/had a problem with the rpi3 wireless, is, I believe
> the dac+ pro but I think there is an exchange available if
paul- wrote:
> Yes you do have a soundcard, you just don't have a DAC on the RPI. Who
> makes the Digi+ that is a critical piece of information.
>
> If the product is made by Hifiberry, then rpi3 onboard wifi is almost
> guaranteed to fail.
Yes it is a HiFiBerry. I tried their Digi+ Pro
paul- wrote:
> You need to supply more information. You have not even told us what
> soundcard you are using. Also, the only wifi that is known to not work
> is ralink chips. If you are using the rpi3 wifi, it works fine here. I
> have 2 of them and a zero-w running.
Hi Paul, I have no
I have 3.20beta5 installed and running very nicely with RIP3 WiFi.
Thank you! 3.20beta5 does not work with WiFi, which is a shame because
the 3.11-audio did.
In both 3.11 and 3.20 96KHz files appear to play but no sound comes out.
I use a Digi+ with optical output into my Caiman SEG DAC.
Greg Erskine wrote:
> Hi fsger,
>
> Please refer to this post:
> http://forums.slimdevices.com/showthread.php?105018-Announce-piCorePlayer-2-00=852039=1#post852039
>
> You need to ssh into your pi and use vi. Let me know if you need further
> information.
>
> regar
JackOfAll wrote:
> On the Pi3, I2S is also wired to the Bluetooth chip as well as the GPIO
> header. This was causing a problem with HAT boards that run as bit/frame
> master, (when Pi3 was initially released), of which the DIgi is one.
> Greg will have to tell you how to do this, because I
I have been using the piCorePlayer with a RPI3 and an Audiophonics DAC
for the RPI and was getting a very good sound - both using wired and
wifi. The wifi has been very good and rock steady.
I thought I would try output via SPDIF to my Beresford Caiman II DAC so
I bought a hifiberry Digi+
31 matches
Mail list logo
