Jump to content

Blindeddie

Members
  • Content Count

    31
  • Joined

  • Last visited

Community Reputation

19 Good

Recent Profile Visitors

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

  1. It looks like you just have to have a default Saved (once) and you can change it per instance/project and the (without setting any changes as the default). for example I opened an instance of K4 created 8 stereo outs and renamed them Out 1-8. Without saving that as a default, the out list in CbB looked wonky like the one shown above. I saved as the default then reloaded the project and all was good. I opened a new project, loaded K4 and the outputs were named as the default I had saved (out 1-8). I renamed the outs in the new project and everything looked perfect (without saving my changes as the default). saved the project and closed. Reopened the first project and outs were still named out 1-8. closed that project opened the second one (where I had renamed the outs) and the names I had changed for the outs were reflected properly in CbB. what I did not test was if any out names in existing projects/instances were affected by setting the default... I don't think they should as the default should only be applied to "New" instances of Kontakt... I think...🤔 I hope that makes sense. Peace, Blindeddie
  2. Once you make the changes, you need to save the Kontakt Out mapping as the "Default" (Either All or VST), then close the project and reopen the project...the outputs should then show properly. I tested in K4, K5 and K6 (appears the issue does not occur in K6, but if it crops up, this should work). I am assuming that due to the "Dynamic" nature of creating and naming outputs, that unless the changes are "Saved" so to speak, that they do not translate properly...One of the many weird Kontakt things... Peace, Blindeddie
  3. Check the Midi Channel the KB is transmitting from, it may be set to a specific channel that does not correspond to the Mid channel of the track/Instrument you are trying to control. Try setting the Track for "Omni" midi input or Change the transmitting channel of the KB to match the midi channel set to receive on the track. Hope that helps! Peace, Blindeddie
  4. OK, well that resolution was short lived, the issue popped up again so I did some monitoring and it appears this is a problem with the Firestudio and or the drivers. I was looking at the "Universal Control" app and I adjusted the Buffer size from 128 to 256 and the Sample rate jumped up to 96K then to 48K and finally settled back in at 44.1K. Opened CbB and the Sample rate had changed back to 96K. Maybe time to get a new interface... Peace, Blindeddie
  5. Hi Noel, Well it appears that some NI gear that I use was causing the issue with the sample rate. They are midi controllers that have built in audio Interfaces and once I deleted the ASIO entries for them, problem resolved...at least it appears so, only time will tell. Thanks for the info, Blindeddie!
  6. Thanks Noel, will take a look and see what I can find... Peace, Blindeddie
  7. Hey Noel, Not sure if it is possible, but are there any "switches" that can be used when opening CbB that would output the Driver enumeration to some type of log so I could see what drivers are being queried and which one may be causing the erratic behavior of the sample rate? (kind of like a debug mode) just figured I would ask. Thanks, Blindeddie
  8. Still wrestling with this myself... I have tried everything I can think of, cannot find a resolution.... In my case, I think it is just old and outdated drivers (Presonus Firestudio which is a discontinued and non supported device). Drivers have not been updated since 2016... I refuse to purchase a new interface in the hopes that this will "Go Away" as it works just fine when it behaves... This issue also presents itself in other DAWS...that will remain nameless... Not much help...just venting... Peace, Blindeddie!
  9. You need to find out if the midi file contains all "Patch Change" info on a single track. Right click all the midi clips and check the event List and look for patch changes and delete it. Xpand2 does not follow the GM standard for patches, so what might be a Piano In TTS-1 could be an synth patch in Xpand2. Make sure the event list is configured to show All events. Peace, Blindeddie
  10. If it works using Mackie Control in other Daws, it should work in Cakewalk, but once to set it up in preferences (Add the Mackie Control and select the Zoom midi ports in and out) go to "Utilities --> Mackie Control" and the Properties page opens up. if you put a check in "Disable Handshake" it should connect the Zoom... I don't have a Zoom, but this has worked for other non-Mackie devices I have that have MCU support. Hope that helps! Peace, Blindeddie
  11. Use the Smart tool instead of "right click-->Split..." There does not appear to be a way to turn off the dialog when choosing it from the context menu. Peace, Blindeddie!
  12. If the start points of the clips are different, then you would need to align the clips manually to get them in sync. One thing you would need to do is turn off "Snap to Grid" see page 380 of the reference guide. this would allow you to move clips at no specific resolution. There is also a Nudge Command "Process --> Nudge" (see page 376) that will move clips based on settings that you choose "Process --> Nudge --> Settings". And the reason I point you to the manual is that there are a lot of Grid and nudge settings and I am too lazy to type it all out...😝 Peace, Blindeddie
  13. I may be wrong, but I think you are talking about crossfading. Check out Page 439 in the manual, to see if that is what you are looking to do. basically it fades out one clip while fading in another which gives you a somewhat seemless transition between two clips (eliminating pops or clicks). if I am off the mark, sorry! Peace, Blindeddie
  14. I have had this issue before, all were activated prior to scanning, but did not show up until I ran as Admin...whether its required or not is besides the point, that is what worked for me...doing it has worked for me many times and usually solves my problems when it comes to plugins. Its the first thing I do when I have issues. Peace, Blindeddie
  15. I checked the authorization process for Nimbus, and it uses ILok authorization. The plugins I was having an issue with also use ILok Auth. I had to run two separate Daws as Admin in order to get them recognized, so hopefully the fix is as easy as that... Peace, Blindeddie
×
×
  • Create New...