Amberwolf

Since you're not using Sonar or Next (nest?), what program are you using? What does it's manual say those codes mean? (we can't look it up because you didn't tell us which program, etc). What audio interface are you using? What driver are you using to run the audio interface? Which driver mode are you using? What latency is the program set to use with that driver? What resolution and bit depth are you recording and playing back at? What effects, if any, are you using on the tracks, in the project, etc? Are you doing input monitoring within the program to hear the recording realtime? Are you playing back other tracks while recording? Do they have effects on them? Do you have any high latency plugins requiring a lot of CPU? Etc.

Available for local pickup in Metrocenter area of Phoenix, AZ, USA. Free to good home, though I'll accept any money thrown my way for them. Piano is mostly tuned, but after you move it, it will need retuning. Comes with an unused tuning kit; there are free phone apps you can use to help you tune it. It's a Kimball 404P #T26204 probably from the late 1970s: Amberwolf's Music Studio Technical Stuff Piano is very heavy, over 400lbs, bring at least two strong people to get it into your large transportation device, or all your stubbornness; I won't really be able to help much. (I originally got it here by myself in a bicycle trailer built / rebuilt for the purpose, but I wouldn't recommend it The SB Cruiser : Amberwolf's 2WD Heavy Cargo Trike & Dog Carrier ). Upright electronic organ is much lighter, don't know the weight but one person can move it relatively easily. It has MIDI output, so can be used to control synths, etc on a computer or other MIDI capable hardware. I've not used the organ since getting back here into the house after the fire (it was a replacement for stuff lost in that fire so I could keep playing music). The piano I very rarely use and it's large and I could use the space for a workbench in my bedroom to work on wolfy-robot-project stuff instead. Piano when hauled home (hasn't changed since then, except for a bit of toothmark work on hte left front leg by either Peebs or the Schmoo when they were puppies, but that doesn't affect it's sound or structure. The organ is presently behind my brother's art stuff in the storage room, so I can't access it to get better pics. This shows the console and keys, the stuff on top is not part of it (though I'll sell the Yamaha TG33 in the middle if someone really wants it; I know they don't generally go cheap). I think it's the Discovery version, don't know the specific model. These are some pics from a Reverb.com page listing for what looks like the same model

Behind You Lie Many Unseen https://amberwolf.bandcamp.com/track/behind-you-lie-many-unseen Evolving cinematic track, 3:42 long. The Elven rock hard in the last minute. 04-25-25: 042425 000001 100034n -- First public version 04-27-25: 042425 000001 200063t -- timing and mix changes, and glitch fixes. 04-28-25: 042425 000001 200075v -- replaced awkward section and fixed tuning glitch 04-30-25: 042425 000001 200104z -- tweak intro percussion

Did the plugin update itself (or was it manually updated or changed) between the time it worked and the time it didn't? Did anything else on the system update itself (or was manually updated or changed) between the tiem it worked and the time it didn't?

you set each device to send on a diifferent channel, and the daw to receive on a correspondnig channel for teh orrespondnig track

Oh, also, when I've got the basics of a track laid down for a synth that gets stuck notes, I do the freeze as well. But then I clone the resulting audio track (not the midi part) to a new audio track including events and properties and effects, etc., then mute or archive the synth track. Then I can work with the rest of the project, and if I only need to do simple cutouts or volume changes on that synth's audio I can do that to the audio clip, and only unfreeze the synth to edit specific note changes, add controller data, bends, etc., then refreeze it. If I have certain edits already complete as audio edits, I can then mute the ranges of the new freeze that I've already done in the first one or that didn't change, and then mute all the ranges of the old freeze that changed in the new freeze. (or I'll even mute the MIDI clips in the ranges of the old freeze that don't change, so they don't even generate new audio). So that's one workaround for synths that can't be arsed to shut up.

For me, with synths like those made by RGC (Z3TA, etc) the problem is caused by the way the synth is designed to expect note-off events, vs the way SONAR sends them. SONAR sends note offs as regular notes with zero velocity, but some synths don't accept that as a note-off, and expect a real actual note-off message. THere are some other threads and posts about stuck notes that may have more details, but IIRC there is an option in newer versions of SONAR (and maybe CbB) that allows note offs to be sent in the other way, or maybe it was that the panic button can be set to send a note off message for every note rather than a global all-notes-off message (which some synths don't accept). If none of these things fix the issue for your synths, then you may need another way to send the note off messages or to stop the synth output. In my ancient SONAR I don't have the modern options (which is why I don't remember what they are ) , so for Z3TA note hangs, for instance, I can toggle the built-in arp on or off and back again, and it will stop all notes. But that has to be done in each instance, so I leave the UI open almost offscreen with just the arp button edge showing. (I could probably setup a remote control for that button but never tried). The thing that normally causes the stuck notes for me is that I stop playback before the end of the note on that synth. If I stop between notes, they don't get stuck.

04-22-25: 042025 000001 200049h -- added accents, emotionalized ending https://amberwolf.bandcamp.com/track/the-beaten-dog 04-22-25: 042025 000001 200054i -- added backing sounds 04-22-25: 042025 000001 200058j -- cleanup and timing

04-21-25: 042025 000001 200042g -- extended, clarified, enhanced, filled. https://amberwolf.bandcamp.com/track/the-beaten-dog

FWIW, there is a feature request in for this, and some discussion of possible implementations, including how an MFX might be able to do it if someone were to write one. (other than the bluecat) There is also another thread that has methods to actually do this listed (but I haven't tested them), starting on this page And there are other threads discussing it, some of which are in this search https://discuss.cakewalk.com/search/?&q=multiple midi&type=forums_topic&quick=1&search_and_or=and&search_in=titles&sortby=relevancy

04-21-25: 042025 000001 200030d -- corrected version https://amberwolf.bandcamp.com/track/the-beaten-dog Something went wrong somewhere with the previous version, and all sorts of bits got mixed up in where they should have played, so the previous version is garbage. I should've listened to the export before uploading it. Been fixing that, new much much better version now, (I listened to the export to make sure!) you can tell what's what now.

If they did that here in Phoenix all he would've found were some little mummies, explaining why his "radio" only rattled....

New one, with lyrics (spoken word), less than a minute long. The Beaten Dog https://amberwolf.bandcamp.com/track/the-beaten-dog Please...save me let me go this life is kinda hard why? my people...my people, they left me. Why? trust me--there's a reason: I'm a shadow... I'm free....which way do you think we should go? Not the lightest song in the world.

It would be nice if there was a screen that listed each plugin, synth, mfx, etc., along with which track or bus it's in or clip it's applied to, and which order they are in when several are in the same bin, and which preset was used (if any, and if not a list of settings values with an option to "create presets for all". That could be used to rebuild a project should it become corrupt, or to know what plugins were used in a project so they could be installed in a new system ahead of time (like you're doing) without having to reference the missing-plugin dialogs. The closest thing I know of to do this sort of thing is ProjectScope by Adam Czyk "czyky", which at least provides a list of fx used. http://forum.cakewalk.com/ProjectScope-helps-find-CWPs-and-keeps-them-organized-updated-to-Producer-Edition-m3218609.aspx?high=projectscope http://forum.cakewalk.com/ProjectScope-for-Sonar-Project-Files-CWPs-updated-to-support-new-Sonar-project-features-m3584169.aspx https://adamczyk.com/miscellaneous-files/88-projectscope-exe-for-cakewalk-project-files

If you remove the midi hardware, including all the driver software for it, from the PC's that do have midi hardware, do they then work? If not, then it isn't having hardware or not that causes the problem--it's something else. If it does work, then you'd have to find what setting in the program or tracks is different from the hardware to the no-hardware setup. The easiest way to do that is take screenshots of program settings and track settings of working vs not working, and then compare them.

Then it can't be a bus problem, because you aren't changing anything about the bus assignment or bus properties. If you would provide sufficient details we could probably help you figure out the issue.

What happens if you *don't* disable the MIDI hardware outs? What happens if you don't use Simple Instrument tracks, and just use regular separate synth and MIDI tracks?

That shouldn't matter. I have midi outs *and* use VST synths just fine. If you're having trouble only on those specific machines, something else is going on. What exactly are your complete MIDI settings for the program itself, on the machines that work, vs the machines that don't? (screenshots are best) What exactly are your complete project settings for machines that work, vs machines that don't? (screenshots are best) What exactly are your complete track (MIDI, Audio, and Synth) settings for machines that work, vs machines that don't? (screenshots are best)

What exactly does "insert it to a track" mean? Normally that phrase means to insert a plugin in the FX bin of a track, but doing that with a synth probably won't produce the result you want--synths normally have to have their own synth track to operate correctly as a synth. For certain synths designed for it, being inserted into the FX bin of an audio track may allow them to work as an effect, but may not be driven by MIDI.

Also make sure you didn't use track manager to hide some tracks that have VV clips in them. If you don't have a specific visual layout of clips in each track, you can also enable layers/lanes in each track and then "rebuild layers" on each track to force no clips to overlap with any others visually in the same lane/layer, making it much easier to see everything. I also vaguely recall a wierd thing I sometimes saw with VV clips (one of several reasons I stopped trying to use it very early on) where a clip could just randomly become a "sliver", that could not even be seen on the track, but selecting everything on the track would make a barely visible outline of the clip that I *could* see, and delete or use clip properties (alt-enter) to change it to a length I could see and work with.

Cronus / V-vocal was what really old SONAR versions used for manual hand-tuning of audio clips; Melodyne is currently used for that, AFAIK, but there's no way to automatically switch from one to the other. If you're going from an old version of SONAR in the old computer to a newer one in hte new computer, you'd have to bounce all the V-vocal clips in a project to plain audio with the old version if you want to keep the tuning changes you made to the clips. If you want to redo all those changes you could remove the v-vocal clip versions and revert to the original (muted) versions of those clips (usually hidden "underneath" the vvocal versions IIRC).

If regular notepad won't work, you can probably use https://www.flos-freeware.ch/notepad2.html

There are MFX that do this; I think you can do it with one of Variorum's; maybe this one There's at least one other thread around here about an MFX to do this.

Is your car an old orange Charger?

I've never really dived into mine for any of the sends, but when i found mine a few years ago at goodwill and started looking up information on it so I could find or build a power supply for it, some of what I read said that there were some combinations of send/return setups that would / could never be used together, and that you'd decide which one to use based on whether you needed it before or after some other part of the mixer (fader, etc), or if you were using it to send a specific mix or set of channels to a monitor for a specific player, etc. I don't remember enough of the routing specifics to be certain of this, but I think you can choose which aux you're sending to in each strip, or not send at all, to send to a specific fx box or a specific player monitor, etc. The manual describes the controls on each part of the mixer, but assumes you already know what that kind of control does. I only have very basic familiarity with mixers, so most of it I didn't follow very well. It also has a "schematic" showing how signals are internally routed from place to place, where they are buffered, switched, amplified, etc., but it's probably tough to follow if you aren't familiar with electronics schematics. (I had intended to experiment once I got it wired into the whole system, was going to use it to replace my ancient MOTU MM7s that I no longer had an easy way to control (ancient laptop with my touchscreen setup had died) and setup all my external hardware to be able to use my two rack fx (Alesis MV III and Lexicon something-or-other thrifstore find) and/or my ASR88's internal FX on the auxes / fx loops, then back into my GL8*24's rackbox....but then a bunch of bad stuff happened to some of my dogs, one after another, and I never got back to it. Since I haven't even turned the rack on with that stuff since then, I doubt I'll ever get back to using it. So if anyone needs a cheap mixer, or some ancient rack FX... ).