Messages

On EOS M when i choose jpg
31 config and 55 total , srm 2x31


when i choose RAW then it goes to 20 config and 23 total srm 3x31




canon 5D II:
RAW photo:

config 28mb
total 183mb
srm 6x38mb
when i enable liveview in this mode , it drops srm to 4x38mb

JPEG:
config 32mb
total 259mn
srm 4x38mb
in this mode when i run liveview to get video it drops srm to  2x38, config and total stays the same


Sooo... which one is better to use for raw video ? Isnt it better to spend less memory on photo to get more for raw recording ?

Is there any chance that MLVApp will get VP9 codec export ?

Exact centering, at least to me, is hard to get. Cmos 5 and 7 maybe also modifying ratios could get you there.

Exact cenetering for C mount lenses is not that hard but the issue is on the side of adapters, not all adapters are centered identically, i have two and their center is different just a bit to unhide vignette in the corner one one and hide on another one  + some lenses vignette sooner and some later, lots of variables to take on, its just better to crop and leave as is.

Hey id definitely donate for 5d2 as i have one and development stopped since few years
These cams are not that expensive now, you can get one for about £250 about 300$

Great, im glad we were able to reach the goal and cam is in your hands 

M50 or R

oh yeah i remember that now

I can see you can buy used 100Ds on ebay for about 250$ so if you go that route, youre almost set as of now
https://www.ebay.com/itm/374093222731?epid=144819519&hash=item5719b1934b:g:z1YAAOSw3xdiiahC

Hey thats great, i dont own 100D but i will dontate cause of what you did for M that i do own

Holy crap ! Just tried it on eos M , i set 2.8k 10 bit, 24fps , sd overclock 192-240, got 61-62MB rec speed and i was able to record one minute, it stopped at 01:05...
Danne heres HDMI output when i record 2.8k in this new version, half of the screen is pink stripes
So that means now 3k is possible to implement on eos M ?
I set 3k and reg 6014 to 480 and got 23.3 fps , i can get 30secs this way but 23.980 wont get me even 5secs with 6014 set to 525.My cardwrite speed on PC is 80MB
Sadly all other non crop modes are broken, and hang the camera when pressing record, so i cant record in fullsensor width modes.
Ok turning off lvface hack fixes camera hanging on non crop modes but its the one hack that helps the most to gain extra speed.
How i can capture 5D2 log to provide You with correct addresses for lvface and awbd functions that are needed to make it work on 5D2 ?

Hey anyone knows what address i neeed to adjust to finetune shutterspeed on this camera  like on EOS M ?

Hey masc , what should i add to encoding string to make x265 not use more than lets say 40Mb/s when encoding video ? i use this now but when the footage is noisy or theres lots of stuff in focus then i get about 90Mb/s and its slowing down playback , its nice for shots with blurred bgs but for deep focus it can bump up the bitrate depending on how noisy/detailed video is :

Code Select Expand

if( m_codecOption == CODEC_H265_H_MOV || m_codecOption == CODEC_H265_H_MP4 || m_codecOption == CODEC_H265_H_MKV )
            quality = 17;
        else
            quality = 19;

        program.append( QString( " -r %1 -y -f rawvideo -s %2 -pix_fmt rgb48 -i - -c:v libx265 -preset veryfast -tune fastdecode -crf %3 -tag:v hvc1 -pix_fmt %4 -color_primaries bt709 -color_trc bt709 -colorspace bt709 %5\"%6\"" )
                    .arg( fps )

This was default:

Code Select Expand

        if( m_codecOption == CODEC_H264_H_MOV || m_codecOption == CODEC_H264_H_MP4 || m_codecOption == CODEC_H264_H_MKV )
            quality = 14;
        else
            quality = 22;

        program.append( QString( " -r %1 -y -f rawvideo -s %2 -pix_fmt rgb48 -i - -c:v libx264 -preset medium -crf %3 -pix_fmt %4 -color_primaries bt709 -color_trc bt709 -colorspace bt709 %5\"%6\"" )
                    .arg( fps )

for 8mm or 16mm emulation use 1440*1080 in crop mode and cctv lenses for this.
i use lenses for 1/2' sensors , super 8 will get you vignette so you would have to crop to maybe 800*600, notnsure.
1/2' covers about the same as 16mm film lenses.
this will get you moire free footage

overall best quality is 2800*1080 or something similar ( ita almost 3k!!) i use it and 2500*something(2.5k).
some cctv lenses dont covee 2800 or 2500 so i use 2400*1400 (16:9).
also upscale when rendering, it will retain more details.

man, nobody told you but its not a constant precise crop formula, its total manual adjustment of what acmera lets us record and card speed factor.
Sometimes you chop off pixels from crop modes to get more recording time.
its a hack, if we will somehow get even more speed from cards, the crop will get more pixels and field of view will be bigger, with slow sd cards crop gets smaller part of full resolution image.
easiest thing you can do, compare full resolution photo size to raw mlv resolutions.
but remember that crop modes are not centered super precisely into the middle of the sensor
your math does not apply, you can divide full res photo by 3 , and even then some pixels can get discarded depending on what ml coders choose.

I got them, cant open them in mlvapp with dng to mlv converter tho...

GReat, i cant find dng samples with human face tho, to convert from raw16 i need to compile converter for win
Details like this( not having dng samples for people to tinker with) can and will harm/limit interest , id like to check how footage behaves under tonemapping algos in mlvapp cause not all dngs give same results, it would probably also need cam matrix.

what format it is? dng frames? + pcm wav?

ill donate 20$ by paypal but i dont own 100D, i like the idea tho.
Where?
Maybe find a reliable dude who can accept paypal donations, so he will buy the cam in your country for you on ebay or somethin

wrong topic...

Milk and Coffee 10,12 and 14 bits in raw on my canon M or 5d2 are hard to tell apart, 10 bits have noisey blacks so i use it when i have no choice and footage is too high res for continuous recording
Dynamic range is identical on all 3 bitdepths, i tested it, there wasnt more stuff and even if there was its just junknoise ,you can test it easily too.I use 12bits.

Im leaving settings for modifying mlvapp source here for myself but also for others whod like to change default stuff.
I did modificatioons cause default quality wasnt enought for me or was too high that resulted in very slow playback (h265 very high or very compressed quality, nothing inbetween)
I did that:

changed defaults in mainwindow.cpp:

Code Select Expand

        if( m_codecOption == CODEC_H265_H_MOV || m_codecOption == CODEC_H265_H_MP4 || m_codecOption == CODEC_H265_H_MKV )
            quality = 18;
        else
            quality = 20;
Second value is the medium setting ( high number - less quality and the lower numbers than defaults - the more data is put into compression) 20 is ok for me at this point in time for medium.
I really recommend to export in 265 10bit, it nicely retains a lot of colours from raw files.


Second thing i had to take care of was jpeg export for single frames, i put through mlvapp a lot of DNG files from camera and from my phone, so i needed much better compression so instead of default one , i changed it to 97 (100 is best ).

To do this i modified in singleframeexportdialog.cpp:

Code Select Expand

        QImage( ( unsigned char *) imgBufferScaled8, getMlvWidth(m_pMlvObject) * stretchX, getMlvHeight(m_pMlvObject) * stretchY, QImage::Format_RGB888 )
                .save( fileName, "jpg", 97 );

Thats about it, im leaving this here in case ill get back to new builds of mlvapp trying to apply these changes and i forget what i modified.
Also one thing i forgot but managed to remind myself today, i had already folder with all needed dlls and files for exe but i exported/compiled in x86 which failed to start with these dlls, i have to remember that its x64 build and change mingw to be x64 in qtcreator.

so sensor scan speed is a bootleeck or card writing speed is the issue?

I have these


Heres all EOS M stuff
https://drive.google.com/file/d/1aYPdzzul5OS81WwgO8z19t2zG-dKoF79/view?usp=sharing

Just make it anonymous or less official, setup donations link and let it be, if nobody is sure if someone donated or not, theres no issue of breaking the law, if donations will reach the goal then just post message about acquiring the cam, doesnt matter when and how it was obtained.
Everyone donating has to accept the fact that he wont be acknowledged and mentioned for donating and thats it.
Not accepting donations is mostly a legal issue.Or moral in some exceptions.
Anyway i doubt that canon cares about this cam , its almost 10 years old and it wont hurt their sales.

Wow, so there is a chance for android port ? Id buy extra phones just for rendering