Re: [Dino-list] working dino?

[Lars Luthman]

On Thu, 2010-01-28 at 14:14 +0200, Marius Stoica wrote:
> Hi,
> 
> I managed to complie dino on puppy linux 431 with jack 0.118.0 and
> lash 0.5.4 (using the 0.2.2 tarball patched for the 27510 bug)
> dino starts ok, lash works fine also, but jack transport is stuck
> (because of dino). 
> I can see in qjackctl that the bpm is 0 and any change made in dino
> for the bpm wil give an abnormal
> number in qjackctl and the transport remains stuck.
> I believe this has something to do with the jack transport code in
> dino, maybe it must be updated to the latest jack api.

I can't reproduce this - I built the latest code from the 0.2 Git branch
from scratch, and the transport seems to work. QJackCtl shows the tempo
as 100 BPM when Dino is started, and I can play and pause both in Dino
and QJackCtl and change the tempo in Dino. I have the same versions of
JACK and LASH as you do (latest in Debian Testing).

Have you tried multiple times? Does the bug always happen?


> I also tried to compile from svn and got this error:
> # make
> Generating dependencies for src/libdinoseq/track.cpp.....
> Merging dependencies....
> g++ -c -o src/libdinoseq/track.o -fPIC -DPIC -g -O2  `pkg-config
> --cflags libxml
> ++-2.6 jack` src/libdinoseq/track.cpp
> src/libdinoseq/track.cpp:1178: error: expected constructor,
> destructor, or type conversion before '<' token

You mean from Git, right? There is no SVN repository as far as I know.

This is probably because of a namespace collision (sigc::signal
vs ::signal). The code in the master branch in the repository at
Savannah is pretty much abandoned, I'm doing a complete rewrite in my
local repository. The only reason I haven't pushed it to Savannah yet is
because I wanted to have something buildable there, but if the master
branch doesn't even build I might as well just overwrite it.

Even if it built the code in the Git master branch at Savannah is not in
a usable state. 
> Is there any way to have a working dino?

The latest 0.2 code _should_ work. It works for me. Are you sure you
don't have something strange going on with your system, such as multiple
versions of JACK installed? Incompatible jackd/libjack versions is the
only reason I can think of right now that would cause the type of
problems you describe.


--ll

signature.asc
Description: This is a digitally signed message part