However if you double click the second user actor (and it is a global actor) then surely you don't really need a second window opening as it is the same thing anyway. Could you not just bring the (already open) expanded actor window into focus?
And you could keep the tabs but just have the option of dragging the window out of the tab to a new window (like your browser).
Sometimes you need to watch what is happening inside an actor and watch what is happening in the main patch. You can't do this at the moment.
Failing that maybe a keyboard shortcut to cycle between windows would be an option?
I am using snapshots alot, and I find them very powerful.
I even find that usually I can do many updates to my patch and simply update my snapshots and all is well.
However, sometimes things happen, and they are lost of overriden etc. Also once you have many it gets confusing what is what.
I would like to be able to give a name to each snap shot, that is shown right after its number, further I would like to be able to save these snapshots.. maybe scenename-snapshotname.fileExtension ?
and be able to load them back into a scene if needed.
I would love to be able to select an audio file in the record stage settings, that would be used as the Live capture sound source (played at the correct speed).
Many of my effects are setup using live audio to drive them, but have to be repatched before they can be recorded since the audio ch data doesn't work as expected.
I know that it is possible to set up a cue sheet for each scene and link it to your trigger or triggers, however, I would like to use scenes as my main cues and triggers within a scene as sub cues. I know this is easy within Isadora, but I would like to have the ability to have cues / scenes automatically add a prefix of a number (or letter based on user prefs). For example, we run a series of about 20 different scenes in our lobby area here and each time I add in a new scene (or move them around) I either have to renumber everything or start adding in a secondary naming system (like 16.A). I know that numbering isn't always the system of choice, but if you're trying to mirror a text file somewhere for easy reference -- auto numbers make things move faster for sure.
Further, I think it would be fantastic for a global cue sheet that breaks down triggers within scenes, automatically. The information is already there!
Some Cue (scene 1)
Some Subcue (trigger 1.1)
Some other Subcue (trigger 1.2)
Some Other Cue (scene 2)
Lastly, it would be great to have the ability to then export that global sheet to a text file. Of course, you can take a screenshot, but then you can't style it!
If this is already possible and I am overlooking something or there's already a way to do this, please tell me!
My only thought is that wireless video is not really there yet.
many VJ's have talked about it on the VJ forums and unless you are willing to spend a lot of cash to hire in big machines (basically mini microwave links) then its just not really "performance ready."
The cost of running a huge HDMI/VGA or Cat 5 cable is much cheaper rather than running expensive wireless video.
The apple TV is great but meant for home/classroom use.
However I thought that Isadora did see the display ports as an output - there has been a full post on this thread about the macbook retina and display ports?
I knew it wouldn't be easy, but I asked in case...
For the moment I'm working with demo versions on my exported patches on other macs.
By the way, is Firewire video output still locked on demo version ?
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
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?
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.