Why has the smaller version been discontinued? This one's pretty confusing with doubled modules and for 90% of applications an overkill.
TBProAudio: CS-5501 - Channel Strip Plugin for Windows and Mac OS X
-
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
-
- KVRian
- Topic Starter
- 800 posts since 16 May, 2014 from Germany
Well, it is hard to maintain 2 similar products over the yearsantic604 wrote: Fri May 07, 2021 8:55 amWhy has the smaller version been discontinued? This one's pretty confusing with doubled modules and for 90% of applications an overkill.
CS-3301 is still available (download, bug fixes).
-
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
But it can't be purchased anymore?
-
- KVRian
- Topic Starter
- 800 posts since 16 May, 2014 from Germany
Well, we think it has not much value to sell a product that does not get new features, only bug fixes
Last edited by TB-ProAudio on Fri May 07, 2021 9:39 am, edited 1 time in total.
-
- KVRian
- Topic Starter
- 800 posts since 16 May, 2014 from Germany
-
- KVRian
- Topic Starter
- 800 posts since 16 May, 2014 from Germany
Update to V2.1.0:
- NEW: true mono, reduced CPU
- UPDATE: GUI reflects mono mode
- FIX: Cubase/Nuendo VST2, OS switch no longer changes channel config
- FIX: Sat, avoid sat pipeline overload
- FIX: Sat, avoid fluctuation overload
- FIX: AAX load default values
- FIX: AAX fader link
- NEW: true mono, reduced CPU
- UPDATE: GUI reflects mono mode
- FIX: Cubase/Nuendo VST2, OS switch no longer changes channel config
- FIX: Sat, avoid sat pipeline overload
- FIX: Sat, avoid fluctuation overload
- FIX: AAX load default values
- FIX: AAX fader link
-
filippenokdanil filippenokdanil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=480044
- KVRer
- 1 posts since 27 Nov, 2020
Hey! I want to ask you, is it normal that when the plugin is opened, the RAM load increases by 1.5 gigabytes, and when the load is closed, only 30-50 megabytes?
-
- KVRian
- Topic Starter
- 800 posts since 16 May, 2014 from Germany
Hmm, we see only 20-30MB increase, no 1.5GB spike.filippenokdanil wrote: Fri Aug 20, 2021 6:26 am Hey! I want to ask you, is it normal that when the plugin is opened, the RAM load increases by 1.5 gigabytes, and when the load is closed, only 30-50 megabytes?
-
- KVRian
- Topic Starter
- 800 posts since 16 May, 2014 from Germany
Update to V2.3.0:
- NEW: variable clip module position (plugin menu)
- NEW: variable ABLM positions (plugin menu)
- NEW: smart bypass
- NEW: Freeze ABLM Lite gain
- NEW: force mono mode, only left channel processing
- UPDATE: toggle online update check
- UPDATE: auto plugin update check
- UPDATE: in/out meter
- UPDATE: AAX, add category "Dynamics"
- FIX: wrong recall of complex module routings
- FIX: WIN, crash when changing routing button with middle mouse button
- FIX: FET comp ratio (internal negative ratio)
- FIX: Ableton VST3, wrong default init GUI scale
- FIX: PT, AS crash
- NEW: variable clip module position (plugin menu)
- NEW: variable ABLM positions (plugin menu)
- NEW: smart bypass
- NEW: Freeze ABLM Lite gain
- NEW: force mono mode, only left channel processing
- UPDATE: toggle online update check
- UPDATE: auto plugin update check
- UPDATE: in/out meter
- UPDATE: AAX, add category "Dynamics"
- FIX: wrong recall of complex module routings
- FIX: WIN, crash when changing routing button with middle mouse button
- FIX: FET comp ratio (internal negative ratio)
- FIX: Ableton VST3, wrong default init GUI scale
- FIX: PT, AS crash
-
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
The selling point of any channel strip is that it's easy to see what's going on at a glance and that it's fast to work with.
CS-5501 is an antithesis of that design, with modules hidden away behind complex drop-down menus and signal flow that doesn't support obvious drag & drop. This could be a perfect channel strip, but it won't be until UI & workflow are sorted out. (IMO, obviously).
CS-5501 is an antithesis of that design, with modules hidden away behind complex drop-down menus and signal flow that doesn't support obvious drag & drop. This could be a perfect channel strip, but it won't be until UI & workflow are sorted out. (IMO, obviously).
-
midi_transmission midi_transmission https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=298730
- KVRian
- 1045 posts since 13 Feb, 2013
I don't agree that it's too complicated or complex for a channel strip.
I think it's great that you have the possibilities. You don't have to use them when you prefer to keep it simple. So I don't see the disadvantage?
I think it's great that you have the possibilities. You don't have to use them when you prefer to keep it simple. So I don't see the disadvantage?
-
- KVRian
- Topic Starter
- 800 posts since 16 May, 2014 from Germany
Update to 2.4.1:
- NEW: FET compressor mode, 76 style (FET 1)
- FIX: Ableton VST3 fader link
- FIX: compatibility of automation parameter to prev. versions
- FIX: crash preset recall (GUI scale)
- NEW: FET compressor mode, 76 style (FET 1)
- FIX: Ableton VST3 fader link
- FIX: compatibility of automation parameter to prev. versions
- FIX: crash preset recall (GUI scale)
-
- KVRian
- Topic Starter
- 800 posts since 16 May, 2014 from Germany
Thank you. We will consider it in one of the next updatescrickey13 wrote: Wed Feb 23, 2022 7:42 am Hello TB, could you implement gain to bandwidth link in the EQ section? It would be a nice workflow thing. Another opto compressor mode wouldn't go amiss too. Thanks.
