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 - xNiNELiVES

#51
Quote from: ted ramasola on August 20, 2013, 09:00:19 PM
Their first batch got sold out already, but hopefully I will be able to test one by end of the week or early next week.
I'll keep you guys posted how it gows on the 5D mkII and 7D and hopefully a 5D mkIII.

http://www.amazon.com/KOMPUTERBAY-256GB-Professional-COMPACT-Extreme/dp/B00EM9I6II/ref=sr_sp-btf_title_1_13?s=electronics&ie=UTF8&qid=1376990373&sr=1-13&keywords=cf+1200x

How did KB send you that card? I was set up to be a tester for KB but never got notified. Did you?
#52
Quote from: ted ramasola on August 20, 2013, 08:55:08 PM
KB already knows these results. They have provided me with assistance on the tests I have been doing.
By end of the week I will be testing their new 256gig 1200X CF card to see if they work with the 5dmkII and 7D. I might also be able to test it with a mkIII.

What I like is that they are following magic lantern developments and are trying to see which firmware will work with most canon cameras.

There are trade offs so a decision will have to be made on their part.

For instance, older firmware allows their high capacity cf cards to be compatible with mkII and older models.
However, this makes the cards susceptible to software or hardware corruption when used with older usb 2.0 cf readers.

New firmware adds better protection to the cards making the older cf readers "not detect" or see the CF cards thereby protecting it from being shorted or corrupted
however this makes them incompatible with several canon models.

256GB 1200x, Jesus christ man.

Wouldn't it be possible to flash a custom firmware developed my magic lantern to fix this?

I mean I rather use the old firmware because I have USB 3.0, I thought the older firmware has slower CF r/w speeds and is incompatible with ML. Is this true?
#53
Good tests. Hope KB sees this with their account.
#54
I actually have this exact same problem while stargazing. I believe in the movie section there is a subsection called movie tweaks. In this menu there are options for the blue light.
#55
@TheUnknown
That conversion needs to be adjusted because he's on a 1.6x crop body. That 18mm is actually a 28.8mm. 450/28.8= 15.63 seconds.
Also I'm guessing you copied that name from the hacker on COD.

Now you should adjust your exposure for how bad the light pollution is in your location. If you're at a really dark location, such as Yosemite or something, choose 30", 3.5, 3200 ISO. If you don't use 3200 iso you can lose a lot of detail. It's like underexposing a photo in daylight.

I would never shoot with a 50 (80mm) for a timelapse. Only unless you have a specific foreground you want to magnify on and stars are a secondary thing.

If you go out shooting in a dark location with a 15 second exposure at iso 800 your timelapse is going to turn out crap because you won't see anything. Trust me that's what happened to me in the past. Just deal with the star trails anyways you'll never see them unless you are looking at them in a 100% crop.

Look for example at these two photos I took, the darker is in ISO 800 then second is 3200:
https://dl.dropboxusercontent.com/u/814675/IMG_3166.jpg
https://dl.dropboxusercontent.com/u/814675/IMG_3167.jpg
Both were also using 30 second exposures and an aperture of 2.8.
#56
Yes of course, these write speeds go for everything.
#57
Quote from: ted ramasola on August 15, 2013, 02:08:56 AM
With the current build for the 5D2 that is dated aug 9 compiled by a.d.

The highest possible res to record is at
1880x1058 16:9 = 1049 approx frames

Highest continuous recording is at
1880 x 940 2:1 = record till your CF card is full (64gig around 15 minutes)

Highest 16:9 continuous recording is at
1728 x 972 = record till your CF card is full (64gig around 15 minutes)

Highest res in crop mode is at
2144 x 1076 = 358 approx frames

near full HD res in crop mode is at
1920 x 1076 = 1223 approc frames

Highest 16:9 continuous recording in crop mode is at
1856 x 1044 = record till your CF card is full (64gig around 15 minutes)

Thanks for updating this.
#58
Quote from: thefix on August 15, 2013, 12:34:26 AM
Thanks for the constructive criticism, I will have to try what you suggest next time. You are correct about the editing I didn't do any editing it was exactly as it came out of the 600D. I just might have to invest in Photoshop and ditch my open source program gimp for any edits I try in the future.

Thanks again for the feedback! :)

No problem. One more thing, make sure you shoot in RAW.
#59
Share Your Videos / Re: 1880x800 RAW 5DMKII
August 15, 2013, 12:25:25 AM
Sharper than a knife.
#60
Quote from: thefix on August 14, 2013, 11:56:08 PM
Nice work, it puts my similar post to shame.

Thanks!

Yours isn't bad at all, you just didn't compensate the movement of the milky way in your timelapse. You have to purposely aim your camera to the direction the milky way will come into frame. Use the iOS app starwalk. Its very helpful.

The second thing you didn't do was edit correctly. You need to have a very high contrast curve set up to contrast the dust lanes of the milky way from the black surrounding (space).
#61
Quote from: Canon eos m on August 13, 2013, 11:31:15 AM
Interesting picutre! This picture rocks and is truly awesome. Mind sharing the workflow?

Yeah I import the photos -> open with ACR (Photoshop CS6), increase the a bit over a stop and give a really high contrast curve, correct vignetting, CA, etc. Then downsize to a lower resolution close to what you want. Then crop the image to give a 16:9 Aspect ratio. -> Export to jpeg or tiffs -> Open all exported (edited) photos with quicktime pro as an image sequence. Then export the clip.

You can also change the size. Luckily ACR actually allows a horizontal resolution of 4096 so no other resizing was necessary. If for example I wanted my  timelapse to be 1920x1080 and photoshop allows only the downscale of images to a bit over 2k, I'd then have to downscale upon the export in quicktime.

Here's the moab timelapse:


[4096x2304, 16:9]
#62
He means that if any camera you should sell it should be the 60D not the 50D.
#63
Wouldn't it not be allowed here? Or is there no restriction?
#64
Quote from: 1% on August 13, 2013, 01:26:45 AM
50D is to 5DII as 6D is to 5DIII... similar firmware and components with only a few changes $2K+ more.

Yeah I'm just saying that if anything the 5D2 should be just as fast, if not faster when it comes to write speed. Am I right?
#65
Quote from: CFP on August 12, 2013, 08:34:16 PM
I saw benchmarks of the 5D Mark II reaching write speeds slightly over 90 Megabyte/s, just like the 50D.
And the 5D Mark III even reached 130 Megabyte/s. Its SD-Card controller's hardware limit is 21 Megabyte/s.

Well if anything the 5D Mark II should be better than the 50D. They were released at the same time, except the 5D2 was around 2000 dollars more.
#66
Quote from: Tichro on August 12, 2013, 08:55:19 PM
I have only one word for this...
Absolutely stunning,,, OK actually that's 2 words, even so that is a very nice timelapse.
I have become slightly addicted to making timelapse sequences but I'm using ML's silent picture feature, I don't want to wear the shutter out on my 550D.

I also wish that I had access to a location that has a truly dark night sky, there's far too much light pollution where I live.
Damn those street lights  >:(

Thanks!

Yeah living in northern california (bay area) sucks for stargazing. I went to the darkest recorded sky in the world: Natural Bridges National Monument. It was verified to be a class two sky (bortle sky chart). The milky way was so bright it cast a shadow on the clouds. Yes clouds. The entire sky was full of clouds except for tiny patches. I flew and drove 1000 miles to find the sky cloudy. With the pictures I got the milky way looks sooo colorful and sharp. It looks as if its already edited. Bryce canyon definitely had a moderate amount of light pollution. I have a timelapse of Moab, it was mostly clear but some clouds came in... Moab has worst light pollution than bryce canyon... I'll upload the timelapse of Moab soon...
#67
This pertains to the website because it was shot with ML Intervolemeter:

[4096x2304, 16:9]
#68
Quote from: kgv5 on August 12, 2013, 08:07:31 PM
According to the chart from

http://www.magiclantern.fm/forum/index.php?topic=6215.0

it is 75 MB/s.

For 5D3 is 100 for CF +20 for SD so devs have managed to squeeze almost the full speed.

LOL I said that because that what the max speeds we are attaining with Raw Video. It doesn't mean its the actual limit.
#69
Whats the 5D2's theoretical hardware limit for its CF slot max speed?
#71
Quote from: kgv5 on August 12, 2013, 07:06:08 PM
Newest module from #277
This gave me very good results, great work  :D   : Buffer fill method 3, CF-only buffers 2

1920x1080 16:9  29,97fps >>>   ~109-110 (91+19) so shows continous ok.
2240x1260 16:9  24fps      >>>   ~113 (95+19) continous ok
2560x1090 2,35:1 24fps    >>>   ~115 (96+19) continous OK

I tested buffer=3 CF=2 and buff=3 Cf=3, after couple tries i had an impression, that B3CF2 speed was more stable, B3CF3 had similar speed but more variations. But its hard to say really, maybe just coincidence, when tried again it was stable, even maybe a bit faster than B3CF2.

These tests are crazy, 2.5k continuous, Jesus.
#72
Quote from: g3gg0 on August 12, 2013, 11:43:25 AM
1) intention, its still experimental
2) this was on 5D2, right? can you use these both modules (dont forget to enable trace) and send me your raw_rec.txt after recording with a spike? it should be in the root folder. upload it using http://upload.g3gg0.de and send me the [D/L] link (right-click, copy link)
3) if you stop recording, it should disappear
4) uhm, just dont enable it? ;)

1)
2)

3) Even if I stop recording, the buffer status never disappeared. The rest of the info disappeared after a good 15 seconds or so.
4) I don't enable it but what happens if someone did? I realize this is only an experimental copy of the new MLV Format, I guess you'll just disable it in the final versions.

Will trace the bug with the lag spike.
#73
General Development / Re: Need help merging code, etc.
August 12, 2013, 06:59:36 PM
I'm using a build from A.D. Should I download his source or something?
#74
I'm gonna go out on a limb and say you used your phone ;D.

Thanks for the response, I'll get the module.

Again I have these bugs though, I don't know if you saw them earlier:

1) Videos save to the root of the card?
2) As soon as the video starts recording a MASSIVE lag spike occurs that lasts for a few seconds following with a extremely short record time of 96 frames at [email protected].
3) Buffer Status/Information display doesn't disappear
4) Card spanning should be removed for the 5D2 version (because it doesn't have a dual card slot, as you know)
5) I can't write any tag, no text display comes up.
#75
Quote from: gnarr on August 12, 2013, 07:11:08 AM
Could someone here post a small mlv file from a 5D3? I need it to test code that I'm working on.

I posted a 5D2 clip a few posts above...

Well I'm still waiting on the IME module. Should I download it from the 5D3 package? Where's this located?