Bit Perfect Audio from Linux
Feb 11, 2015 at 11:07 PM Post #316 of 544
thanks for the idea, not sure what you mean by "the full file" as it streams continuously I thought but perhaps not.  I will try pushing the size to 16384 and cut the period to 512 to see what happens.
 
I cannot believe it is the network since the throughput is very high, no? 
 
Feb 11, 2015 at 11:25 PM Post #317 of 544
If the buffer is small a network dropout of 1 second can be an issue, as within that one second it has already played all the samples it had stored. Raising the buffer allows for it to not need a connection for several seconds or even minutes at a time, eliminating network as a issue if it still occurs.
 
Feb 12, 2015 at 12:18 AM Post #318 of 544
The buffer is now set to 16384 and period is still 1024.  First drop was at about 45 minutes, so it seems it is helping.  thx.  I'll keep my fingers crossed to see if it can maintain or better.  I may also try cutting the period down as well as the size to keep the drive pinged more frequently.
 
Feb 12, 2015 at 9:27 AM Post #319 of 544
I think the buffer settings in Deadbeef are a bit strange. I use Mopidy and the default GStreamer backend settings are 200ms for buffer and 10ms for period.
This means that the buffer and period are sample rate dependent.
 
For a 16/44.1 file the buffer size is 8820 (44100*200/1000) and period size is 441 (44100*10/1000). For a 24/96 buffer size is 19200 and period size is 960.
If you set the buffer size in GStreamer to 1 second (1000ms) you will get a buffer size of 44100 for 44.1KHz and 96000 for 96KHz.
 
This is not the case for Deadbeef where the settings are fixed no matter what the sample rate is. That said the default 8192 and 1024 should be sufficient.
I hope you'll find a way to fix the problem.
 
Feb 14, 2015 at 8:29 PM Post #321 of 544
  The buffer is now set to 16384 and period is still 1024.  First drop was at about 45 minutes, so it seems it is helping.  thx.  I'll keep my fingers crossed to see if it can maintain or better.  I may also try cutting the period down as well as the size to keep the drive pinged more frequently.

 
keeping the drive busy might be the key. i also have dropouts from a usb hard drive (and i know why).
my external case puts the drive to sleep after 5min idle time, so after almost every song that's longer than 5min there's a dropout. maybe your NAS behaves in a similar way.
 
Feb 15, 2015 at 11:52 AM Post #322 of 544
Some network adjustments may have helped as well with drops now seemingly only occurring with some higher rez tracks.  Another head-fier noted that he had some drops and attributed them to usb bus interrupt conflicts.  I may try moving the USB dac around to some other ports to see if that has an impact.
 
Feb 15, 2015 at 7:17 PM Post #323 of 544
It could also he the way the program handles the buffer. On my machine (4790, 32gb ram) I had dropouts regularly with Clementine and a few others. But with other applications I had no such issues. To be noted however with Clementine even the largest buffer would act as if I hadn't changed a setting. Using network over power doesn't help.
 
Feb 16, 2015 at 4:51 AM Post #325 of 544
MPD, goggles, foobar in wine all performed flawlessly with default settings, of course your mileage may vary. I usually keep another machine around to be a dedicated playback machine (volumio or daphile) these days though, so apart from keeping my bitperfect guide up to date and in working order i don't dabble in the desktop side much. Unless of course there is an issue that could use a look at that is probably reproduceable (like this one).
 
Feb 27, 2015 at 12:57 AM Post #326 of 544
I'm trying to get 192/24bit to my Cambridge Audio DacMagic100.  Using Deadbeef I've been able to achieve 96/24bit, but as I understand it, usb can't achieve anything greater than this without a driver.  Unfortunately Cambridge Audio doesn't have a Linux driver.  So is there some way to get around having a driver (I don't have any experience in compiling my own kernel) or would optical, spdif, or usb 3.0 be able to achieve this? 
 
Thanks guys!
 
Feb 27, 2015 at 1:08 AM Post #327 of 544
Ahh 
  I'm trying to get 192/24bit to my Cambridge Audio DacMagic100.  Using Deadbeef I've been able to achieve 96/24bit, but as I understand it, usb can't achieve anything greater than this without a driver.  Unfortunately Cambridge Audio doesn't have a Linux driver.  So is there some way to get around having a driver (I don't have any experience in compiling my own kernel) or would optical, spdif, or usb 3.0 be able to achieve this? 
 
Thanks guys!

I don't feel that is correct :
 
From ta device "Bus 002 Device 007: ID 040d:3410 VIA Technologies, Inc"
 Playback:
  Status: Stop
  Interface 1
    Altset 1
    Format: S16_LE
    Channels: 2
    Endpoint: 4 OUT (ASYNC)
    Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
    Data packet interval: 500 us
  Interface 1
    Altset 2
    Format: S24_3LE
    Channels: 2
    Endpoint: 4 OUT (ASYNC)
    Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
    Data packet interval: 250 us
  Interface 1
    Altset 3
    Format: S32_LE
    Channels: 2
    Endpoint: 4 OUT (ASYNC)
    Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
    Data packet interval: 250 us
 

All the way up to  : 384/32 
 
Feb 27, 2015 at 2:12 PM Post #328 of 544
  I'm trying to get 192/24bit to my Cambridge Audio DacMagic100.

 
The XMOS chip does not require drivers in Linux. Can you get sound through the IEC958 in the device list?
 
Feb 27, 2015 at 8:28 PM Post #329 of 544
 The XMOS chip does not require drivers in Linux. Can you get sound through the IEC958 in the device list?

^ is that the chip the DacMagic 100 uses?  I've been using Alsa (with USB 1, Front speaker), but I get the same result using IEC958.  DeadBeaf says that it's outputting 192/24bit and the dac says that it's only getting 96.  I don't know if it helps but the output device says: Cambridge Audio DAC100 USB 1, USB Audio IEC958 (S/PDIF) Digital Audio Output.
 
Feb 28, 2015 at 4:49 AM Post #330 of 544
  ^ is that the chip the DacMagic 100 uses?  I've been using Alsa (with USB 1, Front speaker), but I get the same result using IEC958.  DeadBeaf says that it's outputting 192/24bit and the dac says that it's only getting 96.  I don't know if it helps but the output device says: Cambridge Audio DAC100 USB 1, USB Audio IEC958 (S/PDIF) Digital Audio Output.

 
Sorry, I thought it used the same chip as the DacMagic Plus but just found this on their website:
 
24-bit/96kHz driverless USB Audio 1.0 input

 

Users who are viewing this thread

Back
Top