22 Jul
2010
22 Jul
'10
9:06 p.m.
Excerpts from Folderol's message of 2010-07-22 20:47:37 +0200:
On Thu, 22 Jul 2010 12:43:15 +0200
Pablo <pablo.fbus(a)gmail.com> wrote:
This is the workaround I've used as well, but it's a nuisance.
There was some talk a few years ago about the devs doing a 'proper'
jack implementation, but it seems to have fallen by the wayside.
B.T.W. looking around, I see a number of people are reporting the same,
or similar issues.
Up to now I've run away from using Ardour because it's severe overkill
for the audio work I do, and has a horrendously steep learning curve.
It looks like I might be forced to go that way after all :(
It's not like ardour is the only DAW around. Audacity is also not the
only editor around. Depending on your needs there is at least Traverso
(making huge progress in git), qtractor, ecasound, muse and some more on
the DAW front and mhwaveedit, rezound, snd and others on the editor
front. The best known one isn't necessarily the best one for any given
job.
--
Regards,
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und alle Fragen
offen." Bertolt Brecht, Der gute Mensch von Sezuan
> It usually has through portaudio, which seems to be broken by design
> with regards to jack. At least in audacity it only exposes jack ports
> and auto connects them to the first two ins and outs when transport is
> rolling.
>
I used to use this workaround: Roll the transport and then press
"||"
button. Jack ports will remain exposed so you can connect / disconnect
as you like. Then press "||" again to playback / record.
Regards, Pablo