[OSC_dev] Images ?

[Xavier Miller]

I have an application : send thumnails from the application to the 
controller, so that the remote user can have previews, or upload images 
to the application (but in that case, it would be better a "file tag", 
with name and contents).

A blob is not a solution because it would need to be analyzed twice: 
defining the type (blob), then re-analyze it.
If it is stated as "picture", all OSC applications recoginzing it will 
immediately get the picture, the others will ignore the tag.

For example, images are transferred in ArtNet/MSEX protocol (for 
lighting consoles, media servers, video systems). So why not for OSC ? ;)

Xavier.

Gaspard Bucher a écrit :
> I am not sure I see any cross-application use case where it would be
> needed to have a common picture format. Most of the cases I see are
> image processing applications in which cases you need a lossless
> compression (not some jpg or png). Personally I could use a special
> compressed blob with some meta-data on the size and number of layers
> (multi-plane matrix).
> 
> Gaspard
> 
> On Thu, Mar 5, 2009 at 8:37 AM, Xavier Miller <xavier.miller at cauwe.org> wrote:
>> Hello,
>>
>> In our application, we plan to send images in OSC messages. Is already a
>> type tag defined ? I think it should be interesting to define one, which
>> is not "blob".
>>
>> Something like "p" (picture), then the image format (bmp, xpm, png,
>> jpg... / dimensions), then the image blob itself.
>>
>> Kind regards,
>> Xavier Miller.
>> _______________________________________________
>> OSC_dev mailing list
>> OSC_dev at create.ucsb.edu
>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev