You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A possible issue with the gate output of your imagine module :
When loading a b&w image in your module and setting the mode to “vinyl”, I expected the gate output to always be 0v whenever the read head would be above the color black. But if you look between the 0:09 and 0:14 mark in this video (https://youtu.be/inIrWf5oIa8), sometimes the read head over black will output a constant 10v value instead.
If you could consider adding this more traditional behavior as an option for how the gate output work, it would be greatly appreciated.
Thanks,
Loops
The text was updated successfully, but these errors were encountered:
This was my response on the community forum, to provide more context here:
The gate logic is not looking at levels in the conventional way. It’s not open on rising voltage and close on falling voltage. It’s a flip-flop at edges detected by max delta in a 9-sample window that exceeds the threshold. This algorithm doesn’t end up matching the natural intuition about the levels in the image.
Please open an issue, and I’ll look into adding an option for a different gate algorithm that is closer to intuition or the traditional rise/fall gates-from-audio method. I think it would be a nice addition.
A possible issue with the gate output of your imagine module :
When loading a b&w image in your module and setting the mode to “vinyl”, I expected the gate output to always be 0v whenever the read head would be above the color black. But if you look between the 0:09 and 0:14 mark in this video (https://youtu.be/inIrWf5oIa8), sometimes the read head over black will output a constant 10v value instead.
If you could consider adding this more traditional behavior as an option for how the gate output work, it would be greatly appreciated.
Thanks,
Loops
The text was updated successfully, but these errors were encountered: