All times are UTC+02:00




Post new topic  Reply to topic  [ 719 posts ]  Go to page Previous 163 64 65 66 6772 Next
Author Message
 Post subject: Re: Stereo Tool 6.00
PostPosted: Fri Feb 04, 2011 12:55 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
Quote:
Quote:
You probably need to increase it by 1 ASIO grain (1.33 ms?). I think I should update the ASIO buffer configuration to match whole grains.
I still heard a very soft click with 4.0 ms. I think it's totally fixed with 5.4 ms.
Edit: did some testing with Asio granularity of 128. When changing the buffer the whole system crashed and rebooted.
1. I suppose that's when the CPU load is really high (stress test)? So during normal usage this shouldn't occur?
2. Wooh! Well, if the whole system crashed, it must be a driver (Juli@) issue... Which isn't too surprising, unfortunately (I've had a number of such reboots too in the past on XP).


Top
   
 Post subject: Re: Stereo Tool 6.00
PostPosted: Fri Feb 04, 2011 12:59 am 

Joined: Sun May 02, 2010 11:26 pm
Posts: 547
Now the same with 48 samples. I see the system getting very slow when that happens. Yes it's with 100% CPU load.
But with this version i can get very low latency because it's now also working with asio buffer granularity of 48 samples.

Do you have a formula to calculate the grain size in ms, so i know the buffer step i have to set per asio granularity?


Top
   
 Post subject: Re: Stereo Tool 6.00
PostPosted: Fri Feb 04, 2011 1:21 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
Quote:
Now the same with 48 samples. I see the system getting very slow when that happens. Yes it's with 100% CPU load.
But with this version i can get very low latency because it's now also working with asio buffer granularity of 48 samples.

Do you have a formula to calculate the grain size in ms, so i know the buffer step i have to set per asio granularity?
Sure, granularity_in_samples / sample_rate. That's in seconds, multiply by 1000 for ms.

So:
- 48 samples, 48 kHz: 48 / 48000 --> 1 ms!
- 256 samples, 192 kHz: 256 / 192000 --> 1.33333333 ms.


Top
   
 Post subject: Re: Stereo Tool 6.00
PostPosted: Fri Feb 04, 2011 1:22 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
BETA601-032: Finally a full build of all the modalities again:
- ASIO clicks and pops issue should be solved (again...)

Question: Are they also fixed if you set the priority to Higher? (so not real-time)

Winamp DSP plugin: http://www.stereotool.com/download/dsp_ ... 01-032.exe
Stand alone version: http://www.stereotool.com/download/ster ... 01-032.exe
VST version: http://www.stereotool.com/download/vst_ ... 01-032.dll
VST version (No SSE2): http://www.stereotool.com/download/vst_ ... 01-032.dll
Command line version: http://www.stereotool.com/download/ster ... 01-032.exe
Linux command line version: http://www.stereotool.com/download/ster ... ETA601-032 [not available]
Linux GUI version: http://www.stereotool.com/download/ster ... ETA601-032 [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.
- Fix BYPASS mode in stand alone version DONE
- Fix 4096 in stand alone version
- 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. DONE
- Check ASIO on single core behavior... DONE, option available
- Change ASIO latency interface (lower values, more fine-grained; display actual latency after rounding)
- 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? - WAIT FOR FEEDBACK
- 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. - WAIT FOR FEEDBACK - Make this level depend on the input level (gives less artifacts when not needed) DONE
- Set Steepness a bit higher than before because there are far less artifacts. DONE
- Bojcha: "There is strange "tone" at LEFT channel (tested ST dsp), caused by Bass Boost, but not always!" - Seems gone now - DONE
- Something is wrong with ASIO if there's only one channel instead of 2.
- Bypass is not good again
- phoenix: Direct sound at any buffer doesnot work unless MultiCore is ENABLED! FIXED
- phoenix: "Change of Thread Priority: Now this really needs working. I'll try to make you understand the pattern that I'm observing. Normal and High donot work. Only REALTIME works depending upon whether ST is run using elevated privileges or not. So if I run ST as Admin, it changes to REALTIME in Win 7/Win Vista, else it sets it to HIGH. Now clicking on Normal or High puts it back to the priority at which ST was running just before setting it to REALTIME. So if it was set to Above Normal(using task manager), it reverts to that when clicked on Normal or High from ST Sound Confg Window." - BEHAVIOR UPDATED
- bojcha: When i change Soundcards samples it should ask me to restart program or somehow to deal with it. Currently it hangs. Moving buffer size or bypass ON/OFF, resolves it. - REPORTED TO BE OK NOW
- phoenix: ASIO sound disappears on enabling multicore. - SOLVED
- Allow setting Realtime priority on Vista (if possible, Admin rights?) - NOT POSSIBLE
- Change buffer size configuration to match whole ASIO grains (probably only displaying them) - DONE
- 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. Another step is possible to reduce them further (probably 50% more)
- Hangups during closing of stand alone version. (hThread) Solved???
- I notice when Opening and starting program is a bit slower, minimizing to tray slower too. but it's ok.
- Fix different priority settings (GUI back to normal prio) - BUSY, waiting for feedback...

Questions:
* Multiband: Question: Is Steepness behavior ok? - AS GOOD AS POSSIBLE NOW, AND CAN BE TURNED OFF.
* 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?


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.
- Use double overlap (allow quality levels > 100%) to strongly reduce artifacts
- Introduce extra latency between 512 and 1024 by upsampling or downsampling


Top
   
 Post subject: Re: Stereo Tool 6.00
PostPosted: Fri Feb 04, 2011 1:30 am 

Joined: Sun May 02, 2010 11:26 pm
Posts: 547
Clicks are fixed for me with Real-time selected. Not with Higher. But i can now set Asio buffer granularity to 48 kHz. So steps of 0,25 ms with fm output. So that's pretty amazing.


Top
   
 Post subject: Re: Stereo Tool 6.00
PostPosted: Fri Feb 04, 2011 1:37 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
Quote:
Clicks are fixed for me with Real-time selected. Not with Higher. But i can now set Asio buffer granularity to 48 kHz. So steps of 0,25 ms with fm output. So that's pretty amazing.
With Higher, do you get clicks with large buffer sizes also? Just to know if these are ASIO thread clicks again, or others. (If ASIO, I may be able to fix it).

Note: Without real-time priority, you'll NEVER be protected against high CPU loads. But without that, at Higher priority, do you still have clicks (so Stereo Tool itself causes them), or are they gone then?


Top
   
 Post subject: Re: Stereo Tool 6.00
PostPosted: Fri Feb 04, 2011 1:42 am 
User avatar

Joined: Tue Mar 17, 2009 2:56 pm
Posts: 4231
And @ Eldorado: BA Asio on High Priority? Clicks ?


Top
   
 Post subject: Re: Stereo Tool 6.00
PostPosted: Fri Feb 04, 2011 1:46 am 

Joined: Sun May 02, 2010 11:26 pm
Posts: 547
For Higher priority it's the same behavior as before with the restart thing. So with buffer of 5000 ms clicks.
With BA Asio also clicks at high priority not at realtime.
Both times tested with CPU stress test on. So 100% CPU load.


Top
   
 Post subject: Re: Stereo Tool 6.00
PostPosted: Fri Feb 04, 2011 1:47 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
Quote:
For Higher priority it's the same behavior as before with the restart thing. So with buffer of 5000 ms clicks.
With BA Asio also clicks at high priority.
Both times tested with CPU stress test on. So 100% CPU load.
Ah ok, and without CPU stress test? Without Realtime you'll never be completely protected against high CPU loads...


Top
   
 Post subject: Re: Stereo Tool 6.00
PostPosted: Fri Feb 04, 2011 1:57 am 

Joined: Sun May 02, 2010 11:26 pm
Posts: 547
Without stress test, Higher is better than normal but difference is very small. I have to set buffer a bit higher, with Asio buffer granularity of 256 i have to set it from 2.7ms to about 5.4 ms. But then it's also without clicks on normal, but it depends on the restart button.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 719 posts ]  Go to page Previous 163 64 65 66 6772 Next

All times are UTC+02:00


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Limited