The file system is ntfs and I have installed the additional drivers for additional file systems (I also tried with an ext4 formatted drive, same result). I set a password and when first accessing the share on windows I was asked for username and password to which I entered username tc and password the one I set.
When you say login, login where? I want to access the share from a windows machine.
I can ssh in and if I try to write to the drive I get permission denied.
Last edited:
Hello! I have read great things about pCP and was hoping to give it a try.
I have a couple of uninformed questions, if you'd bare with me for a few lines:
- I don't have all my music downloaded, I rely on AirPlay or Spotify to play a lot of music
- I have installed a Spotify Connect server on my current RPi that I love and use most often
Would there be a flow in pCP that would allow me to stream music in such a way? Or am I limited to playing locally stored music?
Thanks for any insight,
Best regards,
Rafa.
I have a couple of uninformed questions, if you'd bare with me for a few lines:
- I don't have all my music downloaded, I rely on AirPlay or Spotify to play a lot of music
- I have installed a Spotify Connect server on my current RPi that I love and use most often
Would there be a flow in pCP that would allow me to stream music in such a way? Or am I limited to playing locally stored music?
Thanks for any insight,
Best regards,
Rafa.
hi Rafa,
There are Logitech Media Server (LMS) plugins that give you AirPlay and Spotify streaming. LMS runs on various platforms.
There is a lot of help on the Squeezebox forums.
Squeezebox : Community : Forums
regards
There are Logitech Media Server (LMS) plugins that give you AirPlay and Spotify streaming. LMS runs on various platforms.
There is a lot of help on the Squeezebox forums.
Squeezebox : Community : Forums
regards
Greg,
I'm a retired audio designer (well "retired" means being my own boss and working only on projects and designs that interest me and are not commercially driven
) - I've built streamer hardware based on the RPi (well CM3 modules so we can optimise the hardware).
Our Audio hardware is interfaced to the RPi via USB and we also have a serial UART channel so we can also communicate with the Linux hardware with an APi.
I'm fully aware of the RPi USB PHY limitations, but USB gives us:-
1. DAC as Audio Master clock (Critically important).
2. DSD and 384 / 768KHz High Res support
We can also perform MQA hardware decode in the USB audio coprocessor (XMOS).
I'm old school and all this streaming talk goes way over my head, the only streaming device I've really used was the SBT (just for radio stations (BBC) - no LMS server installed), but I remember it was very intuitive and "just worked".
Some say that the UI is dated, but to me that's just stupid - IMO its logical, clean and simple, I dont need or WANT more...
I remember the days Vista was released with its AERO UI (or some such) which required a super computer to run it and at the end of the day was slower then my old XP box...
It annoys me that these "youngsters" care about flashy looking UI's at the expense of stability, usability and responsiveness - but I digress....
Would you mind me using your software on my hardware designs (if we move forward I'd be happy to send you sample units) - and can your software:-
1. Be installed on 4GB eMMC of the CM3 module, we could use the CM3 lite and external eMMC (upto 256GB) but the eMMC memory is packaged in BGA devices and this brings a whole bag of hurt to production.
2. Drive a local UI (such as an internal touch screen or HDMI monitor + wireless keyboard)?
I'd be happy to "donate" a fee per unit installed... if we work together...
I'm a retired audio designer (well "retired" means being my own boss and working only on projects and designs that interest me and are not commercially driven
) - I've built streamer hardware based on the RPi (well CM3 modules so we can optimise the hardware).Our Audio hardware is interfaced to the RPi via USB and we also have a serial UART channel so we can also communicate with the Linux hardware with an APi.
I'm fully aware of the RPi USB PHY limitations, but USB gives us:-
1. DAC as Audio Master clock (Critically important).
2. DSD and 384 / 768KHz High Res support
We can also perform MQA hardware decode in the USB audio coprocessor (XMOS).
I'm old school and all this streaming talk goes way over my head, the only streaming device I've really used was the SBT (just for radio stations (BBC) - no LMS server installed), but I remember it was very intuitive and "just worked".
Some say that the UI is dated, but to me that's just stupid - IMO its logical, clean and simple, I dont need or WANT more...
I remember the days Vista was released with its AERO UI (or some such) which required a super computer to run it and at the end of the day was slower then my old XP box...
It annoys me that these "youngsters" care about flashy looking UI's at the expense of stability, usability and responsiveness - but I digress....
Would you mind me using your software on my hardware designs (if we move forward I'd be happy to send you sample units) - and can your software:-
1. Be installed on 4GB eMMC of the CM3 module, we could use the CM3 lite and external eMMC (upto 256GB) but the eMMC memory is packaged in BGA devices and this brings a whole bag of hurt to production.
2. Drive a local UI (such as an internal touch screen or HDMI monitor + wireless keyboard)?
I'd be happy to "donate" a fee per unit installed... if we work together...
Last edited:
picoplayer no DSD128 audio with Allo Boss and iQAudio DAC+
Hello,
maybe somebody here can help me on this matter. Using piCorePlayer (v4.0.0-b7 but same with 3.5, squeezelite with DSD mod) on LMS I'm able to play DSD64 (using C3-PO Plugin transcoding from PCM or DSD64 native file using DSDPlay plugin). Trying DSD128 files or transcoding from PCM to DSD128 I have no audio.
I understand DOP can't support DSD256 but I guess DSD128 is supported by Allo Boss (I was able to play DSD128 files using Volumio)
There is any special setting for piCorePlayer in order to obtain DSD128 playback ?
PS
Same problem using iQaudio DAC+ but not sure if it supports DSD128
Thanks
Damiano
Hello,
maybe somebody here can help me on this matter. Using piCorePlayer (v4.0.0-b7 but same with 3.5, squeezelite with DSD mod) on LMS I'm able to play DSD64 (using C3-PO Plugin transcoding from PCM or DSD64 native file using DSDPlay plugin). Trying DSD128 files or transcoding from PCM to DSD128 I have no audio.
I understand DOP can't support DSD256 but I guess DSD128 is supported by Allo Boss (I was able to play DSD128 files using Volumio)
There is any special setting for piCorePlayer in order to obtain DSD128 playback ?
PS
Same problem using iQaudio DAC+ but not sure if it supports DSD128
Thanks
Damiano
To be able to run DSD128 as DOP you need to have pCp with audiokernel installed.
DSD128-DOP requires PCM support @ 352k8.
The pCP audiokernels come with patches that enable up 2 384k on DACs like the Allo Boss.
Standard RPI kernels won't support DSD128-DOP on these kind of DACs. DSD64 is max.
DSD128-DOP requires PCM support @ 352k8.
The pCP audiokernels come with patches that enable up 2 384k on DACs like the Allo Boss.
Standard RPI kernels won't support DSD128-DOP on these kind of DACs. DSD64 is max.
Last edited:
Sorry for being a bit sloppy on that one. Just a "bit" though.
Because my actual original message related to DSD in response to the OPs question still holds.
Here's my more precise response:
The codec driver PCM512x does not support SR 352k8 - which prevents from running DSD128-DOP.
Below the relevant code snippet I've just taken from the latest 4.14.73 and 4.14.66-rt RPI kernel sources proving it:
Code:
static const u32 pcm512x_dai_rates[] = {
8000, 11025, 16000, 22050, 32000, 44100, 48000, 64000,
88200, 96000, 176400, 192000, 384000,
};BTW: The official RPI kernel sources are neither "mainline" nor "standard" as Tim suggests.
The RPI kernel branch adds numerous patches to "mainline" ( which is the kernel master managed by Linus Torvalds)
Bottom line:
That means that all distros without customized kernel (and a related codec patch) - and that includes Moode (if I'm not mistaken) - won't support DSD128-DOP for this DAC family.
pCP corrects this with its audio kernel.
I hope this clarifies the situation.
And yes - 384k will work by default - if the HW manages to support it!
Last edited:
No problems at all with 24 or 32/352.8 on my Allo Boss w/mainline kernel
Code:
pi@rp3:~ $ uname -a
Linux rp3 4.14.73-v7+ #1148 SMP Mon Oct 1 16:57:50 BST 2018 armv7l GNU/Linux
pi@rp3:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: BossDAC [BossDAC], device 0: Boss DAC HiFi [Master] pcm512x-hifi-0 []
Subdevices: 0/1
Subdevice #0: subdevice #0
pi@rp3:~ $ cat /proc/asound/card0/pcm0p/sub0/hw_params
access: RW_INTERLEAVED
format: S24_LE
subformat: STD
channels: 2
rate: 352800 (705600/2)
period_size: 16384
buffer_size: 65536Attachments
Dear Soundcheck, thanks for your explanation.Sorry for being a bit sloppy on that one. Just a "bit" though.
Because my actual original message related to DSD in response to the OPs question still holds.
Here's my more precise response:
The codec driver PCM512x does not support SR 352k8 - which prevents from running DSD128-DOP.
Below the relevant code snippet I've just taken from the latest 4.14.73 and 4.14.66-rt RPI kernel sources proving it:
BTW: The official RPI kernel sources are neither "mainline" nor "standard" as Tim suggests.Code:static const u32 pcm512x_dai_rates[] = { 8000, 11025, 16000, 22050, 32000, 44100, 48000, 64000, 88200, 96000, 176400, 192000, 384000, };
The RPI kernel branch adds numerous patches to "mainline" ( which is the kernel master managed by Linus Torvalds)
Bottom line:
That means that all distros without customized kernel (and a related codec patch) - and that includes Moode (if I'm not mistaken) - won't support DSD128-DOP for this DAC family.
pCP corrects this with its audio kernel.
I hope this clarifies the situation.
And yes - 384k will work by default - if the HW manages to support it!
I'm running pCP with audio kernel.
Concerning the DSD playback I'm doubtful Allo BOS and similar DAC support DSD playback. I suspect pCP convert the DSD stream to PCM 352800 and when trying with DSD128 he try with PCM 705600 but fails .
Below the pCP log:
DSD64
[19:32:37.778048] sendRESP:210 RESP
[19:32:38.224902] _read_header:192 id: DSD len: 28 consume: 28
[19:32:38.224962] _read_header:159 DSF version: 1 format: 0
[19:32:38.224974] _read_header:169 channels: 2
[19:32:38.224983] _read_header:170 sample rate: 2822400
[19:32:38.224994] _read_header:171 lsb first: 1
[19:32:38.225003] _read_header:172 sample bytes: 2305843009213693951
[19:32:38.225013] _read_header:173 block size: 4096
[19:32:38.225021] _read_header:192 id: fmt len: 52 consume: 52
[19:32:38.225031] _read_header:179 found dsd len: 12
[19:32:38.225040] dsd_decode:768 setting track_start
[19:32:38.225049] dsd_decode:817 DSD to PCM output
[19:32:38.245904] _output_frames:64 start buffer frames: 24576
[19:32:38.246019] _output_frames:149 track start sample rate: 352800 replay_gain: 0
DSD128
[20:02:46.546575] output_thread:687 open output device: hw:CARD=BossDAC
[20:02:46.547382] alsa_open:351 opening device at: 705600
[20:02:46.548548] alsa_open:381 reopening device hw:CARD=BossDAC in plug mode as plughw:CARD=BossDAC for resampling
[20:02:46.550973] alsa_open:422 opened device plughw:CARD=BossDAC using format: S32_LE sample rate: 705600 mmap: 1
[20:02:46.551397] alsa_open:513 buffer: 120 period: 4 -> buffer size: 84672 period size: 21168
[20:02:46.551667] alsa_open:530 unable to set hw params: Invalid argument
Beside the DSD128 support, the main question is, the log lines:
dsd_decode:817 DSD to PCM output
means that the DSD stream is transcoded to PCM?
thanks
Following the previous message.
In order to send DSD output to pCP the -D option should be used but even if you not get any error. No sound in output. See logo below:
[22:29:00.669211] sendRESP:210 RESP
[22:29:00.723513] _read_header:192 id: DSD len: 28 consume: 28
[22:29:00.723618] _read_header:159 DSF version: 1 format: 0
[22:29:00.723646] _read_header:169 channels: 2
[22:29:00.723666] _read_header:170 sample rate: 2822400
[22:29:00.723684] _read_header:171 lsb first: 1
[22:29:00.723700] _read_header:172 sample bytes: 146336736
[22:29:00.723718] _read_header:173 block size: 4096
[22:29:00.723735] _read_header:192 id: fmt len: 52 consume: 52
[22:29:00.723757] _read_header:179 found dsd len: 292675596
[22:29:00.723775] dsd_decode:768 setting track_start
[22:29:00.723794] dsd_decode:821 DSD64 stream, format: DOP, rate: 176400Hz
[22:29:00.749947] _output_frames:64 start buffer frames: 108544
[22:29:00.750161] _output_frames:149 track start sample rate: 176400 replay_gain: 0
[22:29:00.751558] sendSTAT:179 STAT: STMs
[22:29:00.751829] sendSTAT:179 STAT: STMt
[22:29:00.760244] output_thread:687 open output device: hw:CARD=IQaudIODAC
[22:29:00.760908] alsa_open:351 opening device at: 176400
[22:29:00.761959] alsa_open:422 opened devicehw:CARD=BossDAC using format: S32_LE sample rate: 176400 mmap: 1
[22:29:00.762085] alsa_open:513 buffer: 80 period: 4 -> buffer size: 14112 period size: 3528
So again, I believe Allo BOS doesn't support DSD playing without conversion to PCM.
In order to send DSD output to pCP the -D option should be used but even if you not get any error. No sound in output. See logo below:
[22:29:00.669211] sendRESP:210 RESP
[22:29:00.723513] _read_header:192 id: DSD len: 28 consume: 28
[22:29:00.723618] _read_header:159 DSF version: 1 format: 0
[22:29:00.723646] _read_header:169 channels: 2
[22:29:00.723666] _read_header:170 sample rate: 2822400
[22:29:00.723684] _read_header:171 lsb first: 1
[22:29:00.723700] _read_header:172 sample bytes: 146336736
[22:29:00.723718] _read_header:173 block size: 4096
[22:29:00.723735] _read_header:192 id: fmt len: 52 consume: 52
[22:29:00.723757] _read_header:179 found dsd len: 292675596
[22:29:00.723775] dsd_decode:768 setting track_start
[22:29:00.723794] dsd_decode:821 DSD64 stream, format: DOP, rate: 176400Hz
[22:29:00.749947] _output_frames:64 start buffer frames: 108544
[22:29:00.750161] _output_frames:149 track start sample rate: 176400 replay_gain: 0
[22:29:00.751558] sendSTAT:179 STAT: STMs
[22:29:00.751829] sendSTAT:179 STAT: STMt
[22:29:00.760244] output_thread:687 open output device: hw:CARD=IQaudIODAC
[22:29:00.760908] alsa_open:351 opening device at: 176400
[22:29:00.761959] alsa_open:422 opened devicehw:CARD=BossDAC using format: S32_LE sample rate: 176400 mmap: 1
[22:29:00.762085] alsa_open:513 buffer: 80 period: 4 -> buffer size: 14112 period size: 3528
So again, I believe Allo BOS doesn't support DSD playing without conversion to PCM.
DSD native doesn't work on I2S-HATs.
It's got to be DOP - DSD over PCM.
The SW volume control must be locked at 100%!
A DOP stream can not be touched by any DSP functionality, which would corrupt the
stream.
A DOP stream requires double the bandwidth compared to DSD native.
That's why DSD128 -DoP (@352k8) is max for PI-HATs.
On USB DACS DSD256 native works fine.
I'll check later if the Boss works on DoP128.
It's got to be DOP - DSD over PCM.
The SW volume control must be locked at 100%!
A DOP stream can not be touched by any DSP functionality, which would corrupt the
stream.
A DOP stream requires double the bandwidth compared to DSD native.
That's why DSD128 -DoP (@352k8) is max for PI-HATs.
On USB DACS DSD256 native works fine.
I'll check later if the Boss works on DoP128.
