The quality is impressive. I was using HDMI before which already sounds
great, but with the HiFiBerry there is even more clarityin the music and
more dynamic range. I did not try 192k files yet, but uncompressed Flac
music (Wimp HiFi) sounds really good.
I'm not 100% sure about the alsa settings
JackOfAll wrote:
Code:
sudo usermod -a -G audio cs-web
sudo systemctl restart cs-web
Thank you and Triode - works very well now.
slackhead's Profile:
I'm sorry for the off topic, but I need to ask... I've been curious
about the prometheus, are you happy with it? Do you have any idea on how
it compares to other ES9018 DACs? (I'm specially interested in comparing
it to the Buffalo III, since it's the one I've chosen).
I did not have time
I have my Hifiberry hooked up to a vintage Sony TA-2650 amp with KEF
Chorale speakers and I must say that I'm very impressed with the
quality. The only thing I'm strugglin with is the LMS (on another
raspberrypi) becoming very slow after a few days of use, I need to
reboot every day otherwise it
psketch wrote:
Hi Steen
Sorry - I'd missed it. I've just replied.
pete S
Hi Steen
Not sure if you'd seen my PM, but I did reply to yours (somewhat delayed
though)
pete S
psketch's Profile:
@piotrus
The alsa settings are parameters for Squeezelite. You can set them in
the PiCorePlayer or Squeezelite options. If you habe no clicks and pops
or distorted sound then you probably don't need to set it. I had to use
it on Squeezeplug 6 for HDMI and also on older PiCorePlayer versions.
I'm
psketch wrote:
Hi Steen
Not sure if you'd seen my PM, but I did reply to yours (somewhat delayed
though)
pete S
Hi Pete
Thank you
I'm almost ready with the new version - so I will let you know.
Steen
piCorePlayer a small player for the Raspberry Pi (25MB in RAM).
Homepage:
I've managed to test F20 with the stock Fedora kernel and prerelease
3.13 together with my mytek DAC and UAC2 compatible DAC.
Here are my findings:
Stock Fedora (3.12.6-300).
- UAC2 compatible DAC, everything works OK. Including highres and DSD
DoP output
- Mytek with my Mytek driver
dsdreamer wrote:
DSD- PCM works, but outputs at 352.8 kHz. (Is that expected?).
Yes, DSD64 - native PCM @ 352k8. DSD64 - DoP PCM @ 176k4.
Thank you for testing!
JackOfAll's Profile:
lintweaker wrote:
Stock Fedora (3.12.6-300).
- UAC2 compatible DAC, everything works OK. Including highres and
DSD DoP output
- Mytek with my Mytek driver (packaged by Clive), Everything works
OK, including highres and DSD DoP output(*)
Great!
lintweaker wrote:
slackhead wrote:
Thank you and Triode - works very well now.
Thank you for testing. When I had a quick fiddle, prior to releasing the
package, I was using pulse device on desktop, and didn't notice that the
hardware devices were missing from the drop-down list... Oops!
DJanGo wrote:
May i check whats happen if i nc the lms to volume up and down the pi
over the next night[/b]
Worth a shot...but if the player is playing, the data stream should keep
it awake. but possibly it it still the lack of local activity. I
used a ping every 30 seconds and that
CS-WEB-0.1-0.3.GITFD196CD
Changes...
Code:
* Thu Jan 16 2014 - 0.3-fd196cd
- Apply cs-web-squeezelite-vis.patch.
Add VISULIZER to squeezelite config page.
- Apply cs-web-squeezelite-created-by.patch.
'created by' line starts with a hash.
DJanGo wrote:
edit one one of my pi (the last one) i'll changed crontab like this (not
running my bugfix right now)
(..199.1 is my audionetwork wlan router - means the pi pings every 15
min. the router)
Code:
crontab -e
*/15 * * * * ping -c 1 192.168.199.1
Thanks to Triode and dsdreamer for the initial flirc config file for the
squeezebox remote.
I've added more functions for the remaining unconfigured keys from
dsdreamer's map.
Sleep = Escape/Back
Power = Power (Only from Now Playing screen)
Favorites = Favorites
Search = Current Track Info
dsdreamer wrote:
Eight bells and all's well.
Code:
[root@wandquad ~]# uname -a
Linux wandquad 3.13.0-0.rc8.git1.2.1.cs.fc20.armv7hl #1 SMP Tue Jan 14
17:32:29 GMT 2014 armv7l armv7l armv7l GNU/Linux
[root@wandquad ~]# uptime
07:30:52 up 8:08, 1
ralphy wrote:
Thanks to Triode and dsdreamer for the initial flirc config file for the
squeezebox remote.
Thanks, Ralph!
dsdreamer, can you let me know where you want to go with this At the
moment on the website jivelite page, we have links to Triode original
FLIRC config and your
lintweaker wrote:
Haha! ;) I just compiled 3.13.0-0.rc8.git2.1 on my x86_64 box to see if
the mytekusb2 driver would work there. But it would not boot. Somehow
there is no ramdisk image...I cannot recall hearing they are going to
stop using it for F21 (could be). Trying again...
bakker_be wrote:
Wasn't the plan not to need an external DAC :P
Sure. LOL. But we are not there yet. What we do have is a motley crue of
users with external DAC's USB (UAC12, 3 modules in use, generic,
hiface, mytek), HDMI, and SPDIF. Plus the on-board sgtl5000, for
analogue out, which I'm
Of course we won't leave anyone behind, I was only joking ;) Will Johns
DAC solution even do DSD? It's of no interest to me, I'm not planning on
getting any DSD. With much of the music I listen to I consider myself
lucky to find decently mastered redbook, but I can imagine the situation
being
JackOfAll wrote:
Until lintweaker trys playing music to his mytek DAC, then it
locks-up... ;)
Haha! ;) I just compiled 3.13.0-0.rc8.git2.1 on my x86_64 box to see if
the mytekusb2 driver would work there. But it would not boot. Somehow
there is no ramdisk image...I cannot recall hearing
bakker_be wrote:
Will Johns DAC solution even do DSD?
Perhaps as a longer term goal, but for now, the DAC chip we're using for
the CS hardware, PCM5142, is PCM only.
JackOfAll's Profile:
Hi,
I try to download
http://www.communitysqueeze.org/images/wandboard/CSOS/F19-R2/CSOS-Wandboard-Quad-F19-R2-20130910-1.img.7z
but I get always:
Error 403
You don't have permission to access
/images/wandboard/CSOS/F19-R2/CSOS-Wandboard-Quad-F19-R2-20130910-1.img.7z
on this server.
Thanks for
Mr. Floppy wrote:
I try to download
http://www.communitysqueeze.org/images/wandboard/CSOS/F19-R2/CSOS-Wandboard-Quad-F19-R2-20130910-1.img.7z
but I get always:
Error 403
You don't have permission to access
/images/wandboard/CSOS/F19-R2/CSOS-Wandboard-Quad-F19-R2-20130910-1.img.7z
on
lintweaker wrote:
Haha! ;) I just compiled 3.13.0-0.rc8.git2.1 on my x86_64 box to see if
the mytekusb2 driver would work there. But it would not boot. Somehow
there is no ramdisk image...I cannot recall hearing they are going to
stop using it for F21 (could be). Trying again...
Just pushed
sbp wrote:
I would be very interested in seeing the result of your experience if
you used a LAN cable. For me I sometime see the same using LAN. So don't
think that all of our problems are caused by power saving by the WiFi
adaptor. Somehow squeezelite is the only program that are affected.
JackOfAll wrote:
'kernel-3.13.0-0.rc8.git2.2.fc21.src.rpm'
(http://alt.fedoraproject.org/pub/alt/rawhide-kernel-nodebug/SRPMS/kernel-3.13.0-0.rc8.git2.2.fc21.src.rpm)
seems to be the latest nodebug rawhide kernel. Maybe try building that?
Thanks, tried that. Still no initrd img file :( Not
lintweaker wrote:
Thanks, tried that. Still no initrd img file :( Not sure what is going
on here. I'll retry with the next rc or 3.13 final.
Have you tried running re-running dracut by hand..
Code:
cd /boot
sudo dracut
Hi guys
I've been playing with piCorePlayer 1.10 for the first time and it is
very nice!
I do have a couple of questions about the setting-up of parameters, the
first to permit access to a hidden wireless network, the second about
nominating a Squeezebox server.
1). ACCESS TO A HIDDEN WIRELESS
Reeshar wrote:
To connect to a Squeezebox server on a different subnet I need to
nominate the server explicitly.
However, if I set a server IP using the picoreplayer setup command (and
save the settings) the server name doesn't appear in the command shown
by ps:
lintweaker wrote:
Thanks, tried that. Still no initrd img file :( Not sure what is going
on here. I'll retry with the next rc or 3.13 final.
I'm clutching at straws, but I've got a sneeky feeling that your
problems might be related to the selinux-policy bug that causes package
scriptlets to
Reeshar wrote:
Fairly easy to fix, hopefully?
Richard
Actually it is.
I've edited the */usr/local/sbin/config.cfg* file to remove the _IP
from the end of SERVER_IP and done the same in the
*/usr/local/sbin/set_server.sh* file. I've then saved the files back to
the permanent file system
JohnSwenson wrote:
If the software guys can do this I could add a separate board that plugs
in either to the wandboard IO connectors or the special connector on the
CSP.
I'm going to bite my tongue and be quiet! ;)
Reeshar wrote:
OK, I've spotted the bug in the following file:
/usr/local/etc/init.d/squeezelite_initd
Code:
case $1 in
start)
echo Starting Squeezelite
start-stop-daemon --start --quiet -b -m -p/var/run/squeezelitehf.pid --exec
Reeshar wrote:
Hi guys
I've been playing with piCorePlayer 1.10 for the first time and it is
very nice!
I do have a couple of questions about the setting-up of parameters, the
first to permit access to a hidden wireless network, the second about
nominating a Squeezebox server.
1).
Hi everyone, I'm new to Pi, having purchased one just for picoreplayer!
but I'm having a problem with the wifi...
I downloaded v1.10, installed it to a SD, installed Logitech Server and
had the Pi working perfectly with ethernet connection. I changed the
output to 3.5mm jack and changed the
sbp wrote:
Hi I haven't tried such a setup, however if you are happy to manually
change a file, I think you could do it by changing the content of the
wifi.db file.
it contains the ssid name, password and encryption.
steen
I've had a look at that but it only seems to map to the SSID, the
paul- wrote:
I used a ping every 30 seconds and that did not work.
yupp same same but different after the volume up down nc :confused:
paul- wrote:
Does this player do the exact same thing when connected via the ethernet
port?
Yupp
paul- wrote:
What version kernel and firmware are you
Biblu wrote:
Hi everyone, I'm new to Pi, having purchased one just for picoreplayer!
but I'm having a problem with the wifi...
I downloaded v1.10, installed it to a SD, installed Logitech Server and
had the Pi working perfectly with ethernet connection. I changed the
output to 3.5mm jack
DJanGo wrote:
all the same, but had this issue since my first pi (that should be
1year)
I have 3 rpi's running squeezlite my first pi is over a year old too
(All of mine are 512k versions). There were a couple of networking
bugs in Squeezelite that didn't get worked out until the
Reeshar wrote:
Firstly, your IP address will change when the Pi connects via wireless.
This is because the Pi's WiFi adaptor has a different MAC address to the
physical connector so your DHCP server will think it's a different
device.
You can find out the new IP address by resetting and
Biblu wrote:
Hey Richard,
Thanks for the reply :)
Yeh the IP address changing caught me out at first, but I logged onto my
router and watched the new device pop up so I knew I had the right IP
address.
The IP address of the Pi is 192.168.0.95 (ethernet) and 192.168.0.96
(wifi), the
Reeshar wrote:
OK... So you can definitely see that the Pi is connected to the router
and has got an IP address by looking at the router?
If yes, normally at this point I would suggest connecting a screen and
keyboard directly to the Pi so that you can test connectivity outbound
onto the
I read up about wifi compatibility briefly before ordering so got the
same adaptor: Edimax EW-7811UN.
The pi definitely has a wireless IP address through looking at the
router; I can see both the wired and wireless ip's.
The mac is my server and what I am using to access the Pi, and yes it is
Biblu wrote:
I read up about wifi compatibility briefly before ordering so got the
same adaptor: Edimax EW-7811UN.
The pi definitely has a wireless IP address through looking at the
router; I can see both the wired and wireless ip's.
The mac is my server and what I am using to access
My HiFiBerry DAC arrived today and I waisted no time in connecting it
up. Issue is that I get no audio output. What is the recommended way
of setting it up. I tried scanning for USB devices but it does not
show. What parameters should I pass or will it just automagically be
found on the Pi ?
bcdaus wrote:
My HiFiBerry DAC arrived today and I wasted no time in connecting it up.
Issue is that I get no audio output. What is the recommended way of
setting it up. I tried scanning for USB devices but it does not show.
What parameters should I pass or will it just auto-magically be
47 matches
Mail list logo
