@hollyjw

it works. You must link the monitor ID to the video out of the video In Watcher.

Click on video to get this panel and enter the ID of the Monitor Control (in the picture it is 1)

best

Jean-François

@mr_j

In Isadora 3 you can create a Virtual Stage (done in the Stage Setup window) and send to that rather than out to Syphon.
Then use 'Get Stage Image' to grab the image from the stage, and continue to work on it.
The workflow is a lot like your piping method, but fully internal to Isadora, and if using GPU-video very fast.

Dear All,

In the Isadora User Group, Yoshi Tanokura asked:

Hello!  I'm sorry to bother you with a basic question, but if I have a video of an actor acting in front of a green screen, how can I superimpose an image and manipulate the image?  For example, if I want to slide the background image off to the side while a different image slides in, how can I set it up...?

I used the Chroma Key actor and was able to set the background, but that's the extent of my success.  I would love to find out the various way of achieving this.  Thank you!

Below is an example patch for Isadora 3.0.7 that should help illustrate the idea.

You'll need to turn your video camera input on in the Live Capture Settings for this to work, and probably you'll need to adjust the 'hue' input of the Chroma Key.

Enjoy,
Mark

chroma-key-background.zip

@woland

Brilliant! 

Many thanks!

jbb

@gaspar

NDI HX Camera from Newtek is now back in the Google Playstore. 

Best Michel

I use NDI on a closed network (with no internet access) on an iPhone. It's great. A good, fast network is important.

Cheers,

Hugh

@videosmith

Great! Gonna try that as first thing in the european morning!

Thanks!

@fubbi cheers again for helping out on this! Your instincts were right!

@juriaan

This is the expected behavior 🙂
and it will remain this way.

@Kathmandale 

Thanks for the pointers, insight and knowledge. All very helpful and good information to digest.

I downloaded the videos off a list from youtube ( copyright is in place) and the exhibition is part of public facing element on vaccines. The content was existing videos given with consent for the project. I am playing about 12 videos on a loop and all was fine till I realised the designer had put a rounded rectangle in place.....

I take you points re warping. I will follow your guides ref re-using the mask directly and see how I get on. All the scene are set up with a user actor so I can trial it quickly enough.

Again, many thanks for all the advice.

eamon

@woland thanks!

@fred I can see how that would be convenient for many things. I'm less than a month into learning this, so everything is new.

I'm still having trouble getting the mouse wheel to control the zoom. It doesn't seem to deal well with feedback loops. I want to get a value, add the scroll wheel delta, and put it back in that value. But even watching for triggers, I haven't gotten it to work cleanly. Seems to add the number a bunch of times in a loop.

For now, I'll just use right-mouse-down with vertical position for the zoom.

So I have left-mouse-down to drag the box around the screen and right-mouse-down to change the zoom. It's working well enough, but it seems kinda hard to get the mouse wheel controls to do what I'm looking for.

@houssem

@DusX, can you have a look at this. Works fine on Mac, seems to be a Windows issue.

Best Michel

@keftaparty

Yes, it's very odd: I can control the ATEM from Companion, no problem.

And I can see the OSC port - 12321 - and address (for example/press/bank/1/2/ ) at the bottom of the Companion configuration page

I can put these values into Isadora's OSC Transmit or OSC multi-transmit actors, but they don't seem to be successfully sent to the ATEM.

Maybe I have entered the values wrong in the actor:

For OSC Transmit I have:
UDP Address: localhost
port: 12321
address: /press/bank/1/2
use type: on
Value:

@sage

By the way, you don't need the video to image actor anymore. The video  input  and vider output are mutable so you can connect a ci actor to your video player:

@eraserhead said:

deactivates editing of the parameter until the knob has reached that value. So if my knob is at "0" and the parameter is at "100", the "100" value won't change until the knob gets to 100, instead of jumping down to "3" as soon as I start moving the knob.

I made a patch that does this as well as relative (but relative is much worse because it gets really inaccurate until you get back up to 127 and it resets). 

2020-11-20 - 3.0.7 - Relative Midi Encoders.zip

@angélique said:

Is that possible to split one stage in three  only with one projector so that my parameters (the size of each split) could be kept for the following scenes?

Like DusX said, you can use Chopper actors to break your video into thirds. I'd then suggest putting those in a User Actor because when you make changes to this User Actor in any Scene, you can choose the save the changes to all instances of the User Actor. So if you have this User Actor that contains your Chopper and Projector actors in all your Scenes, you can adjust it in any Scene and the changes will be made to all the User Actors in your other Scenes too.

Another method is to route all your video back to a secondary Scene and have that Scene be the only one that has Projector actors. Take a look at my Global Mapping Template.

If you're talking about actual signal splitting to physical displays (i.e. you want to have different Stages assigned to different thirds of a physical display), please take a look at this article: https://support.troikatronix.c...

je vous remercie beaucoup pour votre réponse, je l'ai essayé et il fonctionne. 

@jvo96

Just keep in mind that NDI needs more cpu than syphon. If you need the feed on the same machine syphon is the better way to go.

Best Michel

On a related point, I used to make great use of a plugin shared on the forum years ago called 'ReadTextFromFile' or something very similar to that. I can't remember who shared it originally but it was great. It allowed you to read a plain-text file line by line, so was perfect for titles, captions, etc and you could edit the text in a text friendly package that could be easily shared with writers/directors etc.

I guess now that work flow could be replicated with the Data Array actor. You could also use it to record and recall other settings, such as font size, colour, position all stored in the same tab-seperated text file. The file could be easily shared and edited by other people as well.