Jump to content

scook

Members
  • Posts

    9,681
  • Joined

  • Last visited

  • Days Won

    27

Posts posted by scook

  1. Can't change presets like that but here are a couple of idea

    1. Sends - create buses for each of the different effect chains needed and automate the sends to the buses.

    2. Clip FX - each clip in a track has an FX rack just like the track FX rack. Effects stop and start and clip boundaries which may not be desirable.

    3. Automation - just as you started out doing. It is possible to copy and paste the automation as needed. The arranger feature in 2020.04 may make this approach easier than it currently is. To avoid abrupt changes in delay time, you could use multiple instances of plug-in. Because the delay does not have a way to automate its bypass, the MixL and MixR will need to handle the task.

     

    • Thanks 1
    • Great Idea 1
  2. 17 minutes ago, StudioNSFW said:

     Even upgrading to the new release adds a new major feature (arranger) which means that there is a greater risk in upgrading in that projects will no longer open in my safety net, my paid for and damned expensive X3 install.

    There has never been a guarantee of forward compatibility.

    That said, projects created in 2020.04 using the arranger feature open in X3. Like all versions of SONAR, opening projects created in CbB will generate a warning message about the project being created with a newer project and the chance of missing features.

    So far, the only features that completely prevent projects from opening in SONAR are patch points and aux tracks. Opening a project containing patch points or aux tracks in a version of SONAR that does not support the feature, such as X3, will fail.

    17 minutes ago, StudioNSFW said:

    I would be happy as a clam with a perpetual and frozen version of the software.

    That would be X3 in your case

    17 minutes ago, StudioNSFW said:

    Will I be forced to accept an upgrade eventually to re-activate? 

    Tough to predict the future but my guess is at some point a feature will be added using an MS library that won't load in older OSes. Much like what happened between X2 and X2a with multitouch support. X2 was the last version of SONAR which could be installed on XP because the libraries needed for X2a were not available for the OS.

    • Thanks 1
  3. Make sure only the track being recorded has input echo enabled. I turn off Always Echo Current MIDI Track in order to have better control over which tracks have input echo enabled.

    Also some plug-in have the ability to generate or pass through MIDI data. It is a good idea to turn this off when it is not needed. For those synths that have this option, it is enabled by default. To review and set "Enable MIDI Output", open the plug-in UI and click the VST2/3 drop down above the UI. This image shows a plug-in with the option enabled.

    M9I2IRu.png

     

    Please avoid creating multiple threads on the same subject.

     

  4. 11 minutes ago, Evael said:

    I want when I say 'None input', no signal to come in the track, no matter how much a press the buttons.

    This is not how the program works.

    By design, turning on input echo requires an input other than None on instrument and MIDI tracks. To that end, tracks set to None change to Omni when input echo is enabled.

    This is why I turn off Always Echo Current MIDI tracks and assume manual control of both the input drop down and input echo.

     

    Feel free to file a feature request.

    • Like 1
  5. 10 minutes ago, Craig Anderton said:

    I didn't realize Exports were always made from the Master bus when you selected Entire Mix

    The default "Entire Mix" is essentially "What you hear" - IOW all tracks and buses that point to the mains.

    As you know, the Export dialog also permits exports from the master bus or any track or bus.

  6. 34 minutes ago, Evael said:

    I tried disabling 'Always Echo current MIDI Track' but the problem is when I manually click on the monitoring icon next to rec-arm icon on the track, it keeps reverting it to All imputs - Omni, whils it still says None.

    Definitely a bug!

     

    Not a bug, I explain why later in the the thread linked above (note: monitoring icon = input echo)

     

  7. Actually @Craig Anderton in CbB I route the master bus to a "final bus" which routes to the hardware output.

    Sonarworks would go in the final bus FX rack.

    It does not affect exports because exports are made using the master bus. There is no need to change routings for export.

    New tracks are always automatically added to the master bus because it is still the default bus.

     

    Of course, this routing assumes the headphones use the same main ports as the master bus. If the headphones can monitor different hardware ports, instead of a "final bus" a send on the master can do the same job.

     

    • Like 1
×
×
  • Create New...