Re: [linux-audio-dev] Re: [linux-audio-announce] gmorgan-0.06
Hi! I hate to write this in english because i dont know if i can explain what i meant. On Viernes, 25 de Julio de 2003 01:26, Thierry MARX wrote: > Sorry to tell you that... But try to tell us your progress only on major or > semi major updates... There is no need to tell that you have understood how > to make a Makefile : ).Post Only when you got something working good and > not only plaining somethin or debugged something minor... Sorry .. no more posting announces, yes you rigth, maybe i confused this mailing list with my program mailing list, and yes now i know how to do a Makefile ... a big step for me ... but i really think that i will never do something good ... sorry, then no more posting. >Your product will be much more appreciated ;) Sorry but i cant understand why I made all this things with illusion, not with knowledge, and i dont want lie to anyone. I made the the programs not for people appreciate, i made for people use. > If you have any question tell this mailing about help but don't take us for >fool who don't know how sounds works. > > On Wed, 23 Jul 2003 21:06:08 +0100 > > holborn <[EMAIL PROTECTED]> wrote: > > News on v0.06 > > - > > - Finally solved problem with CPU user system time. > > - Program runs with 2 threads less. > > - Added FIFO priority and memory lock. > > - Added Clear Bar in Pattern window edit for Bass,Acc1,Acc2 and Acc3. > > - Added small Help window in Pattern window edit. > > - Added Preset List Editor. > > - Added Note Drum Name Editor. > > - Added Program Change Slider. > > - Added "safe" Mode 2 for melodic accompaniments. > > - Added Patterns. > > - Minor bugs solved. > > -- 2 days work, alone with beer? ;) -- No ... one month reading ... maybe reading not understanding ... about threads .. asking here ... and not here ... about why my program eats 100% of system user time and sorry i dont read your reponse ... and yes, you rigth, there are small changes in the program, but maybe usefull if someone use itbut you rigth again ... that's not the place to announce. Maybe will be better speak about if New Age is satanic music . sorry Paul .. you know you are my hero. :) Sorry but i have a big respect for all the people here all of you knows about sound, programming etc ... what i will never know. All ...sorry again for the spam and thanks. Josep
Re: [linux-audio-dev] calling all planet ccrma users ...
> >Don't run up2date, just use apt. There should be a full set of updates > >for redhat in the apt index on CCRMA's servers. > > > >apt-get update > >apt-get dist-upgrade > > > >Do this in between the "install apt on your RH box" and "install Planet > >CCRMA magic kernel RPM package" steps. > > yes, but i'm connected to CCRMA by a 56kB dialup, and using apt for > this is not really feasible ... i've collected all the pieces i need > for ardour step by step, and eventually i'll use a friend's cable > modem to get the ISO's. A cable modem is your friend (or is it the other way around?). Planet CCRMA does not really work over dialup unless you are VERY patient... -- Fernando
Re: [linux-audio-dev] calling all planet ccrma users ...
> >From looking at the date I'd guess it comes from up2date, which is > >included in planet. > > yeah, but you can't use up2date on a machine not connected to the > internet. so a machine configured without being updated (i.e. not > really 8.0 anymore) doesn't have glibc 2.3. i supposed RH are defining > 8.0 as "8.0 plus any updates we say are part of 8.0 ...". sigh. Hmmm, no, I sort of define it that way because I build all new packages with all the redhat updates installed (up to that point in time). You do not really need to have network connectivity for the updates if you dowload the updates iso cdrom for rh8, it should include all the needed stuff. > i rebuilt the RPMs from nando's SRPMs. > > and now i just found out that i have a brand new Hammerfall DSP with a > revision number not recognized by the driver. this means i would have > to install the entire kernel source RPM (27MB!) from the planet, plus > the alsa kernel SRPM, edit the source code, and then rebuild ALSA (you > can't rebuild ALSA without the relevant kernel source installed). sigh > again, doubled. Welcome to the club! (of people rebuilding things for the nth time and saying "sigh"...) > still, at least i can justify being paid to do this :) and i have to > say that the Linux Audio Systems splash screens for Grub and for GDM > look pretty nice! i get a warm feeling inside seeing these things on > such a superb machine :) > > i guess i should get it connected to the net, and run up2date as well, > eh? Or point to the Planet CCRMA repository and get the updates from there. All the same. -- Fernando
[linux-audio-dev] Re: [linux-audio-announce] gmorgan-0.06
Sorry to tell you that... But try to tell us your progress only on major or semi major updates... There is no need to tell that you have understood how to make a Makefile : ). Post Only when you got something working good and not only plaining somethin or debugged something minor... Your product will be much more appreciated ;) If you have any question tell this mailing about help but don't take us for fool who don't know how sounds works. On Wed, 23 Jul 2003 21:06:08 +0100 holborn <[EMAIL PROTECTED]> wrote: > News on v0.06 > - > - Finally solved problem with CPU user system time. > - Program runs with 2 threads less. > - Added FIFO priority and memory lock. > - Added Clear Bar in Pattern window edit for Bass,Acc1,Acc2 and Acc3. > - Added small Help window in Pattern window edit. > - Added Preset List Editor. > - Added Note Drum Name Editor. > - Added Program Change Slider. > - Added "safe" Mode 2 for melodic accompaniments. > - Added Patterns. > - Minor bugs solved. -- 2 days work, alone with beer? ;) --
Re: [linux-audio-dev] kernel 2.6
On Jueves, 24 de Julio de 2003 17:46, Michael Ost wrote: > Is there SCHED_FIFO style priority available in the new kernel, with its > new threading model? Realtime audio processing doesn't share the CPU > very well. The ear can pick out even the slightest glitches or delays. > So for Linux to be usable for audio applications or embedded audio > devices it needs something like SCHED_FIFO. > > On Thu, 2003-07-24 at 06:03, Tim Hockin wrote: > > All, > > > > I haven't used kernel 2.5/2.6 for any audio stuff yet. I'm at the Linux > > Symposium this week - do we have any requests or gripes with 2.6 that I > > can relay to the core kernel guys? Audio is a workload they don't really > > test. > > > > Tim Hi! p9:/home/holborn/gmorgan/src# uname -a Linux p9 2.6.0-test1 #5 mié jul 23 10:40:31 BST 2003 i686 GNU/Linux p9:/home/holborn/gmorgan/src# ./gmorgan -l MisStyles.gms -b MisProgs.gmo -r MisPat.gmp gmorgan v0.07 - Copyright (c) 2003 Josep Andreu (Holborn) SCHED_FIFO SCHED_FIFO p9:/# ps wlaxO+y F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTYTIME COMMAND 4 0 9375 5689 -51 0 31884 31880 schedu SL pts/1 0:01 ./gmorgan -l MisStyles.gms -b MisProgs.gmo -r MisPat.gmp 5 0 9377 9376 -51 0 31884 31880 snd_se SL pts/1 0:00 ./gmorgan -l MisStyles.gms -b MisProgs.gmo -r MisPat.gmp Here runs i think :) debian sid. Josep
Re: [linux-audio-dev] kernel 2.6
Is there SCHED_FIFO style priority available in the new kernel, with its new threading model? Realtime audio processing doesn't share the CPU very well. The ear can pick out even the slightest glitches or delays. So for Linux to be usable for audio applications or embedded audio devices it needs something like SCHED_FIFO. On Thu, 2003-07-24 at 06:03, Tim Hockin wrote: > All, > > I haven't used kernel 2.5/2.6 for any audio stuff yet. I'm at the Linux > Symposium this week - do we have any requests or gripes with 2.6 that I can > relay to the core kernel guys? Audio is a workload they don't really test. > > Tim
Re: [linux-audio-dev] kernel 2.6
On Thu, Jul 24, 2003 at 06:03:33AM -0700, Tim Hockin wrote: >I haven't used kernel 2.5/2.6 for any audio stuff yet. I'm at the Linux >Symposium this week - do we have any requests or gripes with 2.6 that I can >relay to the core kernel guys? Audio is a workload they don't really test. I'm not an expert at all, but I guess with the pre-empt patches in and Andrew Morton's low latency patches, we are ok in the latency department ? We should (*should* cause we didn't test it yet) be ok wrt. latency, as I hope that there are no more long held locks and most of the big kernel lock is gone. Any other things we can come up with ? v
[linux-audio-dev] kernel 2.6
All, I haven't used kernel 2.5/2.6 for any audio stuff yet. I'm at the Linux Symposium this week - do we have any requests or gripes with 2.6 that I can relay to the core kernel guys? Audio is a workload they don't really test. Tim
Re: Redhat9/NTPL/SCHED_FIFO (Re: [linux-audio-dev] some interesting docs for 2.6 testers...
The person to ask would be Fernando from CCRMA, I have an RH9 lowlat machine, and I haven't noticed any problems, but I cant run that machine at very low latencies anyway due to soundcard suckiness. I think I would have noticed if SCHED_FIFO was just ignored. - Steve On Thu, Jul 24, 2003 at 02:05:35 +0200, Kjetil S. Matheussen wrote: > > This is something I'm wondering about as well. I'm a system administrator > for 8 linux audio workstations, and the university wants us to switch > to redhat 9 (which use ntpl) before the end of the year. If redhat9 doesnt > support SCHED_FIFO, I won't do that, and should tell the university as > soon as possible.
Redhat9/NTPL/SCHED_FIFO (Re: [linux-audio-dev] some interesting docsfor 2.6 testers...
This is something I'm wondering about as well. I'm a system administrator for 8 linux audio workstations, and the university wants us to switch to redhat 9 (which use ntpl) before the end of the year. If redhat9 doesnt support SCHED_FIFO, I won't do that, and should tell the university as soon as possible. On 23 Jul 2003, Michael Ost wrote: > Is anyone seeing problems with SCHED_FIFO thread priority and the new > threading model in the 2.5/2.6 kernel? I read that the mode isn't > supported. But it (or something that works like it) is fundamentally > important to my Linux audio application. My audio thread has gotta have > uninterrupted, top priority scheduling. > > There was the start of a thread on this on this mailing list about a > month ago, but I didn't see many follow up messages. Perhaps some of you > who are trying to use the new kernel have some information to share. > > Thanks... mo > > === > Michael Ost, Software Architect > Muse Research, Inc. > [EMAIL PROTECTED] > > On Wed, 2003-07-23 at 09:54, Werner Johansson wrote: > > I'll give it another shot then, disabling the kudzu-probing (using an Emagic > > 2|6 USB audio interface on the audio box, so no fancy probing necessary)... > > > > Has anyone successfully compiled a recent 2.5 kernel using gcc 3.2-7 (Redhat > > 8)? I read some warnings about broken kernel optimizations with gcc 3.x - > > but that might have been resolved long time ago? I will start digging into > > this and see what works, audiowise. > > > > /Werner > > > > - Original Message - > > From: "Joern Nettingsmeier" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, July 23, 2003 9:48 AM > > Subject: Re: [linux-audio-dev] some interesting docs for 2.6 testers... > > > > > > > Werner Johansson wrote: > > > > Hi! > > > > > > > > I've been doing some early 2.5 tests, but as I'm running RH8 with the > > Planet > > > > on top of it there seem to be some problems actually building a 2.5 > > kernel > > > > (the linked texts here mention optimization problems with the default > > > > RH-shipped gcc as one). So far I haven't been able to boot the 2.5 > > kernels > > > > properly (yes I have the console working, and the new modutils). Is > > there > > > > anything like a FAQ somewhere as how to actually build a kernel that > > would > > > > play nicely with a stock RH8 system including Planet CCRMA on top, or do > > I > > > > have to redo everything from scratch? > > > > > > first of all, you should refer to Documentation/Changes in the kernel > > > source tree and make sure all your userspace tools are up to date (the > > > most critical being the modutils). > > > then you could look at the .config file for the redhat kernel and mimick > > > the configuration for 2.5 (where applicable). expect some things to > > > break, though. i usually only do it to the point where the system works > > > for me and ignore any further boot-time error messages from init scripts > > > that miss some modules etc. > > > > > > disabling hardware scanning seems to help a lot - when i tried the new > > > kernel on my powerbook running yellowdog, i had to disable kudzu (the > > > hardware scanning tool). > > > > > > > > > > /Werner > > > > > > > > - Original Message - > > > > From: "Joern Nettingsmeier" <[EMAIL PROTECTED]> > > > > To: <[EMAIL PROTECTED]>; "ALSA development" > > > > <[EMAIL PROTECTED]> > > > > Sent: Monday, July 21, 2003 8:36 PM > > > > Subject: [linux-audio-dev] some interesting docs for 2.6 testers... > > > > > > > > > > > > > > > >>hello everyone! > > > >> > > > >>if you are thinking about testing the new 2.6-pre kernels (which would > > > >>be helpful to shake out problems with typical audio-workloads that might > > > >>not get tested by others), here are two links worth a read (found on > > > >>lwn.net): > > > >> > > > >>* the 2.5 "what to expect" document by dave jones: > > > >> http://lwn.net/Articles/39901/ > > > >> > > > >>* the wonderful world of linux 2.6 by joe pranevich > > > >> http://www.kniggit.net/wwol26.html > > > >> > > > >>best, > > > >> > > > >>jörn > > > >> > > > >> > > > >>-- > > > >>All Members shall refrain in their international relations from > > > >>the threat or use of force against the territorial integrity or > > > >>political independence of any state, or in any other manner > > > >>inconsistent with the Purposes of the United Nations. > > > >>-- Charter of the United Nations, Article 2.4 > > > >> > > > >> > > > >>Jörn Nettingsmeier > > > >>Kurfürstenstr 49, 45138 Essen, Germany > > > >>http://spunk.dnsalias.org (my server) > > > >>http://www.linuxdj.com/audio/lad/ (Linux Audio Developers) > > > >> > > > >> > > > >> > > > >> > > > >> > > > > > > > > > > > > > > > > > -- > > > All Members shall refrain in their international relations from > > > the threat or use of force against the territorial integrity or > > > political independence of any state, or in any other manner > > > inconsistent w
