could somebody tell me why this patch doesn't work on my max462runtime on intel macbook pro os10.4.9 ?

each time i record and automaticly play a file, i have a bad header info.

and it works perfectly on max457 / powerbook os10.3.9...

i surely made a mistake, but i can't find what.

each time i record and automaticly play a file, i have a bad header info.
however the file is well recorded.
if i re-play it, it's ok...

why ?
i become crazy.
i surely made a mistake, but i can't find what.

bad-header-info-only-on-runtime462osx49-2

here's the patch (upload file didn't work...):

here's the patch (upload file didn't work...):
http://pan-etc.net/fp/rec-test.zip

https://cycling74.com/forums/index.php?t=msg&th=25059&start=0&rid=3579&S=dd2c619aab58cc0c59e57cab974f81f7

I don't see what this user's problem has to do with this at all. 

Sounds like the patch loads and runs, but that there's a problem with 

Am 18.03.2007 um 19:40 schrieb Mattijs Kneppers:

> t=msg&th=25059&start=0&rid=3579&S=dd2c619aab58cc0c59e57cab974f81f7

> Interactive audiovisual sampling soft- and hardware

I don't see what this user's problem has to do with this at all.  
Sounds like the patch loads and runs, but that there's a problem with  
the recorded audio.

>
> have a look at this one:
>
> https://cycling74.com/forums/index.php? 
> t=msg&th=25059&start=0&rid=3579&S=dd2c619aab58cc0c59e57cab974f81f7
> --
> SmadSteck - http://www.smadsteck.nl
> Interactive audiovisual sampling soft- and hardware
>


yes, i don't think it's a os1049 problem.

yes, i don't think it's a os1049 problem.
max launch fine with the combo update.

no problem so far on a MacBook pro. What's really wrong for you? What 

no problem so far on a MacBook pro. What's really wrong for you? What  
are the steps to reproduce your problem?

Quote: Emmanuel Jourdan wrote on Sun, 18 March 2007 21:58

----------------------------------------------------

What are the steps to reproduce your problem?

open the patch, put on adc, record few seconds and sop the recording.

i just find a way to avoid it, insert a [t b s] -> [del 10] (for bang) -> [zl reg], just before sending to buffer.

is it my disk access to slow ? or something like that ?

Quote: Emmanuel Jourdan wrote on Sun, 18 March 2007 21:58
----------------------------------------------------
What's really wrong for you? 
What are the steps to reproduce your problem?
>
> ej
>
----------------------------------------------------

the steps are very simple.
open the patch, put on adc, record few seconds and sop the recording.
you'll have a bad header info message.

i just find a way to avoid it, insert a [t b s] -> [del 10] (for bang) -> [zl reg], just before sending to buffer.
and it works.
is it my disk access to slow ? or something like that ?


in fact it's works better with 20, 25 ms delay before sending to buffer.

Quote: elt wrote on Sun, 18 March 2007 20:32

> yes, i don't think it's a os1049 problem.

Ah, sorry. When there is a call to avoid an update I usually stay far away from it, which perhaps explains my premature reaction.

I looked at your patch but I don't understand what to press. Could you include some steps to reproduce? I also miss ej.led.js.

Quote: elt wrote on Sun, 18 March 2007 20:32
----------------------------------------------------
> yes, i don't think it's a os1049 problem.
> max launch fine with the combo update.
>
> please try the patch and tell me.
>
----------------------------------------------------

Quote: elt wrote on Sun, 18 March 2007 22:26

> open the patch, put on adc, record few seconds and sop the recording.

> i just find a way to avoid it, insert a [t b s] -> [del 10] (for bang) -> [zl reg], just before sending to buffer.

> is it my disk access to slow ? or something like that ?

Oh, sorry, missed that one. But what should I press to start recording? Also I see #1 arguments in the pvar objects. Isn't this patch supposed to be used as an abstraction?

Quote: elt wrote on Sun, 18 March 2007 22:26
----------------------------------------------------
> the steps are very simple.
> open the patch, put on adc, record few seconds and sop the recording.
> you'll have a bad header info message.
>
> i just find a way to avoid it, insert a [t b s] -> [del 10] (for bang) -> [zl reg], just before sending to buffer.
> and it works.
> is it my disk access to slow ? or something like that ?
>
----------------------------------------------------

yes it seems to be effectively a question of time.

with some [pipe] and [del] i can solve it.

but i'll study your solution, just to learn more.

yes it seems to be effectively a question of time.
with some [pipe] and [del] i can solve it.
but i'll study your solution, just to learn more.
:-)


in fact i have to insert delays to have it working properly.

path to filewatch -> 50ms - 1 to filewatch -> 50 ms end of recording.

i don't really understand how work filewatch.

could you please tell me what is wrong in my patch ?

the filewatch process is in the subpatch "record".

in fact i have to insert delays to have it working properly.
path to filewatch -> 50ms - 1 to filewatch -> 50 ms end of recording.

could you please tell me what is wrong in my patch ?
the filewatch process is in the subpatch "record".

and here's the patch: http://pan-etc.net/fp/rec-test.zip

bad header info only on runtime462/OSX49