[Protux-devel] RTS problems

[Remon Sijrier]

I've run mplayer on this computer but don't know if it was with RTS or not. 
But I didn't have problems (audio dropouts) with mplayer, and I can't get 
ardour at work here :-( (jack installation problems)

> This is strange, I have been using in RTC *all the time*, and it is pretty
> normal and stable here. But when I set setuid , I indeed get some crashes.
> Only running as root seems to make it run smoothly.

Do you mean, that protux isn't running smoothly with SUID?

> Running in real time is a requirement to get low latencies.  

Of course, but it shouldn't crash the program or freeze your computer ;-P


>So I suggest you to check what happens
> with other applications that use real time scheduling, such mplayer or
> ardour.
Ehm, the only program I know of which use RTS on my computer is the artsd . 
And that app. is running fine, but I don't know if it's running "almost" RT 
or RT.

I compiled MADM with param.sched_priority =  80 (min = 1, max = 99), and 
everything is fine now even if I use the same testcase:

Compiling Protux, running protux, recording audio and using Vertical Zoom like 
an idiot :-)
Result: No xruns at all, and protux running rock stable, hehehe

As far as I understood, running a process with Real Time Priority is a risky 
thing. And running it with "almost" Real Time Priority give the same results, 
but (on my computer): "no deadlocks" in the kernel or something else freezing 
my whole computer.

And low latencies has also much to do with the kernel, using an preemptive 
kernel is also a big step forward in having low latencies. The good news is, 
that within a few months we can use kernel 2.6.x which is even preemtable in 
the kernel itself.

Only thing I can say is, just give it a try and use priority = 80 (or somewhat 
lower/higher) and see what happens if you put a real high load on your CPU, 
and do not use a higher priority then necessary.

Can somebody help me with this:
Where can I set the width for the TPA??
Thanks :-)

Remon

>
> On Tuesday 09 September 2003 07:25, Remon Sijrier wrote:
> > Luciano,
> >
> > I've send this mail allready yesterday, but it seems my mail client
> > wasn't properly configured.
> > If you receive the old mail, ignore it and read this one instead please.
> >
> > <snip from old mail>
> > Just to let you know, I compiled the latest libmustux with the 'realtime
> > scheduling', and used SUID to set protux execution with root permission
> > to enable RTS.
> >
> > It locked up my computer twice  :-(, and the only thing I could do was
> > rebooting, ending up with a corrupted file-system. *sigh*
> > There was a high CPU load (compiling protux, and using protux with RTS at
> > the same time) and thats probably why it all goes wrong. But it shouldn't
> > have happened!!
> >
> > I'll spare you the details getting my system up and running again, but I
> > strongly suggest to not use RTS but only a HIGHER scheduling priority
> > (Not realtime)
> > </snip>
> >
> > I'm using Debian unstable, and Qt3.2.1 is now the qt version in unstable.
> > So I'm using this version now.
> > I'll do some experimenting with QThread::Priority() to see if it works,
> > I'll let you know about my experiences with this.
> >
> > I've the feeling Qt3.2 is faster at least for drawing text, and also
> > repainting the Widget seems faster.
> > Only small problem for now, is that the TrackPanelArea is to width again.
> > Where can I set the width for the TPA??
> > Don't know if this has something to do with this qt version or not.
> >
> > That's it for now,
> >
> > Greetz and enjoy using this (almost) rock stable dev. version of protux
> > ;-)
> >
> > Remon
> >
> > On Monday 08 September 2003 22:33, Luciano Giordana wrote:
> > > This release has almost-only remons work in protux and more
> > > improvements I did in MADM. Remon's work has no changelog (yet, right
> > > Remon ;-) ) so I plan to add a summary in changelog soon
> >
> > _______________________________________________
> > Protux-devel mailing list
> > address@hidden
> > http://mail.nongnu.org/mailman/listinfo/protux-devel