Subject: Sync'ing midi and audio (was RE: [linux-audio-user] Introduction)
From: Stuart Allie (Stuart.Allie_AT_hydro.com.au)
Date: Mon Jan 14 2002 - 23:42:47 EET
I have started collecting various apps and thinking about how to combine
them so I could have midi sequenced tracks combined with recorded audio. My
current plan of attack is very similar to Kai's, maybe using timidity or
iiwusynth as a midi-renderer. The weak point in the plan, as Kai points out,
is synchronizing midi sources with the recorded audio. I believe that
Guenther's xgmc does this to some extent, but I haven't looked at that yet.
So, does anybody have any suggestions, or references, as to how to go about
making timidity or iiwusynth render audio in a synchronized fashion? (Sync'd
with ecasound or whatever.)
Cheers,
Stuart
--------------------------------------
Dr Stuart Allie
Technical Programmer
Hydstra Pty. Ltd.
4 Elizabeth St, Hobart, Tasmania, 7004
Ph (03) 6230 5760
Fax (03) 6230 5363
Email : stuart.allie_AT_hydro.com.au
--------------------------------------
> -----Original Message-----
> From: Kai Vehmanen [mailto:kai.vehmanen_AT_wakkanet.fi]
> Sent: Monday, 14 January 2002 9:17 pm
> To: linux-audio-user_AT_music.columbia.edu
> Subject: Re: [linux-audio-user] Introduction
>
[snip]
> ... I'm the author of ecasound and ecawave, so I'm slightly partial
> here.:) Possibly the biggest limitation of this setup is that
> I need to
> divide the recording work into sequenced and nonsequenced
> phases. First I
> create the sequenced background parts, either with soundtracker or my
> hw-sequencer. When I'm pleased with the results, I record/render the
> sequenced parts to ecasound. Then starts the live-recording
> phase. Now the
> obvious problem is that after doing the shift, I can't go back to the
> sequenced material and change things.
>
> The above limitation seems like a big thing, but I had to do the same
> exact thing with analog multitrackers, so it's not something
> unheard of.
> And what's important, it works. I get basicly unlimited
> number of tracks,
> fast access to alternate mixes, very flexible effect setup, and even
> more importantly, with very little hassle (for me anyways).
>
> As for future plans, I'm most interested in solving the
> sequenced-vs-nonsequenced problem. Possible solutions:
>
> - MIDI synchronation -> ecasound driving a hw-sequencer; there's
> already support for some of the MTC/MMC functionality, but
> I haven't had
> time to test it much; Ardour has better support already in place,
> I'll intend to test that, too
> - inter-app connections; JACK is one possible solution here - by
> adding JACK support to for instance soundtracker, and transport
> control features to JACK, ta-daa, problem solved
> - hacking ... making a custom version of ttrk or possibly the
> new shaketracker (both tracker-style MIDI-sequencers) that
> is connected to ecasound - not very elegant, but possible and
> doesn't involve a lot of work
> - any ideas? :)
>
> One already working solution is to have the background parts as a
> soundtracker module, and use the module file as one ecasound
> input. This
> works (rendered w/ mikmod), but the quality is not the best
> (soundtracker
> is _much_ better at rendering mods than mikmod).
>
> --
> http://www.eca.cx
> Audio software for Linux!
>
This archive was generated by hypermail 2b28 : Mon Jan 14 2002 - 23:39:51 EET