> I think he meant using it for measuring the time between calls,
> in unixes we have gettimeofday for this, but in windows there isnt really
any way to do it, since there's no way to get high res timing beyond 10ms.
Actually there is (QueryHighPerformanceCounter). It's accuracy it's better
that
On Wed, 17 Apr 2002 01:14:28 +0200 (CEST)
Tim Goetze <[EMAIL PROTECTED]> wrote:
> xk wrote:
>
> >In Windows I use the rdtsc assembler instruction. It returns a 64 bit
> >integer (in EAX:EDX I think) which represent the amount of processors cycles
> >that have passed from the last reset. Computin
On Tue, 16 Apr 2002 09:34:21 -0400
Paul Davis <[EMAIL PROTECTED]> wrote:
> >I need to do some timing code - for some basic kind of sequencing..
> >Since ive not written this kind of stuff before, i'm unsure as to the best app
> >roach for accurate timing.
> >
> >I've played around with using sign
xk wrote:
>In Windows I use the rdtsc assembler instruction. It returns a 64 bit
>integer (in EAX:EDX I think) which represent the amount of processors cycles
>that have passed from the last reset. Computing the difference between two
>values and taking into account the freq of the CPU (you have
>one remark on the code paul posted: occasionally interrupts can be
>dropped if a higher priority thread is present on your system
>(RT audio on a single processor for example); so you cannot just
>assume time has advanced by 1 / rtc_frequency seconds per poll
>return.
the assumption in the cod
>In Windows I use the rdtsc assembler instruction. It returns a 64 bit
>integer (in EAX:EDX I think) which represent the amount of processors cycles
>that have passed from the last reset. Computing the difference between two
>values and taking into account the freq of the CPU (you have to figure i
Nick D wrote:
>On Tue, 16 Apr 2002 09:34:21 -0400
>Paul Davis <[EMAIL PROTECTED]> wrote:
>
>> >I need to do some timing code - for some basic kind of sequencing..
>> > [..]
>> >What approaches have people used, and how successful were they?
>>
>> poll(2) on /dev/rtc. You will need to be root, or
In Windows I use the rdtsc assembler instruction. It returns a 64 bit
integer (in EAX:EDX I think) which represent the amount of processors cycles
that have passed from the last reset. Computing the difference between two
values and taking into account the freq of the CPU (you have to figure it
ou
On Tue, 16 Apr 2002 09:34:21 -0400
Paul Davis <[EMAIL PROTECTED]> wrote:
> >I need to do some timing code - for some basic kind of sequencing..
> > [..]
> >What approaches have people used, and how successful were they?
>
> poll(2) on /dev/rtc. You will need to be root, or have CAP_RESOURCE,
> t
Frank Barknecht hat gesagt: // Frank Barknecht wrote:
> And without SuSE I think, ALSA would be as far as it is today.
ahm, I meant "wouldn't" of course.
--
Frank Barknecht
On Tue, Apr 16, 2002 at 01:27:49PM +, Nick D wrote:
> Hi all,
>
> I need to do some timing code - for some basic kind of sequencing..
> Since ive not written this kind of stuff before, i'm unsure as to the best approach
>for accurate timing.
>
> I've played around with using signals for thi
>I need to do some timing code - for some basic kind of sequencing..
>Since ive not written this kind of stuff before, i'm unsure as to the best app
>roach for accurate timing.
>
>I've played around with using signals for this - with setitimer(..) and then c
>atching the signal, but it doesnt look
On Tue, Apr 16, 2002 at 10:25:33AM +0300, Kai Vehmanen wrote:
> Did you issue 'guest' as the CVS password?
Wow, that's embarassing.
Thanks,
PW
Hi all,
I need to do some timing code - for some basic kind of sequencing..
Since ive not written this kind of stuff before, i'm unsure as to the best approach
for accurate timing.
I've played around with using signals for this - with setitimer(..) and then catching
the signal, but it doesnt l
On Tue, 16 Apr 2002 11:53:29 +0300
Juhana Sadeharju <[EMAIL PROTECTED]> wrote:
> >From:Nick D <[EMAIL PROTECTED]>
> >
> >Debian is, once you get used to it, probably the best OS in the world!
> [ ... ]
> >Yeah, the only problem is the 'stable' release is always way too old.
>
> I have ha
Hi Juhana,
Juhana Sadeharju hat gesagt: // Juhana Sadeharju wrote:
> I have had major problems with Debian:
> [installation probs]
Well, obviously you have been bitten by installar bugs. They are not
acceptable and should be fixed, maybe some of them are already. But
you also speak of a weak sp
>From: Nick D <[EMAIL PROTECTED]>
>
>Debian is, once you get used to it, probably the best OS in the world!
[ ... ]
>Yeah, the only problem is the 'stable' release is always way too old.
I have had major problems with Debian:
-Installer started installing from the network, even I had told
tha
On Mon, 15 Apr 2002, Paul Winkler wrote:
> I want to try ecasound with jack, but I find the 2.1dev7
> tarball won't build with latest jack cvs.
Yes, you need the CVS version. 2.1dev8 changelog has grown quite huge, but
as I'm still somewhat buried-alive-in-work, I haven't had time to release
it
18 matches
Mail list logo
