David Baay

You lie Youlean! Nothing crashes in Reaper, and nothing crashes on a Mac. Doubly impossible!

The metronome only follows what's in the Meter/Key View and reflected in the project Timeline. And Audiosnap only really cares about beats per minute. The Beats Per Measure setting in the clip map is just a convenience for you to keep track of where the downbeats are when setting markers. In any case, the answer is no, it's not possible to set different meters in the Clip Tempo Map. You would need to split up the clip at downbeats where the meter changes. I would suggest you first go through the whole recording and enter all the meter changes; the project tempo doesn't have to be following the clip to do this. Then, rather than using Audiosnap, use Set Measure/Beat at Now to manually align the timeline to the clip as needed.

Never seen anything like that. Would be interested in seeing a project or steps to create one that reproduces it.

Kontakt has options for managing how much of the sample set loads that might help. SD3 is pretty light and I'm seeing no delay with it, loading several projects I hadn't opened for years. I wouldn't pay to much attention to other threads about slow-loading unless the symptoms are near identical to yours and they ultimately found a solution that you might try. There can be many different causes, and most of us are not experiencing abnormally long load times. Check your Windows performance monitor in Task Manager to see what it's working on when the load "hangs". You might need to get familiar with Microsoft Process Explorer or Process Monitor to get a better handle on it.

I'll have to look into that because I've "disabled" the Connect service several times in different ways, and it always seems to "revive" itself at some point.

Numeric Peak indicators hold whatever peak level is reached until they're reset or playback is restarted. If you're looking at the same track in the TV and CV, and only starting/stopping playback with no other change in the project state, it's hard to imagine how they would get out of sync. But if any sends or buses are involved, switching mute/solo/send/interleave states or gain/volume during playback could get things out of sync depending on the routing. Arming a track or otherwise changing where the meter is picking up the signal (i.e. pre/post-fader) can also produce unexpected results. Regarding the change in metering overnight, I would be inclined to think you were simply mistaken about the state of the project when you saved iand/or what you were looking at, and what you're seeing now is accurately reflecting the current stae of the bounced audio and metering settings But it's also possible that some FX plugin was reset to initial conditions on being reloaded and isn't producing the same result it was before because it's not linear phase or something like that. You might get a better idea of what happened by importing the three generations of clips (as-recorded, after applying gain, after bouncing together) from the audio folder into separate tracks of a new project and seeing how they compare. This is a case where the problem would need to be captured on video or by sharing steps to reproduce it in a new project in order to fully understand what's happening. All I know is that just about every time I've encountered a situation in which levels were unexpected, it turned out I was misunderstanding something about the routing or looking at the wrong meter. It happens easily.

I haven't set up or used a control surface for a long time so I'm not the one to give detailed guidance; I just wanted to check that the basics were right which sounds like they are. All I know is that when a keyboard stops working as a basic MIDI performance controller, it's often because ACT has taken over the port as a control surface.

Or just drag/slide/nudge the MIDI track out two measures, and Ripple All should take care of it.

Are the keyboards using independent USB MIDI connections and the Mackie is plugged into a seprate interface port so nothing is daisy-chained? Then did you set up theMackie as a control surface in ACT, and were the other ports possibly included inadvertently.

In the mean time, if you know what the offender is, you can just move the .dll so CW can't load it, open the project normally, and remove the "missing" plugin instance(s).

Record both outputs to a stereo track and zoom the waveforms. Any meaningful true-stereo difference should be obvious. I'm not familiar with these synths, but if they have onboard FX some of those might manufacture stereo content that isn't in the raw audio from the synth section.

What if you try that setup in standalone Kontakt or in another VSTi host?

Oops. I hate it when that happens. ;^) But, yes, the OP needs to determine whether the Hammer 88 is outputting the full range, and if not, why not.

Not exactly. What I said was that the option to Always Echo Current MIDI Track is enabled by default in a new installation. When you insert a new Instrument track it will automatically become the current/active/focused track so the Input Echo button will be enabled in Auto-Thru mode (as indicated by an "A" in the icon). It was mentioned that Input Echo needs to be enabled on an audio track to hear the input while recording with or without FX. More generally, it needs to be enabled to hear live, external input, whether recording or not.

I think the CC11 messages and envelope will be in contention and one won't consistently prevail over the other. CC11 operate within the maximum Master Volume level established by CC7, so to some extent you can compensate for a limited range of CC11 by raising/lowering the Master Volume. But you should probably just pursue getting the PCR800 to respond correctly to the Expression Pedal as Promidi described. It might just be a matter of ensuring the pedal is at one extreme or the other when you power up the keyboard.

Are you saying that writing volume automation on a write-enabled bus works on a new project but not on the existing one where you initially tried it?

By default, the keyboad is just going to generate MIDI CC11 messages in response tp the pedal, and that's what will be recorded. In order to use it to write automation, you would need to set up the PCR800 as a Generic Control Surface and map CC11 to write automation. And rather than "recording" automation, you enable Write on the track and write the automation during playback. Since setting up a keyboard as a Control Surface will interfere with using is as an ordinary MIDI controller and takes some work, I would suggest you just go ahead an record CC11 as usual and leave it that way. If you really want it to be implemented as an automation envelope for editing, you can convert it after the fact by Clips > Convert MIDI Controllers to Envelopes.

Playback of pre-existiing MIDI is more like playing recorded audio because CbB can look ahead and buffer up the audio in advance rather than having to process each MIDI event as it arrives "unexpectedly" in real time. This is what the Prepare Using XX Millisecond Buffers setting is al about in MIDI Preferences. The default is 50ms which is equivalent to approximately 18 buffers of audio. If it's really about bridging 32-bit plugins, Jbridge is very inexpensive and can be used in place of CbB's Bitbridge. I used it for years until I swore off 32-bit plugins altogther as it addressed some other issues with Bitbridge. https://jstuff.wordpress.com/jbridge/

I can't reproduce a problem playing back a loop-recorded clip once looping is turned off, other than that recording sound on sound will produce loud transient from all the active lanes playing back together. There's no point in submitting a report of a problem that can't be reproduced but... Are you already logged in when you choose Submit a Request, or your issue is at logging in? Maybe clear your browser cache or try a different browser.

… or any buffer that’s not an even multiple of 64; a showstopper with several interfaces I’ve owned.

Yes, strange, as Always Echo Current MIDI Track is enabled by default in a new installation. You must have disabled it a year ago and forgot.

30 ticks is the new default minimum loop length when you enable loop selected range with nothing selected. Personally I thought it was pointless and potentially problematic to go this low but it was requested. It sounds like your interface driver is having trouble with it. Hot key L will toggle looping off.

That line indicates you have an old, seldom-used Enhanced Keyboard Editing mode enabled. Numkey 0 (zero) toggle it on/off.

I don’t often use the arpeggiator, but have never seen the problems you describe when I have so I suspect it has something to do with the specific project setup.

Yes, a .CWP file by itself should be small enough to attach here, directly.