Just upgraded to 3.2.6 and surprised to see the massive increase in CPU usage for live capture. I'm on a mac using a HD USB webcam, set to 1280x720 capture in Isadora. With 12 cores (so 1200% is max), Isadora 2.6.1 jumps to about 90% whereas Isadora 3.2.6 jumps to about 950%. Just wondering what's happening there?

@jfg thank you !

i will try it

@emullis

They've essentially said the same thing to me. Hopefully if they hear from enough of us they'll add the feature back in.

@skulpture said:

A seperate pop out window for the control panel with full screen features would be amazing for kiosk style installations.

 Logged :)

@notdoc

This is already quite possible through the use of Comparator and Time Comparator actors hooked up to the 'position' output of the Sound Player or Movie Player actor.

>>>Example File<<<

@notdoc

Unless I misunderstand, what you want to do is trigger things based on the current play position of a video or audio file. This is already quite possible through the use of Comparator and Time Comparator actors hooked up to the 'position' output of the Sound Player or Movie Player actor.

>>>Example File<<<

@dbini Thank you so much for your tips. I will definitely look into the IR option. I'm intrigued that CCTV camera can be used to create amazing effects like you did! At the moment, due to the budget restrictions, we may need to opt to the placing the camera in different area option.. haha.. Thanks, again!

@mark_m

strongly agree...

@morfin_mafer

Yes, that's exactly what you need! Perfect.

@kathmandale really great, always wanted the AE wiggle ability!

@woland 2juriaan

Thanks a lot 

@gunther Thanks !

@woland said:

Do you have OBS's virtual webcam going at the same time?

 No. I saw that, so I closed OBS. But Zoom is opening a 'crash report' dialogue box literally every time I open it, so I think the problem is there. I've reinstalled it twice. Sometimes I get the black screen as above, sometimes i get the OBS image below:

@dillthekraut @dbengali

Hi there, Mark here. We've discussed at our tech team meeting today and I personally have no answers as to why this would on macOS. We have added as a concern and will be investigating it over the coming few weeks. If we can find a way to recreate the problem on our on computers, I (meaning Mark) will put some code into an Isadora debug version to monitor this and see if we can prevent it.

Best Wishes,
Mark

@dusx

thank you very much, found your dm.

r.

@woland Thank you so very much for all of this, SUPER HELPFUL! I'm enjoying learning this software so much and yes that article helped a lot! 

@dusx

aah yes that worked well! Thank you for the help!

@rotrocchia said:

is there a way to send audio from the video players to separate sound players? 

Unfortunately, no. We have plans to make an audio output from the Movie Player so that the audio can be run through other audio actors, but at the moment you can't send the audio from a Movie Player actor to a Sound Player actor. The article Bonemap linked above about multitrack audio using macOS is the place to go for multichannel audio routing with the Movie Player actor.

I'm not sure if there's a solution for multi-channel audio routing from a Movie Player on Windows right now. @DusX @Juriaan any thoughts?

@rotrocchia said:

Isadora recognizes the Tascam but none of the equalizers in the Audio View are showing any input even though all of the speakers are producing sound.

This is because the Audio View is for the new multichannel audio routing system that's been implemented in the Sound Player and Tone Generator actors. Audio from the Movie Player actor uses different audio code and thus won't show up in the Audio View. We intend to give the Movie Player actor the same multichannel audio routing capabilities as the Sound Player and Tone Generator actors as soon as we can but at the moment we've got our hands full developing IzzyCast.

@bbonilla

We are working on a feature that will allow these to be controlled from the Control Panel, but for now the only way is knowing what the source's name will be ahead of time and hard-coding in a Selector actor connected to a Popup Menu or Radio Button Control and using that. So unfortunately, at the time being, if you don't know the name of the sources when you're creating the file, you currently can't use the Control Panel to select different sources for the Screen Capture and NDI 5 Watcher actor plugins.

You can, however, do something like this: https://recordit.co/Mr7nY6e6Mq

Example file ---> DOWNLOAD

Steps:

Optional: In Isadora > Isadora Preferences > General Tab > User Interface you can set Control/Actor Font Size to the max (24).You may need to zoom in once to get everything to re-draw with the proper proportions (only this first time, from then on it'll be fine. Small bug, already logged.)Go into the View Menu and hide Toolbox (which also hides "Toolbox Filter"), Media + Information (also hides "Media" and "Information", Scene List (also hides "Cue Numbers"), Snapshots, Audio (hidden by default), and Status Bar (which also hides Timecode). The only hidable thing that's left unhidden is "Scene Settings" (so we can use the hashtag menu to navigate).Make your Control PanelPut big instructions in itOn the Scene Editor side of things, right-click the Screen Capture/NDI 5 Watcher actor, select "Show/Hide Properties", then hide any inputs that the user won't need access to in order to simplify things as much as possible.Put BIG Comment actors with clear instructionsEncapsulate each of the actors you want to navigate to in a Background actor and rename the Background actor to "#[ACTOR NAME]"This will allow the User to easily find the actor you need them to be able to find using the hashtag menu at the bottom right. (See the gif: https://recordit.co/Mr7nY6e6Mq)Use these big Comments and the Background actor to make it very clear what to do and how to get back to the Control Panel.Now your user can open the Scene Editor, find what they need, modify it, and go back to the Control Panel easily.

@dusx

I'd like to add, this is a system setting, done in the monitor settings (color managment) of the OS. Every device does offer a specific color range, it can show. So it may be able to show more or les colors or have the same amount of possible colors (eg. 16+ milions), but differences in the color shift. You need to match the color profile to the displays/projectors profile (some standards are sRGB, Rec. 709, DCI P3 e.g., or even device specific). This applies to print as well. This is easier on MacOS then on Windows, as MacOS already offers some profiles. Just switch between them and you'll immediately see the difference.
find some details here.

One other setup is a quiet unknown: Full vs. limited RGB. RGB values on full are 0 - 255 for each color (Red, Green, Blue). Limited only use 16 - 235. Full is used by PC and grafic setup, while limited is most time for Video. 
Here is an complete article for it.
This setting has to be consistent for the whole chain of devices, from Input (if some camera capturing is done) over the GPU output to the display device or needs to be converted properly.
If not, results are crushed shadows and flat highlights or gray blacks and whites.