Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

foolcontrol - power fool DSMC camera control

Patrick Spohrer said:
Any plans for compatibility with Blackmagics new micro panel?

-patrick
Click to expand...

Hello, foolcontrol supports BM's mini recorder for video input via their desktop video SDK (software developpement kit) but as far as I know there is no SDK for their panel.
I own a tangent, and do not think i'll get a panel exclusively for resolve at the moment, so no immediate plan to be support it.
 
When marking a frame using 'm' on the keyboard - if you press a little too long, multiple frames are marked.

Is there a way to counter that?
 
Robino_J said:
Were you able to stop the m key from repeating?
Click to expand...

Sorry have been shooting the last couple days. So I just did it now... it's available in the beta build 215 :

http://foolcolor.net/foolcontrol_beta.zip


BTW the repeat behaviour / rate in foolcontrol should inherit macOS's keyboard System Preferences for 'Key Repeat' and 'Delay until repeat'.

Quick fix (only for M key as some other keys need to be repeatable like focus or Motion Mount shortcuts) so let me know if it works for you.
 
I've been using foolcontrol for ios for a while now but recently bought a scarlet-w and a decided to also buy the foolcontrol osx to step up the foolcontrolling, but the cameras wifi crashes a lot and that's annoying when using the iOS-app but even more so when using foolcontrol for OSX because when reconnecting to the camera, the camera changes the focus (as if it is calibrating the lens) and that makes the osx-application almost useless, is there a way around this?

Since the wifi in this camera is so bad and I'm starting to give up the idea of it getting any better I'm also curious about getting a work around using cables, we don't have a Gig-E port on the camera, but if I've understood correctly it should be possible to use the ctrl-port, how do we do that?
 
Petter

Please email me mika at foolcolor.net .... I can certainly add an option to disable the lens calibration on connect and send you info on the DIY ethernet to serial cable solution for OS X.
 
I'm still in hope to find a good configuration that allowed me to use Foolcontrol with wifi, for two reasons:

1 - I do not use PC (only Mac) And as far as I understood, I need to use a PC to configure the hardware converter every time I need to use it ?

2 - My main purpose is to use it with a RED inside a housing, so a simple antenna with wifi in the housing is a simpler solution instead of a DIY converter using the control port.

That said, I've found that the wifi signal of RED is a little bit moody, even in infrastructure mode, no matter the firmware version. Take a look at this thread where I've posted my assumptions: http://www.reduser.net/forum/showthread.php?159772-Wifi-unreliable&p=1745163#post1745163


I would really like to make wifi a trusty option. Any thoughts?
 
Rui Guerra said:
I'm still in hope to find a good configuration that allowed me to use Foolcontrol with wifi, for two reasons:

1 - I do not use PC (only Mac) And as far as I understood, I need to use a PC to configure the hardware converter every time I need to use it ?

2 - My main purpose is to use it with a RED inside a housing, so a simple antenna with wifi in the housing is a simpler solution instead of a DIY converter using the control port.

That said, I've found that the wifi signal of RED is a little bit moody, even in infrastructure mode, no matter the firmware version. Take a look at this thread where I've posted my assumptions: http://www.reduser.net/forum/showthread.php?159772-Wifi-unreliable&p=1745163#post1745163


I would really like to make wifi a trusty option. Any thoughts?
Click to expand...

The hardware ethernet -> serial converter I sent you info for only needs to be setup once on a PC... And that can be done in parallels or bootcamp setup (I only use mac here too).

That said Ryan Canon from reefphoto / Nauticam posted a nice DYI antenna extension he tested for underwater housing and DSMC2 wifi setups... it might be a better solution for you as it does not require PC setup or providing 5V inside the housing to the converter hardware...

http://reefphoto.com/kb.php?id=108

Looks like they now even has a cheap product for sale to do this on a nauticam housing :
http://reefphoto.com/shop/index.php?main_page=product_info&products_id=9222


It does require a properly working wifi tho and maybe your camera or setup has some interferences / wifi issues that need to be worked on first... RED did improve camera wifi reliability in recent beta FW... hopefully that will solve your issues once it becomes a release version.
 
Hey Mikael,

Yes I'm aware of the ReefPhoto solution. I'm using a similar one here, and I've tested with success several times before using it on set. But Murphy's Law dictated that it failed in two different situations on set, with the exact same configuration that was previously tested.
That's why I've run some more tests at my office, without any housing or surface cables; just the Weapon (with top handle and Red touch 7") and next to the computer (less then 50 cm away) to see if there is some reliability issues with the wifi itself. And sometimes I saw that the connection just freezes up and a camera reboot is needed. Most of the time this solves the problem, but not always. And of course that our friend Murphy was with me on set so no matter the number of camera power up/down cycles, the connections didn't came alive again :-( My assumption is that wifi signal strength plays a major role here.

Good to know that the PC configuration is only needed once for the hardware connection. But I really want to avoid that route altogether.
Even better will be a more robust and reliable wifi connection. Didn't know that the new firmware also improves wifi connectivity. In my tests with the BETA version, I didn't noticed any improvement, but of course they are not scientifically done and this is not yet a release firmware.

Meanwhile I am trying some slightly different antennas. Another option could be a router inside the housing to create a very strong wifi network and another router (in repeater mode) at the other end of the cable at the surface. Maybe this way the signal gets strong enough that the connection stays strong and reliable.
 
Mikael Lubtchansky said:
Or a jetpack SDI module with GIG Ethernet... that's 100% reliable :)
Click to expand...

Not really...besides the obvious additional cost, it will not be usable inside my housing, with the two V-lock batteries... :)
 
Hi Mikael, I have a question. Where/how do I access the single frame trigger in the Foolcontrol menu? I can't seem to find any reference to it in the forum. Thanks.
 
Morgan Ryan said:
Hi Mikael, I have a question. Where/how do I access the single frame trigger in the Foolcontrol menu? I can't seem to find any reference to it in the forum. Thanks.
Click to expand...

It is called 'Mark frame' (M shortcut on OS X)

It should only visible after recording has been started as to not clutter the interface...

On iOS it is at the top of the main page where pre-rec button is located while idling...

it is called 'mark frame' or 'trigger' depending on which recording mode you are using...

Let me know if you need any more help with that feature.
 
Hi. I can't get foolcontrol OSX to see my Red Weapon connected through a Teradek Colr.

Colr is in infrastructure mode and connected to my onset network. The colr is in the same subnet as my computer.

Tried automatic scan and manual scan by the IP reported by the colr and neither are working. In the RED submenu, the default 172.16.x.x IP wasn't showing up, it was a different number. I manually entered 172.16.x.x and it still isn't working.

Colr settings:

Connection State: Connected
IP Address Mode: Camera Link
IP Address: 172.16.2.1
Subnet Mask: 255.255.255.0
MAC Address: D8:80:39:46:7C:B5

I have the RED set to 172.16.2.10
Subnet 0.0.0.0 - should this be 255 255 255 0?

Thanks!
 
Gianennio Salucci said:
....
Subnet 0.0.0.0 - should this be 255 255 255 0?
Click to expand...

Yes... 255.255.255.0 for subnet

are you using ethernet between COLR and camera ?
if so you should use DHCP mode on camera setup...

direct connection setup video :
https://support.teradek.com/hc/en-us/articles/216947908-COLR-FoolControl-Direct-Connection-

using another on set router setup video :
https://support.teradek.com/hc/en-us/articles/217446317-COLR-FoolControl-On-Set-WiFi-


should work like this if all goes well :)
https://www.youtube.com/watch?v=EdZF77Ur4EA
 
Mikael Lubtchansky said:
Yes... 255.255.255.0 for subnet

are you using ethernet between COLR and camera ?
if so you should use DHCP mode on camera setup...

direct connection setup video :
https://support.teradek.com/hc/en-us/articles/216947908-COLR-FoolControl-Direct-Connection-

using another on set router setup video :
https://support.teradek.com/hc/en-us/articles/217446317-COLR-FoolControl-On-Set-WiFi-


should work like this if all goes well :)
https://www.youtube.com/watch?v=EdZF77Ur4EA
Click to expand...
Thanks for the reply. Connected to camera through Ethernet. DCHP mode displays a non 172.16.x.x number which the teradek videos says it needs to work. Everything looks connected but can't get foolcontrol to see the colr by searching for camera OR by manual IP. Not sure which manual IP to enter anyway... The colr or the camera?

Is this a possible routing issue? Colr is connected to the red and my network successfully.
 
You must log in or register to reply here.
Back
Top