> Thanks everyone for all the help on my architecture questions. It seems
> like a lot of the best practise functionality has tools/components for it
> already in Jack. I *was* planning on using rtaudio in order to be cross
> platform, but if it's a lot easier to get things done in Jack, i could
> live
> with being limited to linux and OS X.
>

Jack2 runs on windows too. Just that it hasn't seen as much adoption as
most of us round here refuse to work with MS tech unless paid a lot of
money to do so. Some of us just refuse outright. But Stephan and his team
have put in a lot of effort to make it work on MS platforms.

> Just wondered if I could poll opinions, for a real time step sequencer
> meant to do super tight timing and by syncable with other apps, is Jack
> going to be a lot easier to work with? Should I just lay into the jack
> tutorials?
>

It doesn't take long to get a jack app up and running. Its the front end
that will consume the vast majority of your time.

> And is it straightforward to use the perry cook stk in a jack app?
>

https://ccrma.stanford.edu/software/stk/usage.html

Several options can be supplied to the configure script to customize the
build behavior:

--disable-realtime to only compile generic non-realtime classes
--enable-debug to enable various debug output
--with-alsa to choose native ALSA API support (default, linux only)
--with-oss to choose native OSS audio API support (linux only, no native
OSS MIDI support)
--with-jack to choose native JACK API support (linux and Macintosh OS-X)
--with-core to choose Core Audio API support (Macintosh OS-X)



> thanks everyone
> iain
> _______________________________________________
> Linux-audio-dev mailing list
> Linux-audio-dev@lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-dev
>


--
Patrick Shirkey
Boost Hardware Ltd