Jump to content
SAU Community

Recommended Posts

EDIT: Just realized the upload onto youtube has compressed it so much you can hardly see anything. Also it seems like the colours are lost in the stars..

This sucks lol.. Anyone know where else i can upload the video? Or exactly what settings to create the video? As in frames per second.. What format etc..

Just a mini timelapse video i have created.

You can see the Orion Star constellation in this video smile.gif

Theres about 100 or more images used to create this.

No editing was done to any of the images. Just a process of 100 images stacked i guess. Its sorta how i do stair trails..

The earth silently rotates while you sleep:

http://au.youtube.com/watch?v=WR2dXt8EY_8

Hope you like it.

Edited by siddr20
Link to comment
https://www.sau.com.au/forums/topic/255312-my-mini-timelapse-movie/
Share on other sites

Isn't it possible to create a video like this with a whole recorded video while it's night?

I think it would be a more fluent passage if you create another video with a spool part of your whole recording.

But whatever i really like your video :P

Isn't it possible to create a video like this with a whole recorded video while it's night?

I think it would be a more fluent passage if you create another video with a spool part of your whole recording.

But whatever i really like your video :P

You mean actually taking a video from a video recorder?

I dont think it will come out nicely. But then again i dont own a video recorder so i wouldnt know.

Also these pictures are 13 second exposures. So doubt the video recorder could capture all the light in.

Hense why ppl take pictures instead as your slr camera can capture as much light as you intend it to.

so how did you do it? the actual photo taking i mean

was it a manual - press the shutter every few minutes kinda deal?

or do you have some fancy timer that does it automagically

I captured about 100 images or so. Perhaps more (havnt really counted but theres heaps lol).

Each image is a 13 second exposure.

I noticed the stars slowly disappearing away behind the roof and hense why i stopped. Unless i would have left the camera on till the memory card filled up.

The same way you can do star trails. Stacking 100 images or so.

Heres my 1st attempt i did a while back.

Startrails1aresizesig.jpg

what i mean is how did u take the pics?

did you manually press the shutter - wait 13secs - manually press the shutter - wait 13secs - and repeat (another 98 or so times) ??

ie so its a manual process where you sit there taking pic after pic for 20mins or so - correct?

Oh nah nah the shutter release cable was held pressed in. I came back 20 minutes later and turned it off..

If you got a shutter release cable you will know what i mean.

But now you are wondering how does the camera take pictures every 13 seconds or so. Its called burst mode. Use that setting, with release cable and it will keep taking photos till you turn it off.

You mean actually taking a video from a video recorder?

I dont think it will come out nicely. But then again i dont own a video recorder so i wouldnt know.

Also these pictures are 13 second exposures. So doubt the video recorder could capture all the light in.

Hense why ppl take pictures instead as your slr camera can capture as much light as you intend it to.

Yeah i mean a video camcorder(?) i saw a few videos at youtube of timelapses and i thought they were just very fast videos

Like this one:

But all right, thank's for the lesson :(

No worries.. Let me know how you go :D

this is how i went! pretty dodgy but its a proof-of-concept for me!

(was just taken at my back door - so next time i'll go somewhere a bit better and hopefully I'll get something nice)

Star_Trails_001.jpg

ps nice and big one just for you :(

Great work for your first attempt :D

Stars looks thin and thats what you want (as in the lines)

Now the next thing to do is to find the southern Polaris. So you get the whole circle look.

But well done on your first attempt.

The software i suggested will help heaps as well ;)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Latest Posts

    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
×
×
  • Create New...