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


Since you're the pro, do you know why ACES 1.0 OCIO config does not include a standard sRGB D65 ODT? Closest is a sRGB D60 Sim. This is kind of bizarre since sRGB monitors are all calibrated to D65.

This question was asked here but the answers are confusing and very vague...!topic/academyaces/N85bt9Aqn48
Quote from: 1% on February 13, 2013, 05:30:43 PM
Hmm... is it 4:2:2 though? they co-designed with ti  so they could have solved some of the regular encoder's problems. They renamed the parameters slightly already. Have to look inside to see.

Only 4K is JPEG 8bit 4:2:2, H264 is the same options as 5D3, plus 50p/60p mode and s35 mode.
Quote from: 1% on February 12, 2013, 11:22:50 PM
Best thing would be to make the YUV buffer 1:1` and encode that. or figure out the LV jpegs (422). The scaling is what really degrades the image.

You won't get much from anything except 1d firmware decompile. the encoder probably inside the digic package... and I thouht 1dc 2k/4k is jpeg, not 264

Only 4K is M-JPEG, all other recording formats are H264.

ok then, maybe we'll just leave the mystery as it is?

which directions are we heading towards now? focusing on the scaling and bitrate parameters?
ok, well I guess 1D C uses a different h264 encoder then.
built-in card readers is definately USB 2.0
Nice find, well done :)

does this mean, 1080/50/60p is possible in the hardware?
What do you mean by, "This breaks 60P?"
General Chat / Re: LQ video compression in Canon DSLRs
January 12, 2013, 05:11:20 PM
Turn the full range flag on is better i think
General Chat / Re: LQ video compression in Canon DSLRs
January 12, 2013, 12:23:35 AM
Quote from: 1% on January 11, 2013, 01:00:04 AM
Heh, I guess I'll have to post up samples of the new compression (and broken 4x4 matrix files). No leaves right now tho and the indoor stuff doesn't have enough motion.

Now canon uses rec.709 and when you add the matrixes some crazy pro HD formats.

Only 5D3, 6D, 1DX and 1DC use Rec.709 space, and the "VideoFullRangeFlag" seems to be off by default in the perimeters.
Quote from: 1% on January 06, 2013, 11:34:46 PM
It produces similar bit rates and results to 600D. IPB makes higher rates for some reason before stopping. I can set it to target whatever rate I write to the file. It does crash/stop a bit more than the custom written version for 600D. Rate control halts with CRF 13 so I had videos producing almost 1/2 frames at CRF 1 and 2 and then 1/2 at like CRF 13. Averages out to better than stock. Video looks just like 600D video but I didn't pixel peep.

Its less dependent on ISO than digicIV. I made an 80Mbps 640x480 video with CBR. I can't open any files with bit rate viewer so haven't seen the graph.

There are a few test functions in the firmware to set some of these. Also need to see if my IPB videos are 5.1 or 4.1, I never new profile was supposed to be lower.

*, they are 5.1

You got IPB file with level 5.1? that's pretty impressive, the max bitrate is 300Mbps with 5.1, and only 62Mbps with 4.1 (according to spec)

In my tests I was able to hit 62Mbps with IPB mode. 150Mbps in ALL-I mode.

Maybe high bitrate IPB is better than standard bitrate ALL-I.
Great work!

Level might be an arbitary value, just a flag or something, it's implemented as 4.1 for IPB, 5.1 for ALL-I

Did you shoot any samples? what's the max average bitrate you got after the hack? under what ISO?
Archived porting threads / Re: EOS M
November 26, 2012, 06:25:32 PM
nice cup in the background :P
Quote from: driftwood on November 24, 2012, 01:31:20 PM
Good work Marvin:

Can you experiment with the two patches ratecontrol= in ciombination with maxbitrate / minbitrate ?

Change ratecontrol value to =1 then =0 together with entering values into min/max bitrate.

I'm still looking for a value for cpb ncoded picture buffer/dpb. Maybe Maxbitrate is like GH2's Top settings (declared bitrate) and Minbitrate could be a reinterpret of 'Bottom' settings which we worked out to be the CPB size.

We need higher coded picture buffer settings for adjusting the bitrate higher - ie they work in unison.

Failing this, somewhere there must be something in the code that declares a cpb. We need to find it.

both resulted in ERR70 when i tried

please take a look at this post:

some tests have already been done, might save you some time :)
Quote from: Steven Griffith on October 13, 2012, 11:01:07 PM
Hey KarateBrot,

super stoked that you're happy with the styles!

For anyone who's interested in VisionColor, please note that it is neither a flat picture style nor does it give you a 35mm film look out of the box. It is basically an enhanced version of the neutral picture style that mimics some of the behavior of film with a custom gamma curve and colorimetry that was created with the Kodak Vision 3 5213 as the main reference.
VisionColor comes with a semi-flat version (VisionTech) and the option to test the current beta of VisionLog (Log-space style)

Read more on our website!
Karatebrot, thanks a ton for spreading the love!

- Steve // VisionColor

Thanks for developing this amazing picture style. How do you compare VisionColor and VisionTech? Have you done any comparison with Marvel's Cine?
Feature Requests / Re: Main/High Profile H.264 encoding
October 03, 2012, 10:10:45 AM
Quote from: shanel on October 03, 2012, 08:31:21 AM
Hi 1%,

- I'm not sure what you are referring to when you say 5.2 and 7?

- On QP, ML already has control for QP via Qscale.

- At high bitrates, profile can be a bigger driver of quality than just bitrate. Baseline profile offers only a limited set of the technologies that make H.264 powerful (No B-Frames, no CABAC, etc.) On a encoded-quality-per-bitrate basis, the 5d3 will blow older cameras out of the water as a result.

Although 5D3 uses High Profile, Canon seems intentionally crippled the quality, CABAC is turned off by default (see the bitrate thread). Without ML, 5D3 won't offer many visible advantages on codec/compression.
Reverse Engineering / Re: (M)JPEG encoder
September 27, 2012, 10:15:52 PM
Quote from: y3llow on September 27, 2012, 03:31:02 PM
Is there any chance of a jpg via your work (whilst not recording), a short mov and a jpg from photo mode of the same static scene for comparison?

My observation:

the quality goes like, photo mode JPEG ≥ MJPEG (LV) > .mov file

photo mode JPEG may have an edge on resolution, but in terms of colour and DR they are pretty much the same.

On my 5D3 they are sharper than the movie file, noise seems more finer.
Quote from: mgm on September 20, 2012, 10:07:29 PM
At US$12,999 plus tax, you'd need roughly 250-300 donations of $50 dollars each to buy a 1DC.

Many 1D/5D/7D owners looking for a real upgrade from 1080p would be willing to donate if you open a special donation fund for this project!



The actual price is $10408, see link in previous post.
Quote from: joxxie on September 20, 2012, 09:52:19 PM
well if i pull the trigger on one .. i will definitely do it if he needs it

I would suggest you save the money on an 1D C

this is currently the cheapest preorder. Will be released in December.
This is just an update file yeah?

I remember when Alex and me was dumping the 5D3 firmware back in March, we need to get a full dump from the camera itself.
Already got a dump? that's great, let's wait for 1D C and its firmware update then  ;D
1D C is still a beta unit at the moment and there is no firmware update for it, also it's not publicly available yet. therefore a dump is not very practical at this time.

I'm going to hire an 1D X for a sport shoot in early October so I'm able to do a firmware dump if there is an interest.
Andrew Reid is not a very reliable person in my opinion, there ARE some hardware differences, they are mainly about sensor cooling.

1D C is scheduled to go on sale this December (retail price €8038 or $10408), if a firmware update comes out later I think it's really worth looking into, because it's got all the "dream" features we want on a standard EOS DSLR, such as 1080 50p/60p, crop shooting, log gamma and MJPEG 4:2:2. Maybe we can take a look at how they implement these features and try them on 5D Mark III or other cameras, rather than porting the firmware to a 1DX.

However I believe these features are programmed to run on dual DIGIC 5+, so it's quite a challenge in my opinion.
Reverse Engineering / Re: (M)JPEG encoder
September 20, 2012, 07:45:29 PM
Quote from: a1ex on September 20, 2012, 07:30:45 PM ;)

that's eye-opening... but it still hurts me when I see grammar mistake  :-\