David Baay

Studio One gives the same incorrect result as Sonar, indicating BBCSO inherently has issues with offline rendering using default settings. I tried other settings and the result only got worse. (e.g. completely flatline audio). This will need to be taken up with Spitfire support.

How about Snr for the free tier with the abbreviated feature set.

Click the 'Advanced' radio button at the very bottom of Preferences.

See Process > Nudge > Settings The three Nudge values can be set in samples as well as seconds, milliseconds, ticks and SMPTE frames. I often set them to something like 1, 4 and 12 samples so I can additively get whatever exact amount I need with a few keystrokes in either samples or milliseconds (e.g. 4 nudges of the 12 samples = 48 ticks = 1 millisecond. For a known, larger amount that would require a lot of nudges use Process > Slide which supports measures, ticks, seconds and frames. ...or Snap By which can be set to a specific number of samples.

When you're able to provide a reproducible case for the Bakers to investigate. 🙄

Not applicable to audio.

I think any plugin that can do this will necessarily be using lookahead and adding undesirable delay compensation latency to the whole project. If it were me, I would just Nudge the audio clip to where it needs to be. If it's a channel of a stereo track you can bounce to split mono, nudge the late channel back, and bounce back to stereo if desired. You can set a single-sample Nudge value and nudge during playback to dial in the offset. I'm thinking you should also invert the polarity of one of the tracks since a pressure peak inside the drum will be a pressure 'trough' outside once the phase is corrected.

Is this still involving Spitfire's BBC Symphonic Orchestra? I know the Bakers are already looking into that, but if you're having issues with other plugins I'd be happy to look at any demo project for which I have (or can acquire for free like the Spitfire library) the relevant plugins to see if I can repro the issue or maybe help identify an avoidable cause. Bounce/Freeze/Export all use basically the same code so it's no surprise - even expected - that an issue with freezing would also manifest in a non-realtime export.

No, Channel Tools cannot advance a signal and there is no included plugin that can.

If you have more than one track doing this, it's probably not the arperggiator. It may well be the plugin not playing nice with Fast Bounce. In that case, another thing to try would be increasing your ASIO buffer or setting a non-zero BounceBufSizeMsec value in Preferences > Audio > Configuration File to override it when fast-bouncing. I have mine set to 20.

Let's make it change. Please PM me links to some zipped projects so I can help you get this sorted... to satisfy my curiosity if nothing else.

Any chancee the track's arpeggiator is enabled and giving a different result when frozen/fast-bounced? I have encountered this in the past and had to use realtime bounce to get the desired result.

Welcome back to Sonar and hopefully newfound health! Yes, Workspaces is one of the few features that have been reserved for Premium.

I think your issues are likely all or mostly related to using a project template that had empty Prochannels originating from the hack/bug in SONAR 8.5 as we have discussed before. Your incessant re-posting that you can't open old projects in Sonar is getting tiresome and is misleading new users that this is a common problem. Please get it figured out or let it go. I'm here to help if you want to share some more non-working projects to troubleshoot.

What are the symptoms of not loading in Sonar Free Tier? This is absolutely not typical. Many here have projects and even WRK files going back decades that open without any issue. You should open a dedicated thread to troubleshoot your issues.

There have been issues reported with a recently released driver update from Focusrite. I dont know whether Focusrite have yet addressed this. Check their website/forum for info, and maybe try downloading the previous driver release.

Whatever is going on is not new to Sonar. On my non-touch screen laptop CbB has the same small-sized three-octave keyboard as Sonar. And on the touchscreen, they both have the larger 2-octave one which makes sense for touch-playability. I don't think I have ever seen more than three octaves in any version of SONAR/CbB/Sonar on any machine.

I'm not aware of any VSTs that send MIDI to a virtual OUT from the UI keyboard, but it's possible such a beast exists.

If you had a touch screen, it would be big in Platinum the same way it is in Sonar - probably even bigger because Platinum doesn't use vector graphics which are, in fact "wonderful", notwithstanding the handful of teething problems that some (not all) have encountered, depending on their display hardware, monitor setup, O/S configuration and project layouts which are infinitely variable.

That is definitely not right, and nothing like what I get. I have two laptops with different display resolutions but scaling adjusted to give very close to the same amount of realestate in Sonar. One is touch and one is not. The touchscreen shows two octaves and the non-touch shows three. The keyboard on the touch screen is much bigger, using approx. 60% of the screen width while the keyboard on the non-touch screen uses only about half that. But both are displaying the octave and hold controls amd full key lengths.

Working here, also. What exactly is not working? Not loading, not responding or some function not having the expected effect? Possibly the FX bin itself is disabled? This has caught me out a number of times.

A Move is inherently a Cut-Paste. That said, I thought Ripple All would always move everything regardless of Cut/Copy and Paste settings. If that's not the case, I think it should be. I'll try re-testing with one or both of my Copy/Paste Special dialogs set to exclude Meter/Key changes. EDIT: I retested this, and Ripple All seems to move everything, as expected, regardless of Cut/Paste Special settings. As this point, I think you might need to share a stripped-down copy of your project with exact steps to reproduce the issue.

What are you using for an audio interface, and are you trying to have MIDI in the project drive the sound engine in the Nautilus? If so, and you want to monitor the Nautilus' output through CbB (as opposed to direct from the Nautilus to headphones/speakers), you need to have an audio track in CbB with Input set to the audio input to which the Nautilus' audio output is connected, Output assigned to your audio interface (usually via a Master bus) and Input Echo enabled. If that's not the setup/intent, let us know what's in the project and how you're routing MIDI and audio.

Are you not able to record to an armed audio track, or is it just that you don't hear live output because neither the Mackie's direct monitoring mode or the Sonar track's Input Echo are engaged? You need to have one of the other - but not both - enabled in order to hear yourself in real time (since you're recording from a mic, I presume you're monitoring output from the Mackie via headphones...?). For monitoring your own performance while recording, you'll want to be using direct monitoring because 27ms of latency at 512-sample buffer is going to be to much for input monitoring The windows audio settings are only relevant to Windows sounds and generic multimedia players and browsers that use it; Sonar is going to be using the interface driver directly via its ASIO driver so the Windows audio setup doesn't matter, but you might do better to assign your onboard audio (e.g. Realtek) as the default I/O device for Windows, leaving the Mackie dedicated to Sonar so there's no chance of a conflict.

The question was about how many octaves are displayed at once.