@msanii This is the service/process, that is playing your videos you loaded in the movie player actor.100% is totaly fine as it defines the 100% by processor thread it uses. If you have a dualcore processor with 4 threads, the process can use up to 400% theoretically.This is why the graph below is just showing a low processor usage of around 20% (lower left numbers, System + User. Idle is what is unused CPU power) while the process is  at 100%. BestDill

@markIt' look grate. I'm impatient to try. Whishing you good job to achiueve this release.Best rgard Oliver

this request is no longer needed, now renting

Thank you so much for all your input! All your comments make it easier to make the decision.... Best regards to everybody!

@fred Going prores didn't quite resolve the issue. Coming back to the issue of odd bitrates. Do you mean odd as opposed to even numbers or odd in the not coherent sense. Attached is media-info screen capture indicating data for one of the videos. By the way I forgot to precise the After-effects work is done on a windows machine hence the use of Lavf57.83.100media-info data

@dusxI will try it,Thank you so much

@bonemap  I agree with many of the things you are saying. And that is why I create last year the Isadora Latin Network -RIL- the only art network authorized by troikatronix in Latin America, to give workshop, artistic project developments and share different experiences about Isadora and its great potentialBest,Maxi

@Michel ok I will after the V3 release.  Thanks!Best,Maxi

@fred said: Just a simple collect all media (and it collects everything in the project and copies it to a location of your choice, organised in bins and media types.  Yes, this would be such a useful feature when moving, backing up and archiving projects. The versioning feature is also an interesting one.Best wishesBonemap

@dusxHi,thanks for this. I tried it out and it works almost fluent.best wishes,frank

@stephaneDepending how large the dots are you could do that with a usb camera, chroma key to select the color and the eyes++ actors. There you have the obj. count output.Best Michel

@dillthekraut That looks brilliant.All these suggestions look great. It took a while for responses to come so I didn't realise anyone had responded but I've just finished touring my last project and started on the one with the interactive walls. I've got a lot of tech and experimentation to begin but this is a fantastic starting point. I got a kinnect for £8 and a webcam and am away from home for 2 months so I'll have a play with those then try out the Pi/Arduino/touchboard suggestions in the new year. I'll share my progress.

@dusxThanks for that tip too.best,frank

I would recommend going the Black Magic route, as the hardware is well tested with Isadora, and the native drivers are integrated. The AJA may work well, but we have not tested it in house.

@plastictaxi said: ...so, is "2 instance izzy" is a hack? or just a riskier way of running?   The fact that you are experiencing program crashes probably answers this. I guess we learn our own methods and developments when putting shows together. It is really wonderful that Isadora allows the flexibility for each user to craft a unique system.  Technical theatre operators in my city are still apprehensive about my methods when I work in their theatres. They are unfamiliar and skeptical about a software that controls all the technical aspects of the theatre in one box. One of those concerns is really valid, and that is the question of is the system prone to crash? And how long will it take to reinstate the system when if it does? If you are using Isadora and experience a program crash, even once, during a public showing in a large theatre it is going to be hard to recover from that in terms of the level of trust and anticipation of risk when approaching the next production. There are many ways to mitigate the risk, such as assigning a solid black desktop color and setting projectors to a black screen so that you are not suddenly projecting unintended logos and desktop images in front of audiences if Isadora crashes. I tend to develop total theatre projects where all of the elements interact and it all happens in primary and secondary active scenes within Isadora. I am more inclined to run multiple instances of Isadora on separate computers and network them together. Often I will have a patch on a machine that is focused on audio and running visuals and another machine that is running lighting through a dmx interface and running more visuals. I have used KVM switches to monitor and access each machine but generally building one control interface that can be extended to a wireless controller such as TouchOSC. But I would say that using Isadora enables great diversity in application that extends far outside the standard formats of technical theatre and well beyond the architecture of the theatre itself.  We may have to accept that with great flexibility we are prone to programming in less stable territory. And it might be that the openness and diversity of valid approaches possible when developing with Isadora is also a reason that it is underestimated and perhaps undervalued by the sector? I am speculating. Best wishes Bonemap

Thank you! Solved!

@markThanks for this example!best,frank

@mark_m i would like to use two of them. My only Idea for the moment is to use another small computer (Latte Panda) for 1 of the tablets and send mousedata via OSC or netbroadcaster. the other tablet can use the stagemouse.  It would be better to have HID only.h