PeterSt
|
|
« Reply #1 on: May 01, 2020, 01:13:36 pm » |
|
Hi there Zheng,
Let's see whether I can answer your questions adequately;
First off, digital filtering always comes along with upsampling. This is hard to explain, but I could try to convince you that only the upsampling step allows to have the result mostly the same as the original. Think like injected additional samples while the original samples remain. But mind you, this is typical for Arc Prediction and this means of filtering is far from common (at all). The more upsampling steps, the more samples can be injected in between the originals. Thus, with 16x upsampling, 15 samples are injected between each 2 originals. Let's say that they imply (and hunt for) a better transition from the one original to the next original. Not "one big jump" but in 16 small (calculated) steps now. Or in two steps when upsampling is just 2x.
"Custom" Arc Prediction is not really different, BUT in this case a second stage filter is applied on top of the normal Arc Prediction. This is done the most mildly where the (possible) transients of Arc Prediction are sustained. In this case, however, the original sampling points are changed, as in any normal digital filter doing this, but with the notice that this is "measured" (by me with the analyser) to not noticeably change the transients. Do notice that a normal filter will change the transients notably, me always stating that it will changes violins into flutes (think micro transients, implied by the bow and the resin onto the string - the more resin the more "jumping" (transients) on the string).
The more times upsampling, the better the filtering can be applied (this is a story in itself). But notice that this is generally so, because it also can depend on the behaviour of the DAC at higher sampling rates (it needs to process more data and this in itself can be audible in a negative sense). And indeed it is so that some people play our NOS1 DAC at 352.8 instead of 705.6 (upsampled RedBook); less current is used now, which may mean that more reserve is there for stuff like again transients.
As you can see, the transients are almost a hobby-horse to me. The accurate rendering of them is key (in my view).
When playing out 44.1K (from 44.1K) no filtering can be active. Still it may be so that the software may "touch" other parts which again imply processing, but now in-software only. And mind you, as we know, XXHighEnd is "tweaking" all over the place and this is about processing (all over the place). Also more physical things may be in order, like you outputting 44.1K all right, but maybe outputting in 24 (or 32) bits, while the original is 16 bits. Officially this can't matter, but now physically it may imply half more data (or double) towards the DAC, which now must process it. And as we also know by now, everything matters ...
What are the filters in the group [NOS] for? ony for Phasure DAC?
It is that you mention them, otherwise I never even saw them. I suppose they sneaked in the production version, from some testing a long time ago. Please don't use those.
I hope it is all clear a little ! Kind regards, Peter
|
|
|
Logged
|
For the Stealth III LPS PC : W10-14393.0 - July 17, 2021 (2.11) XXHighEnd Mach III Stealth LPS PC -> Xeon Scalable 14/28 core with Hyperthreading On (set to 14/28 cores in BIOS and set to 10/20 cores via Boot Menu) @~660MHz, 48GB, Windows 10 Pro 64 bit build 14393.0 from RAM, music on LAN / Engine#4 Adaptive Mode / Q1/-/3/4/5 = 14/-/0/0/*1*/ Q1Factor = *4* / Dev.Buffer = 4096 / ClockRes = *10ms* / Memory = Straight Contiguous / Include Garbage Collect / SFS = *10.13* (max 10.13) / not Invert / Phase Alignment Off / Playerprio = Low / ThreadPrio = Realtime / Scheme = Core 3-5 / Not Switch Processors during Playback = Off/ Playback Drive none (see OS from RAM) / UnAttended (Just Start) / Always Copy to XX Drive (see OS from RAM) / Stop Desktop, Remaining, WASAPI and W10 services / Use Remote Desktop / Keep LAN - Not Persist / WallPaper On / OSD Off (!) / Running Time Off / Minimize OS / XTweaks : Balanced Load = *62* / Nervous Rate = *1* / Cool when Idle = n.a / Provide Stable Power = 1 / Utilize Cores always = 1 / Time Performance Index = Optimal / Time Stability = Stable / Custom Filtering *Low* (16x) / Always Clear Proxy before Playback = On -> USB3 from MoBo -> Lush^3 A: W-Y-R-G, B: *W-G* USB 1m00 -> Phisolator 24/768 Phasure NOS1a/G3 75B (BNC Out) async USB DAC, Driver v1.0.4b (16ms) -> B'ASS Current Amplifier -> Blaxius*^2.5* A:B-G, B:B-G Interlink -> Orelo MKII Active Open Baffle Horn Speakers. ET^2 Ethernet from Mach III to Music Server PC (RDC Control). Removed Switching Supplies from everywhere (also from the PC).
For a general PC : W10-10586.0 - May 2016 (2.05+) *XXHighEnd PC -> I7 3930k with Hyperthreading On (12 cores)* @~500MHz, 16GB, Windows 10 Pro 64 bit build 10586.0 from RAM, music on LAN / Engine#4 Adaptive Mode / Q1/-/3/4/5 = 14/-/1/1/1 / Q1Factor = 1 / Dev.Buffer = 4096 / ClockRes = 1ms / Memory = Straight Contiguous / Include Garbage Collect / SFS = 0.10 (max 60) / not Invert / Phase Alignment Off / Playerprio = Low / ThreadPrio = Realtime / Scheme = Core 3-5 / Not Switch Processors during Playback = Off/ Playback Drive none (see OS from RAM) / UnAttended (Just Start) / Always Copy to XX Drive (see OS from RAM) / All Services Off / Keep LAN - Not Persist / WallPaper On / OSD On / Running Time Off / Minimize OS / XTweaks : Balanced Load = *43* / Nervous Rate = 1 / Cool when Idle = 1 / Provide Stable Power = 1 / Utilize Cores always = 1 / Time Performance Index = *Optimal* / Time Stability = *Stable* / Custom Filter *Low* 705600 / -> USB3 *from MoBo* -> Clairixa USB 15cm -> Intona Isolator -> Clairixa USB 1m80 -> 24/768 Phasure NOS1a 75B (BNC Out) async USB DAC, Driver v1.0.4b (4ms) -> Blaxius BNC interlink *-> B'ASS Current Amplifier /w Level4 -> Blaxius Interlink* -> Orelo MKII Active Open Baffle Horn Speakers. Removed Switching Supplies from everywhere.
Global Moderator
|