Jump to content

Blindeddie

Members
  • Posts

    36
  • Joined

  • Last visited

Posts posted by Blindeddie

  1. If you are using the Firestudio as your "Windows" default sound device, that will cause the issue.  I also grappled with this for a long time (as well as Sample Rate Changes) and as soon as I changed the default Windows audio device to the integrated Realtek soundcard the problems went away. To get around not being able to hear web audio, I patched the speaker output to inputs 7/8 on the FS.  If I need the inputs for tracking, I just unplug soundcard outs... I have also considered a second pair of speakers specifically for that.  Hope that works for you!

  2. 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

    • Like 2
  3. 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

    • Like 1
  4. 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

  5. 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

     

  6. 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

  7. 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!

  8. 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

  9. 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

    • Like 2
  10. 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

    • Thanks 1
  11. 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

    • Thanks 1
  12. 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

    • Thanks 1
  13. For scenario 2 that abacab mentions, a simple fix is to run the Cal script "split channels to tracks" and that would create a separate track for each channel.  Cal scripts can be run by going to "Process" --> "Run Cal Script" and selecting the script I mentioned. just thought I would mention it!

    Peace,

    Blindeddie

    • Great Idea 1
  14. Ok, after much fiddling around, I am changing my tune (Puns Intended) I decided to try CbB using theWDM drivers for my interface and the problem went away.  

    I noticed that other Audio apps I use would exhibit the same behavior after I opened CbB  with ASIO drivers then closed it and opened other apps. The  Sample rate of the interface would change to Random sample rates with those apps as well.  If I didn't open CbB the other apps worked just fine.

    So I set up CbB to use WDM then rebooted to get a fresh start. Started CbB and Sample rate stayed at its default Closed it, opened other apps that are using ASIO and no issues with Random Sample rate changes.

    so I think something is going on with CbB and the ASIO drivers for my Interface.  Since all is working smoothly now I will just leave things the way they are, but if anyone has a similar issue or knows Why this would be happening, please share.

    Peace,

    Blindeddie

×
×
  • Create New...