I have started (again) to work on my transient plugin.  For now, I have titled it “Transient Dissector”.  I still have a ways to go, but it is working out for me in my initial tests.  It works exceptionally well in standard test conditions, like a single snare track.  It is less graceful on mixes.  The screenshot below is not my finalized plugin.  There are still a lot of things I need to change.  I have a couple of knobs on the GUI that are no longer needed, and labeling of the knobs would help. 

In the waveform display, I have a black line that indicates the status of the transient detector.  The horizontal lines are showing the the 3 areas: Attack (top), Sustain (middle), and Release (bottom).  Each of the three sections has individual volume controls.

I still have sidechain frequency controls to add, oversampling, waveform settings controls, and to work on the mute/solo button for each band.  I hope to have a beta sometime soon, including a better GUI.

I am getting old.  Twenty years ago, I was playing bass in college.  One of the bands was The Deposits.  We recorded a tape (yeah, CDs were too expensive).  I converted it to MP3 format for my own enjoyment, but nothing more than a few people had it.  Now, I have uploaded it to SoundCloud.  If you enjoy mainly instrumental music with touches of Ska, Metal, and silliness, have a listen.

The link to the album is here.

There is a great independent review of ClipShifter at Reviewer’s Revival.  The direct link to the review is here. 

Here is the changelog for 2.1.  There was also minor optimizations that I did, but I didn’t put all of them on the list.

Version 2.1
+ smaller Settings dialog
+ fixed excessive CPU usage in Studio One (OSX AU)
+ made Threshold End Line hidden when Link button is enabled
+ made Threshold End knob, Attack knob, and Release knob gray/inactive when Link is enabled
+ fixed bug with Windows clipboard paste button
+ changed scaling and range of harmonics control
+ added VST3 32-bit and 64-bit for Windows and OSX

*Paid version:
+ fixed bug with output gain when Double/Oversample is enabled

Version 2.0.1
+ fixed parameter readout flickering in Studio One
+ improved accuracy of loudness meter
+ improved peak detection within waveform history display

*Paid version:
+ fixed threshold inaccuracy when oversampling was engaged
+ added new ‘double’ process while oversampling to reduce samples from overshooting the threshold
+ increase slope of anti-alias curve for upsampling and downsampling (oversampling)
+ added mid/side clipping controls, with input gain, selector, solo, and width controls

Version 2.0.1
+ INITIAL OSX RELEASE AS AUDIO UNIT AND VST
+ added clip reduction display to the waveform view (optional – turned off when plugin loads)
+ new volume zoom control
+ independent release control
+ added smoothness option for waveform view settings
+ revised settings controls for waveform view

*Paid version:
+ reduced CPU load for multiband control
+ reduced CPU load for oversampling
+ revised copy protection for paid version, including displaying the user’s name within the plugin

Well, it is done (I think).  I updated the links to the website and you can get 2.1 here.  I also added VST3 format to both the OSX and Windows versions.

ClipShifter 2.1.0 (final) is so close.  I only have a few more things to do.  I will then update the manual and hopefully everything will be live within the next few days.  Thanks to everyone that has made suggestions and reported bugs.  It has been extremely helpful. 

There are a few enhancements that did not make the cut into version 2.1.0, but I have made several fixes and improvements.  I also add another feature for paid users: mid/side clipping. 

I have released ClipShifter version 2.0.2 beta.  You can get it here.  

Here is a list of the changes. 

Version 2.0.2
+ fixed parameter readout flickering in Studio One
+ fixed excessive CPU usage in Studio One (OSX AU)
+ improved accuracy of loudness meter
+ improved peak detection within waveform history display

Paid version:
+ fixed threshold inaccuracy when oversampling was engaged
+ added new ‘double’ process while oversampling to reduce samples from overshooting the threshold
+ increase slope of anti-alias curve for upsampling and downsampling (oversampling)
+ added mid/side clipping controls, with input gain, selector, solo, and width controls

Version 2.0.1
+ INITIAL OSX RELEASE AS AUDIO UNIT AND VST
+ added clip reduction display to the waveform view (optional – turned off when plugin loads)
+ new volume zoom control
+ independent release control
+ added smoothness option for waveform view settings
+ revised settings controls for waveform view
Paid version:
+ reduced CPU load for multiband control
+ reduced CPU load for oversampling
+ revised copy protection for paid version, including displaying the user’s name within the plugin

Well, I am still ironing out some issues with the beta for ClipShifter.  In the meantime, I decided to try and implement another new feature that I have been thinking about for a while.    It is a control that lets you split the signal into mid/side, and choose which element (mid or side) to process through ClipShifter.  I wasn’t sure of the resulting sound, but it is actually better than I thought.  I think it will be really useful on busses and mixes.

I am still working out some of the specifics with the interface, but it should be ready soon.  When it is ready, I will update the beta to 2.0.2.  At this point, I am thinking that that M/S processing will need to be part of the paid feature-set.

I have finally released 2.0.1.  This version supports OSX Audio Units and VST.  The files are packaged as 32/64 bit Universal Binaries.  The beta also includes some enhancements to the Windows version as well. 

Check out the new features and download the plugin from here.

Well, my new (new from 2009) Macbook is here.  Although it has been several years since I have used a Mac, I am quickly regaining some of my skills.  The one-button mouse thing kills me.  I am a hardcore right-clicker.

I have tested ClipShifter as Audio Units and as OSX VSTs.  The good news is that I am able to load them fine within Reaper and Live.  The bad news is that I don’t have full sound yet.  I know that might sound bad, but it is actually going better than I thought.  I think I should have the kinks worked out soon.  When I do, I think I will release it as a public beta.  This will also include the other changes that I have been making.