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

#1
Thanks, much appreciated. I'll look into provided docs.

Mikhail
#2
Hello guys.

Since I've tried April crop mode module, my shutter-release button has been acting up - it has reset itself twice to AE lock, instead of AFing. Plus microadjustment has switched itself once to a diff value as well. It has never happened to me before and at the time of malfunction the standard ML was installed. No warnings of any kind were shown upong booting with any of the April versions of the ML.

Thanks
#3
Just wanted to give heads up to those who want most of resolution with lossless, but high ISO prevents you from it. You can sacrifice dynamic range but have a lower bandwidth requirement by using lower ISO and doing the pull in the post: the noise will be below the original gain line. Sure enough, it is worse than we'd like it, but...

Unfortunately, ISO 50 doesn't work with video, that would've basically removed one bit out of equation. Maybe there is another cheap (performance-wise) trick to lower effective number of bits, so lossless is more effective?

Here's a question: is there a way to have GD when I'm focusing, etc., but have it auto turned off (with everything else that could be turned off) during the recording?

#4
Hey guys!

Couldn't notice how much cleaner the previews of dark frame usage are. However, I'd say the whole process might be substantially improved: if only we could generate a 'book' of dark frames and, during conversion of the MLV to dng's or transcoding, an appropriate ISO/Shutter/FPS frame would be selected. The 'book' could be fairly easily generated from a continuous MLV file, where Shutter time and ISO are swept manually, let's say once in a second, or (wonderfully) generated automatically by a plug-in in camera.

I have plenty of MLV files, with ISOs all over the place (even real time changed). See my point? I'm sure I'm not alone. Plus, on top of it - I used different FPS. A tag "Dark Frame was already applied", might have a useful potential as well. Though, I'd definitely prefer to apply it to mlv and forget about it.

Surely, some of the permutations might be excessive (like fps) and at times I also was recording into modes different from an uncropped FullHD (sadly).

If the 'book' is too much to ask, then, during generation of black frame mlv's, mlv_dump can average frames into diff files, based on ISO and shutter time. Would be sweet as well!

P.S. Am I correct and MLRawViewer (1.4.3) doesn't support compressed mlv's?

Thanks for the great work!
Mikhail
#5
So far, I've been successful with 1066x 64gb from Lexar and 160mb/s 128gb from Sandisk. Though, none could do what I lusted fullhd @ 30fps, Lexar did it with help of spanning across CF+SD (LCD should be disabled via hack). 24fps worked fine for both. In fact, when hand held, I may shoot 1920x1152, to have extra space for software stabilization.
#6
Cause level of load of processing scales writes to cards. I can get continuous 1920*1080 @ 30fps with CF+SD, only when I disable pretty much everything, including rec blinking on LV. It is impressive (compared to what was otherwise), but not suitable for everything. When GD is on, combined CF+SD isn't that much different from CF alone (both fastest available). The definite advantage of CF+SD is max recording time - not terribly better, but always there.
#7
Earlier in the thread I seen a statement that it's impossible to make crop raw video frame aligned with center. Is it true? This shift goes beyond simple inconvenience (I made crop marks for resolutions I use). To keep plane of focus perpendicular to the line of view, you have to be off side when you shoot. Moreover, sharpness, CA and vignetting are asymmetrical, which affect final quality.

Under good daylight conditions and when I don't need shallow depth of field, I'd opt for crop mode with 2-2.5k, but aforementioned problems make it questionable.
#8
Yes, I of course did make image - to secure data and free-up the CF card for usage. Will think over, Thanks!
#9
Raw Video / Re: Lost video
March 26, 2015, 01:33:19 AM
Ooops, lost this thread of mine.

Anyhow, thanks - I've tried the photorec and it didn't work. It has saved txt files, which didn't make a lot of sense.
#10
Howdy!
First off - great work, much appreciated.

So, what I have is an image of CF card, after in-camera recording failure. Unfortunately it was a new year celebration, crossing the 00:00 mark, so I'd really like to recover it. Right after the failure I took the CF card out, to prevent overwriting. Thus, this exact image contains fragments of all files recorded earlier and not yet overwritten.

The goal: scan it for all possible mlv file headers, then scan for all frame blocks following definitions of found mlv files, then save all of them sorted according to time stamp into corresponding mlv files (with option of filling gaps - if frame is missing, repeat the previous one with correct TS, option of inserting bright/loud dummy frame to make sure I will notice it, option of not inserting anything but what was found). Would be nice to make a check for blocks (i.e. partial / erroneous should be skipped).

Surely, some of them will not workout well, but my interest is primarily focused on the recovery of the last one. I checked definition of C structs, and probably can make a parser, but it should be definitely much easier and faster to get done by Author.

Is this possible/could be made?

Thank you,
Mikhail
#11
Apparently, your camera has to bee freed from other activities in order to take full advantage of spanning - GD should be fully OFF, hacked and it should be 1.1.3 with no hdmi output used.
#12
I got 1080/30 with GD fully off and on CF (1066x lexar)+SD (95 Sandisk).
P.S. 1.1.3
#13
Raw Video / Lost video
January 01, 2015, 10:09:19 AM
Okay, I am sure it has been touched somewhere else...

I've been shooting one of the kind (of course) new year video, crossing the 00:00 mark. At the end camera went into Busy, and, later, Err.

Now I have the bunch of ML0, ML1,... and corrupted, small MLV. Is there any way I can restore what was written to the CF card? Card is intact, I took it out once I realized that there was this problem.

Obviously, I do understand that I was using not 100%-proven piece of software, etc. but... I know camera was writing video on the card.

Any suggestions will be highly appreciated!

Thanks & Happy New Year!
#14
Feature Requests / Re: Cropmark feature requests
November 23, 2014, 05:51:37 AM
Hello there!

I decided to post it in this thread due to its name, even if it is not exactly the same.

Is this possible to make cropmarks file (like the ones included already) on the fly every time we change resolution for crop mode? So in a full LV view we could see precise framing (black/red overlay)? That would be insanely helpful, given auto refresh/reread from this file every time LV is started and actual shift of captured part of the buffer taken into account. Currently I am contemplating about my own one, for a specific set of resolutions, but this whole shift of window thing can render it useless.

I just discovered superiority of crop mode vs. full frame mode in certain cases, but this misalignment and lack of cropmarks makes it unnecessary complicated.

Thanks!
#15
Thanks!
#16
Naturally, the issue with crop mode is framing and focusing - crop window isn't aligned with the center of the center of sensor. Though, I think custom crop marks can be added via bmp (there are 5 of them available, but for different purposes).
#17
In fact, if you think about it - due to 3x3 binning over 2x2 bayer: 1) the best case is 5 green elements over 3x3 2) the worst case is 1 R/B over 3x3. So, if it is straight binning over 3x3, we still lose plenty of incoming light.
#18
AFIK 5D3 doesn't do line skipping (that's why it is superior in low-light, when compared to FF cameras with line skipping, but I suspect it still throws away information), it does binning. Thanks to this resulting FullHD bayer mosaic-ed image isn't as sharp as optimally resized.

Sorry, I am too lazy to repeat my charts shots :) It becomes immediately obvious, once you pull out full frame dng to ACR - sharpness is lower, but what is worse - the binning artifacts are raising their head if you try to sharpen the image - location of RGGB elements is different in each binned pixel. So you can't really make it SUPER nice at 1:1. Obviously, 1:1 has none of this - it is as pristine as normal photo raw. Though, micro-contrast of full frame is still superior, when compared to crop mode.
#19
Just wanted to share: I have reverted to 1.1.3 and was able to record FullHD @30fps (though, zero LV feedback), but what is more astounding - 2560*1090 @ 24fps, in crop mode. Over a minute! Needless to say, it looks better than anything natively FullHd. Keeping in mind that 1:1 sharpness in raw is better than sharpness of full frame raw... wow.

Recording was done to CF (64GB, 1066 Lexar) and SD (64GB, 95mb/s Sandisk), in parallel.
#20
Raw Video / Re: Spanning
September 18, 2014, 09:14:52 PM
Once I got 1066x 64GB Lexar, 1080P @24fps became a no-brainer, always works. Without spanning, or with spanning (64GB, 95mb/s SanDisk). Spanning will just allows longer recordings, since it is split between two cards, where CF is limiting.

However, on 1.2.3 it can't sustain 1080P @30fps, only about 30+ seconds with hack. Using spanning has very little effect, just like with tests: it adds just a few mbs. apparently there is a bottle neck for a total band. I'm sure earlier firmware should really help, since I'm short just of a few mbs.

MLV+sound.
#21
Hardware and Accessories / Re: Remove Lens Coatings???
September 13, 2014, 10:24:04 PM
Coatings have to be on all surfaces. Otherwise there will be about 4% (x0.96) reflective loss of light on every air-glass border there, which would contribute to loss of contrast, flare and loss of light (T stop, which is always higher than F stop). That's why early multi-element lenses were so much darker, than modern multi-coated (multi=many layers on a single surface).

Modern lenses lose only a few percent for a whole lens assembly.
#22
What firmware did you use? Did you leave icon/debug on display for timing? Anything else?
I guess no card spanning?
I'm getting 36-38 seconds on 1066x 64GB Lexar. @ FullHD.
#23
No, photo mode.
Movie, 24fps, GD OFF: 90W/120R.
Movie, 30fps, GD OFF: 85.5W/115R.
All on 1.2.3.
#24
I've got my Lexar 1066x 64GB. It's the fastest card I've tried, faster than SanDisk 160mb/s 128GB, I rented for my SD trip.

I consistently get 120.8-120.9 MB/S writing and 153.8MB/S (yes, exactly this number) reading. Faster than any of 128GB cards I tried before: 2xKB, 4xTranscend. My USB3 says it can do 138MB/s write. Reading is the same as in camera. Pretty fast.

It can do about 15 secs of 30fps at FullHD, more with card spanning (SanDisk Extreme  64GB), but can't sustain it (GD off).

How the heck people get 30fps? Or there is something I don't know? Like they don't get it at FullHD?
#25
P.S. I like my 50L 1.2, starting from f/1.8 it is very sharp over important part of the frame. I mean moire inducingly-sharp.