[Ardour-Dev] OSC control and Tranzport

[Mike Taht]

On Nov 6, 2007 4:17 PM, Giso Grimm <gg3137 at vegri.net> wrote:

> Hi again,
>
> here is my simple implementation of a standalone tranzport2midi
> application (based on other tranzport code):
>
> http://vegri.net/tranzport2midi.zip
>
> This application implements a *very* primitive virtual DAW controller
> which can control midid-controllable applications (e.g. ardour2) using a
> tranzport device. MIDI feedback is not (yet) implemented, as far as I
> remember (I did not look at the code for some months). The tranzport
> link stability is significantly higher than that of libardour_tranzport.


I note that in the "surfaces" branch of ardour that there is a completed
linux kernel driver for the tranzport.
It works well, handling floods of events from the shuttle etc, even on
non-rt kernels.

I was not happy with the interface to userspace, but there aren't a lot of
off the shelf APIs that can handle something as complex as the tranzport.

There's also a completed alphatrack driver in there, it works, same issues
with the API.

Regrettably I have been travelling for much of  the past 6 months and have
not been able to settle in one place long enough to work on this.

I heartily approve of the idea of moving the tranzport interface out of
ardour and into a separate program.

I do note that doing feedback events properly is a hard problem. :/




>
> You can do with this source code whatever you want. Currently I have not
> the possibility to bring this project to a really usable state, but I
> would be happy to contribute/participate.
>
> The reason why I went for a stand-alone application instead of improving
> the ardour tranzport code was that this is more flexible and allows
> control of other MIDI applications as well. It could be nice to put this
> virtual DAW controller in Mackie control emulation mode and use the very
> stable mcu/bcf2000 backend to control ardour.
>
> Best regards,
>
> Giso
>
>
> Ben Bell wrote:
> > (Forwarding to ardour-dev rather than Paul directly)
> >
> > I've got a basic OSC based remote control capable of sending
> instructions
> > to the transport but really I'd like to get some feedback from Ardour
> and
> > do parameterised things like enable record on a given channel.
> >
> > Paul, you mentioned some example code you'd used to test the
> functionality.
> > If you can find it would you mind pointing me at it? I'm guessing that
> the
> > interface would be something like /ardour/track/<trackname>/rec_enable
> > and perhaps I'd be doing /ardour/track/<trackname>/receive_levels or
> > /ardour/track/<trackname>/<plugin>/receive_automations to register an
> > interest in various feedback parameters?
> >
> > Or am I barking up the wrong tree -- is this all intended but
> unimplemented
> > functionality? That's sort of what it looks like from the code but not
> > from what I thought you were saying on IRC.
> >
> > Final question: on the Tranzport. Is the conclusion that it is just not
> > possible to interfce with the wheel reliably from userspace or was there
> > a disagreement about whether it was appropriate? I'm toying with making
> a
> > Tranzport <-> OSC or Tranzport <-> MIDI thing but if the upshot of other
> > people's work is that it's going to be a PITA then I'll spend my limited
> > time on other things.
> >
> > bjb
> >
> >
> _______________________________________________
> ardour-dev mailing list
> ardour-dev at lists.ardour.org
> http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org
>



-- 
Michael David Taht
PostCards From the Bleeding Edge
http://the-edge.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ardour.org/pipermail/ardour-dev-ardour.org/attachments/20071106/9b3b67ad/attachment-0001.htm>