Is there a bug in the poly~ object (Win 457) with the 'mutemap' or the 

'mute' messages ? I sent one millions 'mute 0 1' (wich means 'mute all' 

cf. helpfile and experience), and 'mutemap' always print the same wrong 

things... Test it with the help file itself : tweak the toggle to 

mute/unmute all, 'mutemap' will always say 0 0 0 on my machine...

f.e chanfrault | aka | personal computer music

> >>>>>> |sublime music for a desperate people|

Is there a bug in the poly~ object (Win 457) with the 'mutemap' or the 
'mute' messages ? I sent one millions 'mute 0 1' (wich means 'mute all' 
cf. helpfile and experience), and 'mutemap' always print the same wrong 
things... Test it with the help file itself : tweak the toggle to 
mute/unmute all, 'mutemap' will always say 0 0 0 on my machine...

f.e
-- 
f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> |sublime music for a desperate people|


poly-mutemap-bug

It seems that the 'mute 0 $1' doesn't do anything. Muting/unmuting 

specific voices is shown right by 'mutemap'...

> Is there a bug in the poly~ object (Win 457) with the 'mutemap' or the 

> 'mute' messages ? I sent one millions 'mute 0 1' (wich means 'mute 

> all' cf. helpfile and experience), and 'mutemap' always print the same 

> wrong things... Test it with the help file itself : tweak the toggle 

> to mute/unmute all, 'mutemap' will always say 0 0 0 on my machine...

It seems that the 'mute 0 $1' doesn't do anything. Muting/unmuting 
specific voices is shown right by 'mutemap'...

f.e wrote:
> Is there a bug in the poly~ object (Win 457) with the 'mutemap' or the 
> 'mute' messages ? I sent one millions 'mute 0 1' (wich means 'mute 
> all' cf. helpfile and experience), and 'mutemap' always print the same 
> wrong things... Test it with the help file itself : tweak the toggle 
> to mute/unmute all, 'mutemap' will always say 0 0 0 on my machine...
>
> f.e

-- 
f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> |sublime music for a desperate people|


> It seems that the 'mute 0 $1' doesn't do anything. Muting/unmuting 

> specific voices is shown right by 'mutemap'...

Obviously the mute 0 $1 does something, because this is the first button 

I have to hit if I cal up the poly~ help file. Without I would have 

But if you hit it again it will remember the old mute setting.

Just imagine you have a 128 voice synth, and one voice is sounding, you 

hit mute 0 1, and then mute 0 0. I am sure that you'd be very glad that 

this will NOT SWITCH ON ALL 128 VOICES ouch... (if this would happen 

live is like creating a big feedback fully blown up in a concert...)

The mute map remebers the individual settings, the global mute is 

independant of that, like an additional command...

f.e wrote:
> It seems that the 'mute 0 $1' doesn't do anything. Muting/unmuting 
> specific voices is shown right by 'mutemap'...

Obviously the mute 0 $1 does something, because this is the first button 
I have to hit if I cal up the poly~ help file. Without I would have 
killed myself ;-)

Just imagine you have a 128 voice synth, and one voice is sounding, you 
hit mute 0 1, and then mute 0 0. I am sure that you'd be very glad that 
this will NOT SWITCH ON ALL 128 VOICES ouch... (if this would happen 
live is like creating a big feedback fully blown up in a concert...)

The mute map remebers the individual settings, the global mute is 
independant of that, like an additional command...

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


> The mute map remembers the individual settings, the global mute is 

> independant of that, like an additional command...

Stefan Tiedje wrote:
> The mute map remembers the individual settings, the global mute is 
> independant of that, like an additional command...
It was not obvious...

and it's useless : when all poly~s are muted with a 'mute 0 1' message, 

it's impossible to individually unmute the voices with 'mute n 0' unless 

you unmute them all with 'mute 0 0'. That's absolutely pointless. To 

have a real control, we have to do a for loop (uzi n -> mute n 1). Is it 

something c74 would consider to change or everybody is happy with that ?

>> The mute map remembers the individual settings, the global mute is 

>> independant of that, like an additional command...

and it's useless : when all poly~s are muted with a 'mute 0 1' message, 
it's impossible to individually unmute the voices with 'mute n 0' unless 
you unmute them all with 'mute 0 0'. That's absolutely pointless. To 
have a real control, we have to do a for loop (uzi n -> mute n 1). Is it 
something c74 would consider to change or everybody is happy with that ?

f.e wrote:
>
>
> Stefan Tiedje wrote:
>> The mute map remembers the individual settings, the global mute is 
>> independant of that, like an additional command...
> It was not obvious...
>
> Thanks Stefan.
>
> cheers
>
> f.e
>>
>> Stefan
>>
>

> and it's useless : when all poly~s are muted with a 'mute 0 1' message, 

> it's impossible to individually unmute the voices with 'mute n 0' unless 

> you unmute them all with 'mute 0 0'. That's absolutely pointless. To 

> have a real control, we have to do a for loop (uzi n -> mute n 1). Is it 

> something c74 would consider to change or everybody is happy with that ?

I am very, very happy with it, because as explained before this is VERY

useful, as it remebers the old states. Its easy with uzi to get the

behaviour you think is usefull, but it would be almost impossible to get

the existing behaviour which I love, if it would be the other way around...

You can even switch on of mute states for voices as its globally muted.

Another approach for your desire is to create a mute input, connect it

to a mute $1 message and send target 0, 1 to that input...

f.e wrote:
> and it's useless : when all poly~s are muted with a 'mute 0 1' message, 
> it's impossible to individually unmute the voices with 'mute n 0' unless 
> you unmute them all with 'mute 0 0'. That's absolutely pointless. To 
> have a real control, we have to do a for loop (uzi n -> mute n 1). Is it 
> something c74 would consider to change or everybody is happy with that ?

I am very, very happy with it, because as explained before this is VERY
useful, as it remebers the old states. Its easy with uzi to get the
behaviour you think is usefull, but it would be almost impossible to get
the existing behaviour which I love, if it would be the other way around...

You can even switch on of mute states for voices as its globally muted.
THIS IS WONDERFUL !!!

Another approach for your desire is to create a mute input, connect it
to a mute $1 message and send target 0, 1 to that input...
Nothing cycling needs to change...

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

Poly~ mutemap bug ?