Re: [Traverso-devel] trying latest CVS

[Remon]

> Just tried the latest CVS version. it's all very nice!

Thanks :-)

> But it died with this when exiting:

On exit ? 
Hmmmm....

> Catched the SIGSEGV signal!
> Unable to process thread save adding/removing of object into audio
> processing execution path!
> This is most likely caused by the audiodevice thread (or Jacks' one)
> gone wild or stalled
> One issue could be that you are not running with real time privileges!
> Please check for this!
> To improve future program behaviour, please report this so we can sort
> out the problem!
>
> I've never actually used linux (my own computer) for this kind of audio
> work and i'm not sure how to run it with realtime privs (except running
> it as root, which I rather not)... Can anyone give me a hint? =)
> Anyhow, it shouldn't crash just because you don't run it with rt privs,
> right?

I think this message is a side effect of another problem, due the fact you get 
the SIGSEGV signal. Most likely due the signal handler interrupting the audio 
thread, traverso thinks something has gone wrong.
Did you use the alsa driver, or jacks one ?

Debian / Ubuntu use the modified pam module, which gives users in the group 
audio real time privileges, so normally it should work fine.
If that's not the case, then there are a number of ways to obtain realtime 
priveleges, but the easiest thing is to upgrade to a distro version with the 
modified pam :-)

Still weird you get a sigsegv on exit, is it reproducable ?


> Then some questions:
>
> - is all the available actions listed in the Q menu?

Yes, the Song menu is a little hard to open, need to find a way to make that 
easier ( you have to point to an area which isn't covered by 
tracks/audioclips)

> - is the curve view supposed to work?

Yes, < F2 >, and < F1 > to go back to edit view.

> - copying a clip should draw the clip while dragging it so you see where
> it goes..

Copy clip is a little broken I think, did it work for you ?
Might in fact be the problem of the sigsegv during exit.....


But you obviously have a point here. Painting the whole clip, or just its 
contour, what do you think ?


> - i think it would be good to always play from the work cursor when
> pressing SPACE, but continuing from last playpos when pressing something
> other... (you most often want to replay a part instead of continuing)

Anyone a suggestion on this one ?

> And, my main feature requests:
>
> - audio source and clip list/tree pane, where clips and whole files can
> be dragged and dropped onto tracks

I actually started on this, obviously since there is the audio sources/clips 
view, but making it work is a crime in Qt 4. The tree view classes, model 
view architecture, reimplementing tons and tons of functions, I just don't 
get it.
I would love if someone with more experience in this area could have a look to 
make it at least functional!
(the drag and drop for one)


> - "offline" processing of clip or whole track through external app
> (sox), as said before, it could be a *really* simple but powerfull
> dialog with a commandline entry where some variable is replaced by input
> and output file... a powerful tool for powerusers! ordinary users will
> have to wait until we make nice GUI frontends for sox and have working
> plugins.. =)

It would be very helpfull I think if you can describe what actions you have in 
mind, and what you expect to happen!
Some kind of pseudo code, then it should indeed be very easy to make that 
work.
(Qt has a special class for invoking commands out of the program, very easy to 
use!)


> - track/index marks in the songview, and ability to export whole song to
> a single WAV + TOC file for burning with CDRDAO (which is supported by
> k3b by the way, for you KDE folks... =)

Anything else ?
LOL

Yeah I know, and Nicola wants routing, plugins, subbuses, Niklas wants .... 
and what about me ? 
Let's make a deal, you guys donate xxxx euros, and I make it work for you real 
soon :D

Remon