Amberwolf

Introducing Cap'n Maggie Carrington, "leader" of our reluctant heroes, and fixer-upper of their misadveturously acquired owies, from the Drywater, Mars series. https://amberwolf.bandcamp.com/track/capn-maggie-carrington-drywater-mars-part-8 Presently with some placeholder vocals from Artifact until I finish building the new versions.

Introducing Cap'n Maggie Carrington, "leader" of our reluctant heroes, and fixer-upper of their misadveturously acquired owies, from the Drywater, Mars series. https://amberwolf.bandcamp.com/track/capn-maggie-carrington-drywater-mars-part-8 Presently with some placeholder vocals from Artifact until I finish building the new versions.

Not sure what the picture showing BlueCat's Gain Suite for free in your Plugin Boutique account back in 2020 has to do with the described issues with Scaler...?

Thanks! I'll poke around with it and see what I can mangle with it.

If you didn't use bank/patch changes, and didn't save the preset separately from the project as an FXB or FXB file to manually load into the plugin, then the preset data is simply part of the project data that would be fed into the plugin itself directly and isn't user accessible. If the plugin isn't installed, and you just get the "missing plugin" dialog for it, the preset info is not sent anywhere becuse there's nowhere to send it. If the new version of the plugin is so badly designed that it doesn't understand or accept data intended for it's previous versions, then that data is "lost", in that there is nowhere for you to retrieve it from. To get that data back you'd have to install the old version of the plugin that the data was intended for/came from, and load the version of the project that still asked for it (hasn't yet been replaced by the new one). Then you could try saving the state as an FXP (preset) or FXB (bank) and then see if that data will still load into the new version of the plugin. My guess is it will not, because that's the same data Sonar would be sending it anyway so if it is not accepting it now it probably won't then either. At that point, you would have to manually recreate your preset by taking screenshots of all the controls in all the various parts of the plugin with the old version, and then try to figure out what those correspond to in the new version, and set those controls the same way. It will probably still not sound the same if they've really changed it that much to not accept the old data, though.

Perhaps I'm misunderstanding people's use cases for remote control and midi learn and even ACT, but: If you could't record the incoming control data onto the tracks, how would it be useful for automating things? If all you could do with it was do a realtime control, you could not use it to do anyting more than you could just do within the program or synth interface itself as a one-time change, and would not be very useful beyond avoiding opening the UI sections with the controls you're changing. Being able to automate the changes over time within a project, which is the most useful (to me and probably many or most others) application of external control of a parameter, requires being able to record them into the tracks so that they get played back to the controlled parameter during the project. Otherwise you have to remember all of your sequences of control manipulations and then manually do these over and over eveyr time you play back the project. You must also do them again while you realtime record the project out from the tracks to an audio recording, because you won't be able to ever fast bounce anything without that control data being automated inside the tracks themselves.

If I could just tell the computer what I want and have it do that....

That's about the same reaction I get from JellyBeanThePerfectlyNormalSchmoo when my brother says "the dog" in some phrase referring to her.... :lol:

ok, i think i understand now. (my brain doens't work like normal people's)

A friend in Utah has to ride a bicycle in traffic on roads with holes that he describes as worse than those of old bombed out runways.... I don't ahve a picture of what he actually rides thru, but apparently som of htem are pretty bad based on a google image search I gather that some time ago, Texas tried out converting poorly maintained paved roads to gravel instead of fixing them.... I used to live in farm country in Texas between DFW and Red River, not far off the interstate, and almost all our roads were gravel, even in (the very very small) town. Some of the holes and other road conditions were enough to break vehicles unless they just crawled along or sped really really fast (enough so that they could lose control), and once the schoolbus was broken (axle or driveshaft, I dont' remember as that was a loooong time ago but it was very loud and the adults were very angry) not far from where it picked me up. We used to have "suicide hill" a ways down the road from my house, where the white (limestone?) rock shelf the road crossed was too hard for the occasional road grading to do anything to, so the sharp drop off there just got steeper and steeper as the top of the shelf was graded down onto but the part past it would get graded away and washed / pushed away by traffic and weather, down into a "gulley", making a very short but very steep hill. The bus broke going over that shelf. At some other point I was going down that hill belwo the shelf on a bicycle and skidded out in the gravel trying to avoid a hole or something, and tore myseful up pretty good before sliding to a stop at the bottom. One also had to sometimes avoid large bigger-than-head-sized fossils (and other rocks) eroded out of the limestone, usually ammonites, that could end up in the roadbed (sometimes having been in the roadbed and then pulled out by traffic or the grader, leaving a giant hole), or be sticking up out in the middle of a plowed field.

Thats not in this thread so I still don't undestand this thread's first post? Shouldn't it be in that thread?

Um, what post? Yours is the first one in this thread, and it is from today (11-16-2025)...I'm confused.

I have learned not to even bother visiting channels that do that, same as forum posters that post something useful, and then delete it. I've added many videos from various people to my watch later to learn from when I find the time, only to end up with the message "x number of unavailable videos are hidden", or have a bookmark to a video only to go back and find "can't find this" or "this video was deleted by the user". I've also bookmarked many posts in many forums to go back and read, only to find they're deleted by the user once I get the chance to do so. Whenever I can see or figure out which user it was I "block" them or "ignore" them so I never have to waste time on them again. Now I have another user / channel to add to the list. It's a waste of any user's time to go find things to learn from, only to have them disappear so that when they go back to learn from them and find they're not there anymore. Any content creator that does this is worthless for this reason.

For systems that are fan cooled, that's a fairly common cause of failures, by causing the fan to fail or inlet grilles to clog up, decreasing cooling to the point where heat begins to damage things. I've seen it in many many computer systems (especially laptops). But most audio equipment is not fan cooled (because that's usually noisy enough to interfere with it's intended usage), so it's not a common cause of such equipment. In old stuff, especially a couple of decades or more, and especially that is often left on (even if not active) for long periods, it's more common for elecrolytic capacitors to degrade or fail outright. In stuff that gets thermally cycled frequently with a wide difference between cool and hot states, fractures in the solder (or even PCB traces) for PCB-heatsink-mounted parts or transformers directly mounted on PCBs (vs wired in from off-board) aren't uncommon, and tend to cause problems in the cold state that don't happen in the hot state.

Whenever you put it up I'll see if it will register and operate here (occasionally in testing things like this I've found something that works on a dev system has a dependency that didnt' get packaged with it during compile), then I can play with it and let you know of any issues (or feature requests if you accept those).