Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kuanj]

Media 18 drop out playing .dsf file or ISO.
he loading of a single track takes about 20 seconds and it play
for less than 30 seconds it drops out and resume playing after 8 seconds.
This repeats as the track is being played.

If teh the sampling rate is set at 44.1 thre is no drop out but
dropping out exists only above the 44.1 sampling rate.

Your help is required.

[Matt]

Media 18 drop out playing .dsf file or ISO.
he loading of a single track takes about 20 seconds and it play
for less than 30 seconds it drops out and resume playing after 8 seconds.
This repeats as the track is being played.

If teh the sampling rate is set at 44.1 thre is no drop out but
dropping out exists only above the 44.1 sampling rate.

Your help is required.

It's probably a simple CPU issue.

You will need a machine with about a 2000 JRMark to play DST compressed DSD as PCM.

You can get your JRMark in Help > Benchmark.

[kuanj]

Thanks for the quick response.
How come there is no issue on the AUdioGate by Korg. It is because
JRiver hs too many features which requires  additional processing power?

Thanks

[Matt]

What is your JRMark?

[ampex]

59 build. Many tames strobing and drop out in SACD iso. Network or local playing ISOs no different. Normaly grey indicator point of playing permanently is pushing green indicator of "buffer??" before it. Change pre buffering time give no effect. System utilisation 3-5% processor use and 8Gb memory in playing ISOs. Last of JR 17 builds and 18 before 59 is now problem. Machine is Intell 2700K, 16Gb RAM, SSD, Win 8 64. USB interface RME UFX.
JR17-18 licensed for me.
sorry for my English.....

[ampex]

JR team!
Audio quality is the best, room correction, VST plugins is very cool work  in you product, but you work on many over futures in media center.
All In One solution NO be work right together.
Please, give us AUDIO ONLY version!!

[JimH]

http://wiki.jriver.com/index.php/Simplified_Interface

I'll split your post later.

[bulldogger]

What is your JRMark?

My JRMark is 1829 and I have the buffering issues if I don't first extract the DSD files. No problems when I do. However I am confused. My CPU usage shows as 25% when I am trying play multi-channels SACD iso without first extracting and having the buffering issue. Why would the CPU usage only be 25% and yet, it still be a CPU issue? Just trying to get a grip on what is the hardware limitation so I can make sure to avoid it when I build a dedicated server.

[JimH]

1829 is a good mark, but not a great one.  It may not be enough.

[kuanj]

JR MArk 2010

[ampex]

My JRmark is 4230.

[bulldogger]

1829 is a good mark, but not a great one.  It may not be enough.

Why is CPU usage only at 25% and not powerful enough?

[Matt]

Why would the CPU usage only be 25% and yet, it still be a CPU issue?

If you have a 4 core CPU, 25% can mean one core is pegged.  You should be able to watch this in Task Manager > Performance.

DST decompression is currently single threaded and CPU hungry.

Do you know if your SACD ISO uses DST compression?

[bulldogger]

If you have a 4 core CPU, 25% can mean one core is pegged.  You should be able to watch this in Task Manager > Performance.

DST decompression is currently single threaded and CPU hungry.

Do you know if your SACD ISO uses DST compression?

Yes, I have a 4 Core CPU and the SACD ISO is using DST compression.

[bulldogger]

Ok, I think I understand. The number of instructions per second that can be processed by CPU is not fast enough. It can't stay ahead of the real time playback so it has to buffer, stop playback to catch up. I am not that computer savvy and am just trying to understand everything that is causing the problem so that I can avoid it. Basically a PC with a faster CPU is all that is need to fix this issue, one that can do the calculations faster than the data playback speed.

[bulldogger]

One last question. I see that for a single thread, some of the i5 CPUs are nearly as fast as the i7 and as fast with "turbo boost,"whatever that means? However I noticed that the i7s handle 8 threads while the i5s do 4 threads. Is that relevant for JRiver playback? Are there any scenarios, like say Blu-ray playback with onboard DTS MA decoding, and parametric EQ with convolution filters, where the i7 might work and the i5 not?

[Matt]

Ok, I think I understand. The number of instructions per second that can be processed by CPU is not fast enough. It can't stay ahead of the real time playback so it has to buffer, stop playback to catch up.

This is my theory, but I'm not sure.

The other possibility is that the I/O pattern when reading from ISO (as opposed to DSF files, which you said worked) is less efficient.

If the problem is the CPU usage of DST decompression, a faster CPU would fix it.  We might also consider trying to use multiple threads to handle decompression.

[bulldogger]

This is my theory, but I'm not sure.

The other possibility is that the I/O pattern when reading from ISO (as opposed to DSF files, which you said worked) is less efficient.

If the problem is the CPU usage of DST decompression, a faster CPU would fix it.  We might also consider trying to use multiple threads to handle decompression.

If 25% usage means that one core is pegged, then that is what I am seeing when I look at the performance monitor. When I use DSF files, the result is about 12% usage and no buffering. Perhaps multiple threads to handle decompression is the answer if only one core is being used for decompression. Is that difficult and time consuming to figure out? I realize you all are in the middle of a very large project.

[ampex]

New build and AGAIN all is OK. Problem in 59

[dtc]

I just starting trying DSD files. I use a Intel Atom based Netbook and it was  buffering every 20 seconds or so when converting to 96KHz.  But, I realized the problem was because I was converting to 96KHz. When I changed to 88.2KHz the buffering stopped. 88.2KHz is an integer multiple of the DSD rate, so conversion is much easier to do. That's why SACDs are 88.2KHz. Converting DSD to 88.2 or 176.2 rather than 96 or 192 seems like the right way to go.