Topic: Upsampling real-time Dsd output dsdx4 256 (Read 9934 times)

paoloboccardi · « **on:** July 17, 2017, 02:57:11 am »

Hi, I have a DSD capable DAC, Ares Denafrips and I have a pc (i5 6500 with 16gb) dedicated to audio with Windows 10 pro e and Linux Mint system (low latency kernel). In windows the pc can make a 4xdsd upsample without problems (modifying buffer values) instead on linux not when i go into 4xdsd jumping music. In 2xdsd no problem. What options should I modify? To hear the music I prefer linux.

blgentry · « **Reply #1 on:** July 17, 2017, 07:12:04 am »

What if I told you that DSD to 4xDSD conversions in MC are done with PCM in the middle? That they are not pure "dsd to dsd". Would you still want to do these conversions?

Brian.

paoloboccardi · « **Reply #2 on:** July 18, 2017, 05:15:25 am »

Quote from: blgentry on July 17, 2017, 07:12:04 am

What if I told you that DSD to 4xDSD conversions in MC are done with PCM in the middle? That they are not pure "dsd to dsd". Would you still want to do these conversions?

Brian.

But I want convert PCM to 4xDSD. On Windows no problem: in Linux all it's fine until 2xDSD.

Awesome Donkey · « **Reply #3 on:** July 18, 2017, 05:19:55 am »

Interesting, Windows and Mint installed on the same box (different partitions/drives), right?

paoloboccardi · « **Reply #4 on:** July 18, 2017, 10:57:52 am »

Quote from: Awesome Donkey on July 18, 2017, 05:19:55 am

Interesting, Windows and Mint installed on the same box (different partitions/drives), right?

Yes, the same box in different partitions (ssd hd).

bob · « **Reply #5 on:** July 21, 2017, 02:21:10 pm »

On Windows, MC can set thread priorities and playback is prioritized, not so on linux (until now).

The next build (23.0.21) implements thread priorities on linux.

The linux box must be configured to allow non-root users to do this. The easiest way is to add the following line to /etc/security/limits.conf

@audio - rtprio 100

This assumes the user is in the audio group which on debian is allowed access to the raw audio devices.

You need to log out and back in for the change to take effect.

paoloboccardi · « **Reply #6 on:** July 23, 2017, 08:57:45 am »

Thank you! It works very well

paoloboccardi · « **Reply #7 on:** July 30, 2017, 05:27:46 pm »

Quote from: paoloboccardi on July 23, 2017, 08:57:45 am

Thank you! It works very well

Hi,I have noticed that JRiver on linux use 80% Cpu when upsampling 4xdsd. Windows 10 max 30%.

JimH · « **Reply #8 on:** July 30, 2017, 06:24:31 pm »

It may be doing other work.

paoloboccardi · « **Reply #9 on:** July 31, 2017, 03:15:10 am »

Quote from: JimH on July 30, 2017, 06:24:31 pm

It may be doing other work.

In some case the music 'pauses' for a moment: it happens with the most demanding files.
I think that JRiver on linux should absorb less CPU resources.

bob · « **Reply #10 on:** July 31, 2017, 08:51:06 am »

Quote from: paoloboccardi on July 31, 2017, 03:15:10 am

In some case the music 'pauses' for a moment: it happens with the most demanding files.
I think that JRiver on linux should absorb less CPU resources.

If you have the spectrum analyzer turned on, turn it off.
Also, Jim is correct, it may be doing something else like background thumbnailing.

paoloboccardi · « **Reply #11 on:** July 31, 2017, 04:57:38 pm »

Quote from: bob on July 31, 2017, 08:51:06 am

If you have the spectrum analyzer turned on, turn it off.
Also, Jim is correct, it may be doing something else like background thumbnailing.

I checked, no option is active: the two configurations are identical.

bob · « **Reply #12 on:** August 01, 2017, 08:56:08 am »

Quote from: paoloboccardi on July 31, 2017, 04:57:38 pm

I checked, no option is active: the two configurations are identical.

Not sure how you are reading CPU usage on linux.
If you have two cores the max the conversion can use is 50%. 4 = 25%, etc.
I just tried it and verified that behavior.

paoloboccardi · « **Reply #13 on:** August 01, 2017, 04:43:06 pm »

Quote from: bob on August 01, 2017, 08:56:08 am

Not sure how you are reading CPU usage on linux.
If you have two cores the max the conversion can use is 50%. 4 = 25%, etc.
I just tried it and verified that behavior.

Ok thank you. Tomorrow I will check again and I will do some screenshot for verify if something doesn't work.

paoloboccardi · « **Reply #14 on:** August 07, 2017, 04:35:25 pm »

In attach 2 images of linux mint and windows: jriver 23 4xdsd on the same file, a flac 192 khz 24 bit.

paoloboccardi · « **Reply #15 on:** August 07, 2017, 04:39:13 pm »

And here when jriver linux not playing

bob · « **Reply #16 on:** August 08, 2017, 08:44:00 am »

That's what I'd expect. It's using 82% of ONE core.

paoloboccardi · « **Reply #17 on:** August 08, 2017, 02:44:46 pm »

In windows is the same? I don't see. It's normal that jriver use only one core? I have an intel i5 6500. If is normal I will use only windows version. Thank you.

bob · « **Reply #18 on:** August 10, 2017, 09:08:16 am »

Quote from: paoloboccardi on August 08, 2017, 02:44:46 pm

In windows is the same? I don't see. It's normal that jriver use only one core? I have an intel i5 6500. If is normal I will use only windows version. Thank you.

Yes, DSD resampling is not multicore on any of the platforms.

mattkhan · « **Reply #19 on:** August 27, 2017, 10:08:47 am »

minor but this change makes the jriver log really noisy as it prints this lots and lots of times (~ 1/3 of log statements in my log file are this line)

Code: [Select]

0275332: 1310988160: General: CThreadParallelizer::Process: Error creating prioritized thread, falling back to standard thread

I suggest printing it once (or throttling the log statement)

bob · « **Reply #20 on:** August 28, 2017, 08:57:50 am »

Quote from: mattkhan on August 27, 2017, 10:08:47 am

minor but this change makes the jriver log really noisy as it prints this lots and lots of times (~ 1/3 of log statements in my log file are this line)

Code: [Select]
0275332: 1310988160: General: CThreadParallelizer::Process: Error creating prioritized thread, falling back to standard thread
I suggest printing it once (or throttling the log statement)

Will do, thanks.

INTERACT FORUM

Author Topic: Upsampling real-time Dsd output dsdx4 256 (Read 9934 times)