Amberwolf

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. EDIT 060925: added cover art

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... ).

I'd strongly recommend asking them exactly what they want and in what format. No point in wasting time doing a bunch of work exporting/etc only to have to redo it all again to match their needs. FWIW, if you are exporting each track as a complete full-length wave file there's no need to bounce the clips first. Just select the track for the full time range of the song, and export that single track. You can choose during export to do it with or without track fx.

Are you sending the MIDI on channel 10? If not, try that; it's the "roland" channel for drums (yamaha may use 16 instead). Some drum things don't respond to any other channel than the "drum" channel.

FWIW, having seen this thread ongoing the last day or so, it reminded me of track templates (which I don't normally use), as a way to save time rebuilding a project that has somehow become damaged https://discuss.cakewalk.com/topic/84580-the-next-breath-energetic-short/?do=findComment&comment=592402 and had to start over with a new project file, copying and pasting all the data. So because this thread reminded me of them I exported track templates from the broken file (which included the bussing, fx, routing, etc, thankfully), but as you note none of the automation went with them (I'm not using a modern version, so if it's supposed to work now it probably wasn't a feature then). Still saved me many hours of work. The data including automation I copy/pasted, but had to reassign all the envelopes (other than track volume) as they all became orphaned, but that was all minor work of a few hours compared to what it would've been to rebuilding the whole thing manually. So, thanks for this thread, even if it's for a totally different reason than it was for.

Bandcamp now has the repaired version 040125 000001 200042j-000021. https://amberwolf.bandcamp.com/track/the-next-breath All the automation *seems* to be the same and working, had ot fix a bunch of clip positions, lengths, fades, and some of the stretched audio that showed the waveform in the correct place but played a different segment of the clip. Had to unstretch, reposition, and restretch each one. Rendered them all out afterr that. Just...totally wierd that all these projects could get damaged *after* being saved, and they are all damaged the same way so it is not random file damage from a drive or filesystem issue, etc. And it's not just the audiosnap clips, it's the timestretched ones too, and clip fades in or out. Not all of the non-AS clips were damaged, just some of their edits, but every failure was time-related, position of the edit within the clip (where it showed visually in the correct place but rendering it or playing it back made it obvious it was not time aligned, and I could not find a consistent offset either. The pitch-shifted clips werent' altered, nro were jsut plain slip-edited clips or looped clips. For reference, the broken version is on sounclick here https://soundclick.com/share.cfm?id=14989281 and the just prior to broken version is on soundclick here https://soundclick.com/share.cfm?id=14987155

Because of the recent thread about track templates, it occured to me to use those to save the track and bus states, routings, fx, etc to save a huge amount of time, so I exported every track as a template, then inserted those into the new blank file, then copied all the content from the broken version and pasted into the new file, saving the new file as a new version at each step (just in case, as always). There is a few hundred kb difference between the "broken" version and the new copy/pasted file version, with the new one being smaller at around 1736kb, and teh brokne one at around 2367kb. So there is data not copied over that might be accumulated garbage or errors in the file. I still have to check all the track and clip automation, etc., but it sounds at least roughly the same so it's probably all there. Once that's verified and/or fixed, then I just have to redo the audiosnap stuff.

Well, apparently Audiosnap isn't actually "broken" in SONAR itself, as I can redo the AS on a clip and make it work like before, but all of the AS's in all versions of this project are corrupted. The most common visual symptom is that the entire clip contents visually appear to be in the first half of the clip, with a blank line after that, and AS markers still showing where they should be but not actually working. Audibly the clip contents are full length, and *are* modified by the AS but not by where the AS markers actually are. Resetting things in a clip don't fix it, but if I turn off AS on a clip, then bounce it to a new clip and turn AS on I can rebuild the AS markers as it was before. So I will jsut have to rebuild each clip. Gonna take a while, figuring out what I had done before and redoing it, from the versions of the complete track I'd rendered out previously. And from now on I'll just have to render out every AS clip at every save point to prevent this issue. If I have to retweak the clip I'll just then turn AS back on and do that, then rerender, regardless of what that eventualy does to the audio quality. I still have no idea what could have allowed it to corrupt the previously-saved versions of the files that have not been altered or resaved since originally saving them. However....I *have* been reusing the same project over and over again for a long time now, as I learn more doing this type of music / mixing, just deleteing all the track and bus content / automation but leaving all the fx, routing, tracks, busses, etc. Maybe something has become corrupt in the file itself. So I think I'm going to copy/paste everything from this file to a new file, then manually rebuild the routing/fx/etc., so it's probably going to take even longer to get back to work on this one...but it should eliminate a damaged file as a source of issues.

If it's the driver, then if there was ever a time when it did work without this issue, reverting to that version should correct the problem. (reverting is a lot easier these days than back in Win2k) If reverting isn't possible, you might have to manually uninstall the current driver and manually install older ones until the problem doesn't occur. Sometimes the problem can be a shared file that doesn't get replaced with an older version when reverting, and that is a PITA to figure out and fix. I have no idea what they're like these days, or if they even make video cards useful for this stuff now, but Matrox had the best most stable drivers for their cards back then, and I used one of those before I got the Nvidia (and would've kept using it if it had supported the stuff I needed in the realtime previews, it did a much better job...I still used it in the music machine).