Robert Bone

Please detail exactly what your midi input devices are set in preferences, and also exactly what you are setting for the midi track's Input, and also the Midi Output Channel for the midi track (if set in the parameter - right under the FX bin on the midi track). Bob Bone

DOH! That would have saved me some typing - wish I had read and retained that in his post prior to my authoring that 'book' of a post.

Sounds like maybe an authorization thing. You could try copying all the 32-bit plugins off to a newly-created folder that isn't included in the VST scan path in the plugin manager, then deleting the 32-bit plugins from the folder that IS currently included in the VST scan path, and then trying to add back in, say 10 or 20 32-bit plugins back into that folder (copying them over from the folder you had saved them all in). This way, you could kind of work your way through a few at a time, where if any batch of 10-20 got hung, you could pull those back out of the scanned folder, and try maybe 5 of those again, or 2, or 8, or some smaller number from that last batch that had failed, repeating this until you were able to build up that scanned folder again with only those 32-bit plugins that scanned successfully. Then, you would be able to work out why the specific ones you were able identify as causing the VST scan to hang, had issues..... I hope the above makes sense. I do think that licensing can be a frequent cause of these kinds of issues, but if you are just now moving all of those 32-bit plugins to a 64-bit Windows, then some of those 32-bit plugins could just freak out at running bridged in a 64-bit environment. IF you determine that the failing to scan is primarily caused by bridging with the Cakewalk-included Bit-Bridge, you could also consider buying the commercially available bridging software called J-Bridge, which can often give better results for some 32-bit plugins (it runs about $20, but do keep in mind that it won't be able to help ALL 32-bit plugins run in a 64-bit Cakewalk). SO, for whatever the worth, I keep the vast majority of 32-bit plugins in a VST32 folder, in Program Files (X86), but I only keep a folder I named Bridged in the VST scan path in the Cakewalk Plugin Manager, and the only plugins that are kept there, and thereby available for Cakewalk projects), are those 32-bit plugins that I have tested and found stable for use in a 64-bit Cakewalk. If I find a need for some additional 32-bit plugin, mostly from those in my VST32 folder, but sometimes newly-downloaded off the web, I will add just that individual 32-bit plugin to the Bridged folder, and will make sure it works, before allowing it to remain there for general use in projects. This keeps MY system quite stable......Doesn't help my composition or playing skills, but at least I am not crashing or hanging due to 32-bit plugins. Bob Bone

If you arm the midi track for Record, and then hit the transport Record button, (or hit the letter 'R' on your computer keyboard), then play notes on your Z1, if any midi data is coming through, you should see it drawn on the midi track as you are recording, and after you hit Stop (or the space bar on your computer keyboard), that midi data should still be visible on the midi track that is routed to the Kontakt instance, and your Z1 for input. I thought maybe just seeing if any midi data is getting recorded would be a reasonable place to start. Additionally - as a separate test, if you open the Kontakt instance, in your project, there should be a keyboard at the bottom of the Kontakt instance. If you do not see it, then click If you arm the midi track for Record, and then hit the transport Record button, (or hit the letter 'R' on your computer keyboard), then play notes on your Z1, if any midi data is coming through, you should see it drawn on the midi track as you are recording, and after you hit Stop (or the space bar on your computer keyboard), that midi data should still be visible on the midi track that is routed to the Kontakt instance, and your Z1 for input. I thought maybe just seeing if any midi data is getting recorded would be a reasonable place to start. Additionally - as a separate test, if you open the Kontakt instance, there should be a keyboard at the bottom of the Kontakt instance. If you do not see it, then look at the top of the Kontakt instance window, and you will see a round toothed gear, that is for setting, and to the right of that is an icon/button that looks like a multi-pane window - and THAT is what you want to click on - the little arrow at the bottom right corner of that icon/button. That will open up a little menu of options for what is displayed - like the Output Section, etc. One of those options is for displaying a keyboard at the bottom of the Kontakt instance. Anyways, you can test whether or not you get output from Kontakt, coming out of that instance's associated audio tracks, by clicking on notes on that keyboard, using your mouse. It's just a validation that you have a working instance of Kontakt, able to actually produce sound when notes are triggered. If it doesn't produce sound on the associated audio tracks, then you have an issue between the Kontakt instance (or one of multiple instruments in the instance), and the associated audio tracks. If, on the other hand, you DO hear the appropriate sounds coming from the audio tracks, when using the mouse to play notes on the Kontakt instance's keyboard, then that part of it all is OK, and there is some issue with the Z1, or something like the output midi channel on the midi track being different than the midi channel the Kontakt instrument is set to. I suppose you could also double-check to make sure you don't have something like Port B instead of Port A (each midi Port gets its own distinct 16 midi channels, and there can be Ports A, B, C, and D available to pick from). You should have: 1) your Z1 checked in Preferences as a valid midi input device 2) The Z1 transpose function should be set to match playable notes in the Kontakt instance (like you wouldn't want to have the Z1 transposed down several octaves when the Kontakt instrument doesn't have playable notes that low, etc...) 3) A Kontakt instance with at least one loaded instrument (if only 1 instrument, then it will automatically be set to receive and respond to notes on midi channel 1) 4) A midi track with its output set to the Kontakt instance you are trying to trigger notes from. Input can be set to None, Omni, or specifically to your Z1 (doesn't have to be set to the Z1). If your Z1 is left to its default, it will transmit on midi channel one. You can always FORCE the midi channel output from the midi track to be whatever midi channel exactly matches the midi channel for the desired instrument loaded into the Kontakt instance, by first setting the midi output for the midi track to the desired Kontakt instance, and then setting the Midi Output Channel for that midi track to the desired midi channel - this setting is immediately below the FX Bin on the midi track, in either the Track Inspector, or in Console View. If the Midi Output Channel is set to match the correct midi channel that the instrument in the Kontakt instance will respond to, then it doesn't matter what midi channel your Z1 is set to, because Cakewalk will change it in any midi data output from that track, to match the Midi Output Channel. 5) If this is an existing project, make sure you haven't accidentally switched which midi port you connected the Z1 to the computer with, because that will cause issues. You ALWAYS want to make sure you keep track of which midi devices are connected to which midi ports on the computer - I ALWAYS leave them connected, and if I ever do need to reconnect them, I ALWAYS follow a little map I made for myself, to ensure they are always plugged into the computer using the same midi ports. If you are not sure if this is the case - then I suggest not selecting specific midi devices as the Midi Input for your midi track(s), but instead, just specify Omni. 6) I don't actually HAVE anything for number 6, I just wanted to end on an even number. I quite honestly do not know if I have covered everything I meant to - it is coming up on 2 AM, and my brain has left the building, so this is as far as I go this evening. I hope something in the above not only makes some sense, but maybe also WORKS to get you past your present issues with getting Kontakt sounds to play, using your Z1. Best of it all, and good luck Bob Bone

Do you have a project file you can upload? I can try to see if I can figure out what is happening. Use a file hosting service, like Dropbox or Google Drive, and then post the link to download it here in this thread. If you think I need the whole project folder, then I suggest creating a new compressed folder, and then copying the contents of your actual project folder into the compressed folder, and then upload that. If instead, you think I would have what I need to test out your midi data playing issues, without needing the whole folder, then just upload the file ending in '.cwp', as that is the extension for a Cakewalk project file. If you are not comfortable with posting a download link in an open forum, you can shoot me a private message through the forum, and then it would only be visible to me. I will keep an eye out for either a download link here, or one in a private message, and will do my best to figure out what is happening. Bob Bone

I confess that there have been SEVERAL occasions where I felt like that, after some drive-by brilliant comment from scook, and I have used Cakewalk since before Windows existed, back when Cakewalk was originally developed and released by Twelve Tone. (a long time ago - I won't reveal the number of years, because it makes me realize my age). I mostly work with midi tracks and data, so there are all kinds of things I am still learning about the software, whenever I venture into additional areas, such as recording actual instruments. Little by little, I move my overall knowledge forward. Very happy you got sorted out. Bob Bone

You should also be able to just press and release your sustain pedal, while that midi track is in focus, and that should also turn it off. I sometimes have articulation changes switched on because I played a section where one was deliberately made, and then I move to a different spot on the timeline and there wasn't a midi event that switched it back to what the different section was intended to have - for that situation, I just press the key-switch for the desired articulation - same principle, just pressing and releasing the sustain pedal works too. I don't want to insert a bunch of articulation or other events just because something is left hanging or changed due to my moving around the time line during tracking or editing.. I MUCH prefer to just dynamically adjust the sound, because if I insert a midi event correction - I would then have to go find that event if I end up wanting to make some general change articulation change to that track later on. By only temporarily dynamically switching the articulation or pressing and releasing the sustain pedal, there aren't a bunch of otherwise unneeded events that might become a pain in the rear later. I hope the above makes sense, it is pretty early in my day here, and I am still waiting for my first cup of coffee to finish brewing. Bob Bone

Here are just a few of the links out there - I did a Google search on: Headphones shootout https://www.cnet.com/topics/headphones/best-headphones/high-end/ https://www.techradar.com/news/audio/portable-audio/best-headphones-1280340 https://www.soundonsound.com/reviews/studio-headphones-0 Bob Bone

I always edit/mix with open back headphones - I happen to use an AKG K712 set of headphones, but there are a number of less expensive phones that still sound great. When I record anything involving a mic, I switch to a closed back headphone, so I don't get any bleed from the phones getting picked up by any mic. I suggest you look at some of the shootouts that are out there, on headphones, for some guidance. These compare multiple makes/models of headphones, at different price points. Bob Bone

Glad you have it sorted out, now. So, it appears that either method of inserting a meter change worked all along, and it is just that the insertions were not being done at the measure on the time line where you thought they were being inserted. So - I always make sure the Now Marker is positioned at the point where I want to insert a meter change, and afterwards, I always click a measure back from the inserted meter change, and let it roll over the measure where the meter change was inserted, to make sure it was done where I had intended. Also, make SURE you have the correct check box selected, in the Insert Meter Change dialog box, because one of the options is to insert a new meter change, while the other option is to change the LAST meter change done (and I believe that option - changing the most recent meter change) is the default - which can really mess you up, unless that is what you intended. Almost every time I insert a meter change, I want it to insert a brand new meter change at the current Now Time marker position on the project timeline. Good luck with it all - I hope I explained things enough to where I haven't massively confused you. Bob Bone

You might want to make sure you didn't accidentally insert meter changes in different time line locations than you meant to, with some of the earlier attempts. In any case, glad you are able to move forward again. Bob Bone

I always go to Project > Insert Meter/Key Change, after first setting the Now Marker to where I want the measure inserted, and I set the meter in the dialog box window that opens up. I do this all the time, as I work on prog projects with oodles of changing meters. Bob Bone

Boy - you couldn't have picked a better time to tell me about Samplit, and Sample Robot. The bass player from my Genesis tribute project has a real set of the original Taurus Bass Pedals, and they may be too delicate to use them on a regular basis. He also has no protective case for them, so there is some risk there. Anyways, I bought a shiny new set of Studio Logic Bass Pedals, but they are just a midi controller, so no Taurus sounds. The bass player and I were already planning to sample his Taurus pedals this weekend, so I think I will take a good look at both of these programs. Bob Bone

Are there any error messages when you get crashes? Are there any Windows error events visible in the Windows Event Viewer, that correspond to the time and date of any of the crashes? What version of Windows are you running? Is your Windows maintenance up to date? Is your system BIOS up to date? Are your drivers up to date for your interface? Are these 32-bit plugins you are working with when you crash? Are there any 32-bit plugins already loaded into projects that crash? (please list them if present) The issues you are having are just not prevalent - meaning whatever is happening to your system stability is most likely related to either (or both) your configured environment and/or one or more plugins you are using. If indeed this is the case, then we should be able to work out the issues and get you stabilized. You would see massive numbers of posts in these forums, if Cakewalk itself had problems so severe that the product was unusable, and that is just not the case, further lending credence to the idea that the issues are specific to your system itself or in the particular plugins you are attempting to use. (including 32-bit plugins). I cannot even recall the last time either Sonar Platinum or Cakewalk by Bandlab crashed on me. (I only mention that to illustrate it being stable). Please provide the information I am requesting above, and folks here in the forums will do our best to help you sort through whatever is happening. Bob Bone

I would just use the VST2 version until the plugin company updates their plugin's VST3 version. This happened with some Waves plugins, and I think maybe some Slate plugins too , a year or two back. Bob Bone

Kewl - can you please also provide the info I requested, in my earlier post? It would help me and hopefully others, assist you in figuring out what is happening to crash your project. Thanks Bob Bone

I concur with the thought that using one of the freeware 64-bit sample players would be well worth exploring, and the Tx16wX sample player is 64-bits with LOTS of features. Here is the link to the Tx16wx: https://www.tx16wx.com/ Bob Bone

Good idea, to try. The default size for this buffer USED to be 500 ms, but with one of the later Sonar releases - either in X1-X3 or Platinum, that default got changed to 250 ms, which lots of folks found to be too small, so the general approach by lots of folks was to increase that Prepare Using ______ Millisecond buffers back up to 500 ms, with some upping the size to 750 ms, and a smaller set of folks going up to 1000 ms. I run mine at 500 ms, and that seems to work just fine - experiment with it and if you find improvement to your playback, then go ahead and leave it at whatever setting works well for you. If one of your change attempts makes things worse, no problemo, just change it again to something different. It won't mess anything up if you try a bunch of different settings for this. For ME, I just changed it the one time to 500 ms and left it at that. Bob Bone

Well, on the ONE hand, we have ALL had epic DOH moments, but on the OTHER hand, look at how WELL we have all learned from those moments. I will NEVER again stop at an auto-parts store next door to where my gig was, and pick up a can of brake cleaner spray to get my keyboard's keys cleaned right before we started the gig. Sprayed the keys - and starting about 2 seconds later, in the order corresponding to which end of the keyboard I started spraying, each key's plastic internals melted, causing each key to simply drop down - as the springs for each key were no longer connected to the now-melted little plastic pieces meant to never have brake cleaner sprayed on them.... (the guitar player watched in horror, as each key became instantly unusable, 15 minutes prior to a high-dollar wedding gig. (please forgive me - this was 40 years ago) (I raced down the street to a music store that was just about to close, and essentially gave them all the money I would have been paid for the gig, to rent the exact same keyboard as the one I had decapitated, and miraculously the gig was saved, though I played for free - AND had to pay a couple hundred bucks the following week to have the entire set of keys replaced). I bet NONE of us will repeat these particular DOH moments we have shared... (I have lots of others, but I don't want to make myself cry thinking about them)... Bob Bone

I do not see any minidump - is there any information you can provide on: 1) Your project's contents - in terms of what plugins (synths and effects) you have loaded into it, and info on if it is all audio, all midi, a mixture... 2) Your computer specs - OS and maintenance level, audio interface make and model, Cakewalk version, etc 3) Any info on what kinds of operations you were doing when it crashed - I know you said random, but for a given crash, please explain what you were doing for that particular time a little before the crash and up to it... Bob Bone

Just curious - the Nova has a wide-band compression feature, here is a brief bit from page 11 of the Nova user manual on it, so wondering why you would be adding in the Tube Tech Channel and using its compression (again, just curious): "CHANNEL STRIP NOVA can also be used much like a conventional channel-strip: A compressor followed by an equalizer. This is basically just a mixture of the scenarios “PARAMETRIC EQUALIZATION” and “WIDEBAND COMPRESSION” highlighted above. But it works surprisingly well in the mixing stage." Bob Bone

Yup - LOTS and LOTS of folks had a mixture of bliss and horror, when folks started running 64-bit Sonar while still using a boatload of 32-bit plugins, and there were entire YEAR'S worth of folks complaining about 32-bit plugin x, y, or z crashing Sonar and why wasn't something done about it, etc... The answer now is the same as is was back then - 32-bit plugins are a crap shoot, no matter what bridging software is used, to try to have them work in 64-bit environments, and that is just the way it is. All of those folks who had nightmares with 32-bit plugins had to eventually decide to move to use only 64-bit plugins, whenever possible, and for any remaining 32-bit plugins they just "had to have", some worked with Bitbridge, some worked with J-Bridge, some partly worked with one or the other or both - with some things inexplicably causing crashes, and some just went belly up as soon as they got loaded. J-Bridge does offer some tweaks to try to assist individual 32-bit plugins running in a 64-bit environment. Another thing folks used to do, during that transition period before they finished moving to all/mostly 64-bit plugins, was that for any projects where certain 32-bit plugins were REQUIRED - well, they would have a 32-bit Sonar installed, and do those projects entirely in a 32-bit environment. Some folks even kept a 2nd computer available, usually with 32-bit XP or XP Pro, for working with 32-bit projects and all plugins therefore being 32-bit versions. I don't think Cakewalk comes in a 32-bit flavor (could be wrong), but if someone still had a 32-bit version of Sonar - and needed to do some work using 32-bit plugins, I would suggest installing that 32-bit Sonar, and creating finished tracks there for only those tracks that required 32-bit plugins, then consider bouncing and exporting those finished tracks to audio and then importing them to a 64-bit Cakewalk. I don't know - kind of winging it here - because it has been many years now since I had to deal with large numbers of 32-bit plugins being required for getting the sounds I needed. Once I moved to a 64-bit environment with only 64-bit plugins, I simply never looked back, nor do I want to now (except for the super small number of 32-bit plugins I find still work well in my 64-bit environment, FORTUNATELY, once folks moved over to 64-bit plugins in their 64-bit environments, things almost always INSTANTLY got rock solid with FAR fewer crashes - all the way down to YEARS going by without a crash. Almost all commercially available plugins offered free updates to 64-bit versions, though lots of the old freeware modules (many of which were amazingly good in a 32-bit Sonar), were just never ported over to a 64-bit version. I have a VERY small number of 32-bit plugins that I still use, and I keep the ones that I have thoroughly tested in a separate sub-folder in my VST32 folder in Program Files (x86). This way, only after I have tested out a 32-bit plugin, found it worked in J-Bridge - THAT is when I would move it into a sub-folder called Bridged (subordinate to VST32) and it is only the Bridged folder that I added to my VST search path in Cakewalk. So, I do have access to tested 32-bit plugins, and that is a very small number - I have well over 1200 plugins, and of them, perhaps 20 are 32-bit. Bob Bone

Try going into Cakewalk Preferences > Project > Midi > and remove the default check for the box for: "Zero Controllers When Play Stops" Some instruments tie volume to the mod wheel. Bob Bone

Try going into Cakewalk Preferences > Project > Midi > and remove the default check for the box for: "Zero Controllers When Play Stops". Some instruments tie volume to the mod wheel. Bob Bone

Well, assuming these 32-bit plugs aren't themselves not playing nicely with Bitbridge: 1) Try bumping up your ASIO Buffer Size - just to see if it make any difference 2) Look to see if 64-bit versions of those plugins exist 3) Try the commercially available J-Bridge (around $20), which might give you better results for 32-bit plugins 4) Try finding similar sounding replacement instruments that are 64-bit. Bob Bone