Amberwolf

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

FWIW, a worn out keyboard with dodgy spacebar that "sticks" a little bit can cause multiple spacebar keystrokes to be sent sometimes or everytime the spacebar is pressed. That can be tested in a simple text editor like notepad. (not a complex one with autocorrect/etc as those may mask this issue). The spacebar is physically built badly on many keyboards, with support only at the switch itself on them, with insufficient spring return on the ends, so a press anywhere other than the center above the switch causes excessive wear and then drag during return. Even really good keyboards still wear out this way eventually, though you may wear many of the key faces off first.

FWIW, a couple decades back I used to do 3D modelling / animation with Lightwave3D, and had numerous wierd issues with Nvidia drivers, except for their WHQL versions, which are probably equivalent to the "studio" version they have today. Some of the "gaming" versions they had did a better job at realtime 3D rendering for previews and such, but they caused so many wierd problems (most of them not apparently related to graphics!) that I stopped using anything other than their WHQL, and once I had a working version I then never updated it afterwards, since working is working and therefore no reason to change it (because changing it then risked me not being able to work on things and instead waste more hours and hours troubleshooting and fixing things).

Are you in offset mode? This shows a (+) on the controls in my ancient version, not sure if they kept the symbol in the later versions. In my version O toggles this mode on / off. (fwiw, this topic recently came up over here, too: https://discuss.cakewalk.com/topic/14351-automation-not-working/page/2/#comment-592719 )

Or you happen to be working on some time-critical project and your internet provider happens to go down...or something between you and them gets DDOSed and no connection can be made to their servers thru no fault of either of you. Still keeps you from doing your work (and if it's a paid thing, could lose you a client).

In the options for Keybindings, you can add midi control over functions. Once in the Keybindings dialog, change from "computer" to "midi" and then select and bind the functions you want to the notes you want. If you want to also use the keyboard to play those notes from without operating the functions, there's a checkbox to enable ro disable the control function as needed.

Thanks for peeking anyway. FWIW, audiosnap is a nifty way to rearrange the timing of a clip, even if you only do it manually. For instance, several of the clips I used in the song have the pattern I wanted, but don't fit the timing of the rest of the piece where I need them. So I put it where the first or other main notes or sounds line up with the other tracks, and then enable audiosnap on that clip, and turn on the markers at 'all resolutions". Then I can grab the markers for the sounds that don't line up and just drag them until they do, and "magically" it now fits the rest of the piece. Some of the clips also had wrong notes, so I then render the AS clip and then slice that up into separate notes wherever it's wrong, and use the clip properties dialog to change the pitch as needed. Doing all this to a clip where it stands alone can leave obvious artifacts, but within a mix like this most people wouldn't even notice. I usually end up rendering the AS clips at some point, but for the ones that are messed up, I hadn't reached that point yet. What's worse...somehow, the problems are *retroactive*, meaning that *all* versions of the project have the problem with those clips....and I can't imagine how that is possible.

To show the difference i've uploaded the previoius working version (which doesn't have the played in guitar bit at the end) over at soundclick here: 040125 000001 100042J -- pre-audiosnap-broken-version, without timing problems. https://soundclick.com/share.cfm?id=14987155 The broken version is still on bandcamp here; https://amberwolf.bandcamp.com/track/the-next-breath The most obvious place to hear the differences is in the first several seconds after the piano break in the middle, starting around 1:08 or so.

I'ts more likely that my listening environment and equipment just doesn't let me hear the low low lows. There are I think two synth notes that are prtty deep, maybe they have excessive lows (they sound nice here, but I don't have a useful sub). I'll have to see what voxengo span shows, or a spectrum view in audacity or something. I wish I could play on hte guitar what i hear in my head for the continuation of the last few measures; i'll have to build it in midi driving a vst thru an amp sim, one problem i just noted when i opened the file jus tnow to look at those couple of deep bass synth notes and saw the AS clips screwed up in this latest version--something has gone wrong with every clip i used audiosnap on--it's not like they're unedited, but they're not playing correctly anymore, and they all look screwed up on screen. rebuilding the wave form picturs doesn't fix it; so i have to play with it to figure out what is wrong. Or go back to hte next older version that didn't have this problem..... wierd thing is that there was no problem at all before i rendered out the whole thing as a wave file to post up on bandcamp, but during the rendering process something broke, because a bunch of stuff is now off-time with each other because of the AS clip issues. I've never seen this problem before....

Well, only you would know that the recording isn't finished--the program has no way to know that, so it cannot be crashing because of that. Intermittent crashes for me are almost always plugins. They may not even be in the audio or MIDI path that's being worked on, and they may actually be disabled in the FX bin, but just being in the project one that has issues can cause problems. Eliminating plugins one by one by removing them entirely from a completely separate copy of your project (so it doesn't affect your actual project), and retesting after each removal until the problem stops happening would show you which plugin it is, if it is one.

new version 040125 000001 100053l added at bandcamp link

I was being facetious....trying to be silly

wink wink nudge nudge say no more?

The Next Breath https://amberwolf.bandcamp.com/track/the-next-breath is a short (presently 1m49s) energetic 140bpm experiment currently using entirely wave sounds, some loops, some single hits, most chopped up and pitched, stretched, some mutilated, etc. Mostly from Ghosthack, BigEDM, BlackOctopus, FunctionLoops (most of which prohibit me naming individual contributors for whatever wierd reason, so just giving the company sources). Once I can figure out how to play the bits I want to play in on the real guitar I'll add those, sort of a not exactly lead, and some synth and piano bits played in via keyboard (or drawn in as MIDI if I can't end up playing them right), it'll be a little different, but probably not by much. Eventually there may be an extended version...but this presetnly is already extended to double it's original length. Version list with changes, edited as needed: 04-06-25: 040125 000001 100027f -- First Public Version 04-07-25: 040125 000001 100042j -- detail edits, some mix changes, added further intro sounds 04-08-25: 040125 000001 100053l -- more detail edits, added a couple of live guitar bits (one near beginning, one at end).. More mix changes. Current version always at https://amberwolf.bandcamp.com/track/the-next-breath original version still at https://soundclick.com/share.cfm?id=14984630 for comparison if desired

Just in case: In my ancient SONAR the disable control is only available on the actual MIDI track controls (including inspector view of those controls), not on a synth's track controls. I don't use the combined synth/midi tracks so I don't know how they appear there. (and I don't have the modern Sonar to compare with).

If all audio ends up this way, not just the guitars, there is something in your audio monitoring path causing the problem. This could be a ground on your monitor audio cables, or a plugin or console setting within CbB, or in the audio interface settings or cabling, or if you use an external mixer it could be something there. If it is only on the guitar tracks, then it has to be something common to all the projects with the problem, which almost certainly has to be a plugin on those tracks.

Brownouts can happen anywhere that has sufficient loading on the grid. It used to happen here in Phoenix back in the 80s fairly often, then whatever SRP and APS did then fixed most of it, and we only had it happen a little in the early 90s. After that, brownouts virtually never happened until the last few years when it has happened a few times in the hotter weeks of summer each year, with a few complete power failures as well (oddly those almost always happen late at night when there is much less load on the grid). These days I use a laptop so none of that loses any of my work, since it kinda has it's own built in UPS but a friend of mine a few miles away had power conditioners installed in his condo because he didn't want to risk damage to expensive A/V equipment and bigscreen TV and computer, and UPSes on everything important so no data loss (even on hte DVRs) happens. Some people I know from california (don't know exactly where, but more than one area) have had numerous brownouts over the last several years, mostly in summer, worst when there have also been "rolling blackouts".

I wish I knew the answer...but I'm just stopping in to thank you for the original patch way back when.

That last issue sounds like a MIDI hardware driver fault? Which interface is it? Are there any other MIDI drivers installed? (including loopbacks)