I've verified part of the prep code with my USB SD Card writer so I'm not anticipating any issues with the device. I've also incorporated the Beta10 updates into the script and am in the process of making a few "enhancements" 🙂
-Tim
Definitely. I'm planning to fully support and host it at moodeaudio.org so it can easily be downloaded and launched 🙂
-Tim
Great news. I went ahead and tried with an old IPAD2. Worked the first try and been working all night. No more cutting out. No idea why my cell phone BT has trouble with RPi3. My Pi is running on wifi with BT ON as well. I will test with an older Iphone. In our home I am the only one with Android everything else running iOS or Mac OS.
I know! I was jumping for joy when Tidal was streaming. It's awesome work by Tim and the folks who contributed to build recipe v1.9.Not only is Beta 9 working awesome, I just got Tidal streaming working! This **** rules!
Playback issue:
Most of the time when I'm skipping the tracks the playback is not starting from 00:00:00, it bite a few ms/frames from start.
In continuous play track after track the playback is gapless and smooth.
There is a fix for this?
Most of the time when I'm skipping the tracks the playback is not starting from 00:00:00, it bite a few ms/frames from start.
In continuous play track after track the playback is gapless and smooth.
There is a fix for this?
I thought I did. Maybe reread it again.
My first computer was made in 1965. As I said, I first started with PCs with DOS, not my first rodeo.
Please enlighten me! What are you talking about?
*****
Beside that Arch Linux comes with several advantages over Raspbian
The IMO most important are:
1. Bleeding edge packages ( and here it starts with a more up2date gcc)
2. Rolling release (doubles the bleeding edge package effect)
... and causes much less work - on the long run - for the maintainer
I'm running Arch since years on my own installation. I'd never switch back to
Raspbian for PI.
However. If talking about a complex highly integrated desktop workhorse environment on a PC, I do prefer to run my Ubuntu system.
Enjoy.
Can't figure it out
Hi fellows,
got the several-times-seen-issue 24/96 streamed at 32/96. Found posts about but I can't understand when it's normal, a bug, Squeezbox related or ALSA stories. Of course resampling is disabled. Moode 3.8.4.
What annoys me most is that it is (for all) 24/96 files, output stream 32/96, then Allo DigiOne outputs 24/192 max. Are these extra bits 0 for any reason or resampled?
Thanks!
Hi fellows,
got the several-times-seen-issue 24/96 streamed at 32/96. Found posts about but I can't understand when it's normal, a bug, Squeezbox related or ALSA stories. Of course resampling is disabled. Moode 3.8.4.
What annoys me most is that it is (for all) 24/96 files, output stream 32/96, then Allo DigiOne outputs 24/192 max. Are these extra bits 0 for any reason or resampled?
Thanks!
Attachments
Last edited:
The data gets managed as 32 bit samples inside squeezelite - always!
I guess MPD is not working any different.
And yes, so called zero-padding takes place to fill up the 4 bytes with 0s.
The DAC tells ALSA - the Linux soundlayer - what bit-depths are supported.
ALSA handles the conversion if you choose "plughw:0,0". That means you can output 16bit from squeezelite and if your DAC just offers 32bit, ALSA will do the 0-padding.
If you use "hw:0,0" as output, squeezelite has to deliver exact the bitdepth as supported by the DAC. Otherwise it won't work.
You can try e.g:
to see what your DAC is actually running at.
If the DAC offers several bit-depths you can use either of these.
Bit-Transparency in strict terms pretty much doesn't exist nowadays.
That's no flaw though - especially if only 0-padding is involved.
Enjoy.
I guess MPD is not working any different.
And yes, so called zero-padding takes place to fill up the 4 bytes with 0s.
The DAC tells ALSA - the Linux soundlayer - what bit-depths are supported.
ALSA handles the conversion if you choose "plughw:0,0". That means you can output 16bit from squeezelite and if your DAC just offers 32bit, ALSA will do the 0-padding.
If you use "hw:0,0" as output, squeezelite has to deliver exact the bitdepth as supported by the DAC. Otherwise it won't work.
You can try e.g:
Code:
cat /proc/asound/card0/pcm0p/sub0/hw_params
access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 44100 (705600/16)
period_size: 16384
buffer_size: 65536to see what your DAC is actually running at.
If the DAC offers several bit-depths you can use either of these.
Bit-Transparency in strict terms pretty much doesn't exist nowadays.
That's no flaw though - especially if only 0-padding is involved.
Enjoy.
Last edited:
I have successfully compiled the beta 9 version of moode. I'm trying to run on the RPi3 a AUDIOPHONICS I-Sabre DAC ES9028Q2M but I can't setup hardware volume control (software control is working) , any help with that ?
thanks
Kai
thanks
Kai
@Soundcheck,
I've played a 24/96 and it does send 32 bits as checked with your command line. But my digital card chip, WM8805, is 16/20/24 bits only! Still lost...
(No DAC nor Squeezbox, just ask the Raspberry to send the bits via I2S to a Allo S/PDIF card).
I've played a 24/96 and it does send 32 bits as checked with your command line. But my digital card chip, WM8805, is 16/20/24 bits only! Still lost...
(No DAC nor Squeezbox, just ask the Raspberry to send the bits via I2S to a Allo S/PDIF card).
Hi Malefoda,
What happens if you drop back to the standard kernel that comes with Beta 9?
I am not running squeezelite but don't have an issue with sound here and we have similar stuff:
Input Processing
Source:
NAS/DiskStation (DS212)+/Keith Jarret - Koln Concert/Part IIa.wav
Encoded at:
bit, 44.1 kHz, Stereo, PCM_S16LE
Decoded to:
16 bit, 44.1 kHz, Stereo
Rate:
1.411 mbps
DSP Operations
Resampling:
24 bit, 192 kHz, Stereo (SoX very high quality)
Crossfeed:
off
Equalizer:
Graphic EQ: (off), Parametric EQ: (off}
Chip options:
none
Volume:
Software (MPD 32-bit float with dither)
Output Stream
Format:
32 bit, 192 kHz, Stereo
Rate:
12.288 mbps
Audio Device
Device:
Allo DigiOne
Chip:
Cirrus Logic WM8805
Architecture:
S/PDIF transceiver 24 bit 192 kHz
Interface:
I2S
SYSTEM: armv7l, 4 cores, 1.2 GHz, 13%, 63°
KERNEL: Standard 4.9.61-v7+
Good luck.
What happens if you drop back to the standard kernel that comes with Beta 9?
I am not running squeezelite but don't have an issue with sound here and we have similar stuff:
Input Processing
Source:
NAS/DiskStation (DS212)+/Keith Jarret - Koln Concert/Part IIa.wav
Encoded at:
bit, 44.1 kHz, Stereo, PCM_S16LE
Decoded to:
16 bit, 44.1 kHz, Stereo
Rate:
1.411 mbps
DSP Operations
Resampling:
24 bit, 192 kHz, Stereo (SoX very high quality)
Crossfeed:
off
Equalizer:
Graphic EQ: (off), Parametric EQ: (off}
Chip options:
none
Volume:
Software (MPD 32-bit float with dither)
Output Stream
Format:
32 bit, 192 kHz, Stereo
Rate:
12.288 mbps
Audio Device
Device:
Allo DigiOne
Chip:
Cirrus Logic WM8805
Architecture:
S/PDIF transceiver 24 bit 192 kHz
Interface:
I2S
SYSTEM: armv7l, 4 cores, 1.2 GHz, 13%, 63°
KERNEL: Standard 4.9.61-v7+
Good luck.
Hi,
I'm in Moode 3.8.4, no beta here 🙂
And no playback issue either! But as in your case, there is a 32 bit step in between, which troubles me as I don't understand why.
Just a curiosity issue! Hope that's no luck question 😉
I'm in Moode 3.8.4, no beta here 🙂
And no playback issue either! But as in your case, there is a 32 bit step in between, which troubles me as I don't understand why.
Just a curiosity issue! Hope that's no luck question 😉
Glad its working.
It would seem as per soundcheck's observations the creators of the code MPD and Squeezelite decided to work at 32 bit precision. As you point out we are tied to 24 bits by the WM8805 in the digione. I think we will have to live with this. You could start a debate along the lines can anyone hear the difference between 24 bit and 32 bit recorded/encoded data.
Diving for cover.
It would seem as per soundcheck's observations the creators of the code MPD and Squeezelite decided to work at 32 bit precision. As you point out we are tied to 24 bits by the WM8805 in the digione. I think we will have to live with this. You could start a debate along the lines can anyone hear the difference between 24 bit and 32 bit recorded/encoded data.
Diving for cover.
Last edited:
I see, so the 16 bit processed at 16 bit is adding trouble here. Ok it works at 16 or 32 and that's all. No can of worms, I enjoy the music being 16/44.1 or 24/96 😉
Thanks guys! (And good night!)
Thanks guys! (And good night!)
No issues with 16 bit data either, its is just padded out with the necessary zeros when processing at 24 or 32 bits. It should be completely transparent, so there is nothing to worry about on that aspect.
It appears that many DACs require 24 bit data to packaged as S32_LE with the eight bits of zero padding even though they are capable of only 24 bit depth. So, yes, nothing to worry about, it seems.
Some info here:
audio player - ALSA using pcm_s24le - Stack Overflow
Cheers,
Richard