Matthew Aidekman

DID YOU KNOW: multislider's [RGB:10,0,34] is different than panel's 

Matt's absurd propensity to do anything but be productive.

DID YOU KNOW: multislider's [RGB:10,0,34] is different than panel's  
[RGB:10,0,34]  ????

Matt's absurd propensity to do anything but be productive.
and the letters 'U' and 'P'
the number '2'
and the word 'late'

stupid-bug

http://www.sesameworkshop.org/sesamestreet/

>>> matthew aidekman 09/26/06 7:09 pm >>>

>>> matthew aidekman  09/26/06 7:09 pm >>>
DID YOU KNOW: multislider's [RGB:10,0,34] is different than panel's  
[RGB:10,0,34]  ????

At 5:09 AM -0400 9/26/06, matthew aidekman wrote:

>DID YOU KNOW: multislider's [RGB:10,0,34] is different than panel's 

They're the same for me, on 10.4.7, PPC, Max/MSP 4.6.2

202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X

At 5:09 AM -0400 9/26/06, matthew aidekman wrote:
>DID YOU KNOW: multislider's [RGB:10,0,34] is different than panel's 
>[RGB:10,0,34]  ????

Dan
-- 
Dan Nigrin
Defective Records
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X
http://www.defectiverecords.com
http://www.jackosx.com


digital color meter on OS X reports RGB 8 bit value

On Sep 26, 2006, at 5:18 AM, Jeffrey Hannam wrote:

>>>> matthew aidekman 09/26/06 7:09 pm >>>

> DID YOU KNOW: multislider's [RGB:10,0,34] is different than panel's

> Matt's absurd propensity to do anything but be productive.

> #P message 159 48 69 196617 brgb 10 0 34;

> #P comment 308 196 100 196617 multislider;

> #P user multiSlider 240 140 181 134 -1. 1. 1 2681 0 0 0 2 0 0 0;

> yup
>
> http://www.sesameworkshop.org/sesamestreet/
>
> J
>
>>>> matthew aidekman  09/26/06 7:09 pm >>>
> DID YOU KNOW: multislider's [RGB:10,0,34] is different than panel's
> [RGB:10,0,34]  ????
>
> this bug has been brought to you by:
>
> Matt's absurd propensity to do anything but be productive.
> and the letters 'U' and 'P'
> the number '2'
> and the word 'late'
>
> -matt
>
>
>
>
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P message 159 48 69 196617 brgb 10 0 34;
> #P comment 228 110 100 196617 panel;
> #B frgb 255 255 255;
> #P comment 308 196 100 196617 multislider;
> #B frgb 255 255 255;
> #P user multiSlider 240 140 181 134 -1. 1. 1 2681 0 0 0 2 0 0 0;
> #M frgb 10 0 34;
> #M brgb 10 0 34;
> #M rgb2 127 127 127;
> #M rgb3 0 0 0;
> #M rgb4 37 52 91;
> #M rgb5 74 105 182;
> #M rgb6 112 158 18;
> #M rgb7 149 211 110;
> #M rgb8 187 9 201;
> #M rgb9 224 62 37;
> #M rgb10 7 114 128;
> #P user panel 120 99 267 197;
> #X brgb 10 0 34;
> #X frgb 0 0 0;
> #X border 1;
> #X rounded 0;
> #X shadow 0;
> #X done;
> #P connect 4 0 0 0;
> #P connect 4 0 1 0;
> #P window clipboard copycount 5;
>

It's probably the difference between *255 and *256 in the object's 

code (RGB values in quickdraw are 0-65535 (0*256 - 255*256)). Enjoy 

> digital color meter on OS X reports RGB 8 bit value

> On Sep 26, 2006, at 5:18 AM, Jeffrey Hannam wrote:

>>>>> matthew aidekman 09/26/06 7:09 pm >>>

>> DID YOU KNOW: multislider's [RGB:10,0,34] is different than panel's

>> Matt's absurd propensity to do anything but be productive.

>> #P message 159 48 69 196617 brgb 10 0 34;

>> #P comment 308 196 100 196617 multislider;

>> #P user multiSlider 240 140 181 134 -1. 1. 1 2681 0 0 0 2 0 0 0;

It's probably the difference between *255 and *256 in the object's  
code (RGB values in quickdraw are 0-65535 (0*256 - 255*256)). Enjoy  
the vibration.

> digital color meter on OS X reports RGB 8 bit value
>
> 10 00 34 for panel
>
> 8 00 33 for multislider
>
> looks like multislider is the issue
>
> odd.
>
>
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
> On Sep 26, 2006, at 5:18 AM, Jeffrey Hannam wrote:
>
>> yup
>>
>> http://www.sesameworkshop.org/sesamestreet/
>>
>> J
>>
>>>>> matthew aidekman  09/26/06 7:09 pm >>>
>> DID YOU KNOW: multislider's [RGB:10,0,34] is different than panel's
>> [RGB:10,0,34]  ????
>>
>> this bug has been brought to you by:
>>
>> Matt's absurd propensity to do anything but be productive.
>> and the letters 'U' and 'P'
>> the number '2'
>> and the word 'late'
>>
>> -matt
>>
>>
>>
>>
>> #P window setfont "Sans Serif" 9.;
>> #P window linecount 1;
>> #P message 159 48 69 196617 brgb 10 0 34;
>> #P comment 228 110 100 196617 panel;
>> #B frgb 255 255 255;
>> #P comment 308 196 100 196617 multislider;
>> #B frgb 255 255 255;
>> #P user multiSlider 240 140 181 134 -1. 1. 1 2681 0 0 0 2 0 0 0;
>> #M frgb 10 0 34;
>> #M brgb 10 0 34;
>> #M rgb2 127 127 127;
>> #M rgb3 0 0 0;
>> #M rgb4 37 52 91;
>> #M rgb5 74 105 182;
>> #M rgb6 112 158 18;
>> #M rgb7 149 211 110;
>> #M rgb8 187 9 201;
>> #M rgb9 224 62 37;
>> #M rgb10 7 114 128;
>> #P user panel 120 99 267 197;
>> #X brgb 10 0 34;
>> #X frgb 0 0 0;
>> #X border 1;
>> #X rounded 0;
>> #X shadow 0;
>> #X done;
>> #P connect 4 0 0 0;
>> #P connect 4 0 1 0;
>> #P window clipboard copycount 5;
>>
>


>digital color meter on OS X reports RGB 8 bit value

I stand corrected - I get the same thing here.

At 10:52 AM -0400 9/26/06, vade wrote:
>digital color meter on OS X reports RGB 8 bit value
>
>10 00 34 for panel
>
>8 00 33 for multislider
>
>looks like multislider is the issue
>
>odd.

On 26-Sep-2006, at 17:09, Jeremy Bernstein wrote:

> It's probably the difference between *255 and *256 in the object's 

> code (RGB values in quickdraw are 0-65535 (0*256 - 255*256)). Enjoy 

Actually, in case any one is intending on coding this stuff, panel 

must be multiplying/dividing by 257 (65,535 = 255 * 257).

A lot of code just bit-shifts to convert between 8-bit and 16-bit RGB 

values, but the One True Conversion(tm) requires mult/div 257. 

Richard D. and I had some correspondence about this after he released 

the xgui demo; we also figured out ways to avoid the (slightly 

expensive) /257 with some bit-munging operations that are probably no 

Sorry for being Mademoiselle Je-sais-tous. I'll shut up and go 

Peter Castine +--> Litter Power & Litter Bundle for Jitter

Interface Building for |home | chez nous|

Max/MSP Extremely cool |bei uns | i nostri|

> It's probably the difference between *255 and *256 in the object's  
> code (RGB values in quickdraw are 0-65535 (0*256 - 255*256)). Enjoy  
> the vibration.

Actually, in case any one is intending on coding this stuff, panel  
must be multiplying/dividing by 257 (65,535 = 255 * 257).

A lot of code just bit-shifts to convert between 8-bit and 16-bit RGB  
values, but the One True Conversion(tm) requires mult/div 257.  
Richard D. and I had some correspondence about this after he released  
the xgui demo; we also figured out ways to avoid the (slightly  
expensive) /257 with some bit-munging operations that are probably no  
less CPU-intensive but a lot more fun!-

Sorry for being Mademoiselle Je-sais-tous. I'll shut up and go  
document my standalone problems.

--------------    http://www.bek.no/~pcastine/Litter/    -------------
Peter Castine             +--> Litter Power & Litter Bundle for Jitter
                                Universal Binaries on the way
iCE:  Sequencing,  Recording &
       Interface  Building  for                   |home    | chez nous|
       Max/MSP   Extremely cool                   |bei uns |  i nostri|
       http://www.dspaudio.com/                   http://www.castine.de

While I'd always wonder about OS, version, and so on,

this also makes me wonder about platform and display

settings. It sure looks the same on my laptop. But then

While I'd always wonder about OS, version, and so on,
this also makes me wonder about platform and display
settings. It sure looks the same on my laptop. But then
I'm using brgb 10 0 34....


I stand corrected, Mlles Castine and Dudas. Richard told me to tell 

the list that "both objects (correctly) multiply and divide by 257 to 

(255* 257 = 65535, but if you bit-shift you don't get maximum 16-bit 

value)" and that the problem doesn't happen on Windows, so "that it's 

a mac-specific problem, and has to do with some offscreen funkiness 

that is potentially the system's fault and not the fault of the max 

objects, both of which think they're using the same color!!" And 

furthermore that "this could probably be tested out using LCD in both 

offscreen and onscreen modes, if one were so motivated."

Am 26.09.2006 um 19:25 schrieb Peter Castine:

> A lot of code just bit-shifts to convert between 8-bit and 16-bit 

> RGB values, but the One True Conversion(tm) requires mult/div 257. 

> Richard D. and I had some correspondence about this after he 

> released the xgui demo; we also figured out ways to avoid the 

> (slightly expensive) /257 with some bit-munging operations that are 

> probably no less CPU-intensive but a lot more fun!-

I stand corrected, Mlles Castine and Dudas. Richard told me to tell  
the list that "both objects (correctly) multiply and divide by 257 to  
convert between 8-bit and 16-bit color.
(255* 257 = 65535, but if you bit-shift you don't get maximum 16-bit  
value)" and that the problem doesn't happen on Windows, so "that it's  
a mac-specific problem, and has to do with some offscreen funkiness  
that is potentially the system's fault and not the fault of the max  
objects, both of which think they're using the same color!!" And  
furthermore that "this could probably be tested out using LCD in both  
offscreen and onscreen modes, if one were so motivated."

> A lot of code just bit-shifts to convert between 8-bit and 16-bit  
> RGB values, but the One True Conversion(tm) requires mult/div 257.  
> Richard D. and I had some correspondence about this after he  
> released the xgui demo; we also figured out ways to avoid the  
> (slightly expensive) /257 with some bit-munging operations that are  
> probably no less CPU-intensive but a lot more fun!-


stupid bug