No the Audio version will not currently work with wifi.
Can we please lock this thread?
paul-'s Profile: http://forums.slimdevices.com/member.php?userid=58858
View this thread:
hey trakila
i dont think the audio versions support wifi ??
my pi3 doesnt like the higher channel numbers.
12-14 definately out. 6 is crowded but seems to be stable.
can you see any networks around you normally?
rPi 3 + rasPi 7" LCD + HiFiBerry DiGi+ | rPi 2 + IQaudio DAC+ |rPi 2 +
HiFiBerry
htctyo wrote:
> I use 3.2 final in rpi3 but internal wifi is fail cannot scan any
> network
> but 3.11 is ok
Just upgraded from 3.10 audio to 3.20 audio on mi rPi3 and get the same
error.
Code:
No wifi devices found!
Possible error:
1. USB wifi adapter
I use 3.2 final in rpi3 but internal wifi is fail cannot scan any
network
but 3.11 is ok
htctyo's Profile: http://forums.slimdevices.com/member.php?userid=66802
View this thread:
marshalleq wrote:
>
>
> Anyway, I thought I'd try my luck, in the mean time I'll just keep
> adding Roonbridge manually. :D
>
> Thanks,
>
> Marshalleq
could you write a small howto for installing roon-bridge on pcp?
Are you saying there are screens which can't be exited with the Left
button?!? What would they need on a real Touch?
Yes I believe that there are some pages that do not work with the remote
and not for the reason I discussed with Ralphy
I have to check the code whether we can change this
CloudAtlas wrote:
> Quick question: what is the difference between the 3.2 version of
> picoreplayer on the sourceforge website and the 3.2beta5 version on the
> google website. The implication is that the sourceforge version is
> later and the final released version. Is this the case?
> .
Eyerex wrote:
> Think they said these are the finals if you look in this folder
> https://sourceforge.net/projects/picoreplayer/files/insitu/piCorePlayer3.20/
OK, thanks - I'll give it a go.
CloudAtlas's Profile:
CloudAtlas wrote:
> Quick question: what is the difference between the 3.2 version of
> picoreplayer on the sourceforge website and the 3.2beta5 version on the
> google website. The implication is that the sourceforge version is
> later and the final released version. Is this the case?
>
>
Quick question: what is the difference between the 3.2 version of
picoreplayer on the sourceforge website and the 3.2beta5 version on the
google website. The implication is that the sourceforge version is
later and the final released version. Is this the case?
Thanks.
Jeff07971 wrote:
> Yes I believe that was it
>
>
>
> Yes I believe that there are some pages that do not work with the remote
> and not for the reason I discussed with Ralphy
>
> If I find it again I'll let you know !
I found a work around for my situation. The original SB remote didn't
ralphy wrote:
> It was the 'enter key (go)'
> (http://forums.slimdevices.com/showthread.php?103330-Jivelite-for-piCorePlayer=873277=1#post873277)
> IIRC.
Yes I believe that was it
mherger wrote:
> Are you saying there are screens which can't be exited with the Left
> button?!? What would
mherger wrote:
> Are you saying there are screens which can't be exited with the Left
> button?!? What would they need on a real Touch?
>
> --
>
> Michael
The left button on the remote doesn't work but a mouse click with the
cursor in the right place works.
SB3 / Synology NAS running
Hi,
I have a Pi 3 set up with LMS installed and a Raspberry Pi Screen. I
have just set up Ickstream and Tidal but I have no artwork.What could be
the problem?
Corelli45's Profile:
Jeff07971 wrote:
> This is not a "Fault" as such its just that the standard remote does not
> have the correct button in order to exit.
> This is not the only page to have the problem there are a few I found
> (cannot remember exactly what) you just have to be carefull.
> I had a breif
dhull wrote:
> I have a rpi3 with 3.2 that includes IR support, LMS and Jivelite. I
> found that if I select Pandora, which I don't have an account on yet,
> that a Pandora page is displayed with a message telling me that I must
> be a subscriber. Unfortunately the remote (a standard Slim
marshalleq wrote:
> Hi, I've been manually adding 'Roon' (https://roonlabs.com/) to this
> release for a while because it's the smallest best little distro for RPi
> to do so in my opinion. However, it would undoubtedly be done better if
> it was just incorporated, which is what I am hoping may
Are you saying there are screens which can't be exited with the Left
button?!? What would they need on a real Touch?
--
Michael
___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
Hi, I've been manually adding 'Roon' (https://roonlabs.com/) to this
release for a while because it's the smallest best little distro for RPi
to do so in my opinion. However, it would undoubtedly be done better if
it was just incorporated, which is what I am hoping may be considered
for a future
Jeff07971 wrote:
> This is not a "Fault" as such its just that the standard remote does not
> have the correct button in order to exit.
> This is not the only page to have the problem there are a few I found
> (cannot remember exactly what) you just have to be carefull.
> I had a breif
dhull wrote:
> I have a rpi3 with 3.2 that includes IR support, LMS and Jivelite. I
> found that if I select Pandora, which I don't have an account on yet,
> that a Pandora page is displayed with a message telling me that I must
> be a subscriber. Unfortunately the remote (a standard Slim
I have a rpi3 with 3.2 that includes IR support, LMS and Jivelite. I
found that if I select Pandora, which I don't have an account on yet,
that a Pandora page is displayed with a message telling me that I must
be a subscriber. Unfortunately the remote (a standard Slim Devices
remote) no longer
MrKettle wrote:
> Just trying to set this up (vanilla version) on a Zero W into a Project
> Dac Box RS. The idea was to run into the USB input but I can't work out
> how to get it to work.
>
> The output options look like this.
>
> Squeezelite found these output devices:
>
>
Just trying to set this up (vanilla version) on a Zero W into a Project
Dac Box RS. The idea was to run into the USB input but I can't work out
how to get it to work.
The output options look like this.
Squeezelite found these output devices:
null
sysdefault:CARD=ALSA
sysdefault:CARD=P20
M-H wrote:
> Hi Paul, Indeed finding the bug is difficult without direct control for
> you.
>
> For timing forensics , I am running this on a pi Bplus, and applied utp
> after the boot and first checks , and let /sbin/udhcpc do it work
> later.
> I grabbed the full dmesg output in case it is
paul- wrote:
> Just to make sure you are pressing the right button.
>
> 22600
I suppose it's possible I missed that step.
SB3 / Synology NAS running Logitech Media Server 7.9.0 / Squeeze Lite on
Raspberry Pi 2 & 3
Just to make sure you are pressing the right button.
22600
+---+
|Filename: Screenshot from 2017-04-26 22-11-42.png |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=22600|
paul- wrote:
> Not sure how you are doing this, but here is what I did
>
> Fresh Image
> - Expand SD Card
> - Install extra file systems
> - Setup USB Mount
> - Install Samba
> - Set Server Name, Workgroup, and Share
> - Set Password
>
> Samba Works. and if I ssh in
> >
Code:
dhull wrote:
> Paul,
>
> I've tested installing Samba by installing it at the end of a clean
> install from scratch. I have convinced myself that the Set Samba dialog
> with Samba running and a new password in the field does NOT create a
> Samba user. Invoking the command "sudo pdbedit -L"
paul- wrote:
> Nothing was changed with samba in 3.20 from 3.11. You have always had
> to set the password from the web interface.. this adds a user and
> password.
>
> usr/local/var/lib/samba is already added to the backup set. That takes
> care of everything recursively below.
Paul,
paul- wrote:
> There does appear to be a timing issue when the drivers are loaded, vs
> when the modprobe.conf file is updated at boot time.I'm really not
> sure where to go here without hardware in my hands to work out the bugs.
Hi Paul, Indeed finding the bug is difficult without direct
Wifi drivers are for the most part controlled by the upstream kernel,
there are a few exceptions. I've seen many drivers break due to
upstream changes. The rtl8192cu driver is one that has been a
nightmare. With that driver, we decided to follow what OSMC does and
revert to an older 8192cu
paul- wrote:
> What good does referring someone to a wifi list, when they are trying
> to make something work? I don't think there is any such thing as
> "proved to work" when it comes to wifi and linux.
The point is that if someone really wants to make a pCPlayer wifi then
there is a list of
is it possible to implement a "phone home" in the beta, and have it dump
pCP version
Pi type
dac/audio out
wifi type/model
wifi sig strength
etc
etc
user may be prompted to add a few comments. 100 char max or something
eg. slow to boot. playing everything except BBC iplayer
it might be a way
Wirrunna wrote:
> pCP Team, WiFi dongle issues are a recurring theme with new releases,
> probably because of the vast number of dongles available.
> Listing a "preferred " hardware set is probably not a good call as other
> projects found out in the past, but there is already a very handy table
paul- wrote:
> Works fine here, If I had to guess, there is a channel conflict on your
> router. Try changing your channel.
pCP Team, WiFi dongle issues are a recurring theme with new releases,
probably because of the vast number of dongles available.
Listing a "preferred " hardware set is
I updated my 4 players and my LMS now to 3.20 with no problems after
running the hotfix - all seems to have gone fine. One very minor thing
- the output settings for the USB cards seem to get lost in the upgrade
- in the UI at least. Just needed to go into the UI and reselect the
correct output
Eyerex wrote:
> For some strange reason i can never get the WiFi working on the 3.20
> beta's or final using the Pi3 WiFi all i get is
> Scanning..
>
> No wifi devices found!
>
> Possible error:
>
> 1. USB wifi adapter missing - insert adapter.
> 2. wifi drivers and firmware missing -
For some strange reason i can never get the WiFi working on the 3.20
beta's or final using the Pi3 WiFi all i get is
Scanning..
No wifi devices found!
Possible error:
1. USB wifi adapter missing - insert adapter.
2. wifi drivers and firmware missing - reboot required.
Setup
Pi3
I just did in-situ updates to all 3 of my pCp players. I tried updating
to the "audio" on one and while it updated, the Ratlink wifi wouldn't
work, so I connected an ethernet cable and updated again - but this time
to standard pCp. Working now.
RPi 2B, Kali reclocker, I2S generic DAC on 2 pCps
Thanks guys, another donation made. I am pretty pumped to be able to
hear my Allo Boss. :o
mjock3's Profile: http://forums.slimdevices.com/member.php?userid=49183
View this thread:
paul- wrote:
> Nothing was changed with samba in 3.20 from 3.11. You have always had
> to set the password from the web interface.. this adds a user and
> password.
>
> usr/local/var/lib/samba is already added to the backup set. That takes
> care of everything recursively below.
I'll
dhull wrote:
> In the last beta Samba network share still won't work unless a Samba
> user is added manually. In addition, the new Samba user goes away when
> the system is restarted. I found that I could fix this by adding
> /usr/local/var/lib/samba/private/passdb.tdb to /opt/.filetool.lst.
>
paul- wrote:
> We'll be starting a new thread for the release version. But for the
> Beta guys out there, the release version is available for
> insitu_update.
>
> -Minor tweaks from the last beta.
> -Reloading the reboot page should no longer reboot your pCP device
> again.
> -You can now do
paul- wrote:
> We'll be starting a new thread for the release version. But for the
> Beta guys out there, the release version is available for
> insitu_update.
>
> -Minor tweaks from the last beta.
> -Reloading the reboot page should no longer reboot your pCP device
> again.
> -You can now do
Eyerex wrote:
> Hello is this the final build which is now on sourceforge
> https://sourceforge.net/projects/picoreplayer/
yes. Complete images are availiable on the sourceforge site.
paul-'s Profile:
Hello is this the final build which is now on sourceforge
https://sourceforge.net/projects/picoreplayer/
Eyerex's Profile: http://forums.slimdevices.com/member.php?userid=65695
View this thread:
We'll be starting a new thread for the release version. But for the
Beta guys out there, the release version is available for insitu_update.
-Minor tweaks from the last beta.
-Reloading the reboot page should no longer reboot your pCP device
again.
-You can now do an insitu_update and change
I want to upsample only -16bit/ 44.1hz to 24bit/192hz -. if dsd or high
than 16/44.1 don't change
what command line I need to input in upsample -r 44.1
because I don't know how to set. thanks
htctyo's Profile:
methers wrote:
> Thank you! I can now see that the AMP+ only supports 44.1kHz and 48kHz
> sample rates.
>
> The weird thing is that is used to work before. Perhaps the audio was
> being downsampled somewhere without me realising.
>
> I suspect the solution is to bin the AMP+ and use a separate
Tex wrote:
> but I suspect it's the sound card. You might check with the HiFiBerry
> folks just a quick look on their message board came up with this.
>
> https://support.hifiberry.com/hc/en-us/community/posts/115000578365-Problems-after-upgrade-to-kernel-4-9
>
>
methers wrote:
> First post! Be gentleĀ
>
> I've hit problems that I can't solve on my own despite some tinkering
> and searching of previous threads, so I'm hoping someone can help me
> out.
>
> I previously had LMS installed on my NAS, but now have it running on one
> of my PiCorePlayer
but I suspect it's the sound card. You might check with the HiFiBerry
folks just a quick look on their message board came up with this.
https://support.hifiberry.com/hc/en-us/community/posts/115000578365-Problems-after-upgrade-to-kernel-4-9
Silly me. I was using the audio version of piCorePlayer. I have since
installed the standard version.
I added 'dtoverlay=rpi-cirrus-wm5102' to /mnt/mmcblk0p1/config.txt, and
also added 'softdep arizona-spi pre: arizona-ldo1' to
/etc/modprobe.conf.
Below is the relevant output from dmesg:
Wirrunna wrote:
> . I tried turning off the HDMI port to reduce power draw.
Did you notice improved sound quality? :confused:
We often add options on a whim and don't mention them We need a
better Marketing Department! :D
paul- wrote:
> This is posted for insitu_upgrade. Or burn a 'new image'
> (https://sourceforge.net/projects/picoreplayer/files/beta/piCorePlayer3.20beta7/).
>
> Kernel updated to 4.9.21
> Updated Boss driver, which is supposed to address the clicking between
> tracks when rate changes.
>
>
There does appear to be a timing issue when the drivers are loaded, vs
when the modprobe.conf file is updated at boot time.I'm really not
sure where to go here without hardware in my hands to work out the bugs.
paul-'s
Below is the output from my Pi. BTW, it's a Model B Rev 2.
Code:
tc@piCorePlayer:~$ dmesg
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.9.21-pcpAudioCore (paul@NUC-Devel) (gcc
version 4.9.3 (crosstool-NG
paul- wrote:
> Can you give me the output of lsmod, and look at dmesg to see what is
> logged related to the card.
Hi paul-
I am in the same situation as petar:
Aplay -l and squeezelite -l do not show the cirrus driver/card entries
like raspbian jessie does
Here some exact data:
petar wrote:
> Hi again,
>
> I tried this, and after the reboot, there was still no Wolfson card
> showing (using aplay -l to list the devices).
>
> Anything else I can try?
>
> Thanks,
> Pete
Can you give me the output of lsmod, and look at dmesg to see what is
logged related to the card.
paul- wrote:
> M-H
>
> I've added the missing modules. On your system running 3.20 beta 7
> (Regular pcpCore only), Do this update.
>
> >
Code:
> >
> tc@piCorePlayer:~$ sudo vi /etc/modprobe.conf
>
> Add a the following line
> softdep arizona-spi pre:
After creating a share of a NTFS USB flash drive, no access to that
share from Windows machine though I can see the share. The
username/password is rejected with a note about lacking permissions.
The config info follows:
[global]
netbios name = PICORE
workgroup = HULL
log file = /var/log/%m.log
htctyo wrote:
> My device is Rip3b , I use 3.2beta7 with internal Wifi but fail.
> Cannot scan any SSID . But use 3.11 is fine Wifi is OK
Please supply complete hardware configuration and wifi debug
information.
My device is Rip3b , I use 3.2beta7 with internal Wifi but fail.
Cannot scan any SSID . But use 3.11 is fine Wifi is OK
htctyo's Profile: http://forums.slimdevices.com/member.php?userid=66802
View this thread:
M-H
I've added the missing modules. On your system running 3.20 beta 7
(Regular pcpCore only), Do this update.
Code:
tc@piCorePlayer:~$ sudo vi /etc/modprobe.conf
tc@piCorePlayer:~tc@piCorePlayer:~$ pcp bu
[ INFO ] Backing up files to
M-H wrote:
> Not important to most, but a fault situation that is not handled in the
> script?
>
> If the free storage size is known to be insufficient, we'd better stop
> the downloads, and go to cleanup.
>
> Noted output :
> [ INFO ] You are downloading piCorePlayer3.20beta7
> [ INFO ] You
htctyo wrote:
> 3.2beta7
> cannot connect Wifi
> My devvice is RiP3b
Hi htctyo , I hope you had a typo ( RIP3b vs RPi3b ) else the cause is
known.
Some constructive feedback : My pi-zero with Original raspberry pi
foundation WiFi Dongle is working , and to my knowledge it is the same
3.2beta7
cannot connect Wifi
My devvice is RiP3b
htctyo's Profile: http://forums.slimdevices.com/member.php?userid=66802
View this thread: http://forums.slimdevices.com/showthread.php?t=107223
Hi team,
Perhaps noted with you, but not on the forum:
Wifi chipset MT7601U ( mediatek ) was not working OK in Beta5
I did an insitu upgrade , on my small 128 MB tf card, and it succeeded.
After that upgrade the MT7601U wifi dongle worked.
So a pi Zero, with a 128MB TF card and a 1Euro98 Wifi
BTW, to get the card working on Jessie Lite, I followed the bellow steps
from http://www.horus.com/~hias/cirrus-driver.html
Code:
Configuration for kernel 4.9
Enable the driver
Add the following line to /boot/config.txt to enable the Cirrus Logic card
driver
sbp wrote:
> Yes I think we could try.
> But as we don't have a wolfson card we need info from you.
>
> Can you ssh into the latest piCorePlayer3.20 beta 7
> > >
- Mount mmcblk0p1 (by using the command: m1)
- Edit mnt/mmcblk0p1/config.txt - here you add
> dtoverlay=rpi-cirrus-wm5102 -
that helps, there is a ton of Arizona modules. I wonder if I need the
mic input stuff too just to play sound.
Let me dig into this
paul-'s Profile: http://forums.slimdevices.com/member.php?userid=58858
View this thread:
paul- wrote:
> Just make sure you are using stock raspbian. In the past the Wolfson
> support was a out of tree driver, the support has only recently been
> added to the rpi kernel. Let us know what you can. Also, which
> card are you using, the old Wolfson card, or the element 14 cirrus
M-H wrote:
> No I do not have a working setup anymore, but I will get a copy of
> raspbian and see if can make it work, to compare it against.
>
> The pcp320B7 setup a has the same results, as posted above from
> pcp320B5
>
> And noteworthy : The green led on the clac dims during the boot ,
paul- wrote:
> Definitely seems like the card wants something else. Do you have the
> card working on a different system?
> Getting a module list from a working and then the pCP system would help
> (lsmod)
No I do not have a working setup anymore, but I will get a copy of
raspbian and see if
Definitely seems like the card wants something else. Do you have the
card working on a different system?
Getting a module list from a working and then the pCP system would help
(lsmod)
paul-'s Profile:
sbp wrote:
> Yes I think we could try.
> But as we don't have a wolfson card we need info from you.
>
> Can you ssh into the latest piCorePlayer3.20 beta 7
> > >
- Mount mmcblk0p1 (by using the command: m1)
- Edit mnt/mmcblk0p1/config.txt - here you add
> dtoverlay=rpi-cirrus-wm5102 -
M-H wrote:
> Great !
> I've been waiting 2 years to do something useful with my 2! spare cards
> ( cirrus Logic version )
> Can someone direct me to the B7 download ?, else I have to use the B5
> for the moment.
>
> Greetz MH
sbp wrote:
> Yes I think we could try.
> But as we don't have a wolfson card we need info from you.
>
> Can you ssh into the latest piCorePlayer3.20 beta 7
> > >
- Mount mmcblk0p1 (by using the command: m1)
- Edit mnt/mmcblk0p1/config.txt - here you add
> dtoverlay=rpi-cirrus-wm5102 -
petar wrote:
> Hi there,
>
> Great work on piCorePlayer. I have several Pis at home and they are all
> working really well.
>
> I do have a spare one that has a Wolfson card in it, but unfortunately
> this card hasn't been supported.
>
> I see this new version of piCorePlayer is based on
Hi there,
Great work on piCorePlayer. I have several Pis at home and they are all
working really well.
I do have a spare on that has a Wolfson card in it, but unfortunately
this card hasn't been supported.
I see this new version of piCorePlayer is based on kernel 4.9.17, which
I believe has
Hi Greg,
Greg Erskine wrote:
> Thanks for your feedback M-H,
> I think Beta 7 is recently available.
> Greg
OK I will reload the TF cards with the latest and start over. ( getting
experienced with that ) and I can try the the insitu upgrade , as it is
within the 3.20 release ? lets find out.
The audio version of the beta works perfect here, thanks a lot.
And, as a bonus, I now no longer have the pulsing background noise that
used to irritate me. It was quite soft, but clearly noticeable -
something like 4-5 beats per second.
Thanks :-)
paul- wrote:
> This is posted for insitu_upgrade. Or burn a new image.
>
> Kernel updated to 4.9.21
> Updated Boss driver, which is supposed to address the clicking between
> tracks when rate changes.
>
> Also, just an FYI, do not turn off your HDMI port with 3.20 (Tweaks
> page HDMI power)
I just did insitu updates to all 3 pCp players. I tried updating to the
"audio" on one and while it updated, the Ratlink wifi wouldn't work, so
I connected an ethernet cable and updated again - but this time to
standard beta 7. Working now.
One thing I have noticed on the 3.20 beta is the Harry
paul- wrote:
> I'm going to leave the main repo at 7.9.0 for a while. I modified the
> updater script so you can update to 7.9.1. Once on 7.9.1, nightly
> updates should work as before.
>
> Follow these steps.
>
> >
Code:
> >
> tc@piCorePlayer:~$ cd /tmp
>
kidstypike wrote:
> Option to use/install LMS 7.9.1 nightlies instead of 7.9.0 release.
>
> Many thanks :)
I'm going to leave the main repo at 7.9.0 for a while. I modified the
updater script so you can update to 7.9.1. Once on 7.9.1, nightly
updates should work as before.
Follow these
paul- wrote:
> This is posted for insitu_upgrade. Or burn a new image.
>
>From 3.1x or only earlier beta of 3.20 ?
Paul Webster
http://dabdig.blogspot.com
Paul Webster's Profile:
This is posted for insitu_upgrade.
Kernel updated to 4.9.21
Updated Boss driver, which is supposed to address the clicking between
tracks when rate changes.
Also, just an FYI, do not turn off your HDMI port with 3.20 (Tweaks
page HDMI power) If you do, your I2S soundcard will probably no
Thanks for your feedback M-H,
M-H wrote:
> To help you all with the great efforts, I have upgraded my pcp domain to
> 3.20B5
I think Beta 7 is recently available.
> Sofar I have found nothing I could not fix with the common sense and
> previously posted solutions to known problems.
>
> 2
To help you all with the great efforts, I have upgraded my pcp domain to
3.20B5
Sofar I have found nothing I could not fix with the common sense and
previously posted solutions to known problems.
2 issue's areas however I would like to mention:
1) when using an odd 128MB ( ! no typo !) tf
my wifi is working again with beta7 (skipped beta6)
is anyone getting 24bit over hdmi?
i get samplerates up to 192000 fine, but the bitrate stays according to
hw_params at 16 bit.
thats the last bit thats not working for me.
thanks for this great product.
quadronado wrote:
> I had a similar problem a few days ago. I turned out to be a space in
> the ssid. Maybe you used some special characters in your ssid or pswd?
> When I type the ssid with the space into the pcp webinterface there is
> no problem. Only the newconfig method had problems with
thornton wrote:
>
>
> then copied the file to the pcp partition of the ssd.
> Put the card in the raspi zero w and powered it up.
> It is starting up, the led is blinking for a while, until its a
> unintermitted green light.
>
> But the raspi doesnt appear on my router.
>
I had a similar
thornton wrote:
> Hi everybody, i am new here. I am using daphile and a squeezelite client
> on a raspi (raspbian) very happily.
>
> Now i wanted to install picoreplayer on a raspberry zero w. And i dont
> get it to work.
>
> What i did until now:
> Downloaded piCorePlayer3.20beta6.img
>
My router was using channel 12 or 13. Didnt have this in my head. Now on
a lower channel everything is working fine!
thornton's Profile: http://forums.slimdevices.com/member.php?userid=66793
View this thread:
with all these different dac hats you devs sure have it easy :p:p:p
rPi 3 + rasPi 7" LCD + HiFiBerry DiGi+ | rPi 2 + IQaudio DAC+ |rPi 2 +
HiFiBerry DAC+ | Squeeze Box Touch | LMS + XPenology on HP Gen 8 |
huxmut's
huxmut wrote:
> I dont understand, I have two hifi berry hat's, one digi+ one dac+, both
> work fine with rPi3 built in wifi
>
This was meant for the "pro" boards. The first versions of the board
interfered with the rpi3 wifi. I'm not sure when they fixed the
problem.
paul- wrote:
> ..If the product is made by Hifiberry, then rpi3 onboard wifi is almost
> guaranteed to fail.
I dont understand, I have two hifi berry hat's, one digi+ one dac+, both
work fine with rPi3 built in wifi
fsger wrote:
> In both 3.11 and 3.20 96KHz files appear to play but no
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
1 - 100 of 147 matches
Mail list logo
