After much effort blackmagic changed the way the issue SDK's for the ATEM. I halted development at the moment as it is better to wait for a clear and stable protocol. I will post the code I used if anyone wants to try for themselves. Thanks for those who were interested.
Also, have you tried turning on "Load/Save All Settings When Starting/Stopping Live Input" in the Video tab of the preferences? Enabling that function can (with some devices) lead to a long time when turning on the device... but maybe it will solve the problem? Give it a try.
The retina display is pretty amazing. It's not just that it looks great but also that you can run it at crazy high resolutions which gives you a ton of work space. I run mine at 1920x1200 which is really awesome for drafting or editing. I don't think I could go back to have a lower res screen.
Like Skulpture, I have a patch that works with touchOSC on my iPad to do this. It's really great because one of the default control surfaces is 8 x/y controllers. What makes this patch extra good (IMHO) is that when I go from screen to screen (using one of the other touchOSC surfaces) I send the current settings to those x/y controllers (send OSC to touchOSC on port 8000 by default) and this means that they all jump to their current setting.
It took some work to do this, but has saved me dozens of hours when setting up 'loopdiver'.
There are some example command strings under "Pelco-D command string examples"
You can just double click the Send Serial actor, and paste one of these examples into the dialog box.
Then trigger the actor to see if the PTZ responds.
If it does, then you'll have to do some work to figure out the messages you want to send. The biggest difficulty is that this protocol requires a checksum -- and, unfortunately, Isadora cannot calculate this for you directly. So it's going to take a bit of work to implement this protocol if you need to go beyond simple messages that are fixed, like the ones in the example above.
I will run only isadora on these machines, so no real other processes except OS.
On my i7 I never managed to get anything else than the 4 cores getting used when only using isadora.
That's why I'm thinking switching to faster i5.
As always, you provide a high degree of enlightenment to this community. Thank you for the effort you put into this post.
(P.S. I really am around to be hassled though; it's just a matter of what can get done first. ;-)
Any information for 2 ipcam 576p 15 fps minimum visible together
If I remember, I need to create a stream in quicktime first. Can I see both if it's the same model ?
Is it stable?
With IPCAM2SYPHON its possible to see up to 16 network cams at the same time in Izzy, even if the camera brand and model are the same, because every camera has its own address. The video stream is passed via Syphon from IPCAM2SYPHON to Isadora. I didn't have any issues yet with it.
Can't help you with the Blackmagic Design Intensity Shuttle. I don't have one.
Unfortunately I never had any luck with the EasyCap device, and as the above post describes, gave up and moved onto another device. I found the one that worked for me (Kaiser Baas DVD Maker) off the EchoFX recommended list (http://www.echofx.com/videoglide.html). Maybe others have had better luck with it! Hope that helps.
My first suggestion is that if you want to save money, the best cpu trade off would be from i7 to i5...
Where I have a 2 ghz i7, I seldom use all cores with Isadora, unless using other apps in parallel (which I do for video sharing to a mapping app, in which case the extra cores help run all the software nicely).
If I was to rebuild in a budget now I might get the fastest i5 available (might be like a 3.2 ghz?), that should show some real improvement in Isadoras performance, but might limit me in the multitasking.
my kinect took a heavy kick during a workshop on a darkened stage, shattering its backbone and necessitating a modification. Jamie was talking about doing this anyway to get more control over where the camera is pointing. of course i had to remove the tilt mechanism, so if anybody out there has a kinect with a burnt out motor - let me know and i'll send you all the bits in the base i removed.
That, is strange- are you sure you get a seamless switch? There is no genlock or real frame synchroniser on the individual inputs- if you get a seamless switch it is pure luck- the devices you plug into it (outputs and inputs) and the switcher are getting their refresh sync from the power source they are plugged into- not a black burst generator. If you want a seamless switch you need to sync the signals either by sending reference to all devices (this means you need gear that can accept external sync) or the switcher needs to have a frame synchronizer on every input.
It would be a lot of luck to get a seamless switch- it would mean that when you turned on your input and output devices they just happened to be exactly in sync, some screens react differently when they re-sync- for sure your capture box is not designed to do this (re-sync) quickly just, well. Maybe it takes a little longer to sync than the screen.
To get a round this you can use the freeze actor and hold a frame while the input syncs then switch back to the feed, or if you need the seamless switch you need something with multiple synchronised video inputs like the V4.
Try to set the video settings in the Blackmagic Design Control Panel.
Try to change the settings with video capture stopped.
Try to run isadora as administrator.
That kind of tricky things happened also to me.