I have a video camera that I will turn on its side to capture in portrait (vertical) orientation.

I will feed that into Isadora via HDMI capture. The image will be HD (1920 x 1080) and in landscape orientation.
So I need to rotate that image 90 degrees so that it matches the orientation of the camera. I will use this image across lots of scenes.

I thought I would go:

video in watcher to projector to a virtual stage. Make the virtual stage 1080 x 1920 pxSpin the projector 90 degreesUse Get Stage Image of virtual stage to bring the rotated image in the correct orientation into my scenes.

However, my camera input on the virtual stage does not fill that 1080 x 1920 px stage: I have to zoom in to 175% on the virtual stage's projector to make it do so.
I think this is affecting the image quality.

I tried this:

video in watcher to projector to a virtual stage. Make the virtual stage 1080 x 1920 pxSpin the projector 90 degrees.In the projector turn OFF keep aspectchange height to 55% and width to 178Use Get Stage Image of virtual stage to bring the rotated image in the correct orientation into my scenes.

So this works better, but is this having an effect on image quality too? 

OR am I missing something very, very obvious?!

Here's the  project file for anyone curious...

vertical-video.zip

Or a link to the Isadora file in Dropbox:

https://www.dropbox.com/scl/fi...


Thank you all! 

Mark (no....)

@jaio

If you can find a suitable cube LUT, for converting rec 2020 to rec 709, you could use my 'color grading' shader (TROIKATRONIX : ISADORA - DX – PY – Cube2LUT – ColorGrading).

This should allow you to convert the color, but will not be as true to source as making the conversion in something like Davinci Resolve (my recommended option).

a workaround is to use a font with a capital version like Bodoni 72 and Bodoni 72 small caps and to switch between both.

Best regards

Jean-François

Honestly this confused me too when I was buying my first projector. Lumens measure total light output from the projector itself, while lux measures how bright that light appears on the screen - lux depends on both lumens and screen size. So same projector will have higher lux on smaller screen and lower lux on bigger screen. For comparing projectors, always use lumens since that's the consistent measurement regardless of screen size.

I use an Optoma projector and when I was evaluating, I focused on ANSI lumens specifically - that's the standardized measurement. Some cheap brands advertise "LED lumens" or "peak lumens" which are inflated numbers, not real brightness. For dark rooms 2000 ANSI lumens is fine, ambient light rooms need 3000+. Don't get fooled by high lux numbers on small demo screens in stores - always ask for ANSI lumens rating before deciding.

@alex-x-audio

This looks very interesting. Could you provide a download link for the Max for Live devices?

We'd also love it if you could upload them to the Add-Ons Page with your description, as posts with useful tools eventually get buried in the forum over time.

@woland Many thanks L! Hopefully it’s possible.

Best wishes Simon

@emullis

Actually, if you humor me one more time, there's one thing we didn't try. Based on the fact that you stated this same setup used to work for you with an older version of Isadora, we should try that.

Can you:

In Isadora, go to Help > Open Plugins Folder > TroikaTronix Actors PluginsSelect everything in that folder, then right-click one of them and select "Compress"You'll get a .zip file that you can later unzip and use to restore the contents of this folder later if need beDelete everything except the zip from that folderQuit IsadoraInstall an older version of Isadora using our Legacy Downloads Page (I'd suggest starting with 4.1.1 and working backwards)If you want to keep the recent version of Isadora on your computer too, see this article on how to install multiple versions of Isadora on your computerTry streaming data from Rokoko again with each older version of Isadora and see if any of them are stable with your v2 suit.

One other idea, that unfortunately requires different hardware, is seeing if a Windows computer running Rokoko Studio and Isadora is stable for you. I know this worked for an artist I collaborate with in the UK who uses a v2 suit.

@dusx

Thank you. Managed to do this with the help of Claude Sonnet 4.6  which showed me how to retrain the data using something which has the same landmarks as in your Mediapipe pose tracking examples.
This seems to work very well, thank you. 

Not sure how to share the process? 

I took maybe 25 photos of each of 14 poses (yes, different handstand shapes, of course!)

Then organised them into this folder structure

training_data/
    arms_crossed/
        photo1.jpg
        photo2.jpg
        ...
    arms_raised/
        photo1.jpg
        ...
    lunge_left/
        ...

And then followed Claude's instructions. 

Here's my Colab notebook:
https://colab.research.google....

After I'd successfully trained that and got the files out the other end...

It then gave me the python mediapipe code. 
https://www.dropbox.com/scl/fi...

And that outputs the OSC into Isadora. Two streams, one telling me which pose it is, and the other giving me the confidence about it.

Hope this is useful to someone!!!

Cheers

Mark (not that Mark, who I'm sure doesn't use Claude to do his coding!)

@woland Thanks a lot. That makes sense... ;o)

@jjhp3 said:

Any ideas about getting the VSTs?

Depending on the names, sometimes you can look them up to find them (if they're from a specific company).

@dbini

That helps. Thanks for the quick response.

many greetings

Matthias

@piotrtwon

Hi!

I am going to direct you to our Support Ticket system, so that one of our Support staff members can help you further with this request.
You can open an Support ticket here: https://support.troikatronix.com/support/tickets/new

Short answer; we have options available within the product to do object-tracking in Isadora.

With kind regards,

Juriaan

i think i remember - a long time ago - there was a feature request to get the Eyes monitor feed as a GPU output, but that has not manifested.
it is possible to create a visual representation of the blob tracking system using Eyes++ and a lot of Limit Scale Value actors to process the outputs from Blob Decoders and control Shapes and Lines actors, maybe with a Threshold on the video feed if you want to simulate the blobs. The useful thing is that Shapes, Lines and Text Draw all have GPU inputs so you can daisychain them together to add graphics onto your video feed.

but maybe Isadora isn't the ideal solution to achieve this effect? object tracking in browsers is getting really good these days, i'm sure that a quick search around github will find an app that can do what you need instantly, then you can pull the results into Isadora with Screen Capture

@mark_m

Hi

This is my bad. I confused the qlab one on the add-ons page with a one for isadora/eos.

But, if you peruse the links posted by Woland above, there is a treasure trove of information, guides and files to achieve the aim of using OSC to control lighting cues on the eos consoles. 

I read through those links and ,as usual, leant more than I thought I knew! I would start with those guides and Marks Guru session on OSC. I am sure ETC has OSC guides on their sites as well as having a healthy forum akin to here. One of the links gives a very detailed step by step set up guide here. 

You do not need the console but could practice this set up with 1/2 computers. Once they are speaking via network, then you could play with the command syntax and be ahead of yourself before you enter the venue. The venue lighting staff should be up to speed with this approach as it has become a very normative practice in the industry.

You are only sending a simple GO command to eos at the end of the day. You can specify the number but the syntax is very straightforward etc. Once you have the first one down, then it should be a simple rinse and repeat.

Eamon

@skuven

I've added this to our existing feature request for this

@taeeix

You might try changing the video Projector actor ‘blend’ input from ‘additive’ to ‘transparent’. You could also try changing the same Projector ‘layer’ input to a higher value than the base Projector layer.

Best wishes

Russell

For anyone coming to this for answers like I did, there is now a "Float to Integer" actor that will do this. And if you're using a timer, which actually outputs in millis, divide by 1000 to get seconds first.

@jean-didier

Try:

Without Isadora open, unplug your KinectLaunch Isadorayour Isadora fileChange the 'mode' input on the OpenNI Tracker actor to 'both'Save the fileQuit IsadoraPlug in the KinectLaunch 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.

@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.