using step sequencer to trigger Addictive drums causing massive clipping

Author
wherewithal
Max Output Level: -90 dBFS
  • Total Posts : 13
  • Joined: 2015/12/17 08:33:55
  • Status: offline
2015/12/29 08:50:03 (permalink)

using step sequencer to trigger Addictive drums causing massive clipping

Hi All,
 
Completely new to the world of DAWs so my learning curve is going to be steep. I can't figure out why the return signal of a simple kick/snare/hats/crash pattern for 16 bars in clipping at random points during the loop. Is there a known issue using non cakewalk plugins with the step or is it something with the latency setting? there are no other tracks currently recorded so it seems like it shouldnt by my hardware (win10 64 bit, i5, 8gb RAM)
 
Please help :)
#1

12 Replies Related Threads

    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/29 11:15:08 (permalink)
    A MIDI editing tool like the step sequencer is not likely to cause clipping. It might be helpful to describe your setup a little more fully, starting with the audio interface configuration. Are you using a dedicated audio interface or the internal PC sound chip? Looking in SONAR preferences, what are the driver mode and latency settings. A little more about the audio failure might also help, is the sound distorted or are notes not being played back?
    #2
    wherewithal
    Max Output Level: -90 dBFS
    • Total Posts : 13
    • Joined: 2015/12/17 08:33:55
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/29 11:56:55 (permalink)
    thanks so much getting back.
     
    My ASIO is a Focusrite Scarlett 2I2. my sample rate is 16bit at 44.1hz
     
    I dont have my comp infront of me to look at the ASIO config. the notes are being played but they're either distorting or "jumping" where I'll only get the second half of the sample. the result is the same whether I'm monitoring through the focusrite OR using the headphone jack directly on the computer
    #3
    wherewithal
    Max Output Level: -90 dBFS
    • Total Posts : 13
    • Joined: 2015/12/17 08:33:55
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/29 14:31:13 (permalink)
    Is it possible that its because the VST manager is showing the 32bit plugin for AD and I have a 64bit os?
    #4
    tlw
    Max Output Level: -49.5 dBFS
    • Total Posts : 2567
    • Joined: 2008/10/11 22:06:32
    • Location: West Midlands, UK
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/29 14:42:39 (permalink)
    If the audio meters aren't going into the red, it might be worth trying this - it may be worth trying anyway...

    In advanced MIDI preferences there is a setting for the MIDI preparation buffer. By default it is 250ms. Try increasing it to 500 or even more. That buffer tells Sonar how far ahead to read MIDI tracks to make sure it's ready to play the notes etc. when the now time reaches them. If that buffer overflows then dropped MIDI notes and all kinds of other strange things happen.

    The power of the PC concerned seems to make no difference, either the default 250ms buffer works on a particular system or it doesn't. And for some reason the step sequencer in particular seems prone to overflowing the MIDI preparation buffer.

    Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board,
    ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre.
    Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.
    #5
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/29 14:43:25 (permalink)
    wherewithal
    Is it possible that its because the VST manager is showing the 32bit plugin for AD and I have a 64bit os?


    I don't think so. The OS does not matter but the host might. You should run the AD designed for your host. IOW, if you are running 64bit SONAR run 64bit AD. There is no reason to run 32bit plug-ins in a 64bit host unless the vendor does not supply a 64bit version in which case it is time to look for a replacements.
    #6
    BobF
    Max Output Level: 0 dBFS
    • Total Posts : 8124
    • Joined: 2003/11/05 18:43:11
    • Location: Missouri - USA
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/29 15:00:37 (permalink)
    Have you compared the velocity values of your SS clips to those that ship with AD?
     
     

    Bob  --
    Angels are crying because truth has died ...
    Illegitimi non carborundum
    --
    Studio One Pro / i7-6700@3.80GHZ, 32GB Win 10 Pro x64
    Roland FA06, LX61+, Fishman Tripleplay, FaderPort, US-16x08 + ARC2.5/Event PS8s 
    Waves Gold/IKM Max/Nomad Factory IS3/K11U

    #7
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/29 15:17:39 (permalink)
    AD2 outputs VERY "hot" (aka: loud) for some dagned reason.
     
    In the Console View select ALL the active audio output tracks that are accepting signal from AD2 (in Sonar they are called "Instrument" tracks), hold the Ctrl key on your keyboard (QWERTY keyboard that you type with... not your MIDI controller) and turn down the "Gain" knob of one of the track strips (this will be at the very top of the track strips). The gain knobs for all the selected tracks should turn down simultaneously.
     
    Alternatively you could do the same thing in the Track View by selecting all the same tracks as before, holding Ctrl and lowering the Gain slider control on one of the track's (you will need to have your "Track Control Filter" set to "Mix" to expose the Gain slider).
     
    You could also turn down the volume faders inside AD2 as well so they don't output as "hot" but I usually just use the Gain control in the Console view.
     
    If you are expereincing WILD level fluctuations though this would be due to your "Velocity" settings for each Step Sequencer pattern so read up on the Step Sequencer and how to adjust note velocity levels.
     
    It could also be you have manged to accidentally insert some kind of Volume/Gain envelope on the track somewhere that is turning the volume/gain up and down in an undesirable fashion... but that probably isn't it.
     
    Cheers.
    #8
    wherewithal
    Max Output Level: -90 dBFS
    • Total Posts : 13
    • Joined: 2015/12/17 08:33:55
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/29 16:07:29 (permalink)
    all Awesome suggestions folks, I'll run some tests tonight and check back.
     
    many thanks
    #9
    wherewithal
    Max Output Level: -90 dBFS
    • Total Posts : 13
    • Joined: 2015/12/17 08:33:55
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/30 09:38:51 (permalink)
    adjusting the velocity settings did the trick, I also didn't do the best job in preferences setting up the focusrite now that I review it. Thanks so much everybody. I'm sure I'll be back.
    #10
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/30 13:31:02 (permalink)
    I  would second Beepster's recommendation to pull down the output levels of channels in AD2's GUI - preferable to adjusting Gain in SONAR in my view.
     
    Lowering MIDI velocity is akin to having the drummer play more softly. You'll be hearing only lower velocity samples which may not be what you want, depending on the song. Usually some combination of both audio output level and velocity tweaking are needed to get the right sound, but you want to start by making sure the levels are reasonable when the kit is being played at full velocity.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #11
    BobF
    Max Output Level: 0 dBFS
    • Total Posts : 8124
    • Joined: 2003/11/05 18:43:11
    • Location: Missouri - USA
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/30 13:55:15 (permalink)
    As far as velocities go, it makes sense to me to use the ranges found in the AD libs when creating your own patterns.

    Bob  --
    Angels are crying because truth has died ...
    Illegitimi non carborundum
    --
    Studio One Pro / i7-6700@3.80GHZ, 32GB Win 10 Pro x64
    Roland FA06, LX61+, Fishman Tripleplay, FaderPort, US-16x08 + ARC2.5/Event PS8s 
    Waves Gold/IKM Max/Nomad Factory IS3/K11U

    #12
    stevec
    Max Output Level: 0 dBFS
    • Total Posts : 11546
    • Joined: 2003/11/04 15:05:54
    • Location: Parkesburg, PA
    • Status: offline
    Re: using step sequencer to trigger Addictive drums causing massive clipping 2015/12/31 18:05:45 (permalink)
    BobF
    As far as velocities go, it makes sense to me to use the ranges found in the AD libs when creating your own patterns.




    +1   I find most of AD's included MIDI clips have an optimal velocity range for the samples, a fairly "natural" feel to them with some velocity headroom to spare if and when needed. 

    SteveC
    https://soundcloud.com/steve-cocchi
    http://www.soundclick.com/bands/pagemusic.cfm?bandID=39163
     
    SONAR Platinum x64, Intel Q9300 (2.5Ghz), Asus P5N-D, Win7 x64 SP1, 8GB RAM, 1TB internal + ESATA + USB Backup HDDs, ATI Radeon HD5450 1GB RAM + dual ViewSonic VA2431wm Monitors;
    Focusrite 18i6 (ASIO);
    Komplete 9, Melodyne Studio 4, Ozone 7 Advanced, Rapture Pro, GPO5, Valhalla Plate, MJUC comp, MDynamic EQ, lots of other freebie VST plugins, synths and Kontakt libraries
     
    #13
    Jump to:
    © 2025 APG vNext Commercial Version 5.1