More > JRiver Media Center 18 for Windows

Meitner MA-1 issue with DSD and ASIO

<< < (5/8) > >>

thesnodger:

--- Quote from: Matt on September 03, 2012, 07:27:11 pm ---I would not recommend this.  It could easily lead to playback problems, since it causes threads we schedule as low priority to get elevated enough that they can begin to compete with time-critical playback threads.

--- End quote ---

Fair enough. I can set it back to Normal. However, as mentioned before, I get the dropouts on an Vanilla build with nothing else "tweaked".

Thanks

Matt:

--- Quote from: thesnodger on September 03, 2012, 09:18:01 pm ---Fair enough. I can set it back to Normal. However, as mentioned before, I get the dropouts on an Vanilla build with nothing else "tweaked".

--- End quote ---

I'm not really commenting with regards to the original problem, just making a general suggestion. 

I'm not sure on the original problem.  What is your JRMark (Help > Benchmark)?  What type of DSD are you playing (DFF, ISO, multi-channel ISO w/ DST compression, etc.)?

kuanj:
 Hi Snodger

Thanks

Ychng:
Question to Snodger:

I'm wondering if the dropouts from DSD are due to a different issue than dropouts from the 192 khz file. Did you get DSD dropouts with your vanilla build?

regarding the 192 khz file dropouts, if they are due to the meitner intolerance to bad timing, should happen regardless of the PC setup.
I'm referring to the DSD dropouts when I question your PC build. Do the dSD dropouts happen in the same place in the same file every time? if not, then it is probably a different mechanism than the dropouts from that 192 khz file. Latency/buffer induced dropouts should be more random.

do you ever get 192 Khz pcm dropouts or DSD dropouts from officially released (Hdtracks, channel classics, Blue Coast) files?

Yeang

thesnodger:

--- Quote from: kuanj on September 03, 2012, 10:15:32 pm --- Hi Snodger

QUOTE:
BTW, I am using an extremely tweaked version of Windows 7 x64 with only 5 services running and J River 17 (Build 184) as the shell which I why I am not keen to go back to WASAPI event style as it needs 3 additional services running to work whereas ASIO needs none. Thanks!
UNQUOTE:

Appreciate share the names of the 5 services that are running.

Thanks

--- End quote ---

The services still running are:


* DCOM Server Process Launcher
* Plug & Play
* Power
* Remote Procedure Call
* RPC Endpoint Mapper
* User Profile Service
OK... So it's 6. And you can only do that provided you are happy using the machine completely standalone and only as a Media Player (a lot of other apps won't work). If you have different hardware like a touchscreen you will also need to enable these services. But they are the absolute minimum you need for Windows to run properly. You also won't get WASAPI to work with only these services.

I can compile a guide if there is enough interest.

Navigation

[0] Message Index

[#] Next page

[*] Previous page