Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Pyrofer

#1
Thanks.
#2
Previously in ML I could override the ISO to above 3200 on my 500D when shooting stills.
Now, that option only seems to work in Video mode?

I found this out after travelling 200 miles to do some astro-photography. Needless to say, my plans for nice deep starfields didn't plan out with the Canon 3200 limit :(

I saw no mention of this change or why it has changed. I want to fix it but am unsure where in code this was done?

Could somebody point me to the right place to re-enable ISO override for normal shooting not video.
#3
Share Your Videos / Re: London Eye 2fps
September 05, 2012, 01:44:44 PM
Thanks for the feedback.

I took about a minute for each shot so need to find the best length of clip from them. I think you are right about re-positioning.

The people in the station are from 2 angles and those clips work better than the tho shots of the cars.

Need to find some music to match to it too.

What was it about the Horizon that bugged you? I find the rapid changing on the water more annoying than anything else in that clip.
#4
Share Your Videos / Re: London Eye 2fps
September 04, 2012, 08:54:17 PM
Did some more shooting and editing....

Excuse the poor quality, no idea why the video lost so much resolution in youtube.



Feedback please!
#5
Share Your Videos / Re: First Sky Stars Timelapse
August 22, 2012, 11:55:51 AM
Thanks for all that.

I just got a f2.8 28mm lens I am looking forward to trying.
I was going to use ISO 800 maybe 1600 and 20 seconds.

For time lapse I have been using Movie mode and the fps override. Its much kinder on your shutter!

For the night sky shots though I am doing single long exposure and not time lapse yet. Will see if I can get something good with movie mode and stars.
#6
Share Your Videos / Re: First Sky Stars Timelapse
August 20, 2012, 01:48:40 PM
I quite like this, I was planning something similar but wanted to get more scenery in.

The issue is how long each exposure is. If you want the stars to look good with no trails you need a good fast lens.

can you share the settings you used? iso/shutter/f etc?
#7
Share Your Videos / Re: London Eye 2fps
August 17, 2012, 06:54:23 PM
I was a little worried the focus was too soft...

I am very happy with exposure and lighting, I think I got the scene set right and the speed.

Just not happy with the focus as it is. A lot of the elements I think should probably be sharp are not, still nobody else has commented on that so it can't be too bad :)

Thanks for the kind words. I can't take credit for the sky however, just lucky there !
#8
Share Your Videos / Re: London Eye 2fps
August 17, 2012, 04:54:52 PM
Over 100 views and not one comment?
#9
Very glad the 500D is supported!

I love my camera, ML makes it so much better.

Thanks all :)
#10
Share Your Videos / London Eye 2fps
August 13, 2012, 10:58:52 PM
Trying to get to grips with 2.3, took this last night as practice.
Not my first Time lapse with ML, but this was the first time I used video mode and FPS override instead of shutter timer.
Much kinder on my camera :)



Canon T1i (500D) with 18-55 IS kit lens.
#11
I think the T1i is the 500D right?

That's what I have.

All works well, I get 30fps Max, but under framing works well right the way down.

I am very impressed with the video quality, I love the camera and ML works wonders on it. If you vary the framerate you need to disable audio, I think ml 2.3 has an auto-disable for modified fps rates.
#12
General Help Q&A / Re: Dead pixel...?!
August 02, 2012, 10:40:22 AM
Exactly.

I didn't manually clear any settings.

All I did was change the version of ML on my memory card and the dead pixels appeared.
This is obviously sub-optimal.

Whatever the reason for them being there to start with, I want to know why changing ML version made them re-appear.
#13
General Help Q&A / Re: Dead pixel...?!
August 01, 2012, 10:25:58 AM
These are all very good points, and I am sorry if it seemed I am blaming ML for "heating" or dead pixels.

The fact is, I have used my camera for years and ML on it for as long with no issue. On installing 2.3 latest build I suddenly had a flock of dead pixels all over the screen that were not previously there.

I can pinpoint their appearance exactly at the time I put new ML on by the images I took.

Without a doubt, putting new ML made them appear.

Just telling people to "ignore it" or "google" it does not help.

If ML is clearing something in the camera that had previously mapped out dead pixels, people need to be told BEFORE installing it, something along the lines of,
"ML may cause your camera to forget its dead pixel mapping and show dead pixels you had not previously seen. This is normal and they can be mapped out using this method (...)"

A straight factual answer from somebody who knows what happened to cause this will prevent a wave of "ML broke my Camera " complaints.

I am not saying ML broke my camera, I am saying that people may perceive that and it is bad press ML does not need.
#14
General Help Q&A / Re: Dead pixel...?!
July 31, 2012, 02:54:31 PM
I think the "concerning" part is that from the sounds of the posts, and my own experience these "stuck" and "dead" pixels were not there before 2.3ML, and suddenly on running this FW they ARE there.

There are 3 options,
1>Coincidence, you just noticed them
2>Something about running ML "wiped" the cameras memory of Stuck pixels and the ones that were always there are now visible again
3>Running ML has cause the camera to heat up/whatever and caused additional pixel issues.

Cases 1 and 2 are complete non-events, Case 3 however is worrying.
I think people just need assurance that it is indeed case 1 or (I expect) 2 and not 3.

Can somebody confirm this in any way? Possibly by comparing old Raw images that may contain a dead pixel they expect has "recently" appeared in ML 2.3? (thus confirming it was always there)
#15
I thought the standard way to get serial out of a camera was to flash a LED on the body?
We have one easily available for that.
You can also just flash the screen or part of the screen, that works too. :)

Any more progress on this? I like the idea of auto-guide.

Could you grab the framebuffer when recording video at all for tracking?