Jump to content

Jon Paul Sapsford

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by Jon Paul Sapsford

  1. 21 hours ago, Noel Borthwick said:

    Are you using a custom workspace? Set your workspace to None and retry. 

    Wanted to report back that that did the trick. No idea why the update changed the workspace I was using, but changing it to "none" fixed it up nicely. Thanks for the help!

    • Thanks 1
  2. 19 minutes ago, Noel Borthwick said:

    What are you having to reset? We're not aware of any change that mandates resetting layout. Which version did you upgrade from?

    Upgrading from the last update, 2025.08

    The things I recall off the top of my head that got reset are the console view was closed, and when I opened it the bar that separates the tracks from the busses was resized and in a different position. The height of the send row and the FX chain  row in console view got reset. The browser window returned and was maximized, the track heights were all changed

  3. I just updated to the 2nd2025.08 version and just wanted to give some feedback.

    Resetting every saved  sessions' layout is super annoying. Having to waste time reorganizing all of my windows today is not what  I had hoped to spend my morning doing when opening  projects.

    Is there any chance in the future that we can be warned when an update is going to do that? I know I'll update eventually, obviously, but to have a little heads up  would be nice in case, like I am right now, I'm in the middle of a time sensitive project (yes, I know I'm wasting time posting this, but...)

    • Like 1
  4. I posted about this recently thinking it was a bug (https://discuss.cakewalk.com/topic/89249-default-midi-input-help/#comment-609011) but it's seemingly working as intended.

    So, I am throwing out the request to allow us to change the default midi input when adding a midi track/instrument. It is very frustrating to add a new track, record something, and realize that it was echoing another track into the recording because the default input is "omni" and I didn't change it to only accept input from my midi keyboard.

    Thanks for the great software since forever

  5. Alright, I appreciate all of the help. I was really hoping there'd be a way to change the default on that. 20+ years using the same software creates some pretty strong muscle memory heh, but I'll see if I can get used  to some of the work-arounds you all have shared.

    Thanks again

  6. On 8/9/2025 at 1:26 PM, David Baay said:

     

    Are you maybe talking about the Bandlab web app? Or maybe CW Next?

    In Sonar, the menu path is Insert > Soft Synth. After selecting an Instrument plugin, you get an Insert Soft Synth Options dialog.

    Or you can right-click in Tracks pane and choose Insert instrument which gets you an Add Track dialog with the Instrument tab selected that has an Instrument pick list at the top and an Input pick list under that.

    Yes, sorry, that's what I'm doing (I think it was called that in an old version and my brain hasn't replace it yet? Maybe?). I right click on the track pane and click "insert instrument" which opens up the "add track" dialog box.  Just for clarity sake I screenshotted exactly what I'm seeing.

    The issue I'm having is that with the input defaulting to "omni", I get notes from other midi tracks playing on this track (same goes for if I just add a plain old midi track with no VST associated with it). I am trying to figure out how to change the default input for midi.

     

    image.png

  7. Thanks for the reply!

    So, the issue is repeatable in that if I go to "insert new instrument", it defaults to omni/none, which then has the newly created track accept input from other midi tracks (seemingly random). The same goes for adding just a basic midi track. If I select just my midi keyboard as the midi input from either the dropdown on the "add new instrument" dialogue, or on the midi track's input dropdown, it does not do that. 

    If I select my midi keyboard as the input in the "add new instrument" dropdown, it will persist as the default choice for the remainder of the time I have Sonar open, but it reverts to omni/none when I re-open Sonar. I have also tried changing the input on the "add new instrument" dropdown to my midi keyboard, adding an instrument, deleting said instrument, verifying that the next instrument I go to add has my midi keyboard selected as the input, and then saving as my template, but when I open the template, the issue persists.

    I am trying to figure out how to change it's default input because as I'm sure is evident, it's pretty annoying that every time I add a new instrument or midi track it accepts input from the other midi tracks.

    I also apologize if I'm not understanding what you're asking, I've never had to get too deep into midi signal chains and all that, so this is right at the high end of my pay grade and I might be missing something obvious.

  8. Hello, 

    This issue creeped in sometime in the last year or so, but the default midi input when I add a midi track or an instrument is set to "omni", which makes it super annoying when I go to record on that new track if I have notes playing on another midi track because it'll record those as well. I know I can change it after I add the new track, but with as long as this has been an issue, my brain just won't train itself to do so and I *always* have to do a second take because the first one has another track's midi being recorded on it. 

    I've noticed that if I select just my keyboard as the midi input when I insert a new instrument, it'll default to that when I add instruments from there on it, but it doesn't save with the session (or if I change it and make a template out of it). 

    Does anyone have any idea how to solve this? I am probably missing something, but I can't see why it being like this by default is a good thing.

    Thanks for any tips!

×
×
  • Create New...