Heres a demo.
In this case I am checking only the range of the second bin. The Inside range will show if the bin is the active input.
I am feeding 2 Bins into 1 movie player so that I could easily route the 2 inputs to one test.
The user actors 'DX int thru' are empty actors that just pass the Interger values thru (I use them to allow branching when needed).
So the 'inside' output of the INSIDE RANGE actor will tell us what bin is active. You can use this to output text or what ever you like.

b54ace-findactivebin.jpg

I wish that the codec allowed the compression to be set.
I did not like this about DXV either.

My bad... I forgot to tell I was using sound players! With movie players, everything works as expected. I converted the aiffs to movs, because the sound players would always skip a couple of audio samples when jumping from one scene to another. I am on a mac and 10.8.3.. Tried the pre-release yesterday and that solved many anomalies. Thanks again to Mark!

Best, D.

Thats my understanding as well. Still its the direction I am aiming.
My FFGL collection is already growing.

OK. Test with 11 pictures. Output 1024x576, target frame rate 30. I get 19fps with user actor version and 25fps with chain players.

Target frame rate 60 brings actual FPS to 29. It seems that i can not go up to 100 with this MBP without loosing frame rate. I can get by with 23 maybe. Will see how this turns out. I understand the beauty with this approach where I can adjust to any output on the fly. Great.

Dear Craig,

Thanks for sharing the success story. Good to hear! Best Wishes, Mark

Great thought.
Going to have to work out some user actors for this purpose.
A global option, like I mentioned would be a big plus for me, but this will work in the meantime, just a little more work with multiple sources.

thanks.

Even an addition to the new Current Scene Number actor that outputs the scene label as well would be helpful because it would make it possible to have the patch update a user implemented lookup table automatically without tedious programmer intervention.

DusX: It's a nice workaround, but i won't get the X,Y cornerpin that i need...

I will post this as a feature request.

could please anybody with 10.6.8 try the "Send Bank Select" actor and let me know if it works with SimpleSynth or other software? Thanks

Hmmm.... this seems strange. I'll have to investigate this but will need to do so after Feb 17th. Please send it in as a bug report.

In the meantime, do the following: 1) Make backup 2) Disconnect original machine so backup is not connected to anything 3) Load patch... Isadora will find the files relative to the patch 4) Move an actor to make the document dirty 5) Save This should force the paths to be updated so that it will not look on the remote machine. Tell me if the workaround works or doesn't work for you. Best Wishes, Mark

Yes its true what you say.
It's not really an alternative to what you have asked for but I thought in some cases it can help.

Best,
Michel

Can't wait 🙂

Dear DuxX,

Unfortunately, here's no way to do that. The only way is to turn quit Isadora and restart it.  Best Wishes, Mark

bug report posted

Thank you Mehdi

You might also familiarize yourself with the macro. It's like a user actor but just an individual isolated instance and it does what the group and shrink tool you envisioned would do but slower.

@Mathew, yes apple script for sure would be easier to implement. 

Boygrouping is much more than VNC, it is very intelligent and gives excellent management over your slave machines without really having to see the screens http://vvvv.org/documentation/boygrouping-basics Fred

Thanks Fred for looking into this.

Best,
Michel

I will.
I worry about changing it though, rather than adding the switch as a feature. I think in my case (maybe others) that a fix (that changes behavior) will cause numerous other problems in my patches.
I have a few bugs on the go right now, so expect a test files in the coming week.

I would like to be able to right click and select 'actor count' and see how many times the actor is used in file.
Further, if we could view print and list of the paths to locate all the instances.. eg root->MixerActor->Crossfade->ActorInstance

Later
This could be very helpful, and later may be useful in extending to a debugger system, where on error you can see the path to the at fault actor?? Maybe directly open it?