Robert Bone

I have a drum map for AD2, that Noel put out there, that includes notes mapped for cymbals and there are those for choke on Cymbals 1, 2, 3. I have not tried them, but they are in the map. http://www.noelborthwick.com/cakewalk/2015/02/06/drum-maps-ad2-in-sonar/ Bob Bone

I downloaded the demo - which seems to operate for like 15 or 20 minutes, so I will try to work through all of their combi sounds. Can you please confirm that these 'Moss sounds' you referred to, are Combi sounds? Or, are they basic presets (not Combi)? Bob Bone

Howdy - I happened to see that Korg has gotten around to recently releasing a soft-synth recreation of their Triton keyboard, and I am trying to understand its included sounds. I see from the doc, that it comes with a bunch of expansion packs, but what is not clear to me (never having owned the actual original keyboard), if the collection of sounds that comes with the new soft-synth version have all of the sounds from their Triton Extreme keyboard. I am asking for a friend of mine, a fellow keyboard player, who happens to own and still use an original Triton Extreme keyboard, and he is potentially interest in buying this new software recreation, to use live, because the original keyboard weighs about a billion pounds, but he is concerned about whether or not the software version has all of the "Combi" sounds that came with the Triton Extreme keyboard. He is a bit leery of dropping $249 on the software version, if it doesn't have the Combi sounds from the Extreme included, because those are the sounds he would be interested in. I looked at a couple of his combi sounds (he sent me phone pics of the various parts of 2 of his combi sounds from his keyboard's display window, which show all of the effects and internal routing that give those sounds the rich depth that they have, and I had thought perhaps I could create equivalent sounds using Kontakt instruments and applying similar effects, etc.... to save him from spending the $249, but it seems like a bunch of work for me to do that, SO I thought I would ask here - if anyone knows if the current sounds included with the new Korg software recreation of its original Triton (with its included expansion packs), would then also have the various combi sounds from the Triton Extreme - and if so, that then might justify my recommending he spend the $249 and pick it up, for live use. Sorry for the long post - trickier to explain than perhaps necessary, I need some coffee and am pretty sleepy. THANKS to anyone who might know the answer to the above. Bob Bone

Can you please explain what it was that fixed your issues with this? (maybe I missed you posting it earlier). That way, whatever fixed it for your system, might help someone else out, in the future - should they too have your issue with it. Thanks, Bob Bone

Yup

There is an ongoing issue that I have, because the midi devices and their USB ports got modified, GRRRRR to the friend that accidentally did that to my desktop computer. Anyways, any existing project now contineus to 'see' the midi controller, however absolutely no midi activity is recognized/detected by CbB. The workaround I have been performing is to: 1) In the open project, remove that midi controller in Preferences - Midi Devices, and click Apply, then Save project. then close the project 2) Re-open the project, add the midi controller back in Preferences - Midi Devices, click Apply, then Save the project again. I kind of lumped several steps above, into each numbered steps, just because I look at those logically in that manner. Hopefuly, that won't confuse anyone. SOO - the thing with the above, is that I keep having to do the above steps, and I have not figured out a way to have one final 'fix' to permanently correct this REALLY annoying scenario of having no midi activity detected for my midi controller. On top of the original issue because one midi device moved to a different port, and it wasn't even my midi controller that moved ports - it was actually the audio interface, but it still resulted in Windows remapping the association between devices and ports - so BESIDES this, my desktop has no internal DVD/optical drive - because of the case design, so anytime I have to plug in the DVD drive, that too causes the midi device mapping to associated USB ports to change, and it too causes this issue all over again. This mapping to ports issue has gone on since at LEAST as far back as Sonar 8, and most folks I know zealously guard, and even map out, the USB ports each midi device is plugged into. Can't this generic NIGHTMARE get a permanent fix or at least a reliable set of steps that only need be run ONCE, when ports and device mapping gets altered? Please? Bob Bone

I absolutely LOVE my WA-47. I bought a $9,000 Sony mic for my son, and personally like the performance of the WA-47 just as much. Different mics 'fit' different vocalists subjectively better than others, and I am quite happy with the WA-47. Bob Bone

I used to have a Reaktor 5 patch that would play fine, 1st time, then would be either a half or whole step lower, thereafter. Turnded out that the specific patch tied pitch to the mod wheel, and when the default Zero All Controllers would get triggered after playback, it lowered the pitch. I cannot recall if I simply turned off the Zero All Controllers parameter in Sonar (this was prior to CbB though it still works the same), or if I modified that patch to sever its tie of the mod wheel to pitch,. Anyways, just something you could check, by going into CbB Preferences, and turn off the Zero All Controllers parameter, which is under Preferences > Project > MIDI - just remove the check from the box to the left of where it says: "Zero Controllers When Play Stops", and then click Apply. If you do the above after freshly loading the instrument with the pitch issue, and if this is what has been causing these issues for you, then repeated playbacks should then leave the pitch alone. Bob Bone

Can you try loading VIP into a new project? Also, does it have a VST3 and a VST2 version? If so, and you were using the VST3 version - what happens if you use the VST2 version instead? Bob Bone

Are you referring to the Akai VIP software? Bob Bone

I believe it to generally be best to avoid hibernation when running CbB, or any DAW, because of the hit or miss failure by some audio interface brands/models to properly come back to life, which as was pointed out earlier, is something specific to the hardware and/or associated drivers for those audio interfaces, and not anything that Cakewalk can control. I don't do much tweaking of anything in Windows 10, (or for the computer) for prepping when using a given computer for running streaming audio applications, such as Cakewalk. I pretty much do only the following: 1) Make sure to store sample libraries on SSD drives that are not the boot drive (not the "C" drive) 2) I modify Cakewalk Preferences, so that most content is moved off to a non-boot drive, as well. I do this for all of the folders under Folder Locations, except for those folders that by default are stored in the AppData folder on the boot drive. Please note that in addition to the folder locations under Edit > Preferences > File > Folder Locations, there are a couple more folder paths to modify, under Edit > Preferences > File > Audio Data - and those folders are: Global Audio and Picture Folders (Audio Data and Picture Cache). 3) I whitelist my sample libraries, as well as the Cakewalk Content folder (sub-folders to both are also whitelisted when the parent folders are). I also whitelist the Cakewalk Core folder in Program Files, as well as the Common Files/VST3 folder and the folder containing all of my plugins (I use VST64). All files are scanned for viruses when I download them, as my Downloads folder is not excluded from the antivirus software, and any compressed data is scanned when it gets decompressed. 4) I set my Power Plan to High Performance, with Min and Max CPU set to 100%, set it to never turn off the Hard Drives, and I also disable the USB Selective Suspend. I also never let the computer hibernate on its own. That's about it. (I don't think I forgot anything) Bob Bone

I have a 65" 4K HDTV, and if I use the recommended resolution, I use 200% scaling, or cut resolution in half and run 100% scaling. Seems to be OK at either. Bob Bone

Is it possible you moved a USB-connected device to a different USB port on your computer? If so, please respond, and I will detail some steps for you to help with that. (it is a bit of typing, so it would save my fingers to know whether or not one or more of your USB devices ended up in different USB port(s). Thanks) Bob Bone

Try going to Edit > Preferences , and check the paths for Files > Folder Locations, to make sure they are still valid, and edit them as needed.

If you use Battery, it should also have that -6 dB parameter you can adjust, if memory serves. Bob Bone

Kewl - I had no way to know. Glad some piece of it was helpful. Rock on, Sir. Bob Bone

They all use SATA III, which maxes out at around 500 MB/second. Seek times will be faster than on a HDD drive. Bob Bone

The clipping may not occur on the individual track you are recording with peaks hitting -1 dBFS, but that is almost certainly going to be too hot for many of your plugins to process properly - particularly those that emulate analog gear - as those plugins are designed to work best with an input level at 0 dB VU (which is an average, and they calibrate most VU Meters to -18 dBFS, using a 1k pure sine wave). In addition, if you start running your tracks to various buses, that feed additional busses, you will end up with the signal clipping, eventually. I think it far better to record at lower levels, so that there is a good bit of headroom left for mastering. I believe you would end up with a cleaner and better sound, by lowering your recording levels right from the start, and then if too quiet, simply raising the speaker volume would get it loud enough for your listening, while keeping enough room for a proper mix and master. Don't take my word for it - do a little digging on the internet, and while there are numerous opinions on what a proper recording level is, I would bet you wouldn't find much, if any, guidance that would suggest recording with peaks hitting -1 dBFS. For whatever the worth, I set track gain at or near 0 dB VU, with no peaks louder than -6 dBFS. That gives me an average level that leaves me around 18 dB of headroom, with room for sharp transients to get up to, but not exceding, -6 dBFS. I also have a limiter on the Master Bus set to -1dBFS, to prevent speaker or ear damage. I also make sure that each plugin is gain-neutral , meaning the output volume of any plugin is adjusted to it matches its input gain, through either makeup-gain or gain reduction. I try to run all the way through each channel and its plugins, at that 0 dB VU target, except drums - which I use a target of somwhere between -18 dBFS and maybe -14 dBFS, with no drum peaks above -6 dBFS. Best of luck to you, in any case. Bob Bone

I suggest using the midi track fader associated with the loaded Gentleman instrument, to bring its volume down (check the actual dBFS level shown on its audio track(s), for the actual gain level, because the midi track fader is using midi volume (0-127), rather than the audio gain level shown in the Peak Meter for its audio tracks. For the instrument that is too quiet, I would just use that instrument's associated track's Gain knob, to add some gain there, again observing the Peak dBFS shown on the audio track(s) for that instrument. If you have two audio tracks for that instrument (left mono and right mono), you can select both tracks, then hold CTRL while adjusting the Gain, to move the Gain knob for both tracks at the same time, as that will make both tracks move in the identical amount. The reason I suggest using the midi track volume to bring an instrument down in volume, rather than the Gain knob for the associated audio track(s), is because the Kontakt default volume setting is -6 dBFS, which is still quite loud for recording purposes, and the Gain knob may not allow enough gain reduction to get you to whatever level you prefer to record at. (I use -18 dBFS for sharp-transient instruments, like drums, and a VU Meter setting of 0 dB VU and a peak dBFS of no louder than -6 dBFS). Bob Bone

Wow - you bring Kontakt instruments in at 0? I cannot imagine being that hot on input. How could you not end up clipping? Bob Bone

Kewl - yeah, because the Kontakt default is to set each instrument up to a -6 dB level, which is usually WAY too hot for recording, you can take advantage of its default checked parameter telling each instrument to respond to standard controllers for volume and pan, by adjusting the instrument volume using the midi track fader, stops it from making the volume jump back to that default -6 dB level. It will just stay on whatever level you set on the midi track fader. The only thing with that, is that the scale on the midi track fader is from 0-127 - the midi scale, and that doesn't correspond to a dBFS value, so to get around that, try the following steps: 1) As soon as a Kontakt instrument gets loaded, drop its midi track fader to zero. 2) Alternate between moving the midi track fader up, and playing some notes on that instrument, so that you move up into the range you like to record at (for me that is around - 18 dBFS. (so as you play some notes, every time you move that fader up, look at the associated audio track(s) for that instrument, to see the peak. Doing it the above way, keeps the volume from being insanely loud to begin with, (even if you have a limiter on your Master Bus to prevent speaker or ear damage), and only takes a few seconds to do. After you do this a few times, you will get a feel for approximately where the midi track fader needs to be to result in a peak of around -18 dBFS, or whatever you generally use. If you use VU Meters instead, shoot for around 0 dB VU, which is usually calibrated to be at -18 dBFS - but if you use VU Meters for gain staging, there are a couple considerations: 1) make sure nothing peaks (on the Peak meter) above -6 dBFS, and also, if you have an instrument with sharp transients (like drums), you are better off setting that instrument using the Peak Meter (dBFS) , because the slow reaction of VU Meters could result in clipping. Bob Bone

Not to mention the candy they include with orders. Nice touch

Yeah, but I think you can avoid having to even go into the instrument, by simply adjusting the midi track fader for the instrument. Bob Bone

Kewl - just wondering. Strange symptoms. I have 4 of the M-Audio sustain pedals, and 4 different brands of midi controllers, and some of the pedals work 'backwards' than intended - because in the industry, there are two different polarities used between Yamaha pedals and Roland pedals, and for years and years, it would piss people off, because we would plug a pedal in, only to find the notes getting sustained when the pedal was not pressed, and the notes would release when the pedals would be pressed. The keyboard manufacturers eventually programmed their products to hold some combo of keys down when turning on the keyboard, to flip its idea of when the sustain pedal would sustain or release, and the pedal manufacturers generally also provide a little switch on the side or more often, on the bottom of the sustain pedals, that also flip the polarity - to switch the sustain/release to the other way - and this has allowed life to continue for keyboard players, the world over. On my M-Audio sustain pedals, there is such a switch on the bottom - have you tried switching that and plugging the pedal back into your keyboard? Bob Bone

Is the pedal plugged into an Expression pedal port, instead of a Sustain pedal port? Bob Bone