Wetears

I'm making my 1st patch, a system time -controlled recorder-player. I've got a problem with banging at the beginninging of a second. I guess there must be a better method of doing this. I'm now using select, even though it should only work with ints I guess. It works somehow, but it stops banging time after time. Also it only starts working on a new minute, but I'm ok with that. Just to make it work and not stop since the 1st bang is sent. I'd really appreciate a hint. There must be a simpler way but it seems that I don't get it now. Thanks a lot. Here it is:

Hi
I'm making my 1st patch, a system time -controlled recorder-player. I've got a problem with banging at the beginninging of a second. I guess there must be a better method of doing this. I'm now using select, even though it should only work with ints I guess. It works somehow, but it stops banging time after time. Also it only starts working on a new minute, but I'm ok with that. Just to make it work  and not stop since the 1st bang is sent. I'd really appreciate a hint. There must be a simpler way but it seems that I don't get it now. Thanks a lot. Here it is:

send-a-bang-every-time-a-second-changes-date-object

On 29 janv. 08, at 10:49, Sini Havukainen wrote:

> I'm making my 1st patch, a system time -controlled recorder-player. 

> I've got a problem with banging at the beginninging of a second. I 

> guess there must be a better method of doing this. I'm now using 

> select, even though it should only work with ints I guess. It works 

> somehow, but it stops banging time after time. Also it only starts 

> working on a new minute, but I'm ok with that. Just to make it work 

> and not stop since the 1st bang is sent. I'd really appreciate a 

> hint. There must be a simpler way but it seems that I don't get it 

Centre de Recherches et de Formation Musicales de Wallonie asbl

>
> Hi
> I'm making my 1st patch, a system time -controlled recorder-player.  
> I've got a problem with banging at the beginninging of a second. I  
> guess there must be a better method of doing this. I'm now using  
> select, even though it should only work with ints I guess. It works  
> somehow, but it stops banging time after time. Also it only starts  
> working on a new minute, but I'm ok with that. Just to make it work   
> and not stop since the 1st bang is sent. I'd really appreciate a  
> hint. There must be a simpler way but it seems that I don't get it  
> now. Thanks a lot. Here it is:

What about [change]?
Look at the following patch:

_____________________________
Patrick Delges

Centre de Recherches et de Formation Musicales de Wallonie asbl
http://www.crfmw.be/max


hehe i couldn't help but laugh at your select object...patrick pretty much summed it up already

Thanks a million guys! I learned something new again... Change is exactly what I needed ;) So now it's like this, if anyone is interested:

> hehe i couldn't help but laugh at your select object...patrick pretty

Yes, why easy if you can have it complicated:

Bas van der Graaff schrieb:
> hehe i couldn't help but laugh at your select object...patrick pretty
> much summed it up already

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


> Thanks a million guys! I learned something new again... Change is

> exactly what I needed ;) So now it's like this, if anyone is

Why don't you just delete all delays and metros below the first one??? 

It would do the same... (more or less...)

Sini Havukainen schrieb:
> Thanks a million guys! I learned something new again... Change is
> exactly what I needed ;) So now it's like this, if anyone is
> interested:

Why don't you just delete all delays and metros below the first one??? 
It would do the same... (more or less...)

Thanks for all the helpful tips. This makes learning faster. Yes, Stefan, I cleaned those up a bit (the metros and delays below), but I need them to tell when to start/stop recordings in another sub-patch, and when to start looping those. There is for sure a simpler way for all that, but for now this'll do for me.

Thanks for all the helpful tips. This makes learning faster. Yes, Stefan, I cleaned those up a bit (the metros and delays below), but I need them  to tell when to start/stop recordings in another sub-patch, and when to start looping those. There is for sure a simpler way for all that, but for now this'll do for me.


> but I need them to tell when to start/stop recordings in another 

> sub-patch, and when to start looping those.

Isn't the actual times info enough? You can also have a look at 

cpuclock, to get a higher resolution than date...

> There is for sure a simpler way for all that, but for now this'll do

These metros are not synced, which will create trouble. Its always 

better to have a single source for the timing. In your case its just the 

date object. It doesn't need more, really...

It always pays off to find the simpler ways...

Sini Havukainen schrieb:
> but I need them  to tell when to start/stop recordings in another 
> sub-patch, and when to start looping those.

Isn't the actual times info enough? You can also have a look at 
cpuclock, to get a higher resolution than date...

> There is for sure a simpler way for all that, but for now this'll do
> for me.

These metros are not synced, which will create trouble. Its always 
better to have a single source for the timing. In your case its just the 
date object. It doesn't need more, really...
It always pays off to find the simpler ways...

Send a bang every time a second changes (date-object)