David Baay

Are you appying Reverb or any other stereo FX via sends? If so you'll need to right-click the Send Pan and enable 'Follow Track Pan' if that's what you want.

In this particular case, I think all the FX going gray in the bin kind of gives it away. But I just realized that Mercury doesn't apply the track strip color to the header of the FX bin as Tungsten does; it remains the default black. Not sure to what extent one or the other was intended, but I prefer Mercury's treatment.

Glad to hear it, and hoping for a 'Mercury Classic' version. ;^) I've significantly warmed to the flat look, but would appreciate having a more-3D option. And I'm guessing this will be a big hit with other oldtimers.

Zooming and checking colors with a picker, it appears to me that this is an artifact of the smoothing algorithm blending the edges of the icon with the background, exacerbated by the fine line used to draw the icon. Even the most distinctly 'orange' pixels appear to be very slightly altered by the surrounding background color. If they were all that pure color (i.e. no smoothing), I don't think there would be a difference, but the icon would be badly pixelated of course.

Good one.

So if I'm understanding correctly that this means dragging the clips to start earlier, it's to be expected that the clip lengths will stay the same and a gap will open up after them. To avoid that you would need to lasso the clips in that segment and slip-stretch the start times by holding Ctrl+Shift and dragging the start. I can't say that I've ever tried to combine comping with stretching, but my first attempt seemed to work as expected.

I personally dislike the way Melodyne interpolates tempo changes where none exist, and it can make big mistakes when the rhythmic pattern changes at the chorus. Also, it generally can't handle any significant rubato but that shouldn't be an issue in this context. Worth a try, but I would still opt for the manual method.

Hmmm... yeah, if it's based on the original Lennon tracks, that will definitely not be following a click. P.M. me a link to a shared upload and I can get you started at least with a rough alignment. If it includes a synced click track, it should be quick.

Yes, if they're going out of sync, it's the audio tempo that's out of sync (or varying) against the project tempo. You can confirm this for yourself by enabling the Playback metronome and hearing that the MIDI click stays in sync with it. I'd be happy to take a look at it if the track(s) are freely available somewhere or you can share a zipped copy of the project folder.

It seems some posters here have encountered the problem and understand it, but I don't see a tempo change in the region being edited, and it's not clear to me what action was taken between the first and second screenshot. I'd like to understand fully so I can reproduce it and submit a bug-demo project to the Bakers.

Same question as for MrNoName above: What screen resolution, physical size and Windows scaling? The Bakers will need to know. I'm not seeing that on either my scaled laptop or unscaled desktop monitors, but I have intermittently seen Preferences displayed with oddly bold fonts in the past.

What screen resolution, physical size and Windows scaling? For me everything is noticeably sharper on both a 16" 3072 x 1920 laptop at 160%, and 24" 1920 x 1200 desktop monitors at 100%. The only thing I notice is that the font used in dialog boxes is so fine it almost looks grayed out on the laptop, but it's fine on the desktop monitors.

Segemented meter option is still available in Preferences > Customization > Audio Meters.

It's possible the project tempo needs to be tweaked to match the actual audio tempo. A quick way to do this is to count out 8 measures, Tab/Shift+Tab to the transient that should be at 9:01:000, and if it's not exactly there at 76bpm, hit Shift+M to open the Set Measure/Beat dialog, enter Measure 9, Beat 1 (probably already guessed by CbB), and OK. CbB will modify the initial tempo as necessary to align the timline with the audio at that point. If it's a fixed tempo it should be pretty well aligned through the end of the song. If it still drifts a bit, you can get more accuracy by undoing the original Set, and doing one further out like 33:01 and also manually putting the Now time exactly on the transient with snap disabled rather then depending on CbB's transient detection to get it right on the money. If the tempo still drifts at that point, then it wasn't recorded to a click, and you'll have to Set more points to line it up every 4-8 measures or more.

Interesting. Just saw this and downloaded the project just to see what was going on. I noted the Enable Stretch option was checked (with stretch still at 100%) in Audisnap properties which it should not have been by default. I didn't find that it caused the problem shown in your video even before I disabled it, but I did find the audio weirdly distorted like it had been previously stretched even after I reset all markers. Glad to hear you got it sorted in any case.

You can just drag and drop it into a MIDI or Instrument track from wherever you downloaded it, and it should be immediately ready to roll out copies. It will appear short of 4 beats because the notes are only 1/32 long and it ends on the last one, but once drag past the the end of the first bar, you'll see the beveled corners where it starts to repeat. Also, since you said you didn't want anything too distinct, I set the velocity at 72, but that's easily changed any number of ways, including non-destructively by just putting a Vel+ offset on the track.

Hmmm... unless something has been broken in a recent release, that's pretty weird, and I can't really imagine what could cause that. Can you zip up a project with a small snippet to share? I'll have a quick look here in the mean time. EDIT: Seems all good here, alternately stretching/compressing phrases in a two-hour-long interview. I'm wondering whether you're actually hearing a compressed segment play at the same slower speed as a preceding stretched segment where you started playback or are you being 'fooled' by the fact that the M:B:T timeline is the fixed visual time reference and at a given timeline tempo the Now Cursor will always travel at constant speed regardless of the 'tempo' of the audio...?

I'm not fully understanding your process. Are you matching the tempo track to what you're doing in Audiosnap? If you're just moving transient markers around manually, the total playback time of the clip will not change, and making one section slower by stretching a range of transients will necessarily make the next section start sooner and/or play faster, depending on what's selected, and whether you're using proportional stretching. But where you start playback would not matter in that case so I think I'm missing something about how you're working. If I'm understanding the goal, my approach would be to match the timeline to the audio using Set Measure/Beat At Now, and then enable Autostretch on the audio clip and flatten or moderate the tempo variability using the Tempo Offset by Percent feature.

If the clip was created in Step Sequencer, it's already a Groove Clip, and there is no need to right-click for anything. Just hovering over the edge of the clip will display the slip-edit cursor as Glenn's screenshot shows and left-click will grab the edge to roll it out. I know you want to figure this out for yourself, and I'm all for 'teaching a man to fish', but did you try the Groove Clip I shared?

I like to use the Groove Clip section of the Clip Inspector to set Beats in Clip. Loop Construction is for audio, and I think you're wanting MIDI. Here you go: 4-Beat Closed-Hat Click.mid

^^^ This. When was the last time you rebooted? In the past I've had issues with "zombie" logins to Bandlab that don't work for authentication and persist even after logging out and closing all browser sessions.

Options > Click Behavior > Transport Seeking Stops Playback

When you say 'export', you mean the same as transmit/send, right? I use external MIDI hardware all the time, and have not encountered any issues with regular note and controller data. And I happened to be using MIDI Sync just recently as well without a problem. Start/Stop/Position working indicates the basic port assignments, connections and drivers are all okay. The most likely issue then would be that the transmit/receive channels are not matching.

Sounds like CPU Conservation Mode, toggled on/off by the Pause key, reducing UI updates to one/second. Will affect meters as well as the Now Cursor.

There was a long discussion of issues related to punching in to a Melodyned track a while back. It wasn't clear how much of this was due to CW's implementation vs. inherent limitations of ARA: