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

Pages: [1]
Camera-specific Development / Re: Canon EOS M
« on: December 28, 2015, 08:14:11 AM »
OMFG a1ex, Licaon_Kter, dfort, and dpjandone for making this update possible, it took 9 months but it was the best christmas present i could have gotten from a bunch of people i have never met. you are all angels to me now and i hope you have the happiest holiday season ever!!!!!!!!!!

General Development / Re: 4k Filming
« on: June 25, 2015, 08:45:48 AM »
It's its own dedicated IC.
Do you know if it has a constant clock speed or does it adapt as needed?

General Development / Re: 4k Filming
« on: June 25, 2015, 08:03:12 AM »
i was just wondering where the h.264 encoder is located inside the camera, is it on sensor or is it seperate. if it is seperate from the sensor then you can peltier cool it like people would do in astrophotography that can allow us to cool the sensor or the encoder to -10C or a lot lower ( lowest i've heard is -94C BRRR!! ) in any case i think the biggest problem would be the clock of the h.264 encoder which i can imagine is constant and meant to work at a few levels 1080:max 30fps, 720:max 60fps, 480(WGVA):max 30fps... etc.

Camera-specific Development / Re: Canon EOS M
« on: June 21, 2015, 03:20:02 AM »
so the last 5 failed nightly's are very fixable, but a1ex wants the eos m community to fix fps.engio because it is slightly broken and causes exposure problems for some people ( me included ). that's great that he wants us to fix it but if after 2 months we haven't had any progress and removing fps.engio caused the build failures we should just put it back broken and fix it later. Buggy ML is better than no ML. Also if anyone knows how to fix fps override please do so, or if hudson is reading this please add the fps override back on to the fps override builds.

Raw Video / Re: 12 to 24 fps (FPS override Problem)
« on: May 28, 2015, 07:13:05 AM »
so what is needed to fix fps override just some changed timer check frequency values, or is it way more complicated. i'm just trying to wrap my head around what needs to be done that's all.

The first thing i would like to say is that this doesn't need to be done soon, and i know that it wont be done soon because it means you will need to find an obscure file ( if it even exists ) to even do it at all. But! i think this may be the best way forward for the older, and less expensive cameras because we all know that the three cameras i mentioned have way to low of read/write speeds on SD cards to make any future advancements really worthwhile. Thats why i propose an optional overclock for the ARM processor and DIGIC processor ( along with SD controller if really necessary ). If the DIGIC processor is overclocked we can focus faster, and hopefully have faster burst rates. If the ARM processor is overclocked then the read/write speed can be increased to make for faster burst rates and higher resolution raw video. Overclocking does have some adverse affects that must be adressed, the extra heat produced would normally break these cameras. The way i would fix this is by disassembling the camera and adding a heat sink to the arm and digic processors ( these cameras arent weatherproof anyways so who cares :P )

Pages: [1]