The Raspberry Pi 3

[hondagx35]

Hi scan80269,

My files are in FLAC on the NAS, but I use MinimServer/MinimStreamer to decode FLAC to PCM (WAV) before streaming out, so the PCM bitstream over Ethernet or WiFi for the above file is nearly 17Mbps.

What is the reason behind this?

Frank

[scan80269]

Hi Frank,

My NAS was set up to do FLAC-to-PCM decoding because my Auralic Aries sounds better with FLAC decoding offloaded from its processor. My Pi3 and Pi2 are recent arrivals and I haven't re-configured MinimStreamer to skip FLAC decoding on their behalf. 95% of my content is Redbook 16/44.1, and I used the one DXD album I have just as a stress case for the Pi3.

I was expecting the Pi3 WiFi to be on par with an N150 WiFi dongle in performance (throughput, latency, etc.) but apparently the Pi3 WiFi is disadvantaged in some way. Unfortunately I lack the time to drill into it for better understanding, and I'm also a total Linux newbie.

[GAP]

I set up my RPi 3 on Saturday.

NAS -> Pi over onboard Wifi -> Henry Audio DAC -> NAD c316cbee -> B&W 685

It worked flawlessly with my Henry Audio DAC through USB Async. Have not yet had time to listen for a longer period. I experienced some static noise during first seconds on a few 24/192 tracks. It seems like it might be wifi-related, I increased the buffer size to 4096 and buffer time to 30%, I am not sure if this was it but since then I have had no troubles *cross fingers*, or if it was just a sudden wifi instability on my network.

EDIT: Still, continuous stutter on 24/192 tracks. 24/96 works great. I will try tomorrow with a usb stick, as of now I have no real possibility to try to ethernet:(

Sounds great so far. I experience the sound to be fuller, with greater dynamics and the lows are a bit more emphasised compared to a harsher sound with the same DAC on my Macbook pro. Is this reasonable or am I just crazy?

Thank you very much for this.

[rocklander]

purchased some DACs from aliexpress.. work fine with this, but I noticed one of my units was producing more noise than the other.
various cable swaps and visual testing (my mixer shows signal levels nicely) and noticed that one PI was producing -70~-60db of noise, the other -40~-24db (significant difference).
I swapped the power cables and no difference.. swapped the RCA lead and boom.. the issue followed. I didn't expect the audio cable to make that big of a difference...

[rastus]

I didn't expect the audio cable to make that big of a difference...

A good and interesting discussion about jitter, cables, and their negative affects on digital music. It really put it into perspective for me.

Why digital seems to be affected by power and cables:
http://www.stereo.net.au/forums/index.p ... nd-cables/

The good stuff, I think, starts here (page 13):
http://www.stereo.net.au/forums/index.p ... es/page-13

[andre_chang]

My PI3 + RuneAudio_rpi2_rp3_0.4-beta_20160321_2GB.img

Play file MP3 playback progress can be any forward and backward!
"But in some wav file playback, playback progress can not arbitrarily choose forward back, this function is invalid!"
This problem does not happen on Pi2. It's normal. What's the reason?

This version of the boot speed is very slow!
the last version of the Pi2 in the IP as long as the Ping can pass, the browser on the start of about 20 seconds...
"But the new version of "PI3" from the boot to the browser can open to enter the UI at least to more than 1 minutes."

andre

[rocklander]

should we post requests here?
on the client, if I'm not playing a song yet (and it's on shuffle) I'd like to be able to shuffle to the next song, even though it's not playing one.

the situation is - I have a bunch of songs in my playlist, and I'm about to hit play.. but don't want to hear the song I see up first.. want to shuffle to the next and decide if I like that one, then hit play... does that make sense?

[tboooe]

EDIT: Still, continuous stutter on 24/192 tracks. 24/96 works great. I will try tomorrow with a usb stick, as of now I have no real possibility to try to ethernet:(

Sounds great so far. I experience the sound to be fuller, with greater dynamics and the lows are a bit more emphasised compared to a harsher sound with the same DAC on my Macbook pro. Is this reasonable or am I just crazy?

Thank you very much for this.

Did you get a chance to try a usb wifi adapter? I have the same issue in my music room where wifi signal is very low. I ended up getting a wireless AC bridge and plugging an ethernet cable from the bridge to the Pi3.

As for sound, I totally agree. The Pi or Rune has more emphasis on the mid bass in my system. I am not sure if this is because of the Pi3, Rune, or my Digi+ card.

[PeteB]

This version of the boot speed is very slow! ...

Have you tried running "systemd-analyze" or anything similar, from the command prompt? This would show if some specific service is taking a long time to start, and then other people who have a Pi3 could compare actual numbers with your results.

Code: Select all

systemd-analyze
systemd-analyze blame
systemd-analyze --help

[matlo74]

hi

please find my results :
[root@runeaudio ~]# systemd-analyze
Startup finished in 4.294s (kernel) + 1min 31.236s (userspace) = 1min 35.530s
[root@runeaudio ~]# systemd-analyze blame
1.170s dev-mmcblk0p2.device
1.029s smbd.service
370ms systemd-vconsole-setup.service
344ms nginx.service
236ms avahi-daemon.service
215ms systemd-resolved.service
195ms logrotate.service
172ms rpc-statd.service
157ms systemd-udevd.service
150ms systemd-udev-trigger.service
142ms kmod-static-nodes.service
129ms tmp.mount
119ms systemd-journald.service
118ms nmbd.service
113ms ntpd.service
106ms systemd-sysctl.service
102ms sys-kernel-config.mount
92ms shadow.service
83ms systemd-tmpfiles-setup-dev.service
68ms rune_shutdown.service
67ms systemd-remount-fs.service
55ms php-fpm.service
55ms nfs-config.service
45ms systemd-user-sessions.service
38ms systemd-random-seed.service
34ms systemd-update-utmp.service
32ms dev-mqueue.mount
26ms systemd-tmpfiles-setup.service
25ms boot.mount
16ms redis.service
15ms sys-kernel-debug.mount
14ms var-log.mount
12ms rpcbind.service
6ms var-log-runeaudio.mount
lines 12-34/34 (END)
129ms tmp.mount
119ms systemd-journald.service
118ms nmbd.service
113ms ntpd.service
106ms systemd-sysctl.service
102ms sys-kernel-config.mount
92ms shadow.service
83ms systemd-tmpfiles-setup-dev.service
68ms rune_shutdown.service
67ms systemd-remount-fs.service
55ms php-fpm.service
55ms nfs-config.service
45ms systemd-user-sessions.service
38ms systemd-random-seed.service
34ms systemd-update-utmp.service
32ms dev-mqueue.mount
26ms systemd-tmpfiles-setup.service
25ms boot.mount
16ms redis.service
15ms sys-kernel-debug.mount
14ms var-log.mount
12ms rpcbind.service
6ms var-log-runeaudio.mount