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


  • Similar Content

  • Latest Posts

    • My understanding is that UV tends to accelerate the aging process. If the car has been garaged, then you could probably get away with extending beyond 10 years. FWIW, in 2015, I had tyres on my 180B SSS that had a 3-digit code (2 for week, 1 for decade), ending in 0, so could have been more than 30 years old, but still worked fine. I did replaced them very quickly, though, once I discovered what the code meant!
    • But we haven't even gotten to the point of talking about stateless controllers or any of the good stuff yet!
    • You guys need to take this discussion to another thread if you want to continue it, most of the last 2 pages has nothing to do with OP's questions and situation
    • And this, is just ONE major issue for closed loop control, particularly using PID. One such issue that is created right here, is integrator wind up. But you know GTSBoy, "it's just a simple PID controller"...  
    • Nah. For something like boost control I wouldn't start my design with PID. I'd go with something that originates in the fuzzy logic world and use an emergency function or similar concept. PID can and does work, but at its fundamental level it is not suited to quick action. I'd be reasonably sure that the Profecs et al all transitioned to a fuzzy algorithm back in the 90s. Keep in mind also that where and when I have previously talked about using a Profec, I'm usually talking about only doing an open loop system anyway. All this talk of PID and other algorithms only comes into play when you're talking closed loop boost control, and in the context of what the OP needs and wants, we're probably actually in the realm of open loop anyway. Closed loop boost control has always bothered me, because if you sense the process value (ie the boost measurement that you want to control) in the plenum (after the throttle), then boost control to achieve a target is only desirable at WOT. When you are not WOT, you do not want the the boost to be as high as it can be (ie 100% of target). That's why you do not have the throttle at WO. You're attempting to not go as fast as you can. If the process variable is measured upstream of the throttle (ie in an RB26 plenum, or the cold side pipework in others) then yeah, sure, run the boost controller closed loop to hit a target boost there, and then the throttle does what it is supposed to do. Just for utter clarity.... an old Profec B Spec II (or whatever it is called, and I've got one, and I never look at it, so I can't remember!) and similar might have a MAP sensor, and it might show you the actual boost in the plenum (when the MAP sensor is connected to the plenum) but it does not use that value to decide what it is doing to control the boost, except to control the gating effect (where it stops holding the gate closed on the boost ramp). It's not closed loop at all. Once the gate is released, it's just the solenoid flailing away at whatever duty cycle was configured when it was set up. I'm sure that there are many people who do not understand the above points and wonder wtf is going on.  
×
×
  • Create New...