Here you go, thanks for taking a look at them.don't know if it's a bug somewhere, everything has been working just fine for me on Beta software.
The 30 fps to 96 fps preset works just fine to go from 30/60 to 96/192 with relative in settings. I set this one to one of the arrow keys on the LCD and then other to the up arrow key to go back to 30/60. Is there a way to combine and toggle back and forth with one button?
Yes, you can set it up to toggle with one button, look at this example:
Map a Key to Toggle or Cycle Through Different Settings
Both of your presets are still mapping the LCD UP key to "Magnify: Toggle". That is why once you apply either of the presets the mapping you create goes away. You will need to make the presets map the key to apply the other preset to achieve the toggle effect or don't map that key in these presets at all so you can simply assign these presets to distinct keys.
Last edited by Trent Lillehaugen; 06-01-2012 at 10:48 AM.
Sorry for the confusion, Have the EPIC on the latest BETA software and camera has been working wonderfully, The presets I created aren't. I will keep working at getting the preset right, I've mapped the Key to go to the preset and NOT the Image magnify and it works once or twice properly but then the same key that has been mapped to set to go back from 96 to 30 fps, jumps over to Image magnify on it's own when pushing each respective arrow key on the LCD.
Thank you for you time and care with your suggestions, this is really great and I'm thankful that you guys did this, now just have to figure out it all.
I'll delete these current ones and try again. After reading the instructions you just sent, thanks. No worries, I'll get it eventually.
After a while of programming presets, I finally understand how it all works. The apply preset feature is no doubt very powerful in that you can program virtually any camera function or setting or display to a button. Kudos to Red UI team for designing this system. A quick feature suggestion:
Have the top side handle buttons (the 4 that are by default mapped to frame rate, aperture, ISO, white balance) be able to pop-up its respective menu control, instead of just switching to the slot. So if I hit the aperture button, the aperture menu pops up as if I had touched it on the LCD, so now I can just change the value with the rotary wheel. This makes it a fast 2 step process, instead of the 3 step process now where I have to press the aperture button, then hit the enter button, then adjust the wheel.
Also, have the ability to program in hold button functions. So if I hold down the aperture button it will bring up the advanced menu. Just like when you hold it down on the LCD.
I can see this also being useful for applying looks. Say I set button A to apply a certain look. If I want to switch to the look, I just hit the A button. But, if I just want to view it for a brief moment and then go back to the original look, I just push and hold. Now, I know the press/release mapping can accomplish the idea of holding a button to view, but then it looses the functionality of setting a look.
The only problem with a hold feature on the physical buttons is that it makes it impossible to have a "Press", "Release", and "Hold" event. That is, you can't differentiate between a "Press" and a "Hold" until either the "Hold" time has been satisfied or the button is released (making it a press rather than a hold). This would cause the "Press" and "Release" events to occur at the same time. This means you would need to sacrifice the "Release" event to gain the "Hold" event. It might be nice to give the user the option - but we'll need to figure out how to do so without adding too much complexity.
The "Set Slot: *" actions that are tied to the 1-4 buttons by default work well when paired with the "Slot: Next/Previous Value" actions. If you map the front rotary wheel to "Slot: Next/Previous Value" then you click the 1-4 button and can change its value by using the front rotary without needing to even open up the spinners. However, I think having a parallel set of actions that pup-up the spinner is a good idea and adds flexibility.
On my to do list is to try 2 key mapping tasks, wondering if anyone else has tried these yet.
First should be fairly straightforward, I want to make a multiple photo burst mode, where setting the slider to stills gets met to 96 fps, and then so that record press starts record and record release stops it. This way I end up with multiple short r3d files when capturing stills and makes the function much more like a high speed still camera.
The second is a little more complicated. I want to map a button as a gate check function, meaning a button press would enter playback mode and play the last clip, and release would stop and exit playback for recording again. I realize that I may have to have press enter a preset for playback and release play, then a second press and release stop playback then go back to normal preset and go live on release, or maybe I would need three or four press/release actions to do it all. The main goal is to have one button or maybe two if necessary get me automatically into playback and sta playing and get me back to live when I take an action, either releasing or pressing again.
Has anyone done either of these before to save myself some work?
Hey Trent. Thanks for the quick response! The "LCD (Brain): Cycle Mode" was just what I was looking for.
Would you be able to post a write-up on how to create a soft key that toggles "Enable Look Around" on and off. I couldn't figure it out based on the link you posted about setting up presets.
Or even better... a video on the topic would be awesome.
Great job, and thanks!
|« Previous Thread | Next Thread »|