| Yes, it works without any problems from the command line or from the
jEdit console.
The messages about the cpu usage are:
Running from the Terminal: real: 5.437s, CPU: 0.670s
Running from qutecsound: real: 9.721s, CPU: 9.770s
Is this working on your machine? What can be the reason for such a
cpu usage?
I'm attaching the messages, if you like to compare them.
Best -
joachim
Am 24.09.2008 um 16:06 schrieb Andres Cabrera:
> Hi,
>
> Thanks for the report. You may need to adjust the buffer size. Does
> the file work OK from the command line with the same options? (see the
> Console for the exact command line that QuteCsound is using)
>
> Cheers,
> Andrés
>
> On Wed, Sep 24, 2008 at 12:49 AM, joachim heintz
> wrote:
>> Hi Andrés -
>>
>> I have some problems with the realtime performance of qutecsound.
>> I'm on a
>> MacBook, and even running the simple example below (which comes with
>> qutecsound) with ksmps=1 instead of ksmps=128 gives dropouts. Is
>> this the
>> same for you (or anyone else using qutecound), or can I adjust
>> anything?
>>
>> Best -
>>
>> joachim
>>
>>
>>
>>
>>
>> -odac -iadc
>> ; -o test.wav -W
>>
>>
>>
>> sr = 44100
>> ksmps = 128
>> nchnls = 2
>>
>> instr 1
>> kfreq line 100, p3, 1000
>> aout oscil 10000, kfreq, 1
>> outs aout, aout
>> endin
>>
>> instr 2
>>
>> endin
>>
>>
>>
>> f 1 0 1024 10 1
>> i 1 0 5
>> e
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> "unsubscribe
>> csound"
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body
> "unsubscribe csound"
|