[ardour-dev] feature request; Monitoring Instrument Audio while Recording its MIDI Note Data

[Mark Knecht]

In general I think I agree but I would suggest a possible take a look
at Rosegarden, over even a conversation with Chris, might be in order.
They went through this about 3-4 years ago. There are a LOT of studio
level issues about how MIDI hardware is hooked up, whether you are
using external MIDI routers, whether your MIDI network has potential
loops, whether the MIDI keyboard is the MIDI sound source and where in
that network your sequencer is sitting, whether there is less audio
latency doing it one way or the other, and many more. All of these
combined together drive where you want to break loops.

Keep in mind that if you were using a MIDI processor LADSPA plugin to
modify things like velocity in real-time then you might have to use
the output from your sequencer.

It's not always easy to guess which is best. My experience suggests
things are sometimes different for MIDI keyboards vs. MIDI drums, etc.

Best to provide LOTS of flexibility in this area and let the studio
decide how to make it work best with their hardware. (IMO)

- Mark

P.S. - Ron, I cannot say how many times I've thought about you over
the last 6-8 months and wondered how you were doing. While I suspected
you were lurking on the IRC it's great to see you post here! - MWK

On 7/3/07, R Parker <rtp405 at yahoo.com> wrote:
> Hi,
>
> This is mostly for David R. Disclaimer: the request is
> either A, early B, late or C, just in time...your the
> judge. :)
>
> Monitoring Instrument Audio while Recording its MIDI
> Note Data
> This is a request to have record enabled sequencer
> tracks turn off, or mute, the MIDI output port. The
> idea is two fold; A, prevent the sequencer from
> sending data that's being recorded back to the source
> instrument which causes an audible slapback and B, use
> the instruments audio outputs for low latency
> monitoring.
>
> Benfits
> Not sending sequencer data through the record enabled
> MIDI track output is superior to the standard solution
> where a musician turns off Local Control by manually
> paging through menus at the instrument because it's
> automatic. Muting data output puts the engineer in
> control and enables them to record audio and midi data
> similtaneously with out interrupting the flow of a
> session. Musicans need to focus on their performance
> and not monitoring issues or anything else. Leaving
> Local Control on at the instrument is similar in idea
> and the equivalent of low latency hardware monitoring.
>
> To the best of my knowledge, limited in the sequencing
> realm, there is no drawback to this method. It is much
> less disruptive to the flow of a session than the
> Local Control On/Off solution. It's hard to imagine
> why it's not being done this way in the couple
> sequencers I've been exploring.
>
> parker
>
> Build a man a fire and he'll be warm for a night. Set a man on fire and he'll be warm for the rest of his life.
>
>
>       ____________________________________________________________________________________
> Luggage? GPS? Comic books?
> Check out fitting gifts for grads at Yahoo! Search
> http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz
> _______________________________________________
> ardour-dev mailing list
> ardour-dev at lists.ardour.org
> http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org
>