Dr. Spankenstein

I've tried using the state message but it only prints the direction to the Max window? (I'm after the value as an integer to use in a patch)

I've tried using the state message but it only prints the direction to the Max window?  (I'm after the value as an integer to use in a patch)

how-do-i-get-the-current-count-direction-out-of-a-counter

yes i tried a few route options but cant seem to get the syntax right ( -=? CounterState ?=-

but maybe a little logic could do it , quick and dirty :

yes i tried a few route options but cant seem to get the syntax right   ( -=? CounterState ?=-
     x_mincount  : 0
     x_maxcount  : 100
     x_direction : 0
     x_curcount  : 27
     x_curdir    : 0
     x_carrycount: 12
     x_carry     : 0
     x_under     : 0
     x_carrymode : 0
     x_compat    : 0
     x_startup   : 0
     x_inletnum  : 0 )

On Feb 5, 2008, at 4:56 PM, Rhys Perkins wrote:

> I've tried using the state message but it only prints the direction 

> to the Max window? (I'm after the value as an integer to use in a 

I don't think you can directly. You can derive direction pretty 

>
> I've tried using the state message but it only prints the direction  
> to the Max window?  (I'm after the value as an integer to use in a  
> patch)

I don't think you can directly. You can derive direction pretty  
easily, though:

> I've tried using the state message but it only prints the direction

> to the Max window? (I'm after the value as an integer to use in a

Subtract adjacent values, and test if they are bigger/smaller than zero. 

In principle this is the same as the other two, but easier to patch and 

Rhys Perkins schrieb:
> I've tried using the state message but it only prints the direction
> to the Max window?  (I'm after the value as an integer to use in a
> patch)

Subtract adjacent values, and test if they are bigger/smaller than zero. 
In principle this is the same as the other two, but easier to patch and 
understand... ;-)

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


I'll get to work implemented these. I find that counters are incredibly useful for rudimentary collision detection and this has been a great help.

I'll get to work implemented these.  I find that counters are incredibly useful for rudimentary collision detection and this has been a great help.


as counter will only count if you tell it (him? her?) to do so i cant 

imagine a situation where you wouldnt know the count direction so 

analysing is kind of a waste of cpu cycles i think. can you describe any 

situation that would make such an analysis necessary? just curious...

> I've tried using the state message but it only prints the direction to the Max window? (I'm after the value as an integer to use in a patch)

as counter will only count if you tell it (him? her?) to do so i cant 
imagine a situation where you wouldnt know the count direction so 
analysing is kind of a waste of cpu cycles i think. can you describe any 
situation that would make such an analysis necessary? just curious...

Rhys Perkins wrote:
> I've tried using the state message but it only prints the direction to the Max window?  (I'm after the value as an integer to use in a patch)
>
> Thanks
>
> Rhys
>
>
>

-- 
http://pure.test.at
http://www.heartchamberorchestra.org


Drawing pixels on an LCD screen and then moving them using a counter.

Which direction the pixel appears to be heading in can be detected via the count direction of 2 counters. One for x and one for y.

Drawing pixels on an LCD screen and then moving them using a counter.  

Which direction the pixel appears to be heading in can be detected via the count direction of 2 counters.  One for x and one for y.

to be honest - i still dont understand it. but never mind - dont want to 

steal yr time with unnecessary questions...

> Drawing pixels on an LCD screen and then moving them using a counter. 

> Which direction the pixel appears to be heading in can be detected via the count direction of 2 counters. One for x and one for y.

to be honest - i still dont understand it. but never mind - dont want to 
steal yr time with unnecessary questions...

Rhys Perkins wrote:
> Drawing pixels on an LCD screen and then moving them using a counter.  
>
> Which direction the pixel appears to be heading in can be detected via the count direction of 2 counters.  One for x and one for y.
>
> Rhys
>
>
>

I don't get it either. How do you not know what you've told counter to do?

For those of you who have given up trying to remember the contents of counter.help, I give you the accum object. Upwards, downwards, linear, geometric

> I don't get it either. How do you not know what you've told counter to do?

> For those of you who have given up trying to remember the contents of counter.help, I give you the accum object. Upwards, downwards, linear, geometric

> #P number 236 203 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P fasten 4 0 5 0 173 257 92 257 92 122 110 122;

Andrew Pask wrote:
>
> I don't get it either. How do you not know what you've told counter to do?
>
>
> For those of you who have given up trying to remember the contents of counter.help, I give you the accum object. Upwards, downwards, linear, geometric
>
>
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P message 188 123 14 196617 1;
> #P number 236 203 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P message 105 133 33 196617 set 0;
> #P newex 168 229 32 196617 sel 1;
> #P newex 168 201 31 196617 == 4;
> #P newex 168 161 40 196617 accum;
> #P newex 168 90 30 196617 t b b;
> #P button 168 55 15 0;
> #P connect 3 0 4 0;
> #P fasten 4 0 5 0 173 257 92 257 92 122 110 122;
> #P connect 7 0 2 1;
> #P connect 1 1 7 0;
> #P connect 0 0 1 0;
> #P connect 1 0 2 0;
> #P connect 2 0 3 0;
> #P fasten 2 0 6 0 173 185 241 185;
> #P fasten 5 0 2 0 110 154 173 154;
> #P window clipboard copycount 8;
>
>
> -A
>
>
>
>
>
>
>
>

On Feb 6, 2008, at 3:13 PM, Andrew Pask wrote:

> I don't get it either. How do you not know what you've told counter 

Well, the snippet I posted was from a large-ish patch where I'm trying 

to react to a number stream, and I don't want to know (or care) where 

On Feb 6, 2008, at 3:13 PM, Andrew Pask wrote:
> I don't get it either. How do you not know what you've told counter  
> to do?

Well, the snippet I posted was from a large-ish patch where I'm trying  
to react to a number stream, and I don't want to know (or care) where  
the number comes from.

This patch of mine is excerpted from a much smaller patch.

> On Feb 6, 2008, at 3:13 PM, Andrew Pask wrote:

>> I don't get it either. How do you not know what you've told counter 

> Well, the snippet I posted was from a large-ish patch where I'm trying 

> to react to a number stream, and I don't want to know (or care) where 

analysing any stream of numbers makes of course sense to me but not if 

Chris Muir wrote:
>
> On Feb 6, 2008, at 3:13 PM, Andrew Pask wrote:
>> I don't get it either. How do you not know what you've told counter 
>> to do?
>
> Well, the snippet I posted was from a large-ish patch where I'm trying 
> to react to a number stream, and I don't want to know (or care) where 
> the number comes from.
analysing any stream of numbers makes of course sense to me but not if 
it comes from a counter...

a variant on Chris Muir's that does something with the negative direction as well as the positive direction.

How do I get the current count direction out of a Counter?