-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Channel one gate input not working (hardware works with standard OC firmware) #21
Comments
hallo , barebonesldn ,your not alone ,I have the same problem , first i thought it was my fault (clumsy smd soldering) |
@BAREBONESLDN @themoonscientistandco Please check the Midi-Settings by pressing both (L+R) Buttons. Propable the Midi-Input is "T1" and the port is initalized as "Serial Input". It has happened to me before, but I haven't figured out how to reproduce the condition. |
Hallo eh2k . indeed, that was the problem |
Thank you!
Sent from Yahoo Mail on Android
On Fri, 16 Sept 2022 at 15:41, ***@***.***> wrote:
@BAREBONESLDN @themoonscientistandco
Please check the Midi-Settings by pressing both (L+R) Buttons.
[]
Propable the Midi-Input is "T1" and the port is initalized as "Serial Input".
If it is "USB" so try to change it to "T1" and back to "USB".
After that it should work. Save the Preset with both (L+R) encoder pressed.
It has happened to me before, but I haven't figured out how to reproduce the condition.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Unfortunately this fix did not work for me. |
I figured it out it was the trigger input setting on the channel, it was set to - |
I've tried several teensy 4's and reflashed the firmware several times (with the two latest versions) but for some reason channel one is not responding to the gate signal.
I can get audio out of channel one by using the speech synthesis mode.
The gate input tests fine in the testing menu and works correctly with a teensy 3.2 and standard OC firmware.
Any ideas what could be going wrong?
Thanks Phil
The text was updated successfully, but these errors were encountered: