|
发表于 2012-11-19 13:23:28
|
显示全部楼层
补充下官方的几点意见:
1. dual PC is 'high-end option' and not a requirement 
more about the reasons and experiences when we release JPLAY 5 but to answer your question NOTHING changes related to your 'good old optimized' Buffer settings from JPLAY 4: it's still up to AudioPC/driver/DAC
Your 'client PC' (=anything you have now is, in theory, totally irrelevant so yes, it can be 'low powered'…
(mind you, Marcin has done some tests and, being him, he of course found some 'interesting' things but let's leave that discussion for later, ok? 
2. correct – don't attach any disks to AudioPC 
the idea of AudioPC is to simply take to absolute extremes what we have been doing so far with just software (witness ultra-extreme Hibernate mode) i.e. to eliminate as much 'fat/noise' from typical Windows PC as possible so, in the end, it becomes pretty much unusable as general-purpose PC and can only stream music bits we only care so deeply about 
(unfortunately we can never strip Windows 'to the bone' as it simply was not designed for our maniacal undertaking but it's what's in millions of people's houses so we're forced to make the best of what we have for better or worse 
3. if your NAS is based on Linux (as most are) then it won't work (well, at least not for now)
in theory we might make it work but that's, well, theory or 'future possible directions' for now…. |
|