Midi not working with next button on virtual console
-
- Posts: 1
- Joined: Tue Jul 23, 2024 1:54 pm
- Real Name: Matt Whitsett
Trying to control the next button for a chaser on virtual console with network midi. I have my midi input on a separate universe from the lights, I've made a midi profile, I can see that QLC is getting midi both in the profile using the magic wand thing, I can see its getting midi using auto detect in external inputs when I go to map it on the virtual console. When I send a note, it will work one time, after that it won't work the next time I send that note. It will still see midi in auto detect but will not actually fire the next button again unless I restart QLC. Any ideas on what the issue could be?
- GGGss
- Posts: 3073
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
Welcome to the community.
Could it be that you didn't try the double-press thing? Typically, an external control needs a rising edge. For a valid entry, you need a low -> high transition. You need a second button press for the next button to trigger again. (low -> low = 0, low -> high = 1, high -> high = 0, high -> low = 0, low -> low = 0, low -> high = 1 success)
You can play around with the input profile 'generate an extra press/release' option: https://docs.qlcplus.org/v4/input-outpu ... properties
Could it be that you didn't try the double-press thing? Typically, an external control needs a rising edge. For a valid entry, you need a low -> high transition. You need a second button press for the next button to trigger again. (low -> low = 0, low -> high = 1, high -> high = 0, high -> low = 0, low -> low = 0, low -> high = 1 success)
You can play around with the input profile 'generate an extra press/release' option: https://docs.qlcplus.org/v4/input-outpu ... properties
All electric machines work on smoke... when the smoke escapes... they don't work anymore