Jump to content

Jon White

  • Content Count

  • Joined

  • Last visited

Posts posted by Jon White

  1. If you have plugins in the master bus that load the system a bit, you'll get this.  I tend to have Izotope Ozone in my master bus effects, and unless I deactivate it during monitoring of a VI, I get the latency you are talking about.  Same if I have effects in the soft-synth's channel.  That's always been the case, though, when monitoring realtime soft-synth input within Cakewalk or Sequoia or Nuendo or ProTools.

    My reply here does NOT address your point if you truly are experiencing a change that is simply due to software update, of course.

    I have a Lynx Two audio interface (PC card).

    • Thanks 1

  2. Connect the JUNO directly to the PC.  Period.  Record MIDI into Cakewalk via this and Cake will play the JUNO directly via this. Your MIDI track will receive MIDI directly from the port and it will play TO that port (just pull down the port/device in your track options tabs and select).  Cake will see the JUNO as a MIDI device, so check it as an active device in Settings so it's available.

    There should be no reason at all to use it as a MIDI device through another intermediate device, in my opinion.

    Setup a MIDI track in Cake, assign the input to your JUNO, and, when you "monitor" it and play the keyboard, your JUNO will play.  There is even a .ini file available with the JUNO patches! They will be selectable in the track menu system!  

    When you record this way and then play back the track, your JUNO will play.  How you get that AUDIO saved into Cake will be up to you.  I have my keys going to a mixer whose line output goes to my main soundcard.

    If you want to record the JUNO directly, you can set it up to be a digital audio input. That is, it will be the same as a "soundcard" (an "audio device").  Set it to "VENDOR" driver versus "GENERIC" in its setup menu system, and it will then appear as an audio device in your OS and in Cake.  You'd then record audio directly from it, but probably at the sacrifice of your other audio having to be assigned to the JUNO device (if ASIO, which can only use one device per application) instead of your routine sound device.  That can be a hassle.

    I have all my outboard synths going to a mixer, and then have that mixer's output available to my "soundcard".  You can capture both the MIDI and the audio this way, and then replay/re-record as needed.  What's fun about midi tracks playing your synth is that you can do what I might term "reboard" (assigning a new sound to a MIDI track).

  3. A hats off to every great spirit here who helped Mike.  I admit here and now that I wanted to say "Mike, you have to do your learning and whatnot on your best level first", but I'm a bit changed now due to seeing the great souls here and their patience.

    You'll get there, Mike.  Cakewalk will be a very intuitive, flowing interface for you once you get the audio stuff right.



    • Like 1

  4. I have my TSModel on 2.  

    Noel, I switched to my Line6 Toneport UX2 as my audio device and it was even worse, but that's an old monkey.

    I also use Sequoia as a DAW, and found the Magix Low Latency driver in my registry and deleted it.  No change.  Didn't think that would matter.

    Noel, Lynx writes the following in their notes on the latest driver 24c:


    8.  Added work-around for some ASIO applications (Cakewalk, Studio One, Ableton Live) that set the priority of the driver thread (setting the priority of the driver thread should never be done by an ASIO application per the ASIO specification).  Also added the ability for the end user to turn off the MMCSS priority of the driver thread for applications that insist on setting the drivers thread priority (none that we have found, so far).

    Are they correct about setting the thread priority being a no-no?

  5. Hi Noel, and thank you for posting.  I've talked to Lynx, and you posted here as well to one of my posts a few months ago regarding this.  

    I had the updated Lynx driver, but was confused as to which one of the "Enable MMCSS" toggles (or both) I should turn off, because both Cakewalk and Lynx offer the on/off option.  I called Lynx and asked and they said they did not know that Cakewalk had a toggle.

    To make short of that story, if I have both of the new codes (yours and Lynx'), do I need to turn it off?  It's not a fatal issue like the posting you referenced, just a performance problem.  Are you pretty confident I can use it now?  I don't want to shut it off it it's supposed to work.  If it should be shut off, should I cut both the Cake and the Lynx toggles?

    Also, again, it's the comparitive issues with Sonar/Cakewalk (to other software) that stands out here.  


  6. 9 hours ago, Bill Ruys said:

    This was my thought too.  You have not told us what buffer settings you have set in CW.  It could well be that out of the box, CW used more aggressive buffer settings than your other software.  You need to tell us which driver mode (ASIO, WASAPI, etc) and what audio buffer settings you are using before anyone here can help.  Telling us that "as usual" the audio engine is not up to par and then leaving out probably the most important information is just going to rile people up (which I see, it already has).

    We're here to help, but at least make a reasonable effort to help us help you before telling us the software we all use is not up to par.  Otherwise you kinda come off as a bit of a troll (which I'm sure you're not).

    Bill, thank you.  Very diplomatic interaction!  Yes, my frustration bubbles a bit.  I've also done this for so long that I make the mistake that everyone knows that we veterans do everything right and know what we're doing!  Great cooperative spirit in your post, and exemplary of the best in community cooperation in these days of seeing much turmoil between souls.

  7. On 6/20/2020 at 12:05 AM, LarsF said:

    Different daws may set different ASIO latency, and some have special features like Cubase/Nuendo ASIO guard or whatever it was. Reaper and StudioOne add processing buffers apart from ASIO buffer setting etc. So many things may differ in what daw have as load. Larger latency give more headroom before crackles and pops.

    Did you look in task manager what cpu load is and what is ASIO buffer setting?

    (With and without last plugin, and depending on preset you used)

    The example I mentioned it was added cpu, and when at 55-60%(task manager) or so, some crackles can appear. I run 64 samples ASIO buffers, and a 10 year old quadcore i7 (benchmarking at 5000, where modern cpu i9-9900k of today rate about 20 000) so old cpu in this regard.

    If not related to cpu, something close to what you suggest - something wrong with audio engine - may be relevant.

    I did not bother with 64-bit engine yet, if that matters.

    This is another setting that may differ between daws what is default.


    For me with Cakewalk the default threadscheduling worked the best in that it distribute even on 8 cores(4 physical with hyperthreading give 8 logical).

    Another setting made it use 4 cores only(don't remember which one), so changed it back.


    And my reasoning with what is the largest project that runs normally?

    Thinking that some special plugin here really raise cpu. It could be running a mono plugin on stereo interleave track or other way around. Page 191 in manual mention some special settings that are in plugin manager in how mono is handled.


    Overall thinking is that some default settings in Cakewalk does not make optimal result on your system.

    What a thorough and detailed response.  Thank you!

    I'm always at 48KHz/24-bit/128 samples.  I use the Lynx ASIO driver that works with my soundcard.  I use two of eight stereo outputs and inputs on that interface.  All of my drives are SSDs.  My system crackles when the Cake resouce meters show the cores bouncing around 25%, and always fails when higher.  I did find that my CD/DVD port was causing latency, so I disable that when using Cakewalk (Latency Mon showed me that), but, again, no issues in any other DAWs.

    I truly think Cake does something different in some ways that ends up being problematic for the audio engine.  Just years of experience with it amidst other products.  You make great points, though, as do others.

  8. I record upright bass to jazz quite often, and I do it by having my tone "live", as with all my guitar and analog input -- that being the tone that I present to Cakewalk is from a mixer output and already has my commitment to the final voice.  Short statement: I don't reamp.  Now, if latency didn't exist, I might record tones with live plugins in the channel.  For now, no.

    SO, I have my preamps and analog boxes dialed in, and then my plugins (two ASIO devices can work at the same time if controlled by different applications) doing the rest. 

    Typical guitar for me is BiasFX2 or SGear via my TonePort UX2 (ASIO, 24-bit, 48KHz) and Cakewalk using my Lynx soundcard at the same specs. The TonePort sends its output to my mixer, which sends an analogue signal to the Lynx inputs, and that is the final track sound, overall (but may take on digital/plugin tweaks later).  It takes (pun intended) deliberate commitment and tone planning, but I'm used to that.  The bottom line, so to speak, is that I'm so bad at playing that I need the tone of my guitar, bass, sax, piano to be inspiring as I play, and to be what I see as the final voice.

    Anyway, that sets up EQ fashions in the hardware AND the plugins.  I would say that the preamps and stuff prior to plugins shape my EQ stance more than a plugin.  Message here is, maybe: have the analog voice be the stuff as much as possible.  That will be outboard stuff that you would commit to if gigging, right?  Your tone as the "you" being presented to recording efforts.  I learned this in the studio, as well.  

  9. 22 hours ago, Craig Anderton said:

    Thanks for the props! The most appropriate tools are sometimes the least-expected ones.

    Mr. Anderton, I've enjoyed your engagement and contributions to the recording world for over twenty-five years (Electronic Musician magazines that I still have).  It is my privilege to absorb your thoughts and approaches to music production.   I truly mean that.

  10. 11 hours ago, bitflipper said:

    My favorite for bass is Meldaproductions' MDynamicEQ.

    It's a great static EQ, but being dynamic as well, it's useful for dealing with bass resonances. The dynamic action also lets you add some high-frequency boosts only on the notes that need it. These qualities also make it well-suited for vocals.

    Killer, killer software.  Great citation, Bit.

  11. 22 hours ago, Craig Anderton said:

    All DAWs have different preferences. It's unfortunate that you have to be a rocket scientist to make music these days, but I'm afraid that's the case.  Think of all those preference parameters as a combination lock - get the numbers right, and things work...and then there are all the Windows variables. 

    I still don't miss tape, though :)

    Wow, yes.  What insight and wisdom you show here, Craig.  Truly.

    I had a Tascam deck (4-ch), and it was, although a privilege in the early eighties, a challenge.  15-ips was the blessing, I thought!  But we innovated and got our art down!

  12. On 6/18/2020 at 5:34 PM, John said:

    Ozone 5 and all Ozone versions are very CPU intensive. In many years past I used it on a mixed down stereo track in a mastering template due to my computer would have trouble otherwise. I still, more or less, do that even though I have a system that is very capable. 

    One  trick to try is up your latency enough so you no longer have problems. You can put it back for recording. 


    Edit to add. A rundown of your system would be useful. 

    Thank you, John.  It's a puzzle.  Much of my thoughts on this center on the number of issues with Cake audio when compared to other systems.  I use Pro Tools, too, and it skates through this stuff.

  13. On 6/18/2020 at 4:50 PM, David Baay said:

    Any chance you enabled the non-default  'aggressive' ThreadSchedulingModel=3 in AUD.INI (Preferences > Audio > Config File) despite warnings that it's experimental? Many who have tried it had a result like you describe, and many of those promptly forgot they had made the change and blamed the update... as usual. ;^)


    No, I remembered.  Thanks for the response.

  14. On 6/18/2020 at 5:22 PM, GreenLight said:

    Maybe it was the 'aggressive' ForumPostSchedulingModel = 3 that was enabled by mistake in AUD.INI by the OP?

    I'm not saying things can't be improved, but manners could. 😉

    Thank you for the tip.  I've covered that one prior, hoping for better luck long ago.  I appreciate the response.

    • Like 1

  15. On 6/18/2020 at 2:21 PM, LarsF said:

    You had this and everybody else must have too?

    Last time I had crackle in Cakewalk was when I reached 48 tracks, and sends and stuff everywhere. And this was a mistake due to that Prochannel had activated two plugins on every track, 96 instances.

    Removing those I now am on 80 tracks in same project and still no crackles.

    I run RME HDSP 9632.

    What is your reference with any other daw and tracks and so on?

    Maybe your interface is on the verge already doing what you did, and just that bit better working with other daws.

    So which interface is it, or your feedback is futile?


    Lynx audio card.  Again, though, what hits me is that other DAWs have no issue.

  16. Created drum track in Superior 3, guitar raw input from mic'd amp, bass same, then sang a track.  Three minute song, with a TrueVerb bus, Tony Maserati vocal plugin and Ozone 5 in the master bus.

    Added VocalSynth and immediate popping and clicking for three of the five types of effect.  Rebooted, tried again, same.

    Setup same song in Sequoia, same add of VocSyn afterwards.  Beautiful.  Added VocSyn to the guitar track for fun.  Smooth as silk.

    Went back to Cake and added VocSyn to guitar track -- immediate audio dropuout upon hitting play.  Won't even play.


    Please consider that asking me for specifics on my resources and all misses the comparison point.  I'm quite sure that Reaper and the wonderful Nuendo would have smiled through this, too.   Cakewalk, you must know something about how you are handling audio in detail.  What is it?  It's got to be fixed before anyone but hobbyists, if even they, would feel comfortable even starting a project with it.  Imagine a studio!

  • Create New...