Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

6 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi msmcleod, It did seem to have been a problem with a pitch bend message. I turned that setting off and it seems to be working fine now. Thanks! I had the 4 cores support turned on so I didn't have to change that. I thought I had turned all the extra MIDI controls off previously because of a different problem. There were some extras check boxes still on for some reason including the pitch bend. This is usually how I have my settings: I'm using an ancient KeyRig 49 and I usually only care about MIDI notes and velocity. Thanks again.
  2. I love Bandlab but I've never liked Kontakt. I especially hate the interface. Unfortunately, there are several plugins I like that only work with it. I'm still using version 5.6.5. I've never had any serious performance issues when I've added multiple Kontakt Soft Synth instances into Bandlab projects. In fact, I've been quite impressed at how well Bandlab keeps up with the many Kontakt plugins I've used at the same time even without my freezing them. My computer isn't the fastest but Bandlab does a great job even when I add 50 tracks or more including many Soft Synths: I did notice a few hiccups using Symphobia where a string section or whatever might start to sound out of tune after a while (player fatigue?). I attributed it to a lack of memory or cpu resources but it was easily solved by deleting the plugin in Kontakt and reinserting it again. Not sure why that worked. I could then freeze that track just fine and move on. Recently I started using Evolution Rick 12 and it worked fine until I started recording a track in Sonar. It sounds fine at first and then suddenly starts sounding way out of tune (rock and roll guitar player realism?). There are no error messages and it's also not crashing. It just makes dogs run frantically from the room. My old Symphobia delete/reinsert trick doesn't work this time. It seems like if I free up as much computer ram as possible things maybe get a bit better. I tried increasing the setting below but I don't think it does the trick. Maybe I didn't change it correctly: I generally don't touch any of the Bandlap ASIO driver settings because things seem to usually work fine: Does anyone have any suggestions on how I might improve the performance of this plugin by changing any Bandlab or Kontakt settings? Thanks.
  3. The project has been open for a long time as I continue to work on it. It seems that this message pops up when I take a break and go back and look at the screen again . It doesn't seem to pop up at all when I'm working actively.
  4. I've seen a few posts regarding this error message but none that solves the problem. I started getting this message recently and I'm guessing it might be related to a plugin: Is there any scientific way to understand and fix the problem that's causing this error?
  5. John Vere, Thanks for your response. For the record, this system is Windows 7 64 bit. I'm actually pleasantly surprised at how well SONAR does with this system. The song I'm currently working on has 45 tracks, many of them Kontakt SoftSynths. I rarely have processing lapses and I can always freeze tracks or archive them to improve performance. I'm not a big fan of Windows 10 so I'll stick with this until I have a compelling reason to change.
  6. Speakers are JBL 3MkII. I can test them with a non-Cakewalk sound source to see if that's the problem. I usually only use them for Cakewalk. Thanks.
  7. I've notice that often when I hit play for the first time after loading a song it takes a half a second to hear the first audio parts. If I simply hit play again it's fine and the music starts perfectly. I thought it might be a setting like "Suspend Audio Engine When Cakewalk is Not in Focus" but unchecking that doesn't fix it. Does anyone know how solve this?
  8. QUICK UPDATE: I haven't had any major problems with Kontakt plugins since I changed my MIDI settings as shown above I'm using a keyboard MIDI OMNI input and not even assigning individual MIDI channels to the various Kontakt synth plugins. What's strange is that occasionally I'll still see a MIDI synth input volume light up when my focus is on playing a new part. All the other MIDI synth Kontakt inputs behave nicely and remain silent but one might perk up 'listening'. I checked all the settings and it seems there's no difference between the 'listening' plugin and the well-behaved quiet plugins that also don't have the current input focus. So I'm trying to add a new Kontakt synth and one older pesky channel is playing along also even thought I'm finished recording that part. The easiest way to fix this seems to be to insert the 'listening' plugin again and copy/paste it's MIDI data to the new channel. Then it's well-behaved again. I'm not sure what causes this behavior but it's a bit annoying. Any suggestions are appreciated.
  9. I've got a project with about 50 tracks but it now seems to have a new lag time 'processing audio data " before it starts the export mix ("mixing down audio"). In the past with large projects it would start chugging along export/mixing right away and I could monitor the progress immediately. Is there some setting I might have changed that is causing Bandlab to need to process audio data first before export/mixing? The tracks are a combination of audio tracks. soft synths, and archived tracks of both types. Everything is the project is the same as in my previous projects. Thanks.
  10. Sports Update! Things seems to get better when I changed SONAR to only record MIDI "Notes" (see below). I'm still testing this but turning off the Controller and other check boxes might be what's helping keep the volume consistent. Film at eleven...
  11. I actually don't think it's the keyboard. Once the keyboard records a simple part such as a 'triangle' on 4 downbeats in a measure that records and sounds perfect it's no longer in the equation. The playback mode through the Kontakt triangle VST that once sounded fine suddenly has no volume without any change to the original MIDI recording by the keyboard.
  12. It's an ancient keyboard but I'm not sure about a dirty pot being the problem. I can try another MIDI input device leaving this keyboard out of the equation and report back.
  13. I still haven't been able to solve this problem but I can at least say what doesn't work. I tried any solution I've seen on forums or in this thread without success. Here's what I do know: This only happens with SONAR using Kontakt plugins. It has the some same problem regardless of which plugin is used. The volume suddenly disappears during playback or monitoring. Unchecking SONAR MIDI settings "Zero controllers when play stop" doesn't seem to change anything (or perhaps it does...please read on...). I only use the KeyRig 49 as an input device and nothing else: Changing the Kontakt instrument Options to uncheck the two controller options seems to have no effect. It makes no difference if you use OMNI for the MIDI input channel or select a specific channel number. When you first insert any Kontakt plugin everything sounds correct whether you use the mouse on the plugin's keyboard or use an external MIDI keyboard. The volume disappear after a seeming random amount of time even if you don't start recording or move the transport. It's like a time bomb waiting to create almost complete silence of anything you input. If the master fader in Kontakt is at 1.76 you will not hear almost any volume. If you turn the master fader up to 36.00 and do nothing else you will again hear the volume normally again. It may sound extremely loud at some future point in time after doing this. If you leave the volume after 1.76 but click 'X' to close the program and then immediately insert it in again the volume (usually) magically is restored to normal. Again, all this happens without recording or using the SONAR transport. When it's "happy" the MIDI keyboard volume and the audio channel associated with it via "insert soft synth" show normal volume levels. When it's quiet and "not happy" the MIDI input volume appears the same but now the audio channel shows a slight volume but it is now dramatically reduced. Removing the plugin and inserting it again usually makes everything sound perfect again. You can even record a track and freeze it if you're lucky. This is the MIDI event list when it's not working: I said that turning of the instrument Controller check boxes has no effect but that may not be true. If I turn them off nothing happens immediately. But if I remove the plugin and reinsert it again having unchecked those boxes it will sound okay again. If I don't uncheck them you may not hear the normal volume after reinserting the plugin. I'm not a MIDI expert but I gather there's a volume control request being sent to my MIDI input channel for some reason from some other place. Perhaps someone can advice me where this might be coming from and how to prevent it? Thanks again.
  14. The WA-47 and the WA-47 Jr. are available where I live. The price for the WA-47 is about 160% more than in the States! It still sounds like what might be my best choice. The WA=47 Jr. is priced more reasonably here but sounds like it's not in the same league based on online reviews.
  15. I've seen other users ask about this but I haven't seen an answer that solves the problem. When I add a Kontakt plugin into Bandlab it works fine no matter what the particular plug is. If I immediately record it in Bandlab all is fine. Later it seems like all bets are off. The playback of the original recording is generally fine but there are intermittent issues doing other tasks. If I just click on the MIDI plug in again at a later point and play my input keyboard I may hear nothing. I can increase the volume in the plugin and usually hear it again but then later the volume jumps up to an extremely loud volume. Sometimes when you're playing a part the volume drops out but will sound fine again if your press "Play" in SONAR first. I saw this listed as a solution in a couple of posts but it doesn't seem to solve the problem: Any thoughts?
  • Create New...