All times are UTC+02:00




Post new topic  This topic is locked, you cannot edit posts or make further replies.  [ 759 posts ]  Go to page Previous 133 34 35 36 3776 Next
Author Message
PostPosted: Fri Mar 16, 2018 12:30 am 
User avatar

Joined: Fri Mar 09, 2018 1:31 pm
Posts: 73
Location: FRANCE
.sts configuration file does not contain license key, Hans did things right, so no risk of activation key disclosure by this means :P


!! Never display your stereo_tool.ini file on the forum because it contains your product activation key. !!


Top
   
 
PostPosted: Fri Mar 16, 2018 2:15 am 

Joined: Fri Mar 16, 2018 2:12 am
Posts: 9
Yep... the 041 version came with a worse problem than previous one. The NAM error continues to appear as soon as it open and now the MBs are down full scale and only one channel output. Not working at all. Disabling both MBs brings back both channels. This is the 64bit version.

The 32bit version comes with an new problem too. If we minimize the window it becomes non responsive and crashes, but doesnt show the above problem.


Top
   
 
PostPosted: Fri Mar 16, 2018 7:29 am 

Joined: Sun Feb 03, 2013 2:39 pm
Posts: 334
Quote:
The 0.03/0.04 could very well be a display error - I have even seen cases where a different CPU can give different outcomes.
It's about the ini-file. I reset ST to factory defaults and make a text comparison between different versions.


Top
   
 
PostPosted: Fri Mar 16, 2018 11:16 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11211
Quote:
Yep... the 041 version came with a worse problem than previous one. The NAM error continues to appear as soon as it open and now the MBs are down full scale and only one channel output. Not working at all. Disabling both MBs brings back both channels. This is the 64bit version.

The 32bit version comes with an new problem too. If we minimize the window it becomes non responsive and crashes, but doesnt show the above problem.
The 64 bit issue will be fixed in the next build (which unfortunately failed last night, so tonight).

The 32 bit issue is new to me. I can't reproduce it here. What happens exactly? You click on the minimize button and it crashes then? Or you can't bring it up anymore? Do you get any error message? I did change some code that's related to window sizes, if the window becomes to small (which should not be possible) it could crash. But, minimizing and restoring shouldn't change the window size at all.

Edit: Ah, never mind. I think I just managed to crash it here too, by making it very small and quickly moving it between a 4K and normal monitor. I'll reproduce this in debug mode, then it should be simple to figure out what happened. It might be what you're seeing, I don't know. But let me fix this issue (which I actually *can* reproduce) first. Hopefully that will fix your issue too.


Edit #2: Ah.... so, apparently in some cases when I move my window between the two monitors, it's attempting to draw a 4K image inside a non-4K window. At least that's what it looks like. It only fails when I move my window *to* the 4K monitor. And I can't reproduce it in debug mode, so it's difficult to be 100% certain - but it definitely looks like this. I'll add some protection code that refuses to draw anything if the window is too small - that should fix it (because the next draw event will be ok again).


Top
   
 
PostPosted: Fri Mar 16, 2018 5:19 pm 

Joined: Fri Mar 16, 2018 2:12 am
Posts: 9
Quote:
Quote:
Yep... the 041 version came with a worse problem than previous one. The NAM error continues to appear as soon as it open and now the MBs are down full scale and only one channel output. Not working at all. Disabling both MBs brings back both channels. This is the 64bit version.

The 32bit version comes with an new problem too. If we minimize the window it becomes non responsive and crashes, but doesnt show the above problem.
The 64 bit issue will be fixed in the next build (which unfortunately failed last night, so tonight).

The 32 bit issue is new to me. I can't reproduce it here. What happens exactly? You click on the minimize button and it crashes then? Or you can't bring it up anymore? Do you get any error message? I did change some code that's related to window sizes, if the window becomes to small (which should not be possible) it could crash. But, minimizing and restoring shouldn't change the window size at all.

Edit: Ah, never mind. I think I just managed to crash it here too, by making it very small and quickly moving it between a 4K and normal monitor. I'll reproduce this in debug mode, then it should be simple to figure out what happened. It might be what you're seeing, I don't know. But let me fix this issue (which I actually *can* reproduce) first. Hopefully that will fix your issue too.


Edit #2: Ah.... so, apparently in some cases when I move my window between the two monitors, it's attempting to draw a 4K image inside a non-4K window. At least that's what it looks like. It only fails when I move my window *to* the 4K monitor. And I can't reproduce it in debug mode, so it's difficult to be 100% certain - but it definitely looks like this. I'll add some protection code that refuses to draw anything if the window is too small - that should fix it (because the next draw event will be ok again).

Thank you Hans!


Top
   
 
PostPosted: Sat Mar 17, 2018 7:20 am 

Joined: Sun Feb 03, 2013 2:39 pm
Posts: 334
After a first shock because of the new default skin I saw that you changed the GUI size from integer to floats. However my problem of minor size fluctuations causing the GUI components to rearrange still exists in beta 46. Note that my window position is x=y=0 and the default (height, width) = (831.3333, 1542.6667) shrinks to (height, width) = (793.3333, 1526.6667) occasionally for no apparent reason.


Top
   
 
PostPosted: Sat Mar 17, 2018 9:55 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11211
Stereo Tool 8.55 BETA046

Windows 32 bit:
Windows stand alone: http://www.stereotool.com/download/ster ... 55-046.exe
Winamp DSP: http://www.stereotool.com/download/dsp_ ... 55-046.exe
VST: http://www.stereotool.com/download/vst_ ... 55-046.dll

Windows 64 bit:
Windows stand alone: http://www.stereotool.com/download/ster ... 55-046.exe
VST: http://www.stereotool.com/download/vst_ ... 55-046.dll


CHANGES:
- New skin
- Improved Auto EQ/Bass EQ max boost calculation
- Bass EQ first band might not go down fast enough
- Check scaling issue in non-4K mode
- Check Auto EQ behavior at the start of a song => Problem was caused by Abrupt Change Protection compensation that I added recently...


OLDER CHANGES:
- NAN seen when switching to new compressor mode which also doesn't get recovered - silence afterwards. (Peak mode recovers it though). => Not seen since, must have been something in the earliest version of it.
- Auto EQ move where_i_am back to close to min/max settings to avoid insane response times without SJP
- 4K mode line spacing bigger for presets
- Make default window size bigger for 4K
- Fixed threading issue that was introduced in Sudden Jump Protection a few beta's ago.
- Minimum window size in 4K mode
- Added Basstardizer lowpass filter for output
- Make VST plugin error catching work again.
- Optimized new compressor modes, created separate code paths, put values in a lookup table. Performance vs. legacy mode: Auto EQ 5% faster, AGC same, Symmetric RMS vs RMS 7% faster (if not using Exponential Release, Spectal Balance Compensation etc), Symmetric Peak vs Peak 54% heavier (because it's now based on Symmetric RMS mode instead of Averaging mode, and all RMS modes are heavier than Averaging modes). Compared to BETA037 the performance is 13% better for the Symmetric modes.
- Fix Basstardizer crash
- Fix Basstardizer right window shape
- Fixed Digital Multiband 1 mode Flat frequency response bug introduced in 8.54.
- Fixed Symmetric Peak
- Fixed an issue in Symmetric Peak and Symmetric RMS mode with Feedback^2 enabled, for very fast attack times the Shape is higher now to avoid overreacting.
- Fixed Basstardizer: The threshold calculation was completely wrong, it worked fine on constant bass but not on dynamically changing bass.
- Basstardizer: Make Effect strength slider relative to Headroom (which turns into Harshness) - At higher Softness settings Lookahead now controls punch!
- Fixed DLL closing issue (in Audition and other programs; calling a DLL close from program close caused a hangup)
- Added mono bass fiter to reduce multipath
- Added extra protection mechanism to avoid insane release speeds. For MB, MB2, SB Compressor this can be switched on/off for testing - I will remove the checkboxes once tested.
- Relative release threshold was not calculated correctly for FB and FB^2 modes.
- Moved RECOVER_FROM_NAN outside of adjustChannel_internal_linear_attack_release_feedback_peak_peak_gate_limit to fix compiler crash.
- Bass mono fiter to reduce multipath Done, but parameter needs to be controllable separately.
- Added Symmetric Peak mode. Not at all tested yet!!
- Added Stop Threshold values for multiband compressors. They were already there for the singleband compressors, but not yet for multiband!
- Symmetric modes were visible for Digital compressor but not supported by Digital mode!
- Added "Relative release threshold" slider; removed Symmetry slider. For all dynamics processing things (so LLB, AGC, Auto EQ, compressors). Not 100% sure yet if this is a good idea for Auto EQ. See text below (*)
- Max release speed fixed
- Basstardizer: Fixed issue with difference between left and right
- Crash reported by near05 (fixed?)
- Improved external RDS insertion to allow for noisy RDS signals (some encoders (actually apparently from one specific brand) generate a pretty bad signal, which was rejected by Stereo Tool).
- Added sound card lowpass filter compensation to FM output sound card (so now beside tilt for bass there's also something for highs). NOT YET FINISHED, may cause weird behavior. It will work in many cases, but not in all. Does not work when "Ignore high frequencies" is used. Description will follow when finished.
- New compressor mode. Check all weird settings, optimize, new peak mode, remove faster attack/release, add setting for max release, fix max attack/release speed controls. Things to check: "Peak", "Peak mode", "Feedback", "Feedback^2", "Exponential release", "Max attack speed", "Max release speed". New mode is called Symmetric RMS, there's also a Symmetric Averaging but I will probably remove it because it's not useful. MORE INFO BELOW!
New AGC mode MORE INFO BELOW!
New Auto EQ and Bass EQ mode (not switchable in Bass EQ since that's new anyway). MORE INFO BELOW!
- RDS: Add PTYN
- RDS: Add timeout for TA
- Improved multipath protection
- Improved Stereo Image phase limiter
- Revisit new Hard Limit / Final Limiter with Matt & Wes - Settings removed Waiting for final feedback.
- MPEG detection is too insensitive now -> Probably fixed Waiting for feedback
- UECP UDP mode Waiting for feedback
- TA/TP via MagicRDS. Auto-enable TP if TA is used? (no)
- Added THIMEORT in ASCII RDS mode.
- Spectrum displays are broken in 4K mode
- Compressor/limiter on input before AGC to handle extreme sounds? / 2nd AGC with higher threshold for voice tracks Added, may need new mode. Waiting for feedback.
- Add auto save to Linux build Waiting for feedback
- VST delay appears to be wrong - Phase Delay and Threads
- VST version no 4K
- Backup input - fix overshoot display
- Backup input - check stereo
- Fix web server long URL issue Test release mode needed
- Scrolling through presets in 4K mode locks screen (crashes).
- Pilot-only output for 9 , works but needs to be sent back to O9SG
- Self test crashes
- Fix affinity for Linux and Mac - Mac doesn't support it.
- Edwin's bass effect - is that done now? (Maybe an extra HPF?) -> Not needed for now, based on preliminary tests...
- Put Bass EQ under license
- Do we need multiple Basstardizer bands? -> Doesn't seem like it. Not for now.
- Remove Hans mode from Bass EQ? -> Hid it (Extreme Tweaker mode, Matt mode is default, made it a pulldown instead of a boolean to clarify its behavior).
- Octaviafm extra logging? - Waiting. Once we know the cause I'll run a new build. But I'm not going to hold off releasing the current version, since 1. this issue doesn't have any side effects anymore and 2. it very likely isn't new. -> Nothing heard anymore
- Would multiple where_i_am start points improve attack? YES!!!! Think about how to implement it...
- Enabling low latency output caused crashes
- NAN recovery added to Basstardizer
- Top area of GUI made a bit higher, not all menu items fit before
- Bigger font and widgets on 4K screens
- Added Basstardizer
- Remove warnings that were shown for things that weren't even enabled.
- Fixed NAN in 8.54 in several versions in the clipper (reported by 1 person, appears to have been settings-related).
- Matt's bass effect Ready to get feedback, see "BASS EQ" before or between multibands! See note below.
- Fixed Mac multiband compressor gate error after NAN recovery.
- Add Breakaway Pipeline warning
- Add low input level warning
- Add too little AGC action warning
- Add too much noise gate warning
- Add too much BS412 action warning
- Added ASIO latency setting.
- Made streaming with libVLC easier, WARNING though, the audio quality is still the VLC streaming audio quality, there are better encoders out there. This only affects the stand alone versions.

TODO:
- Fine-tune Auto EQ behavior at the start of a song (might be ok now, but needs more testing)
- Fixed a possible GUI crash at certain specific window size in 4K mode
- Hard limit overshoots (red blinking)
- Is pre AGC affecting audio levels? (With BS412) -> Not specifically for BS412, but it slightly reduces the level even if set a lot higher. Probably needs some offset. -> No, just raise threshold.
- Bojcha's basstardizer filter -> Steeper Output LPF seems to fix the problem
- Add NAN recovery in Normal Limiter
- RadioWorld new ads
- Remove small check boxes that were added for testing.
- Figure out screen resize issue \_/
- Check \_/'s window size changes (sounds like the border size is subtracted or something like that)
- near05 VST crash
- Classical preset
- Aanvraag uren
- Add AM presets
- Check MB2 1% something (see FB chat about crackling sound, which was ok in 8.00). Test with Rhodes54 preset -> Ok. But Spideys Web (7.41 vs 8.54) is different, let's test that.
- Flip switch for latency?
- Test NanoPi

- MB2 band coupling bug: something is wrong, check better-fg-plus.sts -> Seems ok now. Weird.
- Make pilot generation smooth for external feeds for DARC etc.
- Select instance with command line option
- Basstardizer fadeout (Edwin)?
- AM streaming output
- Multi-instance version
- WatchCat: Use "Simple Clipper" for R128 normalization if there's no license for Advanced Clipper.
- WatchCat/Generic plugin: Respond to latency request with different number for step 1 and 2
- AF method B via UECP
- "Stereo Width" in Stereo Image is broken - it causes phase problems if you're using it to go to mono with silence on the other channel. This can be made smarter!
- True Bass puchier - filter out start
- 18 Hz trigger tone
- Declipper check L-R effects
- Reduce extreme stereo
- Raspberry Pi "gedeelde bibliotheek" melding.
- Check out Butt
- Add libVLC instability warning
- Loudness meter (also for streaming)
- Omnia.9 set Stereo signal. Probably fixed? Wait for answer.
- Omnia.9 test/fix logging
- Omnia.9 AutoPilot add flag for generating noise above pilot?
- WatchCat website
- Triple stuff
- Thumb up/down in GUI for presets

- SCA2 use as backup, feed to output without processing, bypassing normal chain. Use to have FM receiver as backup, and then just feed the full signal to the output.
- uMPX 24x2ch interface
- One bass page

- GUI: Hide disabled stuff, far less confusing / much cleaner interface.
- Talk to chip
- 2 jaar
- Fardau
- -24 dB side chain range?


NOTE: Bass EQ
1. This thing should not really be needed because there's already Auto EQ. However Matt Levin insisted that it's useful, especially now that they are playing very old Christmas music, so let's try it out!
2. There are 2 modes: Matt Mode (see checkbox) or Hans mode (unchecked). In Matt mode, the highest band is not adjusted but it is used to determine the levels. So in the last stage, the highest band is in bypass mode, but the other bands respond as if it's working as well. So the bass is adjusted compared to the full spectrum. In Hans mode, the highest band is ignored completely, so if you use 2 bass bands, they are adjusted to match each other, but not the rest of the audio.


New compressor mode info:
About 3 years ago I wanted to redesign the whole compressor based on how water pressure control systems work. The whole idea was to have a compressor that moves fast when it has to, but stands still when it can. And that it would behave 'naturally' - it's something that you could actually build with real components (if you treat water pressure as audio levels).

This appeared to work pretty well. If you play a dynamic track, the compressor acted fast, and if you play an already compressed track it does nearly nothing. This is great - because it doesn't add 'restlessness' to already compressed audio, which would lead to listener fatigue.

Short summary of the rest of this text: It never worked as I envisioned! (And I never even realized that). But now it does!!

Some people have complained about the attack sometimes working too fast - which was mainly noticeable in loud 'S' sounds. The fast attack with much slower release could cause a 'gap' in the audio after the S. But I figured that that was a more or less logical consequence of the the whole act-fast-when-you-have-to idea.

Now fast-forward a bit. Last year, 2 people (Wes Keene and Matt Levin) were working on a preset together with very high compressor ratios and they noticed that in one particular track, a vocal which was originally louder than the surrounding sound actually came out softer. Well, that's not good. It sounds really annoying and broken. After looking into it I found out that my design was actually not - as I had thought - controlling the level based on RMS levels, but based on average sample levels. In most cases that's closer to RMS than peak, but it's not perfect, and as it turned out, in some cases flat out wrong.

So, I added a new mode that actually controls things based on RMS levels. And - different than many traditional compressors - it would control based on RMS levels regardless of whether it's long time or short time levels that you're looking at. Typically, a compressor would use some window over which it calculates the RMS level, and then control the audio based on that. That works great for most content, but if you play a track that for example has a very loud kick every second or so, the RMS window won't help a bit and your long-term level will probably be too low.

So I created a new RMS mode, renamed the old one to Average mode, and thought I was done. But, the problem with loud "S" sounds has gotten way worse! And it was even worse than that: Release was slower than before. So to fix that, I added some "patches": "Big release speedup" and "Big attack slowdown".

This new mode doesn't need that anymore. It's completely symmetrical, and it's still RMS-based, both on short and long time intervals! It still moves slowly when it can and fast when it has to - but not insanely fast if the attack is really big. And release isn't very slow anymore.

Since attack and release speeds are now virtually identical for RMS and Average mode, and you probably prefer RMS levels over Average levels, the new "Symmetric Average" mode is basically useless. I've put it in for now for testing, but I'll remove it afterwards.

The AGC and Auto EQ were suffering from similar issues, and I've fixed those too. There you can just disable "Legacy mode" - if I'm not wrong, the new mode should be better for any purpose than the old one.

Important: The CPU load is really high right now. I will optimize it later.

Also important: You can't just enable this new mode and expect everything to be fine without changing the settings. For small level differences there won't be a difference, but there will be for big differences. You'll definitely notice the slower attack on big level jumps.



Top
   
 
PostPosted: Sat Mar 17, 2018 9:56 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11211
Quote:
After a first shock because of the new default skin I saw that you changed the GUI size from integer to floats. However my problem of minor size fluctuations causing the GUI components to rearrange still exists in beta 46. Note that my window position is x=y=0 and the default (height, width) = (831.3333, 1542.6667) shrinks to (height, width) = (793.3333, 1526.6667) occasionally for no apparent reason.
Ah. That's way more than just a rounding error. It kinda sounds like the border is subtracted from the size, or something like that. Although it's odd that that has more effect on the horizontal than the vertical size...


Top
   
 
PostPosted: Sat Mar 17, 2018 10:31 am 

Joined: Sun Feb 10, 2013 6:58 am
Posts: 152
Location: Sydney, Australia
8.55 BETA046
Stand Alone x64 version
Windows 10

4K Monitor

Can't close it, I have to close ST to get rid of it.

C.


Attachments:
Exception.jpg
Exception.jpg [ 120.31 KiB | Viewed 3713 times ]
Top
   
 
PostPosted: Sat Mar 17, 2018 11:05 am 
User avatar

Joined: Fri Mar 09, 2018 1:31 pm
Posts: 73
Location: FRANCE
Hello Hans,
Nice skin I like very much 8-)


Top
   
 
Display posts from previous:  Sort by  
Post new topic  This topic is locked, you cannot edit posts or make further replies.  [ 759 posts ]  Go to page Previous 133 34 35 36 3776 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:  
cron
Powered by phpBB® Forum Software © phpBB Limited