Amberwolf

Working and left alone is usually greatest. This is why I don't like (or use) systems or software that autoupdate. If I can't turn that off, I'm not using it, becuase it's going to break itself or something I *need* at some point, possibly in an unfixable way (without a wipe/reinstall from a backup image, etc; I've been thru that too many times to trust updates I don't *need* to fix a specific problem).

The only mod I've considered is to install a pair of switches on each key (probably on the hammer-drive mechanics as they're easier to access) and run them to a module (arduino, etc, or even the guts of an old midi keyboard) in place of the keyboard. (pairs of switches are used to get the timing between them, which is used to calculate the velocity) Then I can get MIDI out from it and record what I play (preferably to an always-recording buffer inside the device so I don't have to deal with anything other than turning it on), and then edit out my many mistakes and use a synth piano to export a file I can upload a listenable version to my bandcamp page. Something like the Moog/Buchla Pianobar, but DIY and affordable ( https://www.midiboutique.com/ carries DIY parts to do much of this kind of thing, but is far too expensive for me).

Assuming your plugin responds to zero velocity notes, and assuming you can create a zero velocity note in the host, you'll need one for every note that has been played that might get stuck, at the point the stuck notes should have ended normally.

Not everyone does that (I don't). If something already has the features required for a user, they don't need to upgrade (which always has risks that something they use gets deprecated or broken), and they may choose not to upgrade regularly, or even ever, unless some feature they really want (or need) finally gets implemented the way they want/need it to be (which may never happen). Upgrade-itis is a problem with many people, but not everyone. That said--I agree with the rest of your post.

There's a place (in MIDI options?) to choose to record Sysex data or not. But if the sysex data is causing a problem, it should cause that same problem every time it is sent from the source device, not just when it's played back in a track. If you don't see that happening, I'd guess the sysex isn't causing the problem, but some other data that is not exported in a MIDI clip (i don't know what is and isn't).

And if that software / subscription is suddenly unavailable because of some factor (business decisions, corporate economic or technical disaster, etc), and your work is now trapped in it so that you cannot change anything anymore, export to other formats, etc? If your livelihood revolves around this work, you may be stuck wasting money and time recreating everything in some other software or hardware solution, or even lose clients / opportunities, etc. If it's just a hobby, well, it depends on how important that hobby is to you (for me this hobby is so important for my sanity (such as it is )that I can't risk such a loss; for most that's probably not the case). I expect that for most people it doesn't matter--they'd just move on to the next thing, and it's more important to them that they have the latest whatever than that they keep being able to use it. If the software continued to operate fully but simply didn't get updates or support, that'd be different, and acceptable (for me), but not if it changes functionality. This is why I won't use the current software (even though it has things I would love to use that would probably greatly help my workflow)--I see too many "activation problems"; once activated the software shouldn't require any further action or reactivation--they solved this issue with the original SONAR; once you have your codes they just always work. You're not stuck because of some server problem, network/internet issue, etc. Same thing for 3rd party plugins, etc.

None, if the software functions exactly the same either way. But if the subscription running out means the software no longer does exactly what it did before it ran out, then it's a very different thing, and they cannot be directly compared.

Which instruments? Some plugin coders did/do things in ways that don't respond to the normal method of turning off notes. by sending a note-off, or an all-notes-off command. There are some that ignore those, and instead only respond to a note-on with a velocity of zero, so to turn them off you (or the host software) has to send one of those for every possible note. My ancient version of SONAR can't do that, but CbB should be able to; there is probably a setting in there for the Panic Button to do this. There are also some plugins that "break" (all the RGC plugins I've got, like Z3TA / 2, etc) and get stuck notes all the time; in the ones with an arp I can toggle the arp off (or on) momentarily to stop it until the next time). I suspect but can't test that the second method above would also turn them off--but it is annoying that they don't just respond normally to note-off messages like they should. Since the problem only happens with the new version of Ozone, you should contact Izotope to let them know about it, since something they changed is causing it, and it might be a bug they can fix.

Do you mean: --something that alters the way other plugins work (I doubt this is possible) so they accept and process as mid/side instead of L/R? or --something that changes the signal from L/R into mid/side before it goes into the plugin (but still as a L/R signal since that's all the plugin is "wired" to accept)? or something else?

JellyBeanThePerfectlyNormalSchmoo doesn't care...

Thanks---but since she's actually an alien in a dog costume I don't really want to risk sending her back home to report.... Well, the trike is called the SB Cruiser because it was built to carry them...they're too big for any of the OTS bicycle trailers, so I built trailers first to carry them (one at a time) behind a regular bike, then later the bike version of that trike (CrazyBike2), then eventually built the trike to carry Tiny (the smallest of the ones I've had) so I wouldn't have to pull a trailer (which is inconvenient and can be dangerous on some of the roads around here that there aren't any alternate paths for). It's evolved a lot over the years, from something even more primitive than the one in the piano pic to what you see in the first pics. Some bad 70's scifi vehicles I *still* like better than the siburtruk: There were some concept cars I like the look of and i still want one of these if it comes with all the options and this one was still better than siburtruk OTOH, maybe it's better than the Citicar And I'd vote that it's better than this Thanks! Most everything I have is customized in some way, and what I make completely from scratch myself (like the trike) is unique because it's usually made out of some random junk I ended up with, using whatever I had laying around that happened to do the job I needed it to.

I'll poke around at it with VoxengoSPAN to see what's in there, and an EQ to roll stuff off and see what happens.

Do other sound files play correctly in VLC? Such as WAV sample files from any of your instruments, if you have any, or any of the built-in windows WAV sounds, etc. If they don't, then it's more likely the volume is simply turned down in the Windows volume control, or muted, or the default audio device is set to something not connected to speakers, etc.

If it pops in the same place on every audio track, then there is something happening at that spot *or* after that amount of time. What happens if you add a marker at that spot, then rewind to the beginning and insert some measures, selecting all tempos, events, automation, etc in the checkboxes, letting it shift everthing over, so that the spot *should* move if it's any data that's in the track(s) or buses? If the pop is still at the marker (which moves with the rest of the stuff), then it's caused by something in the data itself somewhere in a track or bus. If the pop is still at the original time, then it's external to the data and is happenign after a specific amount of time and is probably external to the program itself, a driver, hardware, OS, etc thing.

The computer can be frustrating; one thing I do to minimize that is never add anything new to it or mess with it's settings, so it always works the same. But still I sometimes just sit and play at this old '70s Kimball (shown here just after I hauled it home after picking it up free from TrashNothing some years back). It wasn't tuned well even before I got it, and the trip didn't help, so I've done a basic tuning (which took months, including learning how), and so now it just has "character".