Skip to content
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

ext clock broken #1

Open
tehn opened this issue Apr 26, 2019 · 3 comments
Open

ext clock broken #1

tehn opened this issue Apr 26, 2019 · 3 comments

Comments

@tehn
Copy link
Owner

@tehn tehn commented Apr 26, 2019

No description provided.

@okyeron

This comment has been minimized.

Copy link

@okyeron okyeron commented Apr 26, 2019

For the on_select_external error the following change seems to fix the error. Is just the pattern reset the intended goal there?

line 156:

clk.on_select_external = function() clk:reset() end --reset_pattern

Otherwise I'm looking at beatclock.lua with regards to external clock as I'm not certain it's working properly there.

@okyeron

This comment has been minimized.

Copy link

@okyeron okyeron commented Apr 26, 2019

Also a dumb question: I am adding a bunch of debug print statements in beatclock, but none of them show up in the REPL at all. Is there something funny here because it's a "required" module?

Any trick to get those prints in beatclock to work?

@okyeron

This comment has been minimized.

Copy link

@okyeron okyeron commented Apr 26, 2019

Ok - I think I sorted out the external clock problem. (turns out my prints were not happening because process_midi wasn't actually executing)

There are 2 midi.connect() statements in awake. Line 80 and Line 150

As they are, they are both trying to connect to vport 1 - I think the second one is over-riding the first one. At which point process_midi is just not happening. Maybe because the one in init() is blocking the one for process_midi?

If I set midi_out_device to midi.connect(2) then process_midi (and external clock) works again.

So... not sure if this is a larger problem - maybe needing some debug if a script tries to connect to the same midi port twice ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.