fma38 wrote:

The buttons are greyed out as long as your are not connected (Menu Hardware)

So there´s no more simulation-mode?

best, Klaus

fma38 wrote:

klausesser wrote:

So there´s no more simulation-mode?

Just choose the Simulation plugins

Ah - i see, sorry!

But honestly: setting angles or fov by scrolling in the number boxes is VERY uncomfortably. Try to set 75° for both directions . . . to hit it exactly you have to try hard. It was MUCH faster and more comfortable to type in exact numbers.
The wite-coloured numbers on light blue background really don´t help it.

Generally: why did you design it that much more complicated in all respects? All the settings seem to be less comfortable to handle.

System 1.6.1 was more straight, more transparent, more intuitive. Actually one now have to change settings in 5 menues instead of one or two to get the same results. 

What´s the realistic advantage of using the actual system instead of 1.6.1?

Dear Frédéric,

I just started reading this forum. Your first point was about timelapse.

I didn't see others thinking it's necessary but I do!

I'm new to most things here and I don't know if my problems have already been solved.

But I'm killing it in Los Angeles.

I've sold 2 timelapses and a 25 link autopano tour file to Nike.

I'm doing killer work and all the timelapse features I can get need to STAY or get better!

Please!

-Logan

Frederic,

Some time back I mentioned that it would be good to have the option when mounting the camera in landscape orientation to be able to mount it with the vertical arm of the Merlin to then left - when looking from behind the camera - rather than to the right. This would allow the lens axis to be positioned closer to to the axis of rotation and make the camera grip and many controls more easily accessible/usable.

Papywizard cannot currently accommodate that.

You said you'd investigate whther it was possible to add a parameter to allow this to work.

Is it likely to be possible?

Last edited by mediavets (2010-02-12 08:32:07)

Bonjour Frederic

I realise that you are pushed for time and it's hard to make enough time to implement features. But, If you were to put aside some time towards timelapse, I would happily spend the time helping you in the features/requirements development and also any beta testing and bug weeding out.
I'm a director of photography and have time and equipment. I've done many timelapse's (static) but now really want to implement movement with my Merlin head. I would gladly help you-help us, by adding timelapse functionality.
I could happily breakdown features into a timeline of importance/relevancy from the most basic to an advanced level, for a working timelapse application.

The DLSR market has gone ballistic and is set to continue. There is a massive market for a working timelapse solution. You appear to be the keymaster

short of begging, how do I (or we, the HDSLR market) convince you to spare some time?

regards

The most important thing with a timelapse application is to get the head to stop, shoot and then move. If the head is constantly moving it totally limits the ability to take long exposures as the pictures will be blurred.

Your application is great, it's also way more complicated than a simple timelapse application.

For the easiest application it would need:

Set start position.
Set end position.
Set speed. 1-5  based on the heads inbuilt speeds.
Enter how many shots.

You don't need to enter yaw and pitch, you could have the application just spread the shots between the start and end. You don't need anything other than that for a basic timelapse application/function to start with.

If you can set a start and and end position and then just enter how many pictures you want to take in that move. leave the calculations for degrees and time and end shot duration to the photographer. That would be it. Just as easy as that.

Later you could add additional positions to be able to set a path for the camera to go in.

The head can do all that, even with the handset it does most of it, but it can't stop/shoot/move/stop/shoot/move.

Right now the html preset function, while great someone made the time, is very limited. Also it appears that the Merlin might suffer from how long it takes to line-up to the correct position. This can hinder timelapses as it's not always the same.

If theres someone out there who thinks this is something they could put together I'd be happy to pay for thier time.

Seconded.

What a good idea much better than a hand in the picture! this could be an option to be enabled at the moment I sometimes get lost in images especially if its of a similar scene.

Best
Gordon

I'm not sure to clearly understand; what do you want to add in the xml data file? A simple number, increasing at each pano? And have this number shown at the begining of the shooting sequence?

What about showing the start date/time, or the filename? Or both?

Ok.

I first have to find a way to display that number; as Papywizard is cross-plateform, I have to ensure it will have the correct size on all displays...

I have almost finished implementing this feature, but still open to idea to improve it.

Andrew, as I made a dialog to show the counter (with increase/decrease/reset buttons to make some changes, if needed), I also added the snapshot button to trigger the camera (need to add a little delay).

But keep in mind that if you are using an external script with bracketing, the entire sequence will be run, as I just call the shoot() method of the shutter plugin. Please, don't ask for a different setting, it will need too much modifications in different parts of the code, and I don't think it will be usefull.

I will also try to find a place for a similar snapshot button/menu on the main window...

A few days ago, someone asked about a way to wake-up Papywizard from an external program, when shooting with a tethered-based plugin.

Could you explain me what you exactly expect? What mecanism do you want to use? There are several ways to make inter-process communications; some are multi-plateform, some are not.

Can't you implement this in the external script? Papywizard mainly call the script, and wait it returns. If the program used don't work this way, it is very easy to use an intermediate script. I think it can receive all parameters from Papywizard, and give them to the program. Then, it can either add a sleep command to wait for the end of the program before returning (an let apywizard go on shooting), or implement a more complex mecanism, like opening a GUI to ask the user to click when finished, or the inter-process communication.

If I had a concrete example, I could help to write such script.

I made new tests, and it now seems to work in fullscreen on my Nokia!

fma38 wrote:

I will also try to find a place for a similar snapshot button/menu on the main window...

And were you able to ?