David Baay

Check the the Event List view for NRPN messages and delete them or click the VST2 dropdown at the top of SI Electric Piano, go to Plug-in Properties and enable "Do Not Intercept NRPNs". Incidentally, an Instrument track is a combined MIDI and synth Audio track so you can drop the MIDI right in the Instrument track and get rid of your separate MIDI track.

CZ V is working as expected here; not even really seeing a significant delay in drawing the UI. This is with onboard Intel video on my laptop. It also has NVIDIA RTX that I don't normally enable for CbB, but I could try it. I would agree this is likely an interoperability issue between the OP's specific graphics engine and the way Arturia has implemented some feature. Hard to say who's at fault. First step would be to try it in another DAW on the same machine.

So if you just disable the Sonitus Compressor or the Mystique Tape Saturation plugin, which one is silencing the Master bus output? I'm thinking maybe you have the Compressor set to monitor the sidechain input, and there's nothing there.

In my experience, clips that are exactly 2 beats long or a multiple of 4 beats with strong beats on quarter notes get looped properly with no intervention. If they are some other whole number of beats long or have a lower or higher-frequency of strong transients (e.g. a slow kick/bass pattern or a fast arpeggio or percussion pattern) you generally just have to correct mis-guessed Beats in Clip value. The only time I see things really get screwed up is if the clip isn't trimmed to a whole number of beats and/or the timing of clip is radically out of sync with the project tempo to begin with. I'd be interested in seeing examples of clips that don't Groove correctly and aren't readily corrected by trimming and adjusting the Beats in Clip value.

Quoting myself here, I have to retract this statement. As I posted on the Pianoteq forum, it seems the difference I was hearing and measuring was mostly due to FX in CbB differentially reinforcing the more prominent low-mid frequencies in the new voicing. In other words, my FX settings were already modifying the tone in same direction as the re-voicing.

Dollars to donuts, anyone trying to alternate velocities between two values is starting with a string of notes all at the same velocity that are exactly on the grid. ;^) And even if there's some variation, Select By Filter can usually be made to accomodate that though it might be necessary to make a second selection. I strongly agree Sonar should have a library of basic MIDI selection/transformation rules with user-specifiied parameters to facilitate basic operations like this. And, related to this, that all the existing CAL scripts should be converted to native functions as has been frequently suggested in the past.

Best option is to buy one of the used licenses that are frequently offered for sale on their forum. I effectively got Pianoteq Standard for 40% off which is better than you will ever get from Modartt directly. Only caveat being that you can't resell it a second time IIRC.

Or maybe "Can this be done without a CAL script?" If the notes can't be easily be differentiated by note number, you might be able to use Select By Filter to pick out every other note based on Beat/Tick values. Or you could make a short Groove Clip consisting of just 2 or 4 of the events and roll it out as needed.

So it was a velocity-based fade in 3rd-party-generated MIDI as suggested. ;^)

Any new/updated plugins or a new audio interface in use? A crash to desktop like that usually indicates fatal memory corruption due to a misbehaving plugin, audio interface driver or other hardware driver. I'd also recomend you run a memory test to be sure it's not due to bad RAM. In my 35 years using Cakewalk, the one time I had general instability issues that weren't associated with some specific action, it turned out to be due to a bad stick of RAM. And the crashes only manifested in CW, apparently because no other applications were as RAM-intensive or otherwise using that particular segment.

I'm guessing you actually mean an "Instrument" track (combined MIDI and Synth Audio tracks) and it's the audio side that's being faded. Assuming the track isn't frozen (rendered to an audio file) , the only thing that could readily cause that would be an automation envelope. But if the MIDI is from a 3rd party, it's possible it contains Volume/Expression controllers or even a velocity-based fade. Open the Event List view to check for this.

Yes, a "dry" version of the "Jazz Recording" preset with built-in reverb, delay and limiting disabled - otherwise unmodified.

I'm sure a lot of Pianoteq users here are watching the Modartt forum. but thought I'd give a little heads-up here about the change in sound of this release: It's pretty radical for a "minor" update (not a new version with it's own plug-in .DLL that you can choose not to use in existing projects). If you have mixes that depend on the timbre (and loudness) of the last version (8.1.3 I think), you might want to render the raw Pianoteq output to wave before updating in case you don't like it and/or don't want to re-mix. The new timbre aside, I found at least one of the new "voicings" to be 2.5-3dB louder.

...until you accidentally merge takes that were meant to be separate. Then you'll be asking for a "Smart Unmerge" feature. ;^)

SI Bass's tunng control is very coarse with a range of +/- six semitones. A quick calculation shows 420Hz is ~81 cents (0.81 semitones) flat from A-440 . Holding Shift will allow you to get fine control of the Tuning knob to get to -0.8. I checked, and the actual tuning of SI Bass doesn't change with every tenth of semitone (-0.8 and -0.9 produce the same output) but -0.8 should be close enough.

I used to use a Mackie mixer to manage both input and output to/from my MOTU interface, but removed it from my setup some time ago. Now I use the volume control on the MOTU but it's become terminally scratchy as well. I've considered getting a Big Knob in the past; I'll be curious to see what recommendations you get.

Glad you got too a solution/workaround. I thought you actually needed to create individual split sample files so did not suggest non-destructive alternatives. Reading your original post in that light, I would suggest you use Pan automation with Jump segments and send to two Aux tracks with their inputs set to the left and right sides of the Patch Point.

The MIDI Prepare Using buffer has no bearing on MIDI sent to hardware ouputs. Its purpose is to pre-render audio from soft synths. For bes behavior when starting/stopping playback, changing loop points or editing MIDI during playback, it's best to keep it low. The primary symptom of an insufficient buffer is dropped notes. If you're not hearing that, you probalby don't need to change it from the default of 50ms.

Yes, but the Vel+ fader can add or subtract up to 127, so it goes from -127 to +127 and resets to 0 (no offset).

I'm afraid you're out of luck. The only way to create a non-contiguous selection of audio is by manually Ctrl-clicking segments. I tried some workarounds but had no success.

I think you must mean MIDI Volume faders. Vel+ runs from -127 to +127 and resets to 0. It's MIDI Volume that resets to 101. That said, do you use a hardware control surface or possibly have Remote Control set up on your MIDI Volume controls?

The controller sends MIDI messages to instruct a synth what to play. The meter is showing the velocity of MIDI Note On/Off messages, not audio volume level. What you need to do is right-click in the tracks pane below your existing MIDI track (which you can just delete), choose Insert Instrument, and pick TTS-1 (a multitimbral General MIDI synth) or one of the "SI" synths that comes bundled with CbB (assuming you haven't yet installed any 3rd-party instruments). An instrument track combines a MIDI track and a synth Audio track. To understand how it works, you should right-click the new track and choose Split Instrument Track which will separate the MIDI and Audio parts of it into separate tracks so you can easily examine and play with the controls and I/O assignments of each.

What driver mode? Some ASIO drivers cannot be shared regardless of App settings; I don't know about Focusrite. If that's the issue, it should be sufficient just to shut down Finale and re-launch CbB. If Finale supports WASAPI, changing them both to WASAPI Shared should do the trick. Or Rewire Finale into CbB as a client if Finale supports Rewire (some developers dropped it when it became unsupported).

Hey William, good to see you on the new forum (David Baay = brundlefly). You probably know that hard crashes like that are usually driver-related. I would guess this issue is related to your audio driver being invoked to audition pitch changes. You might try turning off audition (or toggling the audio engine off altogether) and see if gets more stable. If it does, changing ASIO buffer size might help. Otherwise you might need to try a different interface or experiment with WDM/WASAPI to further confirm it's the ASIO driver.

Which problems are those? Many of us have no problems. The only "problem" that has been somewhat frequently reported since this release is"slow loading", which is a generic symptom with many possible causes, most of which have turned out to be system/project/plugin-specific and none of which are specific to this release.