Re: [Lmuse-user] RT, Deicsonze Stuff

[Robert J. <rj...@sp...>]

Hi,

On Thursday 13 Apr 2006 18:13, Hiram Abiff wrote:
> Quoting Robert Jonsson <rj...@sp...>:
> > On Sunday 02 Apr 2006 16:19, Hiram Abiff wrote:
> >> Is deicsonze lacking the ability to save it's state
> >> or am I missing something?
> >
> > Unfortunately you are not missing anything... Our ambition was to bring
> > out MusE 1.0 already. Probably for this reason Nil moved the development
> > of Deicsonze to the 1.0 branch. This leaves us with the unfortunate
> > problem that there is a much more capable version of Deicsonze in cvs,
> > but it's not compatible with the current version of MusE.
>
> Sorry for the long delay, I've been really busy, was working the
> whole weekend, am dead tired.
>
> Concerning deicsonze, I hope it will function full bloom in the 1.0 version
> cause, like I said, in my opinion, it's a decent synth.

It's a very nice synth indeed.

>
> >> also, the sound from deicsonze occasionaly hangs and I get a ghost
> >> note constantly playing. I saw that others had this issue with the
> >> new release. I still get this with muse-0.8.1a. sometimes using
> >> the Reset/MIDI Instrument works, sometimes the ghost note stops
> >> when I select a different instrument in deicsonze and sometimes
> >> nothing helps so I have to restart muse alltogether.
> >
> > Sorry to hear that. For the moment all I can do is suggest you to use
> > another synth. ZynAddSubFX is a wonderful choice ;)
>
> well, I just bough a Yamaha DX7 vintage synth really cheap and am
> learning to use it's FM synthesis posibilities, I created some
> phatt sounds which I include in my first muse track. woot!

(-B

>
> >> 2. I cannot compile the new muse with --enable-rtcap. make goes fine and
> >> then after I issue "make install" at the end I get this:
> >
> > <...> error msg removed
> >
> >> if I do not pass --enable-rtcap to configure muse compiles ok.
> >> but then I have to start muse as root to enable RT capabilites.
> >
> > This is actually a misconception. rtcap is only valid for 2.4 kernels. If
> > I recall correctly you also need a patched kernel.
>
> I patched my kernel. hm.

Ah ;) No harm done I'm sure

>
> > I have to check our documentation on this, it's probably not uptodate.
> >
> >> I followed the instructions on
> >> http://www.muse-sequencer.org/wiki/index.php/Realtime-lsm_module
> >>
> >> but after doing all those things when I try to load the realtime module
> >> with "modprobe realtime" I get a message that there is no such module.
> >> I did a "make modules_install" at the end like it says in
> >> /usr/src/linux/.
> >
> > With realtime lsm I usually resort to copying it by hand ;) probably
> > not right
> > but it works
> >
> > if your kernel modules are in /lib/modules/2.6.666/
> > create a dir /lib/modules/2.6.666/extra and copy the realtime.ko
> > there and run
> > depmod -a
>
> ah so. I did it and now I can load realtime with depmod.
> the latency reported by jack is still 8ms with nrperiods=3 and

Unless you use a usb soundcard I think you should stick to periods=2

> frames 256. I still get periodic xruns. I don't know how much
> latency is still acceptable. I did some research on google
> but only found instructions on how to decrease latency that didn't
> specify how much is too much. I know this really isn't muse related and
> I'm being rude but I would be satisified if someone just answered
> this question and I will look for help somewhere else.

Unfortunately noone can tell you how much latency to have, this you have to 
work out yourself. Basically the latency we are talking about here is the 
time it takes for the audio to come out of the speakers from that you have 
played something. You have to decide how big latencies you can live with.
People playing church organ have to live with latencies of 0.5 seconds (or 
more!)
But basically, less is better. though the hardware+software has a limit. And 
for very low settings more cpu will be needed.

To get the lowest possible latency running 2.6, you need a recent kernel with 
preemption patch added, preferrably with the realtime choice selected I 
think.
For settings check out Florian Schmidts instructions:
http://tapas.affenbande.org/?page_id=3

>
> >> although when I run muse as root, RT seems to be working:
> >> ..
> >> Trying RTC timer...
> >> got timer = 12
> >> showMarker 1
> >> ..
> >>
> >> I run jackd with the -R option, which only works as root as well. This
> >> is a big pain in the ass and a security risk I presume. I set the
> >> permissions on the /dev/rtc device to be in the audio user group of
> >> which I am a member. what can be done to run muse and jack as a normal
> >> user?
> >
> > Try the above and let us know how it goes.
>
> so I did. muse runs fine now, it hasn't crashed in a while, though it
> spurts out some messages in the terminal I haven't managed to copy them,
> will do it when I see them again.

Ok, great.

Regards,
Robert

>
> thnx, robert.

-- 
http://spamatica.se/musicsite/