Images ?
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
Images ?
by Xavier Miller
::
Rate this Message:
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@... http://lists.create.ucsb.edu/mailman/listinfo/osc_dev |
|
|
Re: Images ?
by Gaspard Bucher
::
Rate this Message:
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@...> 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@... > http://lists.create.ucsb.edu/mailman/listinfo/osc_dev > OSC_dev mailing list OSC_dev@... http://lists.create.ucsb.edu/mailman/listinfo/osc_dev |
|
|
Re: Images ?
by Xavier Miller
::
Rate this Message:
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@...> 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@... >> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >> > _______________________________________________ > OSC_dev mailing list > OSC_dev@... > http://lists.create.ucsb.edu/mailman/listinfo/osc_dev OSC_dev mailing list OSC_dev@... http://lists.create.ucsb.edu/mailman/listinfo/osc_dev |
|
|
Re: Images ?
by Xavier Miller
::
Rate this Message:
Hello,
Here is what we want to do with OSC, and we know that OSC is so potentially powerful that we will do it! http://www.scribd.com/doc/4021424/MagicQ-Arkaos Xavier. Xavier Miller a écrit : > 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@...> 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@... >>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>> >> _______________________________________________ >> OSC_dev mailing list >> OSC_dev@... >> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev > _______________________________________________ > OSC_dev mailing list > OSC_dev@... > http://lists.create.ucsb.edu/mailman/listinfo/osc_dev OSC_dev mailing list OSC_dev@... http://lists.create.ucsb.edu/mailman/listinfo/osc_dev |
|
|
Re: Images ?
by Gaspard Bucher
::
Rate this Message:
Your products look really nice ! I understand your need for a simple
picture tag. "p" seems just fine. By the way, we are working on a small set of common osc idioms/features to help applications and controllers talk to each other: http://rubyk.org/oscit It would be really great if you could join in ! I'd love to see something like the MagicQ being controlled or controlling rubyk or other oscit enabled applications / hardware. Gaspard On Thu, Mar 5, 2009 at 9:54 AM, Xavier Miller <xavier.miller@...> wrote: > Hello, > > Here is what we want to do with OSC, and we know that OSC is so > potentially powerful that we will do it! > > http://www.scribd.com/doc/4021424/MagicQ-Arkaos > > Xavier. > > Xavier Miller a écrit : >> 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@...> 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@... >>>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>>> >>> _______________________________________________ >>> OSC_dev mailing list >>> OSC_dev@... >>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >> _______________________________________________ >> OSC_dev mailing list >> OSC_dev@... >> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev > _______________________________________________ > OSC_dev mailing list > OSC_dev@... > http://lists.create.ucsb.edu/mailman/listinfo/osc_dev > OSC_dev mailing list OSC_dev@... http://lists.create.ucsb.edu/mailman/listinfo/osc_dev |
|
|
Re: Images ?
by Xavier Miller
::
Rate this Message:
Hello,
The MagicQ is a lighting console from Chamsys http://www.chamsys.co.uk. I work for ArKaos (http://www.arkaos.net) an interactive video softare company. I will take a look at oscit. Xavier Gaspard Bucher a écrit : > Your products look really nice ! I understand your need for a simple > picture tag. "p" seems just fine. > > By the way, we are working on a small set of common osc > idioms/features to help applications and controllers talk to each > other: http://rubyk.org/oscit > > It would be really great if you could join in ! I'd love to see > something like the MagicQ being controlled or controlling rubyk or > other oscit enabled applications / hardware. > > Gaspard > > On Thu, Mar 5, 2009 at 9:54 AM, Xavier Miller <xavier.miller@...> wrote: >> Hello, >> >> Here is what we want to do with OSC, and we know that OSC is so >> potentially powerful that we will do it! >> >> http://www.scribd.com/doc/4021424/MagicQ-Arkaos >> >> Xavier. >> >> Xavier Miller a écrit : >>> 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@...> 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@... >>>>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>>>> >>>> _______________________________________________ >>>> OSC_dev mailing list >>>> OSC_dev@... >>>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>> _______________________________________________ >>> OSC_dev mailing list >>> OSC_dev@... >>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >> _______________________________________________ >> OSC_dev mailing list >> OSC_dev@... >> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >> > _______________________________________________ > OSC_dev mailing list > OSC_dev@... > http://lists.create.ucsb.edu/mailman/listinfo/osc_dev OSC_dev mailing list OSC_dev@... http://lists.create.ucsb.edu/mailman/listinfo/osc_dev |
|
|
Re: Images ?
by Gaspard Bucher
::
Rate this Message:
Sorry for the confusion.
Since your software is also doing video processing, I will be implementing video processing in rubyk and am interested in enabling external video processing through osc (multilayer matrix) by using a common (compressed/uncompressed) raw image format. The first goal is to use multiple rubyk instances, but it might as well be some other tool. Gaspard On Thu, Mar 5, 2009 at 10:37 AM, Xavier Miller <xavier.miller@...> wrote: > Hello, > > The MagicQ is a lighting console from Chamsys http://www.chamsys.co.uk. > > I work for ArKaos (http://www.arkaos.net) an interactive video softare > company. > > I will take a look at oscit. > > Xavier > > Gaspard Bucher a écrit : >> Your products look really nice ! I understand your need for a simple >> picture tag. "p" seems just fine. >> >> By the way, we are working on a small set of common osc >> idioms/features to help applications and controllers talk to each >> other: http://rubyk.org/oscit >> >> It would be really great if you could join in ! I'd love to see >> something like the MagicQ being controlled or controlling rubyk or >> other oscit enabled applications / hardware. >> >> Gaspard >> >> On Thu, Mar 5, 2009 at 9:54 AM, Xavier Miller <xavier.miller@...> wrote: >>> Hello, >>> >>> Here is what we want to do with OSC, and we know that OSC is so >>> potentially powerful that we will do it! >>> >>> http://www.scribd.com/doc/4021424/MagicQ-Arkaos >>> >>> Xavier. >>> >>> Xavier Miller a écrit : >>>> 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@...> 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@... >>>>>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>>>>> >>>>> _______________________________________________ >>>>> OSC_dev mailing list >>>>> OSC_dev@... >>>>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>>> _______________________________________________ >>>> OSC_dev mailing list >>>> OSC_dev@... >>>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>> _______________________________________________ >>> OSC_dev mailing list >>> OSC_dev@... >>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>> >> _______________________________________________ >> OSC_dev mailing list >> OSC_dev@... >> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev > _______________________________________________ > OSC_dev mailing list > OSC_dev@... > http://lists.create.ucsb.edu/mailman/listinfo/osc_dev > OSC_dev mailing list OSC_dev@... http://lists.create.ucsb.edu/mailman/listinfo/osc_dev |
|
|
Re: Images ?
by Xavier Miller
::
Rate this Message:
Hello,
You can try our demo software, especially GrandVJ. For now, no OSC support yet. Xavier. Gaspard Bucher a écrit : > Sorry for the confusion. > > Since your software is also doing video processing, I will be > implementing video processing in rubyk and am interested in enabling > external video processing through osc (multilayer matrix) by using a > common (compressed/uncompressed) raw image format. The first goal is > to use multiple rubyk instances, but it might as well be some other > tool. > > Gaspard > > On Thu, Mar 5, 2009 at 10:37 AM, Xavier Miller <xavier.miller@...> wrote: >> Hello, >> >> The MagicQ is a lighting console from Chamsys http://www.chamsys.co.uk. >> >> I work for ArKaos (http://www.arkaos.net) an interactive video softare >> company. >> >> I will take a look at oscit. >> >> Xavier >> >> Gaspard Bucher a écrit : >>> Your products look really nice ! I understand your need for a simple >>> picture tag. "p" seems just fine. >>> >>> By the way, we are working on a small set of common osc >>> idioms/features to help applications and controllers talk to each >>> other: http://rubyk.org/oscit >>> >>> It would be really great if you could join in ! I'd love to see >>> something like the MagicQ being controlled or controlling rubyk or >>> other oscit enabled applications / hardware. >>> >>> Gaspard >>> >>> On Thu, Mar 5, 2009 at 9:54 AM, Xavier Miller <xavier.miller@...> wrote: >>>> Hello, >>>> >>>> Here is what we want to do with OSC, and we know that OSC is so >>>> potentially powerful that we will do it! >>>> >>>> http://www.scribd.com/doc/4021424/MagicQ-Arkaos >>>> >>>> Xavier. >>>> >>>> Xavier Miller a écrit : >>>>> 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@...> 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@... >>>>>>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>>>>>> >>>>>> _______________________________________________ >>>>>> OSC_dev mailing list >>>>>> OSC_dev@... >>>>>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>>>> _______________________________________________ >>>>> OSC_dev mailing list >>>>> OSC_dev@... >>>>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>>> _______________________________________________ >>>> OSC_dev mailing list >>>> OSC_dev@... >>>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >>>> >>> _______________________________________________ >>> OSC_dev mailing list >>> OSC_dev@... >>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >> _______________________________________________ >> OSC_dev mailing list >> OSC_dev@... >> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev >> > _______________________________________________ > OSC_dev mailing list > OSC_dev@... > http://lists.create.ucsb.edu/mailman/listinfo/osc_dev OSC_dev mailing list OSC_dev@... http://lists.create.ucsb.edu/mailman/listinfo/osc_dev |
| Free embeddable forum powered by Nabble | Forum Help |
