Amberwolf

Apparently you can ask BOS for it directly here: https://discord.com/channels/943190629826068500/1251269239768219649/1447233893320097822 But so far, you're not really missing anything special.

Then I would check to see what specific differences there are between the settings in each of those vs Sonar, regarding Audio and MIDI. Make a "chart" that lists all of the settings in each one relevant to those, anything that is in the "panel" or "tab" for those in each program, and then compare them to see what's different in the ones that work vs the one(s) that don't.

yeah, it's weird. ghosthack just has a "regular" advent calendar thingy, and you can still access them later. bos's is a strange way of doing it, with the buying a completley unknowikn thing at zero cost, and no access to doing that outside the time window. (though i think the download stays in your account permanently)

Click + on the cart. Checkout for zero payment. Invoice comes up with download link. Viola! Or in this case more like Vocoderish!

So far they've all worked for me (as have ghosthack's, though one of hte gh's is a deal price on a bundle rather than a free pack so i dind't get that one).

the link should take you to a product page where you add it to your cart at $0.00 then complete the "purchase" and it shows up in your downloads. I'ts possible that if you aren't logged in it might not work right (haven't tried).

So....why not do the same thing for MIDI clips, when not viewing the PRV or inline PRV, just clips? Wouldn't that help the UI load? I know there is (or at least used to be) the option to not display clip contents, and I suspect that would speed up UI stuff with bajillions of clips, but that isn't very useful for most operations.

Looks like they actually both exist for real, and the one that has a website is kinda funny http://www.majortomsair.com/ Repairs Your circuit’s dead, there’s something wrong! Can you hear me, Major Tom? We’re experienced, insured, and able to service equipment at your home or office. So whether it’s fried, frozen, or fizzling out, we’re here for you. Give us a call today! https://www.buzzfile.com/business/Ground-Control-Landscaping.And.Design,-Inc.-561-963-7548

Just curious, for the lazy before I go try to find enough info: --do the things in this bundle, especially the video editing software, require internet access, activations, random "validation checks", etc etc? Basically, I want to know if I can use them on an entirely offline computer system, and be able to just reinstall them without worries about the company being around in the future, etc. I cannot use a tool that requires internet access, because if something is ever wrong with the internet anywhere between me and...wherever, or the program somehow unsyncs itsefl from it's license management,it will stop me from doing my work. We all know this never happens, of course. But just in case, I require software that doesn't do this. I am embarking on a new creative process project, a Drywater Mars webisode series, and the tools in the bundle could help with that enough to be worth spending this small amount of money on them. But only if the companies providing them actually trust their users, and don't do what Bandlab products (and many other companies) do even for free software.

If you force the 34" to the same res as the 29", what happens?

But...it shouldn't have to be "got around". If they are allowing it to be got around they are allowing existing users to use it so they ought to just let existing users use it. Not have to dick around to get it.

True... if you don't have a compressor, limiter, compander, etc., that has that function, then if you put it in a bus and route your track to the bus, you can turn on waveform preview for that bus and also see the results.

If you are using mono clips, just use the snap function with only the landmark of audio zero crossings enabled, so your cuts or slipedits all end up on one. If your'e using stereo clips that rarely works out.

Normalizing something only raises the clip's highest peak to the normalized level. If you have many notes of different volumes within a single clip, it will not bring up the lower ones to the same level as the higher ones. You'd have to split all the notes into separate clips first, then normalize each one. To do this without splitting into separate clips per note, you need to use a compressor or compander (compressor/expander). One "easy" way to do it with these is if you have the old VX-64 that used to come with Sonar (maybe still does?) it has a number of good squashing presets you can modify to do what you want.

My brother's apple stuff has an eq on the output built into the OS. I don't know where he changes the settings for that, but there is almost certainly one built into yours, too, ifyou look in your audio settings or wherever else apple might have hidden that. This would help you flatten the output of the iphone and not have to do anyting to the audio before that.

Don't send them to a bus. Change the output of the track to that bus. (presumably right now they all go to yoru hardware out)

What is the process you are using unsuccessfully, step by step? This may help us help you figure out what's missing from your recipe.

My previous post says how to enter it with a key in my ancient version; you'd need to either test it or find it in your keybindings for your version. There is also a menu option somehwere but I don't know where that is in the modern version. Offset is what it says on the tin. It gives you a second version of the control (gain, volume, whatever) to provide you a way to offset the entire automation you've already set or created without having to alter the actual automation. For specifics on the modern version's offset mode you'll probably want to look up offset in the help.

It's not a jump, they just dropped the stage out from under.... Everybody else is wearing velcro shoes.

If you are using non-destructive midi editing, then every clip you split / cut duplicates the *entire* clip, but exposes only the part of the clip between the cuts. So if you make a lot of cuts, you get a lot of copies of the full data of the original clip. If you bounce all those clips (individually or together) you erase all the hidden data. If you never slip-edit stuff back into view, you could temporarily or permanently turn off NDME in your options, but doing this means that every slip-edit you do to a midi clip destroys the information you hide, not just hiding it. Audio clips are always nondestructive edits, so the same applies there. If you have a lot of clips with hidden data, you can make a project VERY slow to save. Frequent autosave can be hell.

FWIW, in any software, if a drag-lock is "touchy" and requires not moving in the direction the lock is supposed to prevent moving in, it's a useless "lock". The whole point of a lock is to ignore any moviement in the direction the lock locks in, so if it doesn't do that, it isn't working.

Not sure what the icon looks like now, but for me it's a keyboard icon near the top right of a plugin window frame. This allows you to to pass or deny keystrokes thru to SONAR while a plugin window is in focus. If it's pasing thru, you can get behavior you don't want or expect if you don't realize this.

Most likely at some point you changed to offset mode and upped the gain or volume output while there, without realzing it. Unless shortcuts have changed, if you hit O it changes to offset, and pressing it again brings you back to automatable controls view. (I think it would be nice to have a view that has both visible to keep track of this sort of thing easier; don't know if that's possible in modern Sonar). So it's easily possible to be, say, trying to rename a track, accidentlly not click on it right, type someting and end up accidentlaly triggering assorted shortcuts via the keys you pressed--and O is a common letter in English0 musical words at least (Vocals, Viola, Bowed, Orchestra, Toms, etc) so ti's very very easy to do this. (ask me how I know 😊 ). Then go change a control (volume, gain, whatever) somewhere, then later on rename *another* track and switch back to automated mode, all without ever realizing it's happened, utnil you run into something like this. Deleting the track fixes it, since it deletes the offset control value. Antoher thing that can cause it is clip gain envelopes, or an automation envelope for the main gain or volume that was later hidden to be able to see something else more clearly, and then forgotten about. Since the value of an automated control still shows on the control, you'd see this change...but not if you did the automation, and hten accidentally switched to offset mode--that version of hte control doesn't change with automation, so.... In offset mode, at least in my ancient version, there is a + sign in the controls that have that mode when you're viewing them. There is no + in them if you're in the automatable view, so it is easy to see which mode you're in if you remember to look for that (took me a while to learn to check).

If you turn the track(s) down, does the problem go away or lessen? If so, you're simply overloading the output whcih causes clipping. Beyond that, we'd need to know how you have the project and metronome setup, your bussing structure, audio driver info, et.c

Are you drawing the notes in and having them end up in the wrong place? Or do you have a clip that you are editing? If you are editing a clip, are the notes in it different than what you see in PRV? Are you using the song key map to tell it to change from the key that it was already in? Or something else? More specific details are necessary to find out if what you are seeing is normal or not, and if not, how you might correct it.