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

Investigate OSC Integration #6

Open
Marak opened this issue Feb 22, 2011 · 6 comments
Open

Investigate OSC Integration #6

Marak opened this issue Feb 22, 2011 · 6 comments

Comments

@Marak
Copy link
Owner

Marak commented Feb 22, 2011

Branch @ https://github.com/catshirt/JSONloops/tree/osc

Deps @ https://github.com/catshirt/node-osc

@tmpvar
Copy link
Collaborator

tmpvar commented Feb 22, 2011

I think this is a great idea, and we could also provide a midi integration.

In it's current state, jsonloops, can only support sending OSC/MIDI data, not receiving. There would be a bit of dev and user experience work to make it process incoming OSC/MIDI intuitively.

@Marak
Copy link
Owner Author

Marak commented Feb 22, 2011

I've a bit of a conversation going with catshirt over PM. I just asked him to elaborate on possible integration points.

There's a lot of ways we can go, maybe supporting OSC OUT from the sequencer would be the first step of OSC integration?

@tmpvar
Copy link
Collaborator

tmpvar commented Feb 22, 2011

Yep, thats what I was thinking

@kn0ll
Copy link

kn0ll commented Feb 22, 2011

out is definitely much more straight forward. like tmpvar said, input would require quite a bit of ui thought (mostly due to multiple clients). i imagine there are technical implications as well once this becomes a hosted operation.

maybe something with clear benefit, like midi from the tracks, would be a good way to start. though even sending output, i'm not exactly sure how this will work on a hosted machine...

thanks for your input guys

@Marak
Copy link
Owner Author

Marak commented Feb 22, 2011

An instance of a JSONloops looper will emit a "step" event on every step of the sequencer. This event contains a snapshot of the entire loop, plus all metadata for controls.

Ignoring all the possible implications of shoving all this data around, we could just add an additional listener to this step event and send it to osc. We could also pre-process the output in node to limit / modify whats being sent out.

@kn0ll
Copy link

kn0ll commented Feb 23, 2011

i have a rough version committed that i presume is along the lines of what you guys expect. screenshot: http://cl.ly/0D2m0a3c1G0Z210D0d3z

one downside to subscribing to the step is that the sliders become a bit "digital", and you can't get true smooth change. for now though, this seems sufficient, since the sequencer track is probably more useful than the sliders anyway.

for the record, i don't actually know how this signal maps in osc software, or to midi. but the graphs suggest something is right, so the rest is figuring out osc / midi / software details.

let me know if this is what you guys had in mind... cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants