hab letztens gelesen, das Black Forest Motion zukünftig mit qDslrDashboard zusammenarbeitet. Könnt ihr schon verraten wie das aussehen wird, was wir erwarten können? Habe im Nezt nichts gefunden und bin doch sehr gespannt.

Gruss

Marcel

ich nutze nun den Slider und die App seit ein paar Wochen. Soweit bin ich sehr zufrieden. Was mich aber noch stört, ist die Tatsache, dass ich für eine Holy Grail Aufnahme die Motion App sowie auch die QDSLR Dashboard app nutzen muss. Für mich sehr Suboptimal, da ich in der QDSLR App immer drinn bleiben muss ansonsten die Verbindung abbricht.

Ist von Seite BFM eine Integration einer Funktion in die App geplant? Wäre super alles in einer App zu haben.

Gruss

Marcel

I find more intuitive to touch a keyframe to move the motor to that location and touch/hold it to enter its edit mode, instead of the reverse like it is now. Do you think this is a thing that could be addressed in the future?

Also, I'd really like the app to keep my phone awake instead of letting it go into Autolock mode...

Thanx

moving motors to the keyframe-positions with the sliders is a little bit tricky,
especially with the lens-unit to move to the exact focus-point.

Slider-Start- and End-Point or Pan/Tilt is not the problem (for me), but the lens-control,
especially you have a narrow focus-depth.   
It could be more exactly and easier to have an external hardware-control
connected to the Pine-Controller (USB- or AUX-connector).

Would be nice, if this is possible !

Best regards and Happy Easter,
Harald

I noticed, that when shooting a shoot-move-shoot timelapse sequence with 3 or more key-frames in slave mode, PINE stops moving to the next interval, once the sequence reached the frame just before the second key frame i.e. externally released camera keeps shooting but the motion control freezes entirely. If the PINE-App is connected to the controller at my external device during this procedure, the App crashes, i.e. exits/shuts itself down without user interaction and home-screen is visible.

Here is the setup that I was testing with:

• External devices: iPhone (8) and iPad Air (2), both running on latest iOS
• Motors: BFM 14:1 + 2x NT Single Axis
• PINE APP: iOS v3.0.3
• Controller: PINE R, firmware v3.0
• Camera: Sony a7III; for slave mode: wired camera to AUX-inupt of PINE via hot shoe adapter and synch-cable
• Camera release: QDSLRDashboard-App, or camera's internal intervalometer (interval set to 5s).
• Power bank: XT-20000QC2, input voltage: 18-19V

This is the most simple test scenario that I have observed the error with:

• 1 motor
• Key frame 1: position 0
• Key frame 2: position 100 (5 frames)
• Key frame 3: position 0 (10 frames)
• The crash occurs after frame 4 has been captured by the camera

These are some further observations that I have made:

• The error occurs, whether the external devices are connected or not.
• The amount of involved motors does not matter.
• The error occurs, regardless which type of camera release I used.
• The error does NOT occur in regular mode (even for the exact same sequence), i.e. PINE controls camera release
• When set to slave mode, PINE performs the movement-test of the multi-key-frame sequence without errors.
• After the error occurred, reconnecting to PINE is possible without the necessity of re-starting the controller. The timelapse module of the app does not state that there is an active sequence and asks whether to re-load the key-frames, or start from scratch. The old key frames are loaded correctly.

My preliminary conclusion is, that the error is independent of the used camera, how the camera is released, or the motor type and therofre caused by a bug in the PINE controller, only. Can someone reproduce the error with a different setup? This would solidify the mentioned theory.

To help out the BFM development team to find a cause/solution, I have attached the bug analysis report that my iPhone generated for the PINE-App during one of my tests. Just let me know if you need anything else!

I am really curios about the cause of the error, and would be happy about a solution.

Best regards and stay healthy,
Kilian

Today I tried for the first time the slave mode with the LRTimelapse PRO Timer 2.5. Connected and set keyframes worked but then I have to start the time-lapse mode by pressing the green play button. I don't see them anywhere in the time lapse area?

Kind regards Frank

Since it’s listed and supported by Pine could you please share the setup settings?

Anyways, How are you guys dealing with switching batteries while shooting. If I disconnect the battery from the Pine to attach a new one, will it continue where it was or reset.

I am not exactly sure how long my battery will last driving the Pine, 2 Nic-O-Tilt (consuming 1.2 A) and either a 5:1 or 19:1 motor for the rail. I have a 12 Volt, 3.5 A, 15000 mAh battery.

Regards

Markus

I tried to use the Setup Wizard to calculate the motor ratio, but that gave me a value of 1:6.26 (See screen shot). But that was not a good value as the pan and tilt head movements were not nearly large enough (I think maybe because there are multiple gear ratios on the Stage R).

Then I spent a while just guessing at increasing higher ratios, and running 360 tests so I could visually compare the initial straight up shot with the final straight down shot... until I got a value that is very close to perfect. That value it turns out is 1:63.18 (See screen shot).

Actually... because there's a calculated amount of overlap in your images, it doesn't have to be perfect. But, for anyone else using the Stage R pan and tilt heads for 360s, manually setting the value to 1:63.18 should work well for you.

Happy shooting!