On Mon, 22 Nov 2004, Uwe Koloska wrote:
Matthias Nagorni wrote:
Exactly: If you set
CONFIG_HPET_RTC_IRQ=n
and recompile the (SuSE 9.2-)kernel, MusE should work.
And why is it set? Normally there is a reason for doing something ;-) Will
this changed setting affect other
Lee Revell wrote:
OK this all looks good. I don't know, it sounds like a bug in Muse.
There must be some incompatibility using a binary Suse Muse package with
a Mandrake kernel.
I don't think so -- I have a SuSE 9.2 and this means SuSE kernel
with SuSE MUSe ;-)
Try a newer version of Muse.
On Sun, Nov 21, 2004 at 03:02:24PM -0500, Lee Revell wrote:
CONFIG_APM_RTC_IS_GMT=y
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
CONFIG_HPET_RTC_IRQ=y
CONFIG_SENSORS_RTC8564=m
CONFIG_SND_RTCTIMER=m
OK this all looks good. I don't know, it sounds like a bug in Muse.
There
On Mon, 22 Nov 2004, Alfons Adriaensen wrote:
On Sun, Nov 21, 2004 at 03:02:24PM -0500, Lee Revell wrote:
CONFIG_APM_RTC_IS_GMT=y
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
CONFIG_HPET_RTC_IRQ=y
CONFIG_SENSORS_RTC8564=m
CONFIG_SND_RTCTIMER=m
OK this all
Matthias Nagorni wrote:
Exactly: If you set
CONFIG_HPET_RTC_IRQ=n
and recompile the (SuSE 9.2-)kernel, MusE should work.
And why is it set? Normally there is a reason for doing something
;-) Will this changed setting affect other settings, scripts,
programs, etc.???
Uwe
--
voiceINTERconnect
On Monday 22 November 2004 16.33, Matthias Nagorni wrote:
On Mon, 22 Nov 2004, Alfons Adriaensen wrote:
On Sun, Nov 21, 2004 at 03:02:24PM -0500, Lee Revell wrote:
CONFIG_APM_RTC_IS_GMT=y
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
CONFIG_HPET_RTC_IRQ=y
On Mon, Nov 22, 2004 at 06:13:22PM +0100, Robert Jonsson wrote:
Ah, good with conclusive proof.
In the meantime I found out about the timer features of ALSA.
http://www.alsa-project.org/alsa-doc/alsa-lib/timer.html
Unless I'm missing something (which I very well might be) it seems to work
Alfons Adriaensen wrote:
the ALSA sequencer API seems to allow *timestamped* events - you put such
an event in a queue and it will appear at the other end at the right moment.
If this is true,
It is.
and if ALSA has an high precision timer available to implement it,
Standard 2.4 kernels
(added alsa-devel to cc)
On Mon, 2004-11-22 at 18:53 +0100, Alfons Adriaensen wrote:
Which leads to the following question I've been asking myself for some time:
the ALSA sequencer API seems to allow *timestamped* events - you put such
an event in a queue and it will appear at the other end
At Mon, 22 Nov 2004 13:21:07 -0500,
Lee Revell wrote:
(added alsa-devel to cc)
On Mon, 2004-11-22 at 18:53 +0100, Alfons Adriaensen wrote:
Which leads to the following question I've been asking myself for some time:
the ALSA sequencer API seems to allow *timestamped* events - you put
the ALSA sequencer API seems to allow *timestamped* events - you put such
an event in a queue and it will appear at the other end at the right moment.
If this is true, and if ALSA has an high precision timer available to
implement it, why should apps like MusE bother to do the fine timing
On Mon, Nov 22, 2004 at 01:21:07PM -0500, Lee Revell wrote:
Yes, my thoughts exactly. You don't even have to use the ALSA sequencer
API, you can use the ALSA timer API directly. You get multiple timer
sources (system, RTC, sound card). It should also be more portable.
Yes, but using the
On Mon, 2004-11-22 at 19:54 +0100, Takashi Iwai wrote:
Yes, I agree that ALSA timer API would be useful for such a case. The
app can reject to run or do some workaround if the queried timer
resolution is worse than requirements.
Well, my guess for the next reaction is the lack of
On Mon, Nov 22, 2004 at 07:00:59PM -0500, Paul Davis wrote:
how far ahead can you queue without getting into trouble when the user
does realtime edits?
think about this for long enough, and i think you will come to same
conclusion: deliver events in a process-callback-style fashion, more
enter as root
echo 1024 /proc/sys/dev/rtc/max-user-freq
this allows users to set rtc frequencies up to 1024 Hz
/werner
On Saturday 20 November 2004 21:59, Uwe Koloska wrote:
Hello,
now that my audio inteerface is working, I can try the wealth of audio
applications.
Starting the
Hi Werner,
söndagen den 21 november 2004 14.16 skrev Werner Schweer:
enter as root
echo 1024 /proc/sys/dev/rtc/max-user-freq
I had tried that previously, tried it again and it does not work for me
atleast.
this allows users to set rtc frequencies up to 1024 Hz
Right, and since
On Sun, 2004-11-21 at 18:06 +0100, Robert Jonsson wrote:
Hi Werner,
Is this a custom compiled kernel or a binary? What is the output of:
zgrep RTC /proc/config.gz
?
Lee
söndagen den 21 november 2004 19.39 skrev Lee Revell:
On Sun, 2004-11-21 at 18:06 +0100, Robert Jonsson wrote:
Hi Werner,
Is this a custom compiled kernel or a binary?
It's the standard Mandrake 10.1 kernel, haven't started with lowlatency tuning
yet.
What is the output of:
zgrep
On Sun, 2004-11-21 at 20:25 +0100, Robert Jonsson wrote:
söndagen den 21 november 2004 19.39 skrev Lee Revell:
On Sun, 2004-11-21 at 18:06 +0100, Robert Jonsson wrote:
Hi Werner,
Is this a custom compiled kernel or a binary?
It's the standard Mandrake 10.1 kernel, haven't started
Hi all,
[OFF-TOPIC]
On Sun, 21 Nov 2004 15:02:24 -0500
Lee Revell [EMAIL PROTECTED] wrote:
OK this all looks good. I don't know, it sounds like a bug in Muse.
There must be some incompatibility using a binary Suse Muse package with
a Mandrake kernel.
Has anyone noticed how cute it sounds
Hi Uwe,
lördagen den 20 november 2004 22.59 skrev Uwe Koloska:
Hello,
now that my audio inteerface is working, I can try the wealth of audio
applications.
Starting the SuSE supplied muse (0.7.0) it refuses to start cause it cannot
use /dev/rtc. Since I used the audio group also for
21 matches
Mail list logo
