Duration and OSC



  • http://www.duration.cc/

    Hello,
    Have you heard about it? It seems a very interesting timeline for Isadora, have a try, it's free! With a RGB actor in Isadora (Mark, any project?), it would make a perfect companion to change colors on time. Give me your advice please.
    All the best, Jacques Hoepffner

  • Tech Staff

    Yup I seen this on CDM a few days ago.

    It's a handy little tool. 

  • Tech Staff

    I have been testing it.. seems to work very nicely.



  • i think this might finally be a CUE solution for linux.



  • Hello,

    Going further with duration, I can send OSC from Duration to Izzy, but not from Izzy to Duration, as to start and stop the timeline. Any one had success with it? Any idea to resolve it?
    Thank you,
    jhoepffner

  • Tech Staff

    Wish I could help, but I haven't got that far with it yet.


  • Tech Staff

    The only thing I can see is this (which i'm sure you've read already...) but incase you missed it...

    Start Playback :_"_Does not have an effect if the project is already playing. If playback started an /duration/info message is triggered"
    I will have a look and see what I can discover. 

  • Tech Staff

    Nope I can't get the OSC back into Duration either. The DarwinRemote that comes with Duration works fine.

    I managed to crash Duration when turning the type on OSC transmit off in Isadora.... Maybe that has something to do with it?


  • Hello,

    I had exactly the same experience, works with DarwinRemote, doesn't works with Isadora and crashes when turning type off…
    I think it's a problem with OSC tagging, not writed the same manner in the 2 apps. I tried with OSCulator inbetween to relay it, no success.
    I am presently trying wit OSCSeq, not so easy and powerful, and Iannix, very uneasy and very powerful, I will give you the result.


  • reHello,

    I found the bug! Isadora sends the tag plus the info with space, like that:
    /duration/ play
    Duration needs no space:
    /duration/play
    I just made a little max app who do the trick, that works.
    I explore the other functions and I will share the result, great possibilities!
    More later


  • Hello,

    Here is the product of my researches. All is working, and Duration make a perfect timeline for Isadora.
    Give me your advice.


  • I forget the file da69bd-isadoratoduration.zip


  • Tech Staff

    Nice work @jhoepffner!

    It's a shame there has to be a MAX patch in between but nice to know it is possible!


  • I wrote to the autor of Duration and I will also write to Mark to resolve the problem.

    I also wrote a little QC patch to obtain color with RGB entry in Isadora (plus alpha value). Un fortunately, QC patches are very processor consuming.
    All is now available in my new github repository (just discovering the service)
    https://github.com/jhoepffner/DurationToIsadora


  • I've being searching for something that would enable me to go to the middle of an Izzy scene for fine tuning dancers movement sincronized with lights and all the whistle and bells... Is this the (best) way to go?



  • I really dont understand your will, what is the "middle" of an Izzy scene, time? space? Its the light synchronised with movement or the reverse? how linked? who ring the bells and who whistle?

    Be more specific!
    What I am working at the moment is to slave some events in Isadora from Duration and some events in Duration from Isadora, no more.
    All the best

  • Tech Staff

    Glad you are having some luck with it. I will try to do the same on windows in the coming days.



  • Dear Jacques,

    Isadora's OSC Transmit actor is doing what you are telling it to do: send a string parameter ('play') to the OSC address "/duration/"
    The format of this messages is: address, type tags, value(s). What you were sending was this:

    OSC    | 127.0.0.1:1235 | 2F 64 75 72  61 74 69 6F  6E 2F 00 00  2C 73 00 00 | /dur atio n/.. ,s.. |

                            | 70 6C 61 79  00 00 00 00                           | play ....           |

    If you wish to send to the address /duration/play" then just put this in the 'address' input and set the 'value' input to '' (an empty string.) The output will look like this:

    OSC    | 127.0.0.1:1235 | 2F 64 75 72  61 74 69 6F  6E 2F 70 6C  61 79 00 00 | /dur atio n/pl ay.. |

                            | 2C 73 00 00  00 00 00 00                           | ,s.. ....           |

    Now, there will still be a type tag ",s" followed by an empty string, but this will hopefully not affect the receiver.
    Give it a try.
    Furthermore -- you really should **never** turn type tags off. If there is no type tag, then the OSC standard states that you should assume the parameter is a float. This is the quote from the OSC spec:
    Best Wishes,
    Mark


  • Dear Mark,

    I will give it a try (I give tomorow a 5 days class about Isadora, good time to try…).
    I have made some other tries, you can see it on github (address gived before),
    Thanks


  • Mark,
    I just tried it and sending a empty string with /duration/play adress doesn't work, that's works perfectly though OSCulator, suppressing the argument, or Max, suppressing the space.
    I wrote to James Georges, I think the fault is on his side, normaly a good OSC message have address: /duration/play and message, like timecode as string : 00:01:30:222 in /duration/seektotimecode who works perfectly.
    But the best way is to enslave Duration to Isadora: varispeed, stop and go in Isadora, capacity to change the parameters in live in Duration, recording it.
    I am just trying to record live OSC in Duration.
    That made a perfect partner for Isadora.
    Thanks


Log in to reply
 

Looks like your connection to TroikaTronix Community Forum was lost, please wait while we try to reconnect.