Conductive Labs Support Forum

Full Version: Strum not working with external clock
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I can't get the strum to work at all when using an external clock. As soon as I switch it to internal clock, then strum works as it should. With external clock only the default, no-strum pad trigger will sends any note data — all other strum settings result in silence, essentially killing the pad channel.
I experienced the same with Pad... which was due to NDLR Cntrl and KB Trans being on the same channel
(03-19-2019, 12:05 AM)MKS30 Wrote: [ -> ]I experienced the same with Pad... which was due to NDLR Cntrl and KB Trans being on the same channel

Thanks for helping with a tip to others!
Steve
(03-18-2019, 11:36 PM)leave trace Wrote: [ -> ]I can't get the strum to work at all when using an external clock. As soon as I switch it to internal clock, then strum works as it should. With external clock only the default, no-strum pad trigger will sends any note data — all other strum settings result in silence, essentially killing the pad channel.

Thanks for posting this sighting!

Did MKS30’s suggestion help?

I’ll have a look today and try to reproduce your sighting.  There was a similar bug with the modulation matrix having to do with internal v. external Clock.  It might be the same issue in a different location. 
Steve
The external clock was not triggering the strummed notes. Also the initial Pad "play" wouldn't strum. These have been fixed and will be posted in a FW update soon.
Steve
Thanks Steve!