Amberwolf

FWIW, if "Privazer" is a tool for secure erasing, using it means you cannot recover any files that are accidentally deleted. On any system where *any* file, *ever*, is important to you, I would never run such a utility, because any deletion of a file means forever losing that data after you run that kind of utility. To prevent that loss you'd have to ensure you copy all your files over to some other media that you never run that utility on, and that then kinda defeats the purpose of a secure erase tool since now you'd have to ensure you've not copied over any files you want deleted, etc. All I can really recommend given your present methods is to get an external backup drive and copy all your important files of any kind to it, then disconnect it from the computer and put it away. Then regularly get it out and reconnect it and copy all the files again, preferably to a whole new separate folder, so that you have *all* the different sets of backup files. It uses more space, but means less likelihood of data loss from a corrupt file. The "best" way to do that kind of backup is to use multiple separate backup drives, and rotate thru them. Say you have three drives; on week 1 you use drive 1, on week 2 you use drive 2, on week 3 you use drive 3, on week 4 you use drive 1, and so on. That means even a disaster where something really bad happens (say, lightning hits a powerline and destroys everything you have plugged into the wall), you still have the copies of the data on the drives that you have put away not connected to anything at that moment, even if you had one of the drives doing a backup during the instant the disaster happens. It still doesn't protect you from things like fires or floods that could destroy everything in the location; that you'd have to have offsite backups (either a harddisk over at a friends or a safety deposit box at a bank, or online cloud-based backups, etc). But if you're so worried about privacy intrusions that you're wiping data out, you probably wouldn't want to give copies of any of your data to anyone else, especially online.

At one time I had a TI SR-something desktop programmable calculator, given to me, and to the right person would be very valuable, but I could not even give it away; sadly it went to the dump with a bunch of other stuff I could not keep some years back. I do still have a couple slide rules though. (they're in the "media collection" along with stuff like a piece of core memory...) https://www.oldcalculatormuseum.com/tisr-60.html

Just for curiosity's sake, do the ones that don't stay the length you drew coincide with the end of a clip in that track?

Hmmm. In this post it's implied that you used one...which specific utility did you actually run that is referred to in that post? Knowing what it is might suggest a recovery option. Being very specific with the info in your replies to us will help us help you better.

Are you sure? Maybe that's not like one either.

You'd have to make sure that the track with the MIDI on it is set to use the hardware midi output that you have connected to the organ's midi input. Then you may need to choose a specific channel to send the data on, if the organ doesn't respond to "omni" input (all channels simultaneously). The organ's manual should tell you how it responds to midi, and/or how to change any settings it might have. Also make sure that the cable connected to the organ's midi input is labelled "out"; if you're connecting "in" to "in" it doesn't send anything. Note that many of the really cheap usb-midi cables don't work right (or at all), if they are just a usb cable going to a lighter-sized "box" that then has midi cables coming out of that. if it's a box with no built in cables that you connect with separate cables, it's probably good enough. There's a recent thread around here about issues with these, and some recommended ones, about a problem where only one note goes thru before silence happens. You can probably fix the organ's floppy-reading-problem by replacing the drive. It may use a standard 3.5" 1.44MB drive, or it might use one that's more specific (like I think my Ensoniq ASR does). There were also apple (macintosh) specific drives that are harder to find, but it's unlikely they used these since your floppies can be read by your laptop. The standard ones are easy to find in scrapped computers, cheap or free, if you look around in local thrift stores. As long as you do a bit of basic reading on how to do it for a typical computer, replacing them is usually very easy. Your device might be more complicated to open up to get to the drive, but probably not by much. Random ebay link to standard drive https://www.ebay.com/itm/403661605804?chn=ps a search for more https://www.ebay.com/sch/i.html?_from=R40&_trksid=p2334524.m570.l1313&_nkw=1.44MB++internal+Floppy+Drive+-laptop&_sacat=0&_odkw=1.44MB++internal+Floppy+Drive&_osacat=0

It should be referring to whatever plugin was being scanned at that time. If that isn't listed anywhere on screen, the message it gives may help figure it out, with some eliminations. In this case, since it's pointing to dspfx.com, it's probably referring to the old DSP-FX stuff that shipped with early SONAR versions. (I don't know if they still came with Platinum or not; I'm not sure DSPFX was still around by then).

If you haven't already, you could try putting it up on ebay, etc, for the lowest price it will allow, for "local pickup only" if you don't want to go thru shipping it (which I expect would be an expensive nightmare). Outside of that, your local goodwill/etc might be able to come pick it up. I see pianos of all sorts and in some awful conditions at my local gw's now and then. (some of them were over a century old, but unfortunately looked and sounded like it)

Does the cleanup utility have a log file that shows you which specific files were deleted? Do those match the missing files? If not, then it didn't delete them, and some other process or program or action has done so. If files have been deleted from the drive, there are recovery utilities that can locate and undelete them, but it's likely that parts of them have been overwritten by other data, a problem that grows worse the longer it has been since they were deleted. With wave files (audio) it's likely that even with missing chunks you can still use the portions that are still present, but you would have to recreate or rerecord any missing bits. Just be careful and read up on reviews of any utility software before you download, install, or use it. I've found over the years that while there are good ones, some of the utilities and "undelete" programs out there are not very good, some are not even real (just scamware to infect your computer with spyware/adware), and some are baitware, where they say they'll do some job but only do a scan to find things to fix but then charges you (more) to actually fix them. I don't have any lists of which ones are any good these days as I haven't done this sort of thing in a long while. If the files were corrupted originally, you could have some program running that interferes with file operations, or that auto-defragments a drive but poorly and doesn't properly keep track of all the file chunks, or an actual hardware problem with your drive (bad sectors, etc) that is causing data loss.

If the VSTs were the typical free type that don't have installers, and you just copied the DLL files into your VST folder when you "installed" them originally, you can copy your VST folder over to get them to the new ocmputer, along with each folder that any of them uses to store it's data, samples, etc, if they are not within the subfolders of the VST folder. There are varying locations the main VST folder could be, or you could have several of them. There is also usually a separate VST3 folder, and possibly a VST2 folder, and sometimes 32bit and 64bit folders. If they have installers / licensing / protections /etc., you're almost certainly going to have to reinstall each one. Some licensed stuff only gives you so many installs, or you have to deactivate it on one computer before you can reactivate it on a new one; those you'll have to check the documentation or the company that made it (if they're still around and still support it) should have the info. The settings and such for Cakewalk/SONAR/etc are probably within your C:\ProgramData folder and the specific username you login to under the C:\Users folder in the Local and/or Roaming folders, Appdata, etc. Copying these over will have different results with different programs. Some (few) will complain when installing them that the settings are already there and you need to uninstall the program first before reinstalling, some will inherit the settings correctly, and some will just overwrite all the existing settings with default values because it can see that the program wasn't actually installed, etc. Some will have other behaviors. I don't know of a list of which programs do which behaviors; it's a try-as-you-go experiment. The actual audio/MIDI/etc programs, soundcard drivers, etc., that you use will probably need to be installed one at a time. If the OS on both systems is the same, you might be able to find software used on corporate systems to create distribution discs that install the same stuff on every system, creating an image from the old system to install on the new one, but if there are significant hardware differences the OS may or may not boot up correctly to continue letting it install all the drivers in the new system, and anything with licenses that are hardware-dependent will also probably complain/not work/etc.

What driver do you have installed for the Saffire? Does Windows correctly see the card in Device Manager? Does Windows correctly see the card in Sound control panel?

OT: I don't have any input to the issue, but I love that you are using the Ensoniq CDR libraries in Dimension--this gives me hope that I can figure out how to do so myself, since there are numerous sounds I love on my ASR88 but wish I had in something directly in SONAR (other than just using SFZ, since I can't actually edit the sound to correct conversion issues). (at some point, somehow I got a bunch converted to GIG format, but I don't remember what I used, and I haven't had a way to use GIG files in ages now, but maybe I can find a way to make GIG into SFZ; I got some other GIGs into SF2's at some point).

Bandcamp.com is where I keep all my "finished" tracks, at http://amberwolf.bandcamp.combut I've used it for WIPs too; it easily lets you replace any part of a "track page" (sound file, artwork, etc) just by using the edit link on the track page. Soundclick.com is where I put up most WIPs until they're finished enough to stick on BC; it also lets you edit anything. The one thing that SC does that BC doesn't is allow you to use a default track artwork/icon if you don't specirfically upload one on each track. BC requires you specifically upload artwork at least 1400x1400 everytime you upload a track. You can use the same one each time, but it isn't done by default by BC unlike SC. If you're looking for people to just find / listen to anything, SC is not the place to do it. I often see a track I put up go to #1 or 2 on the whole site just from a single listen, so SC is obviously not visited very much. BC doesn't have ratings or charts like SC, so I haven't got a way to directly compare the two for that.

Possibly related: There used be (might still be) an issue that if you draw a note in TrackView's InlinePRV near the end of a clip, if the note is longer than the remainder of the clip, it will be cut off by the end of the clip. And if you draw a note outside the clip, it will "disappear" when you let go of the mouse button (but may still be in the clip if you unroll it). I don't recall if it affected the full PRV or not. IIRC turning off NonDestructive MIDI Editing makes these do the expected thing (of putting the note where it should be and as long as it should be), but it shouldn't be required for drawing notes (it should just work).

Have you removed or moved any files? (this might be covered in " There hasn't been any change in my setup" but just to be sure....)

Dunno how much of it is there, but https://web.archive.org/web/20240501000000*/https://forums.presonus.com/index.php

With VoxengoSPAN in each vocal bus I found that at the input to the chain there was some low end less than around -40db from about 150-200z on down. At the output of the fx chain there was less of this, around -48db or less. With my hearing as bad as it is I don't hear a difference between eqing that out with an HPF or not, so you'll have to tell me if you do when I get the new version uploaded and linked here (still poking at it). What I can hear a difference in: There's significant "content" peak in the 200-500hz range, mostly centered right in the middle in a typical bell curve, actually louder than the rest of the spectrum for most of the "harmony" Indian Chant vocals, and it greatly alters the vocals if I take that out, making them really thin. None of the EQs I have are able to notch just whatever might be causing muddiness out without taking out too much other stuff. ; I'll put a version up with this notched out to see if that is the band you're hearing.

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.