David Baay

That's right. Ignoring the OP's mention of SMPTE times, which might just have been intended to indicate where he wants the downbeat in absolute time, changing the time signature to 2/4 at 7:01 will put 8:01 at SMPTE 00:00:17:10 where 7:03 is currently without changing the tempo. If the tempo doesn't need to be held at 90bpm through measure 7, you could also get 8:01 to hit SMPTE time 17:10 by changing the tempo at 7:01 to 4 / 3 * 90 = 120bpm (4 beats at 120bpm to go by in the time of 3 at 90bpm). If there's already MIDI in the project that needs to maintain its absolute timing you can use Set Measure/Beat At Now to make the necessary tempo changes. - Snap the Now time to 7:01, Shift+M for Set Measure/Beat At Now and anchor it where it is by entering Measure 7, Beat 1. - Snap the Now time to 7:01, and SM/BAN it to 8:01. - To get the tempo back to 90 at 8:01. snap the Now time to 9:01 and SM/BAN it to 8:04.

On getting back to this I forgot the OP has indicated it wasn't a problem in CbB. I don't have CbB on this machine but I just checked Platinum, and indeed they preview okay there. I don't know offhand how to determine what tool/method was used to embed the looping metadata and whether they are consistent with some standard/convention. @msmcleod might be able to download the files and have a look.

There was recently an issue with other view parameters were not being restored correctly only on the first project to be opened, so possibly this is another manifestation of that, but I am not able to repro your issue. Is this Sonar free or paid? If paid, are you using Workspaces? Can you share a demo project?

I'm not sure I understand the issue... or maybe that you understand it. Your transport module is showing SMPTE time. That's only ever going to be in sync with whole measures at tempos of 15, 30, 60, 120 and 240bpm, and you're currently at 90bpm where a measure is 1/3 of a second (20 frames) longer than 2 seconds. So the frame value will increase by 20 frames mod 30 with every measure, giving you 20, 10, 00, 20, 10, 00... as you're seeing.

I think there must be some issue with the metadata in the files that tells Sonar they're 'loops'. They do behave like loops when dragged into a project and rolled out, but the preview basically stops when the file ends as it would with an audio file that has no looping metadata added. You might need to take this up with loop vendor. Try replacing your files with these - bounced and converted to Groove Clip loops: EDIT: Just realized I did not export these loops correctly, and the looping info was lost. Fixed by saving from Loop Construction view. I should also note that these are 48kHz where the originals were 44.1kHz. HTHT_125_Hat_Loop_Adder (GC).wav HTHT_125_Hat_Loop_Amped (GC).wav

What is it?

It's always been a challenge to predictably add notes to a specific take lane. It would be nice if focusing the lane did the trick but it doesn't. I'm pretty sure I've formally reported/requested this in the past. In the mean time, the most reliable way I've found is to select a note in the PRV that belongs to the relevant clip and Ctrl+drag copy it to where you want the new note. That note will always be created in the clip from which it was copied and any additional notes you add will go to that clip. This also avoids the problem that creating a note more than aabout 5 beats later than the last note in a clip creates a new clip. Drag-copying a note beyond the current boundary of the clip automatically extends the clip boundary.

It's perfectly safe to Melodyne a flattened comp in the original track. This doesn't affect the comped lanes at all. If you want to change it later, you can just unsolo the flattened comp, delete (or mute) the lane, re-comp, re-flatten and Melodyne again. That said, I always advocate saving a project with a suffixed name before doing major edits so you easily revert if something goes wrong, and I do often archive raw tracks (mostly MIDI in my case) within projects until I'm satisfied with the final product.

I kind of suspected something like that. I tried it myself yesterday and didn't see a problem, but I Melodyned a flattened comp after unlocking it. If you Melodyned the unflattend comp clip in the parent track with lanes closed, it makes sense that the Melodyne clip would replace the individaul takes that comp clip represents with the Melodyne clip in T1. So I'd say it's not a bug, but it could certainly be considered unintuitive if you aren't fully aware of how ARA works and how a comp clip represents take lane clips when lanes aren't showing.

In the Tools module of the Control Bar, select the Draw (Pencil) tool, right-click it and choose 'Line'. As you draw over existing velocities, it will 'trim' them to form a straight line between the start and end points of your drag.

If Windows or other another app is competing for control of the clock rate that could happen. Less likely with a manufactuer-provided native ASIO driver; more likely with onboard audio using WASAPI or any 3rd-party driver. What audio interface and driver mode?

What are you using for a keyboard/controller. Most VSTs will respond to wayward pitch wheel messages the same as hardware modules. How big is the pitch error in semitones? A clocking error between 44.1 and 48kHz would throw it off a little more than a semitone in either direction, but the hardware modules would only be affected if they're being monitored through Sonar.

I don't have CbB on this machine, but Sonar Platinum 17.10 produces the same output on freezing, so either the problem just didn't manifest with the particular MIDI content and instruments you were using at the time or possibly Spitfire have updated their rendering engine since then and created a problem.

Not sure what might have happened but a few observations and questions: - Based on the uppermost take lane being soloed it appears that Flatten Comp was excuted at some point whether deliberately or not. - Are you sure the remaining clip in T1 is your comp, and not just the first take? - Based on that clip's name, it appears to have had Melodyne applied. Was it Melodyned before comping? Normally a flattened comp would be locked and could not be Melodyned after the fact unless it was unlocked first. - Are the takes still in the audio folder? They should be unless Clean Audio Folder was executed.

In truth I don't think there's actaully much of need to distinguish them except when the discussion is about what features are excluded from Snr.

This has come up before, and I have seen it myself in the past, but I don't recall what causes it and can't find any relevant thread on either the old or new forum. Mine are currently all showing only project names and opening/saving by different methods did not seem to have any bearing.

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.