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.

Messages - dpjpandone

Pages: [1] 2 3 ... 12
Yes, you are absolutely correct! Playback is 1080i, but that's because it's playing back a file that has already been uprezzed from 1728 to 1920. Unfortunately for us, the image is only 1728 pixels wide prior to recording (during live preview) so it is not possible to view it at 1920 during preview.

Even if this could be done (which it can't) it would not improve the quality, because you are starting with a video that is 1728, even if you record it at 2k, 4k, or 1 million k's - it's still just an uprezzed 1728.....

Great idea though!

Oh, wait, I just re-read your post, and you have 6D (I thought 60D) - what is the native resolution of raw video (in full frame, not crop mode) on 6D? is it 1920?

Raw Video / Re: Max Shutter speed of 1/120th of a second? Why is this?
« on: August 26, 2015, 02:37:27 PM »
did you try different exposure override method?

I checked 1.4.3 and the green dots are still there... You got me all excited... It definitely fixes the pink dots because it treats them like hot pixels, but it's algorithm is not picking up on the green ones unfortunately... They are a different type of pixel (contrast detection i think?)  They might be hard to see on certain footage, but I assure you, they are present.

Actually,  after further testing, I noticed that the pink dots disappear, but the green dots remain. I guess the software sees pink dots as hot-pixels and corrects them, but the green dots which are contrast detection pixels or something don't get picked up by the algorithm... I did not try it on 1.4.3 - I thought 1.3.3 was the stable release. Have you tried it? does it remove ALL of the dots?

Raw Video Postprocessing / Re: MLVProducer for Windows
« on: August 24, 2015, 07:50:50 PM »

  I downloaded your MLV file (sorry it took so long, it was 1GB, had to do it at work on fast internet)

I made a screen capture of MLV Producer in SRGB, SLOG, and SLOG with Kodak 50D LUT applied (this LUT designed for SLOG)
I also took screen capture of MLRawViewer in the same 3 settings to show the difference.

I uploaded the 6 files here:

There is not much color in the MLV file of the lighthouse, but the difference is still apparent. When you look at examples that has a lot of color in the image, it is even more noticeable. I have tried numerous combinations of colorspaces/corrections and no matter what i do, the resulting image always seems underexposed and desaturated. I thought perhaps It was just me until i saw the images posted above by Kutu.

Since the results are the same regardless of colorspace, it makes me think perhaps the problem lies in the first transform before conversion to any of the colorspaces. I don't know how the processing pipeline goes, but I imagine it debayers to linear first and then converts to the selected colorspace?

Please let me know if there is anything I can do to help you with this. I can send more footage, more test images, more LUT's, review code,  whatever you need.

As always, I really appreciate your hard work on this app, and i feel like this could easily become the best solution for rendering dailies/proxy's of MLV footage with just a few minor adjustments.


Something strange is happening that I never noticed before:

When I first open a file I see the pink dots as usual (EOSM) after it plays a few frames they disappear! Did you implement pink dot removal in 1,3,3!?!?!?  This is amazing!!!!

Raw Video / Re: 12 to 24 fps (FPS override Problem)
« on: August 23, 2015, 08:21:16 PM »
"movie crop mode" is a feature aavailable only on t3i and eosm. It works for both raw and h.264, the great thing about eosm is that movie crop mode is 1:1 pixels (no line skipping) just like other cams, but the preview is full color and framed correctly (unlike other cams that either frame in 5x, or greyscale)

Raw Video / Re: 12 to 24 fps (FPS override Problem)
« on: August 23, 2015, 05:35:47 PM »
3x crop mode is "Movie crop mode" in the ML menu?
You keep talking about this, is this "Zoom mode 3x/5x" for photos in standby? Why bother with it since I can't use it when switching to video anyway?
This is the first time that I see this advice, Why wasn't this specified before daammit!!?!?
Yes it works, 1080@30 can be pushed up to 46.056fps so yeah limiting it at 45fps is nice.

Movie crop mode is limited to 1792 pixels wide, and works with raw or h.264. 5X allows higher resolutions, but the preview is not framed accurately. It can oly be used with raw. So that is why we want a timer_b_min value for 5x, in case someone wants to use fps override with 5x raw video.

So we agree on the values I posted? I will update the pull request and add you and deafeyejedi as reviewers. If you can look at the pull request and click "approve" that would be helpful

I really want to play with this, but I have to change the button to enter command so it can work on EOSM. Is the source online somewhere?

Camera-specific discussion / Re: Canon EOS M
« on: August 23, 2015, 05:03:18 AM »
FYI - shutter fine tuning DOES in fact work, and always has. Someone must have disabled it because they overlooked the fact that timer changes are not applied until you press record (Full Frame mode)  when in crop mode changes are applied immediately. I have submitted a pull request so that we can get this feature back in nightlies.  Thanks to DeafEyeJedi for bringing this to my attention!

EOSM is a funny little thing. It's the only camera that idles in 720p, (hence the squeezed raw video) and the only reason i can think of for doing this is that it somehow conserves battery life. After all, it's battery is about half the capacity of an lp-e8 or similar. I wonder if we can eventually find a way to trick it into staying in 1080p all the time so that we can record full frame raw video without the squeeze factor...

General Help Q&A / Re: I think I just bricked my T3i.
« on: August 23, 2015, 01:43:50 AM »
take the card and battery out. Now put the battery back in and start up with no card inserted. Does it work like normal?

Raw Video Postprocessing / Re: MLVProducer for Windows
« on: August 23, 2015, 01:38:27 AM »
I've noticed that the included SLOG is way off, changing gamma to around -2.20 corrects this.

I've also notice the same as the above post. I would also expect SRGB to look like his example from mlv dump. It seems that perhaps a lot of the functions that are converting from linear may have errors. Can I take a look at your code, at least the lines where the transforms are done, to see if I can help?

General Chat / Re: shooting 4:3 video
« on: August 22, 2015, 05:35:58 PM »
you can buy a used one for as little as $200 sometimes, the only drawback is they dont record audio so you have to slate every shot, but it's definitely the best cam for anamorphic. You definitely need a cam with a CF card, SD is way too slow

General Chat / Re: shooting 4:3 video
« on: August 22, 2015, 09:18:43 AM »
yeah man, enable the mlv_rec module. it's got settings for all kinds of different aspect ratios. 50D is one of the best cameras you can get for anamorphic Because it shoots the full frame in 1500 pixels wide. After you unsqueeze it in post you have 3k raw video!

General Help Q&A / Re: ISO Button
« on: August 22, 2015, 09:07:34 AM »
set ml digital iso to -3 and then when you select full stops with canon button, you are actually selecting multiples of 160. Also, there are shortcuts for iso, wb, and audio gain on t2i/t3i so i imagine they are on t5i as well

Raw Video / Re: 12 to 24 fps (FPS override Problem)
« on: August 22, 2015, 05:11:00 AM »
Yes. Since we are happy with the timer_a_min values, leave them the way they are, but set timer_b_min back to:

 #define FPS_TIMER_B_MIN MIN(fps_timer_b_orig, 500)

and see how low you can push timer b before you have problems (remember to keep your shutter speed at 180 degrees, as this is how you would use the feature when shooting videos.  so if you are starting at 24fps, shutter at 1/50)

When you are testing the 3x crop mode, start with desired fps set to 45, and then start lowering timer b from there (it will save you lots of time and put timer a at a realistic value)

here are the values from my own testing:

FULL FRAME: (we agree on this)

1080p30: 1965
1080p24: 1965
720p   : 1965
480p   : 1965

1080p30: 1195
1080p24: 1195
720p60 : 1195
480p   : 1195

3x:      (here's where our results are drastically different)
1080p30: 1195
1080p24: 1298
1080p25: 1195

BTW, you don't need to check recording vs. not recording because there is nothing in current fps implementation to support that, besides if timer B can go lower when recording vs. standby it's not going to do you any good because you would normally set it in standby, and if it goes lower in standby vs. recording the worst thing that happens is your recording stops.

so to sum things up, the goal is to choose values that give the maximum range of FPS, then pull them back a bit to some meaningful value on the safe side. i chose 650 since that allows me to overcrank up to 45fps (in my testing I can record 44fps reliably)

So I have mine set like:
Code: [Select]
#define FPS_TIMER_B_MIN (fps_timer_b_orig - (ZOOM ? 290 : MV720 ? 57 : MV1080CROP ? 650 : 57))
If we can agree that these values are safe, I will modify the pull request, if not, then I guess we'll have to go with the ones you reported initially.

Raw Video / Re: 12 to 24 fps (FPS override Problem)
« on: August 21, 2015, 11:22:16 PM »
I have had stable and reliable results with my timer B values set to a much larger number (large enough for me to overcrank from 24fps to 45fps and higher using low light method)... but with the values from your table, this is as high as we can go, I'm afraid....

So, it seems to me that these are our options:

1. Leave the values as they are (since you have confirmed them to be safe) and leave the pull request unmodified in hopes that it will be merged as soon as possible, to fix nightly builds
2. Backout the changes in the pull request and do more testing to see if it can be pushed further (just in case a mistake was made when you made the table initially) in hopes that we can agree on safe values that allow for overcranking to at least 35fps
3. Modify values in pull request now so that it can be cranked to at least 35fps (and change them later if anyone else experiences artifacts/problems)

I think option 3 would be ok, since they were initially set to a much higher value anyways, what started this whole "intentionally breaking nightlies" thing was that someone reported an issue, and Alex noticed that the values were wrong.

I think the values for timer A are good, and .616 is an acceptable limit, but I am pretty disappointed with the values of timer B. I would like to use a value that at least allows us to overcrank to the limit of the encoder. The only time I experience artifacts is when The shutter speed is accidentally set too low, but I usually use an 180 degree shutter (because I'm a video guy) so I guess maybe I didn't run into the same stuff you were seeing with whatever shutter speed or FPS override method you used when you made your table.

Would you be willing to do some more testing to see if any of the values in your table can go a little higher? I would recommend keeping your shutter angle as close to 180 degrees (or fps*2) when testing for timer B

I'm sorry to ask you to do this again, unfortunately I was not involved in the conversation when you made the table initially.

Also, do people want lower fps than .616 or is this good enough?

Raw Video / Re: C mount lenses 5x crop mode
« on: August 21, 2015, 02:58:39 PM »
Yes that is the ebay picture!

What resolution was your MLV capture? if it's smaller than 1792 that would explain the extra crop. If you do a frame grab of h264 in crop mode it should look like a 14mm right?

Please upload one of your purple DNG's so we can check it for you

i regularly zoom in up to 150% on source material shot at 1728x724 and I still think it looks damn good. I've seen projects that were submitted 720p projected at 2k that look fine. The most noticeable artifact seen on a big screen is the aliasing from lineskipping. If you shoot crop mode you can push it a lot further.

Raw Video / Re: C mount lenses 5x crop mode
« on: August 20, 2015, 04:59:52 PM »

is the one i use, I also have a 12.5-75 tokina c-mount that i don't really use anymore, if someone would like to play with it, pm me.

The EOSM in 3x crop mode is closest to 1/2" sensor, or 8mm film so those are the types of lenses to look for. the 8-48 is the equivalent of 24-144mm with a maximum aperture of 1.0, and parfocal zoom! It's pretty awesome...

Dfort, can we see some footage with your 4.8mm?

Raw Video / Re: 7D - Cropped View NOT WORKING ANYMORE!?
« on: August 20, 2015, 04:55:52 PM »
What was the date of the older build that works?

Camera-specific discussion / Re: Canon EOS M
« on: August 20, 2015, 03:00:20 AM »
got it now, thanks for that!

Pages: [1] 2 3 ... 12