foolcontrol - power fool DSMC camera control

[Mikael Lubtchansky]

Have you set up the COLR as a bridge for RED in its menu ?
I do not have mine with me here so I cannot tell you exactly where is that setup located in the COLR menu but if you do not get a DHCP address that might be the issue...

Have you contacted Teradek support yet ? They should also be able to help with seeing this up.

 

[Michael Tiemann]

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.

Two things:

Generally, it's 172.24.x.x aka 172.24.0.0/16, not 172.16.x.x
Also, when in that world, 255.255.0.0 is the subnet mask.

 

[Gianennio Salucci]

Two things:

Generally, it's 172.24.x.x aka 172.24.0.0/16, not 172.16.x.x
Also, when in that world, 255.255.0.0 is the subnet mask.

My Colr is saying its subnet mask is 255.255.255.0 and its IP is 172.16.2.1

Tried manually entering the IP on the RED to 172.16.2.10 and its gateway to 172.16.2.1 and its subnet to 255.255.255.0 and no dice. My brain tells me this should work.

When DCHP is checked on the RED, it goes to IP of 169.254.215.219, subnet mask 255.255.0.0, gateway to 0.0.0.0.

Both devices are on newest firmware. No idea here.....

 

[Trent Lillehaugen]

My Colr is saying its subnet mask is 255.255.255.0 and its IP is 172.16.2.1

Tried manually entering the IP on the RED to 172.16.2.10 and its gateway to 172.16.2.1 and its subnet to 255.255.255.0 and no dice. My brain tells me this should work.

When DCHP is checked on the RED, it goes to IP of 169.254.215.219, subnet mask 255.255.0.0, gateway to 0.0.0.0.

Both devices are on newest firmware. No idea here.....

For what it's worth, if the camera's IP address is 169.254.x.x when DHCP is slected that means it could not find a DHCP server and auto assigned itself an IP address pursuant to RFC 3927 (see https://en.wikipedia.org/wiki/Link-local_address).

 

[Pieterjan Djufri Futra]

The wifi still crashes every single time I go into 1:1. I thought it's been 6 months with plenty of firmware updates so I gave it another shot. The app stops responding, the camera can't reconnect to the network and gets stuck on "Shutting down" until you remove the battery.

This was the case with the stock firmware when I got my camera in March and this is still the case today with the 7.0 RC3. This has nothing to do with the signal, the router is 50 cm away from the camera. Once you 1:1, you're done.

A real shame this is taking so long to fix.

 

[Mikael Lubtchansky]

The wifi still crashes every single time I go into 1:1. I thought it's been 6 months with plenty of firmware updates so I gave it another shot. The app stops responding, the camera can't reconnect to the network and gets stuck on "Shutting down" until you remove the battery.

This was the case with the stock firmware when I got my camera in March and this is still the case today with the 7.0 RC3. This has nothing to do with the signal, the router is 50 cm away from the camera. Once you 1:1, you're done.

A real shame this is taking so long to fix.

Hello Pieterjan

I just tested here again intensively switching 1:1 on and off from both the iOS and OS X app connected by wifi (infrastructure) and all seems OK on this Epic-W running 7.0 rc4.

Have you been sending your log files to red.com/support ?
Is it working normally if you enable 1:1 from the touch screen ?

Mikael

 

[Pieterjan Djufri Futra]

Hi Mikael, thanks for the fast reply. I have not sent log files to RED. I have the exact same on my colleagues Epic-W. Would you say this is a hardware issue? Seems like it would be too much of a coincidence for 2 brand new cameras to have the same issues.

 

[Pieterjan Djufri Futra]

http://www.reduser.net/forum/archive/index.php/t-152217.html

This archived thread is almost a year old and no fix in sight. I quickly read through and I can assure you this has nothing to do with ad-hoc WiFi as I've tried at least 2 seperate access points. With the 7.0 Release build on the Scarlet-W I managed to do go in and out of 1:1 2 times until the third time failed and crashed the WiFi. Epic-W doesn't work at all. It seems like the camera is locking up for a second as it changes to 1:1 - long enough for the WiFi to drop.

Is this at least being looked into? Very sad this app that costed €150 has only been useful for filling up my phone storage.




Just found this link: http://www.reduser.net/forum/showth...Scarlet-W-Foolcontrol-losing-connection/page2
Turns out it's a RED issue? Seems weird we have all this streaming and high bandwidth applications running on WiFi but a simple command protocol is too much for it to handle?

 

[Mikael Lubtchansky]

http://www.reduser.net/forum/archive/index.php/t-152217.html

This archived thread is almost a year old and no fix in sight. I quickly read through and I can assure you this has nothing to do with ad-hoc WiFi as I've tried at least 2 seperate access points. With the 7.0 Release build on the Scarlet-W I managed to do go in and out of 1:1 2 times until the third time failed and crashed the WiFi. Epic-W doesn't work at all. It seems like the camera is locking up for a second as it changes to 1:1 - long enough for the WiFi to drop.

Is this at least being looked into? Very sad this app that costed €150 has only been useful for filling up my phone storage.




Just found this link: http://www.reduser.net/forum/showth...Scarlet-W-Foolcontrol-losing-connection/page2
Turns out it's a RED issue? Seems weird we have all this streaming and high bandwidth applications running on WiFi but a simple command protocol is too much for it to handle?

Hello Peterjan...

Sorry to hear about your troubles, I think it would be worth sending some logs files to investigate this issue further.

The app is sending plain RCP command for all its features including MAGNIFY. It does take around 3 seconds to toggle (same as when triggered from a camera button) but it should definitely not be dropping wifi.

fwiw, here is a clip I just shot , toggling in out of 1:1 magnify over a dozen times on a weapon camera running fw 7.0 over wifi (infrastructure in this case)...

https://vimeo.com/foolcolor/magnify

 

[Tom Sefton]

Having Epic-W upgraded to Helium so Im back trying to remember how to setup an Epic Dragon with an offhollywood hotlink device and the Mac OS version of the software.

Is there a guide anywhere for this>?

Mac OS can see the hotlink wifi, but can't see the camera.

Hotlink is connected to the control port...!

 

[Mikael Lubtchansky]

Hello Tom

In camera settings / setup / communication you need to ser the serial port (CTRL) to REDLINK control protol (RCP) so the hotlink can talk to the camera... then the app should be able to detect the camera. Not sure hotlink manuals are still online tho ;-(

Let me know if that was the issue...

 

[Martin Konrad]

I had some problems today when I tried to use foolscreen. Just sharing my solution...
I could not get an image when clicking foolscreen in the menu.
Blackmagic Ultrastudio Recorder, official Apple Thunderbolt cable and latest versions of Desktop Video and foolcolor.
Turns out the video settings for SDI and HDMI frequencies are on the startup page of foolcolor but the software was set to Autoconnect to camera so the page dissapeared to fast to find and adjust settings.
Switching off wifi on the laptop keeps you on the startup page to find and adjust the video settings to match the output (frequency) chosen on the camera under monitor/sdi or hdmi

If you set the camera monitor signal to Auto, foolcolor will crash on startup.
All working as it should now and I can have custom overlays for next weeks shoot.
Fantastic software, thanks again Mikael

 

[Mikael Lubtchansky]

I had some problems today when I tried to use foolscreen. Just sharing my solution...
I could not get an image when clicking foolscreen in the menu.
Blackmagic Ultrastudio Recorder, official Apple Thunderbolt cable and latest versions of Desktop Video and foolcolor.
Turns out the video settings for SDI and HDMI frequencies are on the startup page of foolcolor but the software was set to Autoconnect to camera so the page dissapeared to fast to find and adjust settings.
Switching off wifi on the laptop keeps you on the startup page to find and adjust the video settings to match the output (frequency) chosen on the camera under monitor/sdi or hdmi

If you set the camera monitor signal to Auto, foolcolor will crash on startup.
All working as it should now and I can have custom overlays for next weeks shoot.
Fantastic software, thanks again Mikael

Thanks Martin for the feedback. Will look into that crash issue when having a different framerate on camera and using auto on blackmagic input device... i’ll email you if I need more info to reproduce that...

 

[Martin Konrad]

Can anyone explain why my post disappeared? I posted a few days ago as the foolscreen setup took me a couple of hours due to an "autoconnect" setting skipping past the frequency settings. This was only meant to help others getting stuck during setup, especially if anyone new to foolscreen needs to sei it up quickly on a shoot day. I can still see the post under "last post" on my profile but in the thread it's gone. It says last post is by Mikael but the last post I can see is Tom's post no 87...