It sounds like you're describing a problem that's purely to do with macOS and not Isadora, so I've moved this from the bug reports category. I have not seen this issue before but perhaps someone else has.
thanks everyone for your replies. ndi and yams work indeed. much appreciated. however i am still kinda intrigued about the sidecar option because it actually semi-works.
here are two screenshots for the same file with the macbook and ipad connected via sidecar but different screens assigned as "secondary". when the ipad is assigned as the primary screen or "display 1", everything works smoothly, I can use my ipad as my main display and control the scene while the macbook screen is used as the second display.
case one : workswhen ipad is display 1 and macbook is display 2
however, when the ipad is assigned as the second display, the ipad screen turns white instead of displaying the stage it's assigned with.
case 2- not workingwhen macbook is display 1 and ipad is display2
sorry if this was already clear, but I wanted to make sure that I was able to explain the problem. i'm risking repeating myself because it seems to be a minor problem that might actually be a bug that could be solved with a tiny little patch?
As I stated on the other post, you can move some of your controls to a tablet/iPad and use TouchOSC.
IDEA 2: One Isadora Patch, Two Control Panel Scenes
You can click in between Scenes in the Scene List to split the Control Panel, giving each Scene its own Control Panel. Using one or more background Scenes for your content, (activated with Activate Scene or Activate Scene Amount actors), you can use as many Scenes as you want to make individual Control Panels that all affect your content Scenes. Putting labeled Button Controls connected to Jump Actors will allow you to easily navigate between your Control Panel Scenes. Each Control Panel Scene needs to have an Enter Scene Trigger connected to an Activate Scene actor to activate your background content Scene.
Here's an example patch with multiple (primary [dark blue]) Control Panel Scenes and just one (secondary [light blue]) content Scene
Scene 1 (Effects) & 2 (Snapshots) are separate Control Panels that both affect Scene 3 (Content)Scene 1: Video Effects Control (Primary [dark blue]) uses Control IDs 1-29 (30 and 31 are used to navigate between Control Panel Scenes)Scene 2: Snapshot Control (Primary [dark blue]) uses Control IDs 995-999 (30 and 31 are used to navigate between Control Panel Scenes)Scene 3: Content Scene (secondary [light blue]) uses Control IDs 1-29 and 995-999 (30 and 31 are used to navigate between Control Panel Scenes)
If you use multiple content Scenes, you'll need to make another background Scene for scene control with Activate Scene Amount actors and Envelope Generator actors so that you can fade the different content Scenes in and out from each Control Panel Scene.
Here's an example patch with multiple (primary [dark blue]) Control Panel Scenes and multiple (secondary [light blue]) content Scenes.
Scene 1 (Effects) & 2 (Snapshots) are separate Control Panels that all affect Scenes 3, 4, & 5 (Content). Scene 1: (Video Effects Control) uses Control IDs 1-29 and 33-46 Scene 2: (Snapshot Control) uses Control IDs 995-999 Scene 3: Scene Control (secondary [light blue]) uses Control IDs 33-46 to adjust the intensity of the content scenesScene 3 is a background Scene, controlled by Scenes 1 & 2, that adjusts the intensity of the Content Scenes.Scene 4: Content Scene 1 (secondary [light blue]) uses Control IDs 1-29 and 995-999Scene 5: Content Scene 2 (secondary [light blue]) uses Control IDs 995-999 Control IDs 30 and 31 are used to navigate between Control Panel Scenes
IDEA 3: Two separate Isadora Patches on Two Screens
Control IDs work across Isadora patches, so if you've got:
Display 1: VJ Patch (with actors using Control IDs 1-999) and Control Panel (Control IDs 1-450, for controlling your bin pickers)Display 2: A second Isadora Patch with your second Control Panel (Control IDs 451-999, for controlling your video effects)
The split of Control IDS I gave was completely arbitrary, but this should work if you don't want to put it all in the same patch and use multiple Control Panel Scenes.
@woland yes! thanks, it's pretty much the same idea of using a TripleHead right? I'll try this
Yes, sort of. Making it one big video really helps things stay in synch. You may run into issues if your aspect ratios differ though. This method is also excellent when you're trying to edge-blend content across multiple projectors.
The 2060 will offer you lots of power. I run a 1070 in my laptop and I nearly never max the video card out. . Cpu always maxes first for me.
This may change if your running many outputs with stacks of effects, but I think you will find this card very capable.
The 6bg memory limit is probably the only restrictive spec. I've run into problems with 4 displays (1 operator) when loading large jpegs for manipulation before. Best to keep an eye on vram usage while working (task manager will show you on the second tab)
I like to buy equipment (when I can afford it) because the less I have to rely on equipment that I haven't used before (i.e. that I don't own), the more peace of mind I have. Example: If I build a show that uses a MIDI-USB interface, I'll buy one so that I have it for the tour and for future projects. Plus it lets me experiment on my own with test-builds, rent it out to other designer friends when I'm not using it, and often times having certain bits of tech in my "just-in case" kit has saved the day for more casual/low-stakes projects, pieces, installations, and VJ setups (both mine and others) where everything hasn't necessarily been thought out meticulously ahead of time because ideas are still evolving in an organic way on site. It also has helped me in cases where there's been dud rental equipment or other equipment failure and new equipment is needed too last-minute for rental (or even purchase) to be an option. (Also I'm secretly a dragon but my hoard is equipment, not gold.)
@kurtmeadows in general I would avoid using this method, unless you really need a feature from that pathway (like dual link 444 SDI). Also yes this is limited to a single output. The Blackmagic cards have no processing capability, it will waste a lot of resources to go back and forth from the GPU (where your image is calculated), back to the CPU and out the Blackmagic output.
It seems your need is only monitoring what you output to the projectors, this can be done inside Isadora, or by splitting the output signals, or using a multiview monitor. I would go for adding an extra monitor to you gfx card and asking yourself a split screen preview of everything you need to see. Just use normal HDMI to SDI for your output (even Blackmagic sell these do 50 bucks these days). This way is less cabling and less work for your computer as well as only requiring a single screen for preview monitoring.