On Jun 14 11:54:07, Jacob Meuser wrote:
> On Mon, Jun 14, 2010 at 11:09:12AM +0200, Jan Stary wrote:
> > On Jun 13 23:51:25, Jacob Meuser wrote:
> > > On Sun, Jun 13, 2010 at 10:13:35PM +0200, Jan Stary wrote:
> > > > On Feb 03 15:43:14, Jacob Meuser wrote:
> > > > > On Wed, Feb 03, 2010 at 12:06:20PM +0100, Jan Stary wrote:
> > > > > > Jacob,
> > > > > >
> > > > > > firstly, thank you for all the audio work you do on OpenBSD.
> > > > > > You are turning my laptop into the best audio workstation I have.
> > > > > >
> > > > > > Right now, I am trying to use audacity as packaged in 1.3.9.p0
> > > > > > on a recent -current.
> > > > >
> > > > > yes, audacity is , shall I say, quirky, and not necessarily in a
> > > > > good way.
> > > > >
> > > > > http://jakemsr.trancell.org/liblo-0.26-port.tgz
> > > > > http://jakemsr.trancell.org/liblrdf-0.4.0-port.tgz
> > > > > http://jakemsr.trancell.org/ardour-2.8.4-port.tgz
> > > > > http://jakemsr.trancell.org/jack.diff
> > > > >
> > > > > I plan to get that all committed (plus lmms, updates for ladspa and
> > > > > more modules) shortly after ports unlock.
> > > >
> > > > When this mesaage was recent, I downloaded and built these.
> > > > However, liblo, liblrdf and ardour still don't seem to be
> > > > in the current ports tree. Is there another place to get more
> > > > recent versions (beside the source)? The above links
> > > > don't work anymore.
> > > >
> > > > More generally, what is the status of ardour now?
> > >
> > > it's waiting at least until i386 switches to gcc4. then I'll
> > > reevaluate if it's worth pursuing again. unfortunately, while
> > > I can get it *mostly* working, it has some issues (in complicated
> > > C++ code I don't yet 100% understand) that make it annoying to
> > > use. as in, it usually crashes at least once trying to do basic
> > > import/editing/export. crashes in the import/exportstage are
> > > really super annoying, since I can edit fine :/
> >
> > Same here. I can record, mix, and edit a 20-track session,
> > but then an attempt to export it makes ardour freeze and
> > _jack_ dumps core (destroying the feeling of artistic achievement).
> > That happens with any export parameters.
>
> it has worked for me with UP kernels, but I've never had it work with
> MP kernels.
Will try, thanks for the hint.
> export uses jackd in "freewheel" mode. afaics, it doesn't know when
> it should stop processing.
Yes. The moment an export is started, [someone: ardour?] says
(in the xterm I started ardour from)
Start export at pos = 0
Everybody is at 0
The moment it gets to the 'end' marker (as recognized by ardour)
it says
Export ... not running or at end, no_roll() for 1024.
1024 is the buffer size I specified (just agreed to, really) when
starting ardour. Now ardour freezes and ps(1) says it's a zombie.
Ardour and jack togehter eat up the CPU. If I kill ardour (via Ctrl-C),
[someone: jack?] says
subgraph starting at ardour timed out
(subgraph_wait_fd=14, status=0, state=Triggered, pollret = 0
revents = 0x0)
process cycle within freewheel failed
and jack dumps core.
> > Meanwhile, what are people using as their semi-pro multitrack
> > recording software? (Please don't say audacity.)
>
> well, you can do the actual recording and basic mixing with aucat.
I do, either with aucat or sox. But for some real mixing it's kinda limited.
For, say, more than four tracks, it quickly becomes a pita to specify
relative volumes and pan positions with numbers on the cmd line etc.
> but yes, there isn't much choice for full-featured post-processing.
Fsck that, I'm gonna buy a Mac ("artists" use "macs", right?)
and buy ProTools. (Just kidding).
Jan
