Comments by warf
@eRKa
I’ve fixed the encoder detection. Please download it again and confirm it’s working properly.
I’ve fixed the encoder detection. Please download it again and confirm it’s working properly.
@eRKa
Appreciate the idea! I’ll think about this for the next stage of development. I’ll also study how AOM Triple Fader handles it.
Appreciate the idea! I’ll think about this for the next stage of development. I’ll also study how AOM Triple Fader handles it.
@eRKa
First, please set the HW Type to match your controller:
If you’re using an endless rotary encoder, choose “Encoder (±)”
If you’re using a standard knob (potentiometer), choose “Pot (0–127)”
After that, if it’s still not working properly, I need to clarify this part:
> “but a lot of times when I am switching on other knobs it is not working”
When you say “other knobs”, are you talking about other parameters in Live that you select and try to control with the same hardware knob?
In other words, when you turn the hardware knob, does the first parameter in Live change value correctly, but after you click a different parameter, turning the knob no longer changes that parameter’s value?
If that’s the case, please make sure the Hold button is turned off.
If it’s hard to describe the behavior in words, could you share a short video showing what you do and what happens on screen? That would help a lot.
First, please set the HW Type to match your controller:
If you’re using an endless rotary encoder, choose “Encoder (±)”
If you’re using a standard knob (potentiometer), choose “Pot (0–127)”
After that, if it’s still not working properly, I need to clarify this part:
> “but a lot of times when I am switching on other knobs it is not working”
When you say “other knobs”, are you talking about other parameters in Live that you select and try to control with the same hardware knob?
In other words, when you turn the hardware knob, does the first parameter in Live change value correctly, but after you click a different parameter, turning the knob no longer changes that parameter’s value?
If that’s the case, please make sure the Hold button is turned off.
If it’s hard to describe the behavior in words, could you share a short video showing what you do and what happens on screen? That would help a lot.
@eRKa
Sorry, I don’t have a proper manual ready yet 🙏
Could you try this setup:
- Connect your MIDI device to Live with the right cable.
- Go to Live’s Settings and enable the MIDI input port for your device (make sure Track is turned on for that port).
- Open the I/O section.
- On a MIDI track, select your device in the MIDI From dropdown.
- Set the track monitor to In so it always receives incoming MIDI.
Then press the Learn button in ParamLatch and move a knob on your MIDI controller up and down widely for about 3 seconds.
Sorry, I don’t have a proper manual ready yet 🙏
Could you try this setup:
- Connect your MIDI device to Live with the right cable.
- Go to Live’s Settings and enable the MIDI input port for your device (make sure Track is turned on for that port).
- Open the I/O section.
- On a MIDI track, select your device in the MIDI From dropdown.
- Set the track monitor to In so it always receives incoming MIDI.
Then press the Learn button in ParamLatch and move a knob on your MIDI controller up and down widely for about 3 seconds.
@chinski
I just tested the link and it works on my end. If you’re still having trouble, please tell me exactly what you’re doing and what happens on your side.
I just tested the link and it works on my end. If you’re still having trouble, please tell me exactly what you’re doing and what happens on your side.
@sleepcycle
Thanks for the comment! The most significant difference is the small device width. Having a narrower width is a huge advantage when a track is loaded with many devices. Also, Utility often fails to move in 0.1dB increments even with Shift held down, depending on the screen or mouse resolution.
Thanks for the comment! The most significant difference is the small device width. Having a narrower width is a huge advantage when a track is loaded with many devices. Also, Utility often fails to move in 0.1dB increments even with Shift held down, depending on the screen or mouse resolution.
It should be backward compatible as the core logic is built entirely within gen~.
I don’t have an older environment to verify this myself, so if you could test it and report back here, it would be a huge help!