Hello list...
I am curious to research further about MIDI timing and here is something
I want to ask...
I wonder, if we missed the (MIDI?) event a bit (perhaps 1 miliseconds?),
what would happen? I guess it will be underrun? Or technically, do we
determine a playback as "choppy" by calculating
On the other hand, last night I observed how timidity++ works by using
strace and I found no *sleep() (nanosleep, msleep and friends). Does it
mean, major MIDI software synthesizers use non system sleep mechanism
for the timing?
I believe Timidity++ just uses its synthesizer to convert the MIDI
Mulyadi Santosa wrote:
> I also read that not all Linux kernel sound card driver enable the
> internal card timer, thus the software must rely on system timer.
Most sound cards don't have an internal timer that could be used for
MIDI timing. ALSA uses whatever timer is configured, the default for
--- Stephen Sinclair <[EMAIL PROTECTED]> wrote:
[...]
>
> By the way, there are more ways to time things than just *sleep().
> For example, using sigalrm and setitimer.
>From the sleep(3) man page:
BUGS
sleep() may be implemented using SIGALRM; mixing calls to alarm() and
sleep()
Clemens:
> Most sound cards don't have an internal timer that could be used for
> MIDI timing. ALSA uses whatever timer is configured, the default for
> this is the RTC timer.
It is? For ALSA sequencer queues? I thought the
default was system timer. Maybe it just depends on
the modules you h
On Wed, 2006-10-25 at 15:05 +, Chris Cannam wrote:
> Clemens:
> > Most sound cards don't have an internal timer that could be used for
> > MIDI timing. ALSA uses whatever timer is configured, the default for
> > this is the RTC timer.
>
> It is? For ALSA sequencer queues? I thought the
> d
Chris Cannam wrote:
> Clemens:
> > Most sound cards don't have an internal timer that could be used for
> > MIDI timing. ALSA uses whatever timer is configured, the default for
> > this is the RTC timer.
>
> It is? For ALSA sequencer queues? I thought the
> default was system timer.
Since 1.0
Lee:
> This is/was a bug or multiple bugs in the kernel's RTC driver. It
> started to appear around 2.6.13 because that was the kernel release
> where they regressed the default timer granularity from 1ms to 2.5ms,
> forcing apps like Rosegarden to switch to RTC based timing.
No, it genuinely wen
Me:
> I'm not aware of anyone these days successfully
> using Rosegarden with snd-rtctimer - if anyone out
> there is, do say so.
To test:
* start RG (version 1.0 or newer)
* go to Settings -> Configure Rosegarden -> Sequencer -> Synchronisation
* change the sequencer timing source option to RTC
Me:
> No, it genuinely went from working to broken
And actually, I think my recollection is wrong. I think
it probably broke in 2.6.8-rt, and in mainline in either
2.6.9 or 2.6.10. Before that it worked fine, but we
always used the system timer instead for RG because it
seemed simpler (it wa
On Wed, 2006-10-25 at 16:42 +, Chris Cannam wrote:
> Me:
> > No, it genuinely went from working to broken
>
> And actually, I think my recollection is wrong. I think
> it probably broke in 2.6.8-rt, and in mainline in either
> 2.6.9 or 2.6.10. Before that it worked fine, but we
> always u
On Wednesday 25 October 2006 18:28, Chris Cannam wrote:
> Me:
> > I'm not aware of anyone these days successfully
> > using Rosegarden with snd-rtctimer - if anyone out
> > there is, do say so.
>
> To test:
>
> * start RG (version 1.0 or newer)
> * go to Settings -> Configure Rosegarden -> Sequence
On Wednesday 25 October 2006 15:19, Clemens Ladisch wrote:
> Mulyadi Santosa wrote:
> > I also read that not all Linux kernel sound card driver enable the
> > internal card timer, thus the software must rely on system timer.
>
> Most sound cards don't have an internal timer that could be used for
>
On Wed, 2006-10-25 at 16:28 +, Chris Cannam wrote:
> Success -> play pointer moves smoothly
> Failure -> system locks up solid, reboot required.
Success on Fedora Core 6 with the standard Fedora kernel, rosegarden4,
etc.
AG
14 matches
Mail list logo
