Amberwolf

A couple of decades ago, a friend's mother was shot in the head thru the wall of her home by a drive by shooter (actually a whole group of them in a vehicle). She lived for a while but never woke up. When they caught the shooters (some of them at least), turns out they went to the wrong place and decided to shoot it up anyway. 😠

MIDI doesn't make sound, it just tells something that does make sound which notes to play, how loud to play them, and how long to play them for and when to stop each note. (and a lot of other data but those are the ones you're concerned with at the moment). So you have to use a synth (software synth, softsynth, VST, etc., usually in one or more of the tracks of your project) to take that info and make the sounds you want with it. Some probably come with your version of Cakewalk; if not there are free ones you can use, depending on which specific sounds you want to hear. You can also use a hardware synth (keybaord, rack, etc) but those are rarely free and usually require other hardware to connect them to the computer (MIDI interface, etc). If you open the Synth Rack (by icon or menu), and insert a synth, the default options should open the synth window, and create you a track to put the MIDI into. Then you can use the synth window to choose a sound or sound set that will be played by the MIDI track. If the synth is "multitimbral", it can play several different sounds at once, each on one of the 16 different midi channels. In this case you can just set each song part (lead, bass, drum, etc) to the right channel for each sound as you set them up in the synth, and they can all be on the MIDI track(s) for that synth. If the synth is not MT, then it can only play one sound, and you'll have to use the synth rack to add as many synths as you need for each different part. (this is the usual way projects are done, as it makes a lot of things possible that aren't with a single synth doing it all). Then each song part's MIDI goes into the MIDI track for that synth.

If you're interested in finding the root cause, you might want to look at the MIDI driver list in Cakewalk, for all the ones that are checked (enabled). It might be that there are duplicate or broken drivers enabled, or a loopback (virtual midi port). In this case, if you disable all but the ones you are actually using, then you can continue to use the Omni input.

They're not useless, they hold the bits down in the drives so they don't fly off when it spins up. FWIW, the only "deal" I'd love to get ouf of stuff I've found on the many posted websites is Vocalisa on APD, which would be like $40 with the "rewards" they give you for reviewing stuff (even free things, which themselves can give you rewards)....but it requires the full version of Kontakt, and that's $300, which I can't swing or even justify saving for. I really wish they made a version for something like Decentsampler, or the Kontakt Player. Even if they just had the bare samples available with purchase, I could work with that. 💡 I did get a couple of the super-cheap sample-box deals from APD; for $8 there was almost certainly something usable in five+ "libraries", and indeed I did find some I've already used (the voices in TT # Nex Ool, some of the tympani in The Skaergaard Intrusion), and there are quite a few things in there I will end up using even if it's just single percussion hits out of loops, or sound snippets from other loops, etc. So it was worth the $8, saving me probably weeks or even months (over a long time period of making music) on creating those sounds some other way.

Even 1.6-2gb (vs 16-20gb) would be a tremendous amount compared to the installer size....

Not having used them, but given the installer for the whole pack is only a couple hundred MB, that sounds like some sort of file or folder corruption? Let us know what files you actually find in there.

The Skaergaard Intrusion https://amberwolf.bandcamp.com/track/the-skaergaard-intrusion 101424: 101424 000001 000030a -- first public version This one took about eight hours to get to the first public version, but it was nearly "done" after only three or four hours; at that point I had it's arrangement, sounds, etc all in place, and just did note editing for timing and mistakes playing, along with mix and fx tweaks. To speed the process, I did borrow some of my hand percussion that I'd created for Ookami no Kari no Yume, as well as the base blank track template with synths and fx and buses. More details for the description later; too tired to think right now. EDIT: replaced generic artwork with something more representative Only one partial listen so far (<10% of it played thru, guess they didn't like it at all since that's less than about 30 seconds). New version 101524: 101424 000001 000045s --mix edits, intro edit, add reinforcement parts in some sections, remove extraneous bits in various sections. Still working on it, as usual; building some string and wind instrument modulations, bends, etc. Some percussion transitions to work out. 101624: 101424 000001 000057w -- added further intro bars, fixed missing tymapni taiko etc track (didn't render anymore, reason unknown), numerous other edits. New version 101424 000001 000088E -- numerous mix changes (track envelopes), sound tweaks, added new percussion elements and removed certain perc notes here and there, added certain new sound elements under existing ones. Lots of envelopes for volume, pitch, etc., added or tweaked to mix all the elements in there. Most of the sound elements came from that QL RI cd set, using Vsampler to convert them into folders full of wave files (import into Vsampler, then use Windows Explorer to copy the temporary wave file folder elsewhere, then close vsampler without saving) that I can then drop into the project whereever needed, and use SONAR's assorted tools to pitch up or down or stretch. The sounds used so far are the Irish Low Whistle, the Gadulka, and the Duduk, as well as some Chinese Gong 34" to accent the few crashes in the MisFitKit(modified). I also added some tiny accents out of sounds I've collected over the years called "bigpot5" and "grater"1-4. I would kinda like to use the HurdyGurdy (I like the sound) but I have to read up on how to use it (there's a booklet with the QL cd set), then setup the wave files in a track to work correctly (since it has drones and whatever notes you play). I think I have another version of the HG that might be playable, but I have to look thru my off-system sounds and instruments, in the "i might need this someday" collection of "free stuff". I do that because Vsampler doesn't usually convert anything completely / correctly, and leaves assorted notes (keys) unplayable (silent) even though it has the sample there, and all the settings for that specific key are identical to other keys next to it that use the same sample and *do* play. The zones above the keys correctly play if clicked on, just the specific key(s) doesn't, either via MIDI or via the onscreen keyboard. Vsampler is very unintuitive and clunky to edit things in, so I don't ever try to fix such problems, I just use the wave files directly; it's a lot faster than trying to fix the instrument and then play in parts the way I want them. *** I still haven't located the right wind (flute-like) instrument for the percussive playing I want here and there. Probably going to have to get the one from the ASR88 into the computer. (I think it's on one of the "CDR" collections, so it shouldn't be too tough, just have to do an import process from that). ***building a basic instrument from scratch isn't nearly as hard as fixing a broken import / conversion, but it's pretty tedious, so I don't usually do that either, though I used to try a long time ago. 102524: 101424 000001 000097I -- numerous note changes, mostly in "bassline" track, some in accent tracks. Matched certain sections of bassline to "lead", small mix changes.

Just curious: If you are already familiar with it, and want to save money, why not just use the Sonar you already have? My ancient version still works just fine (even if it doesn't have a number of features the newer ones do) for the music I make, running on a Windows10 machine (it would probably run on 11 as well if my hardware/interface would). And as well, if you already have Reason, then there's no reason to not use it as well; whatever tasks a program is good at (or that you prefer the process in) is a good tool to keep around and use for. I also use Cooledit (even older than SONAR) and Audacity for editing tasks that SONAR isn't useful for or good at, and various other bits and bobs for conversions, etc.

Sound creation is entertaining and fun, and there are a bajillion ways to do it, so if you find that one way doesn't suit you or you don't have the things to do it (and can't find an affordable or free one) in one way, you can try out other ways that accomplish the same end, once you discover the essentials of how to do a particular thing. (that part may take some research, but there are a lot of resources, starting with the internet, and then there are physical books about sound design as well, that can be found at libraries in some cases). Some things are "obvious" once you start playing wiht the controls of synths and fx, and some you kinda have to learn what is actually happening with a specific sound to know how to recreate it...but it is possible to rediscover it without researching others' info if you spend enough time poking around at things (and you could discover a new process that's all your own for your own "sound" while you're at it). I started long ago (80s) with microphones and thrift-store-find reel-to-reel and cassette tape machines, then really cheap casio and yamaha "toy" keyboards, and because I was just doing what I could think of rather than researching anything, reinvented a bunch of processes that had already been known for decades :flushed face: . I started learning electronics and physically altering those cheap machines to do things they werent' intended for, and it was fun, but time-consuming (and sometimes disheartening when I would unfixably break something accidentally, and have to find a new (used) item to replace it. This century, when it started to get really cheap and easy to do stuff in the computer instead, I had even more fun because I could create sounds as presets, save those, experiment more, make chains of fx to do things that just one couldn't, and best of all everything can be saved separately and almost evertything has "undo" so if you make a mistake and didn't save as a new file yet you can go back to what you had before. These days it's even easier, since there are so many freebie synths and fx and sound manipulation programs, there's almost certainly already one around that already has a preset to do a specific thing you want to do.... I don't design all the sounds I use these days, because so many synths / etc come with good usable presets, but I hardly ever leave one exactly as-is, and "twiddle knobs" to see what i'll get sometimes when it isn't quite what I wanted (if I don't already know how that synth "works inside" to make the sound I want directly). For examples you can listen to stuff on http://amberwolf.bandcamp.com where most of the synth sounds I use are from or made on Z3TA2+ with assorted fx chains (mostly stuff that came with SONAR at one time or another), often automated to evolve the sounds over the time of the piece.

It *is* annoying. I use the Sonitus MBEQ, EQ, Reverb and Delay all the time (and the others now and then), at least one of them in every project (essentially since they came with SONAR the first time, perhaps a couple decades back). So I end up automating the band gains in the EQ, for instance, and the individual band bypasses in the MBEQ, the Mix in the reverb and the L & R Mix in the Delay (since the L/R link retardedly only affects the sliders and not external automation you have to use two separate envelopes to do it). In some cases it is easier to have two separate tracks (or buses) with the fx in only one, and either have clips that need fx in appropriate places in each one, or use automation on a track to send or not send to one or the other bus, etc. Or use per-clip fx bins for certain things, though I dislike doing that as it's very difficult to remember which ones have them and I can't automate those with in-track automation that I can copy and paste around. (a process which is difficult enough as it is, as is drawing in the envelopes to start with; though I'm sure that's improved since my version was created). Would save significant time if there didn't have to be workarounds like these. FWIW, I've had this issue with numerous plugins (and synths); almost nothing I have ever used has *all* the parameters I require to be automatable; it's almost always something obviously needing to be (like a bypass, or a mix, etc). My opinion is that if it has a controllable element, it should be automatable, *and* it should correctly expose the value ranges for the automation to the host, so the host correctly labels both the envelope itself, and the values displayed in tooltips/etc (rather than a name that's different than what the onscreen control shows, and values or units that are not related to those the control itself uses).

Sorry for the necropost, but seeing the artwork in the thread, I felt these belonged here (if they belong anywhere ). They were created in an attempt to make an avatar for use in various places; none of them are really what I was after, though, since Google's AI Test Kitchen ImageFX frequently ignores specifics in a user's input description, and is very inconsistent in "understanding" various terms.

Just a data point; probably not relevant: In Ookami no Kari no Yume I use the Radius (Mix Advanced, IIRC) stretching via Ctrl-drag-clipedge on most of the many wolf-sounds within it, some of them by at least as much as 154% longer, or 75% shorter (to help their timing line up better musically), with no significant audible artifacts. (if soloed, I can hear some tiny differences here and there from the unstretched versions, but in the mix it's inaudible, and no one who hadn't heard the originals would likely be able to hear these). Most of the clips are less than a second long, some are a few seconds, and some are as much as nearly half a minute. I don't have the other algorithm available in my version of SONAR, so don't know what results I'd get with it. I think I tried all of the available Radius options in the AudioSnap dialog with Mix Advanced giving the best results (not that there was much difference that I recall).

.

Do you mean you haven't had access to the presets, or access to the plugins? If the former, I can export the presets as a file you may be able to import via the Preset Manager within the Sonitus plugins. If the latter, it could be that the plugins are locked to the version of Sonar that they were installed with (on my system they work with all the SONAR versions I have had, but I had not tried them with CbB back when I tried to use it on the system some time back (had to remove CbB because of problems it caused with the rest of my setup and have never tried it again on here), so I don't know if they can be used in CbB.

Thanks for listening and replying! The vocal part was added after the percussion (and almost all the rest of the song except the distortion guitar sounding bits) was created. I didn't really have a specific intent other than to add the dreamy vocal sound to it, and to experiment with the new vocal samples I had gotten, and try some stuff with Perfectspace I hadn't done before...but it turned out to work with the rest of the music. Sometimes my experimental additions don't work and I leave them out, or move them to an entirely new project and start out with *just* the new stuff, and begin adding things to *that* to make a new sonic sculpture. Most of my stuff tends to be commented as something that would be the background of a movie scene or similar, so I call / tag them "MotionPictureScenes" most of the time. There's one on my bandcamp page called Patterns of Behavior with the subtitle "End Titles" because I was told it sounded like a track that would play during the end titles of a movie.

Having lived in farm country....better see than smell. Or step in.

What does "simple and round theme" mean? A visual theme for a specific program (presumably CbB)? A musical theme? ?? If a visual theme, are you looking for a specific color set, or other specific qualities?

I usually have several music projects going at any particular time. If I get stalled on one, I go to another. Often the resulting process stimulates a thought on how or what to do with the stalled one. Or I just flip the lid up on the piano and start noodling, or pull a guitar down and noodle on that. If I'm stalled on all of them, I go to one of my many other "hobbies" (learning robotics / coding, ebikes, cgi artwork, 3d printing, learning about astronomy / astrophysics and wolves (and many other things (often via random internet walks), but especially those), metalwork, electronics, sound creation (sometimes used musically, sometimes not), "gardening" / yardwork, playing with the dog(s), sewing and leathercraft, helping people with various problems (usually online), reading, etc., etc.). (I also use all these hobbies to fill the time when I can't sleep, which is most of the time, when I am not working the dayjob)

Some thoughts: If you're not posting the project itself, can you at least show us what is in the audio fx bin for a specific track and all of the busses it passes thru on the way to the audio interface? Or, disable all audio fx in the chain, then solo that track and play it. Then render it with fx still disabled, and compare. That will eliminate all the audio fx as a possible cause. (there is an option during the render to not use the fx, but this doesn't change how it's played back, so it's not useful for this comparison). I don't know why an fx would be different during render (realtime or fast bounce) than playback, but if it is, it could be causing this problem. There are synths that have different options for render vs playback; I don't know if any fx do (other than the dialogs you have already found, which are probably not from the fx themselves since they are all identical and probably wouldn't be if they were from the fx manufacturers). Note that even with that menu you've already found, there could be other (manufacturer) settings for this within the actual synth or fx for render vs playback (for instance, Z3TA+2 has such a setting for Realtime Quality and another for Offline Quality within it's Options menu), and if so, you may need to check inside the settings of every synth / instrument and fx to be sure they are set the same to get identical results...but even if they are different settings, you should not have a significant difference in the audio output; they usually only affect the quality of the render, and the difference in sound is usually slight, and does not normally have any volume differences). If it's not already been done, another test is to route one track directly to your audio output instead of to any bus, disable it's fx bin, solo that track, and compare direct playback to a render. (this eliminates any fx bin or bus issue) Another test is to create a blank test project, and copy/paste one track from your existing project to it (and do any synth setup necessary to make it the same as the existing project), and do the comparison within the test project. (this eliminates all of the busses and tracks other than the one copied). It's unlikely that anything above has to do with the problem you're having, but it's worth checking. FWIW, the only times I have ever had a project sound significantly different in render vs playback was when I had something unchecked in the included stuff during the render, but your latest screenshot eliminates that. The only other sound differences I've encountered were from the render settings within a synth, but these were all subtle differences, nothing like what you're experiencing.

During my last collaboration, the guitar track file sent to me had to be manipulated a bit to get it into SONAR, and it didn't lineup with anything. After some processing I got it to the correct tempo/timing, but hadn't yet found the lineup points (it was an improv track to the song I'd already nearly completed otherwise), so when I went ahead and listened to it to figure out where it should start, I found a few possible spots, and it ended up working out better with a different start point, and with some parts cut and shifted around from there, too. If you're curious it's Convocation of Lies over on http://amberwolf.bandcamp.com ; the Lauscho version in the Lies, Truth, and Assorted Inconveniences album has the guitar track, and there are at least a couple earlier versions on the page that don't have the collab guitar track in there (just the original bits I'd played in).

The options below should be available within modern Sonar, but I don't know exactly which dialog they are in. Just to be sure you know, excluding the MIDI device wont' stop it from accessing the audio portions of the device. The MIDi stuff doesn't affect the audio sample rate, only the audio device(s). If you want to prevent an audio device from being accessed at all, you might be able to do that by disabling it in the Windows Device Manager. If not, you should be able to uncheck the audio device from the list of devices in the Audio drivers within Sonar. If all you want to do is keep it from accessing or listing the MIDI portion, then let it add that, then in Midi Options / Devices, uncheck that device's in and out, and it won't be in any of the lists of ports that tracks can access. But it won't stop the audio portion of the device from being accessed, and it will probably prevent you from using MIDI to control the device. So doing what yoru thread title suggests is likely the opposite of what you want to do. I suspect you will get better answers by changing the word in the title of your thread from MIDI to Audio.

Ok. I'll be sure not to reply to you in the future, to avoid causing you problems.

Do you mean Trim? **** If so, you can use Widget Tab Managment to turn that on in the Custom tab view (or make your own tab, or use any of the tabs except "All"). Right click in the empty space below your track strips, and WTM is in the menu there. (mgiht also be elsewhere). **** I don't have any track controls for Gain in my ancient SONAR version, just Trim and Volume for audio or synth tracks. I don't know what's available in modern versions.

I decided to delete it without installing when I started getting emails about free shipping for "my new mk8". First I just went to unsubscribe, until it showed in my prefs that I should get emails about my new Mk8, which I don't have, didn't and wouldn't and couldn't order. A company that can't keep their account info straight, and/or have deceptive info there, etc., isn't one I want to deal with.

At least in my ancient SONAR version, the same option exists in the track view PRV editing options in each MIDI track. In my version it's in the Show Hide Midi Events dropdown button with the little note and the "bar graph".