• Products
    • Isadora
    • Get It
    • ADD-ONS
    • IzzyCast
    • Get It
  • Forum
  • Help
  • Werkstatt
  • Newsletter
  • Impressum
  • Dsgvo
  • Press
  • Isadora
  • Get It
  • ADD-ONS
  • IzzyCast
  • Get It
  • Press
  • Dsgvo
  • Impressum

Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags
    1. Home
    2. Search

    Advanced Search

    Search child categories
    Save preferences Clear preferences
    372 result(s) matching "", (0.03 seconds)
    Woland [ANSWERED] Position Data --> Data Visualization

    @emullis

    So you're all good now? Maybe it has to do with the order in which things are done. Try to experiment with whether it crashes or doesn't crash if:

    1. You open Isadora, then Rokoko, then start streaming
    2. You open Rokoko, then Isadora, then start streaming
    3. You open Rokoko, start streaming, then open Isadora

    To make clean tests, I'd do a restart between trying each of these.

    How To... ? •
    E [ANSWERED] Position Data --> Data Visualization

    Quick follow-up: I completely shutdown and restarted my Mac and restarted. No crashes. 

    How To... ? •
    E [ANSWERED] Position Data --> Data Visualization

    That's right. To test out Legacy, I streamed one of the pre-packaged mocap recordings into Izzy. That worked fine; no crash. 

    To reiterate the problem, I used the same setup for a show back in January, and everything worked great. The only difference now is software. I updated Izzy to 4.1.3 a few weeks ago. Rokoko required me to update the Studio software to the current version a week or so ago. 

    To reiterate the problem: the setup is: v2 Smartsuit, recent version of Rokoko Studio, Izzy 4.1.3, and a MacBook Pro). The crash happens when I wear the suit or stream a recording of me in the suit. I have both softwares running and, when I click "Activate" on the streaming option in Studio, the Studio Live Watcher starts receiving data and then Izzy crashes. Sometimes the crash happens immediately and, at others, it takes a few minutes to happen. I've been sending the crash reports, assuming that's helpful.

    Let me know any thoughts / suggestions.

    Best,
    Eric

    How To... ? •
    Woland [ANSWERED] Position Data --> Data Visualization

    @emullis said:

    2. I checked it with Legacy, and Izzy is not crashing with that version.

     Ah, and so you can't use the v2 Suit with the legacy version of the software?

    How To... ? •
    E [ANSWERED] Position Data --> Data Visualization

    Mine is the no Smart Gloves flavor. 

    How To... ? •
    DusX Add more parameters to Sys Ex Send

    JavaScript can't help. But Pythoner could offer a solution I am sure.

    I can also enter a feature request to extend the actor. Truthfully though that won't be a high priority item, although it might be pretty easy.

    Feature Requests •
    Woland OpenNI + Kinect v2 + macOS

    @jean-didier

    Try:

    1. Without Isadora open, unplug your Kinect
    2. Launch Isadorayour Isadora file
    1. Change the 'mode' input on the OpenNI Tracker actor to 'both'
    2. Save the file
    3. Quit Isadora
    4. Plug in the Kinect
    5. Launch Isadora and open the file

    If it works, you'll be able to use both color and depth, so you won't need to change the mode input again.

    Troubleshooting and Bug Reports •
    J OpenNI + Kinect v2 + macOS

    Hi everyone!

    I'm Jean, new to the community, so hopefully someone has already the answer for this. I've been trying the Kinect v2 on my Macbook Air M1 to play with the OpenNI actor, but had no luck trying the color mode. Depth mode is ok so far, but whenever I change it from depth to color mode, or from depth to both color and depth mode, Isadora crashes or freezes. I wonder if someone has had a similar experience and how has it been solved or managed.

    Thanks for you attention and patience on this matter

    Troubleshooting and Bug Reports •
    Woland [ANSWERED] Cue Times

    @tlaloc said:

    Just to confirm, there is no way to pull the time from the scene time shown here at 0 sec?

     Correct, this value is not programmatically accessible by actors.

    Feature Requests •
    tlaloc [ANSWERED] Cue Times

    @woland

    The reason I wish for this is if I normally use MSC to take cues/scenes, but there is an internal piece that should take the same amount of time as the scene move, I would like for that value to be able to be programmed in.

    Feature Requests •
    • 1
    • 2
    • 3
    • 4
    • 5
    • 37
    • 38
    • 1 / 38