Quote:
Quote:
I still cannot use my sound card properly
You can try older drivers, if you're not already.I know about Juli@ panel - but that means I cannot test if it works
| Stereo Tool https://forums.stereotool.com/ |
|
| Stereo Tool 6.00 https://forums.stereotool.com/viewtopic.php?t=2811 |
Page 38 of 72 |
| Author: | Bojcha [ Fri Jan 28, 2011 1:01 am ] |
| Post subject: | Re: Stereo Tool 6.00 |
I'll try to answer ... FM Output (192kHz/256samples 2,8ms). IF i go lower it starts to sound like very small clicks, like bees. Further down .. less music more bees. Normal output (48kHz/64samles 4,0ms) is actually same, BUT, between 2.8 and 4ms is other type of clicks and under 2.8ms same 'bee' sound like in FM mode. I should get same minimal Buffer Size for both cases 4.0 or 2.8ms or any number. What about "FM calibration" ? In my test it coast 11ms. (512 mode) |
|
| Author: | Bojcha [ Fri Jan 28, 2011 1:02 am ] |
| Post subject: | Re: Stereo Tool 6.00 |
Quote: @bojcha
I am playing sine tone at 40Hz, so it's very easy to hear clicks, pops, etc...
How do you know that a buffer of 2.8ms isn't creating clicks/pops @192khz. Do you use some kind of measurement to get to the correct value? |
|
| Author: | eldoradofm [ Fri Jan 28, 2011 1:06 am ] |
| Post subject: | Re: Stereo Tool 6.00 |
I've did some more testing. I've recorded the output of the tuner while feeding silence to stereotool and it looks like the best setting is indeed 2,8ms at granularity of 256. @2,7 ms there was occasionally some click. When i'm lowering the buffer more, more random clicks appear. I can't find a repetition. |
|
| Author: | hvz [ Fri Jan 28, 2011 1:19 am ] |
| Post subject: | Re: Stereo Tool 6.00 |
I still cannot use my sound card properly (I think there's a bug in Stereo Tool somewhere, will have to check that asap - it's hanging on ALL sound cards on my system now - and I tested one of the previous BETA's that works fine for other people...). But I think I've fixed some issues: - Last FM output sample is now sent out BEFORE the rest of the processing occurs, instead of afterwards. So MAYBE it's possible to lower the latency a bit. - Normal output is now sent out at the same point where FM output is sent out. - ASIO Configure button added - but on my ASIO drivers it does nothing (it does return the correct error message saying that there is no window - so I hope it will work on non-Juli@ cards). For FM, the change is: - Previously when sending 256 samples to the processing chain, 255 older samples were immediately passed to the FM output, then there was a pause of several ms for processing, and then the last 1 sample was sent. Now all 256 samples are sent out immediately. - For Normal output, previously all 256 samples were sent out AFTER the pause, now they are sent out BEFORE. The value 256 is for latency 512, for 1024 it's 512, for 2048 it's 1024 etc. Building now... Of course it's just as well possible that the output is random noise now, since I can't check it. (The buffers do seem to be filled properly, so at least that looks good). |
|
| Author: | Bojcha [ Fri Jan 28, 2011 1:27 am ] |
| Post subject: | Re: Stereo Tool 6.00 |
Quote: I still cannot use my sound card properly
You can try older drivers, if you're not already.Quote: - ASIO Configure button added - but on my ASIO drivers it does nothing (it does return the correct error message saying that there is no window - so I hope it will work on non-Juli@ cards).
On Juli@ should nothing Happen, because Juli@ is using ASIO settings for all apps same and accessible from mixer panel.
|
|
| Author: | hvz [ Fri Jan 28, 2011 1:27 am ] |
| Post subject: | Re: Stereo Tool 6.00 |
Quote: What about "FM calibration" ? In my test it coast 11ms. (512 mode)
As you know, in earlier versions of Stereo Tool (before 5.00) the latency increased when more filters were turned on.In 5.00 I fixed that for most of the filters... But not for upsampling, downsampling, composite limiting and FM output calibration. In 6.01, I've now fixed it for upsampling and downsampling as well, and I've reduced the composite limiting latency a bit. FM output calibration is still as it was in version 4.xx - it causes a lot of latency. I'm planning to fix that in a later version (6.02 maybe) - when I do that I can probably reduce the FM composite limiter latency to 0 as well. |
|
| Author: | hvz [ Fri Jan 28, 2011 1:29 am ] |
| Post subject: | Re: Stereo Tool 6.00 |
Quote: Quote: I still cannot use my sound card properly
You can try older drivers, if you're not already.I know about Juli@ panel - but that means I cannot test if it works
|
|
| Author: | Bojcha [ Fri Jan 28, 2011 1:32 am ] |
| Post subject: | Re: Stereo Tool 6.00 |
we will test 
|
|
| Author: | hvz [ Fri Jan 28, 2011 2:19 am ] |
| Post subject: | Re: Stereo Tool 6.00 |
BETA601-026: - Fixed some more ASIO issues (see my previous post for details). NO CHANGES TO ANYTHING ELSE! WARNING: NOT TESTED! (My sound card driver is having issues) Winamp DSP plugin: http://www.stereotool.com/download/dsp_ ... 01-026.exe Stand alone version: http://www.stereotool.com/download/ster ... 01-026.exe VST version: http://www.stereotool.com/download/vst_ ... 01-026.dll VST version (No SSE2): http://www.stereotool.com/download/vst_ ... 01-026.dll Command line version: http://www.stereotool.com/download/ster ... 01-026.exe Linux command line version: http://www.stereotool.com/download/ster ... ETA601-026 [not available] Linux GUI version: http://www.stereotool.com/download/ster ... ETA601-026 [not available] What remains for 6.01: - Multiband: Adjust band 3 (and others?) 'soft limit' behavior at very low latencies. Maybe: Also check clipping (also for band 3, might be re-enabled!). DONE! - 1 hour - Multiband: Adjust extreme EQ settings before processing to avoid issues caused by steepness. - 1 hour - Multiband: Add 'Enable' button for steepness. 1 hour - Performance: Multiband steepness: Moving UP can be done inside current loop, no separate loop needed. Maybe down too. Currently Multiband is FAR more expensive than before. - DONE, solved in a different way. - 1 day - MAYBE: Make Steepness smarter. That would much better preserve the audio, especially at very low latencies! How: Instead of setting all the levels at AT MOST the level of neighboring bands + a bit, combine adjacent bands, determine total output level, and then fix it such that this combined output level is approached more. (So one very low, one very high --> one a bit less low, one a bit less high instead of both low). - Fix NOISE GATE behavior in VST plugin - Fix 'red output bar' issue. DONE - 1 day? - Fix Highpass filter for higher input frequencies. - Dynamic audio processing window: I've tested this at latency 512, and there it helps. But I don't have a clue what the effect is on higher latencies. They might also sound better, but they could just as well sound worse. - 2 hours. Result: 512 and 1024 got better, 2048 and 4096 got worse. So only turned on for the first two. - Dynamic audio processing window: CPU load is probably a lot higher (haven't measured it yet) due to the dynamic adjustment of the behavior. The dynamic code was originally intended to be executed only once when a latency was selected, and it's not optimized at all. Fixed, CPU load reduced, and for latency 2048 and 4096 there's no difference. - Optimize, 1 day - Reduce downsampling frequency because currently very high frequencies (21-22 kHz @ 176.4 kHz input sampling rate) in the input can cause spikes even if Hard Limit is used. DONE - 1 hour - Vibrations caused by Very deep bass distortion protection at latency 1024. Also (but far less noticeable) in higher latency modes. No issue at latency 512 because there it's turned off. - Fixed, turned it on for latency 512, and turned other bass filter OFF for 512 because it caused distortion. - Check difference in behavior between 44.1 and 48 kHz input for multiband! This could potentially result in really big differences. - No - Performance: Multiband: Remove sqrt(sqrt(cos())), pow(x, .75) etc. - too expensive, replace by lookup table. - NOT FOR NOW, would increase memory usage and hence risk more page faults, so it's not sure that this would improve the performance. - 2 hours - Performance: Move chain variables to a single Struct DONE - 1 hour - Latency: Attempt to reduce Composite Limiter sampling latency - there is no audio anywhere near the filter frequency, so a much shorter delay might still work very well - DONE, composite limiter latency is now 0.9 ms at latencies 512 and 1024 (~1.7-2 ms at higher latencies)! It can be reduced a step further (to 0.5 ms) if I allow a bit more distortion - don't know if that's useful. - Chris: "I still hear diff on Bass and kick between Beta 16 vs Beta 08 on 2048 latency. I hear more bass and kick on Beta 08. Pls check!" - No longer true, apparently fixed in BETA020... (Which does not make sense at all, but anyway) - And I need to check how much the performance is impacted by the latency improvements, in the case where no upsampling and downsampling is needed. This seems to be impacted way more than I expected (could also be Multiband steepness --> Not anymore, fixed). Ah, got part of it: 1% is steepness. Which leaves about 3% to be explained. Het is NIET de FM Hard Limit - ook al bereken ik daar nu meer van. Wellicht chain2 calls? - No, wrong again. Decreased Steepness grain match from every 4 to every 16 samples, extra CPU load is now only 2% - acceptable. - Check/fix Bass Boost ringing reported by Bojcha for higher 'upto' frequencies. REDUCED it a bit, hope that suffices... Less steep filtering (ie. bigger difference between first 2 frequencies) helps. - Attempt to set GAUSS back to 0 - gives MUCH better processing of most filters (no high frequency noise). BUT: Loudness effect in Bjork - It's Oh So Quiet - can that be resolved in another way? BUSY, 1 day? - Frequencies between 60 and 75 Hz are not handled properly yet, and can still cause vibration effects at soft high frequencies in latency 512 mode. (But FAR less than in version 6.00). Fixing this will probably increase artifacts for bass in this frequency range. - Bojcha: "There is strange "tone" at LEFT channel (tested ST dsp), caused by Bass Boost, but not always!" - ASIO latency: Add configurable ASIO granularity - ASIO latency: Add active output push instead of reactive. - No longer needed - I think. Data is now sent to output BEFORE processing. And there's always some processing delay. Might become more interesting when CPU load goes down. - ASIO latency: Make option to increase ST priority. Questions: * Multiband: Question: Is Steepness behavior ok? * Loudness: QUESTION: The changed Punch behavior, is that good or bad? Should I attempt to let Punch behave as it did in the past as much as possible, or not? At latency 512, Steepness can now be set a bit higher than before because there are far less artifacts. For 6.02: - It's possible to send data to an audio buffer AFTER I've returned control to the driver if I call ASIOOutputReady() when I'm ready - Add non-phase linear Multiband stage between AGC and incoming_copy_needed. |
|
| Author: | Bojcha [ Fri Jan 28, 2011 2:22 am ] |
| Post subject: | Re: Stereo Tool 6.00 |
Asio "Configure" button is working
|
|
| Page 38 of 72 | All times are UTC+02:00 |
| Powered by phpBB® Forum Software © phpBB Limited https://www.phpbb.com/ |
|