Messages

I did compile myself, Where to change MODULE_KEY_PRESS macros? you use same format as arkanoid (working) what else could be the problem? Is it because EOSM has "Q" "Set" combined? so game does not start?

Code Select Expand

switch(key)
    {
    case MODULE_KEY_Q:
        running = 0;
        return 1;

game does not start until "Q" ?
The blocks fall, just cannot move or flip them and cannot exit until level fills up and Game Over

Did you test it yourself?

I don't have the cable. I ordered one last week but it hasn't shipped yet

Can someone who had an AV cable or a sescom adapter please test this build and let me know if headphone monitoring is working on EOSM now?

http://hipsterhack.com/2022/11/13/magic-lantern-canon-eosm/

I just realized i posted this in the 5D3 thread,, I'm sorry guys this build is for eosm, please disregard

Does not work on EOSM. The game starts but none of the buttons work.

Wrong thread, please delete

I found my old thread about all-i frames

https://www.magiclantern.fm/forum/index.php?topic=15685.msg152818#msg152818

can't find the videohackU file though 

I have actually never used QEMU

I've always tested everything in camera.

It seems a lot of the guides are outdated. What is the best tutorial/thread to follow for setting up QEMU on a windows machine in 2022?

Wierd.... the HG clone command restores all the loose files in the root directory, but doesn't convert the subfolders, so I'm still trying to figure out a way to convert the files in the "platform" folder.

oh....

Code Select Expand

Clone
To get back a normal repository, just do
hg clone $bare-repo-name $normal-repo-name
E.g., for jagan/bioreader.html, after downloading and decompressing 9d5f5e8e-a6ba-44d6-8bb4-5a689c66ef09-repository.tar.gz, do the following:
hg clone 9d5f5e8e-a6ba-44d6-8bb4-5a689c66ef09-repo/ bioreader

I'm trying to port headphone monitoring, ALL-i frame, and fullscreen magic zoom for my own personal EOSM builds. His work on EOSM and 6d were in the same repository. He figured out a lot of stuff in 2013 that worked fine but never got merged into main.

and btw, sir,  you are awesome for pointing me to this! I never knew about "software heritage"

I downloaded the archive, it seems the basic structure is there but all the files have a ".i" extension and are displaying incorrectly in a text editor  What is the procedure to converting these back into a useable folder?

Ok, maybe this will help. zebras are properly aligned. false color and peaking are not. why? Is zebra already canon/digic display filter and not ML code like the ones that are misaligned?

Does anyone have One Percent's old 6D repo saved somewhere? I'm looking to port some of his work that never made it to MAIN

It might be possible to get the source.  The mercurial build system logged source code changes as part of the build, and copied them into one of the binaries.  I haven't worked with this in much detail and can't remember the limitations.

See parts in the make system around "version.bin", there's some hg logging command that creates it.

so I actually found the Hard drive with my old source today!!!! BUT!!!!

All the files are gibberish!

for example, here is the content of my old features.h:

Code Select Expand

(ØߐTã ¶)šõѶ¾ÑÑóúvŽâ£³?Ê^•Ú#]1íüË™H"ð}]
‡w%?¬°Ã]ýv‹öI9ÑTWssÿ6úÜSç
r¡m×·¤÷£oÅ\vY=†–ê"Ü&G"ÿµ>*œ¯‰i
‰ Ë ßy•6>âfÁáù€E«é¿Jc‰[Ú†ºx/JÏÆÝXDÓ...*õõ-2Q@ÿý$WxèÒhéihÌê
:¶"ÒObhS×#¦ü›½Æ'×/qî¿™2MAÀD‡/ÙÕÜùX#ˆë...:Ζ»àwÏ1«A. b'c¸[dçm¸+ÙÃHP,û™à'·Tþ¥ƒ1g
Ä0ɉ÷hñš ®˜÷
Üê÷¨bSœ}139÷[ò)—¼w°®ë&ú§§o|¤ÏÁÕCÐ,N»Øo°,,ÄØ;,\"}ïÖW9WS×0±Ò;æ)"¬äiCÿh:ĉø¨{ æàH\UußáÉÿ•±Cº<ÓfKw!0ÝÒ~µ‰^,õ9$·Ýøös71Š
­°qÂ
-ûØ)ñÐv‰\0žb‡ÏÎk¢d°1}!åeï÷Õ‹lŒãÐËQ»o¯¸PªI`ˆRi>-ÈìD Z•JdÑAE"t‰%k»‰ ¨¬"{¸F[øÏÛYÍ»7Dñë&AV‹ÒH#7Kšyõ]mËñ-7ˆ±ž8}ø¸ç€ ‰Ê!"L–š:
[K),öLæuévó<K¨²›ÞPõ'ÌãÇ,,¨Ý—zÑkô³M¶uÛ+JKl´âÈÆsºšÒ4W,J#™×ºˆÿfL^?ÓIJ÷Ÿl²N°ŽˆŽÛí4 —Þ°ªòd:5q¼[¬$ä¹›}[Y|D¨f<κ‹Ÿ¨&øiPÛø«Iì3ZÍq%À6
â‡dCÛ)(Â2E±J½]çÞç_{êÞiväµïÄî+äZDìË:2t3åußeD"Ž3¶O"¼´XidÙÙ i§é2©´RwèÏÄ?ÃuMc9¨Ÿ¡c
Î'm†§¥Ï՝kS'—ðb'½çIȉ½ûÚSóZOÁû èúÙ¶ ëÊsRbã8"@‡Øèø¥`.>id, »³hÄÔ ²{>ù*ÝŒÖW ÂpZ7üÍc[á¹òv±
6uŠÑ)~,îð"¶ª?TÑ.;úkÀ•ÿç

©©¶Ã,Xf‡(MÙþŸœ!ÕeƒÄ^×—Žÿ!;öÈÃÇ£7ˆ6·IbËqçO®w²mNè¶‹‡ø¾1™¾'liÛ5œÉ&SÔÇ-­Q𺮻ÝÕYÞD7Üú'U&#ø`«T!±Áy€º¯ú®¯˜¨Ö\ø(ÙòŒ 29é~ùüZ­QO«h1q%ÜI¾Â(I
i!ñ=¢1,,XÏ2¤\F}iOæÊ,›Eª8¸|ٍÁc¤[È—n–Üy8ù/àNô¼½Ük€jÓF#°Ç×#niÃqàGç¥â¸õnfi)`-9
&¹ï$ej¾ÐN¶9ø²|,,üÐúê‰ÁÕ†Ç=YX"§...$0O=Íó'Éðâa¦Ñ5с£âÝ›~ÜÓ.¤ý§¨‰R[ßW3·;êï³ñ¸õQå Yúi
Œ
9§'ŽÈíë©]7Í~N'ÛúÁGÃÆŽË 9k
çØg8¿Ý@#ÕLwUUO-›,Bû9}è¢z®­ê£cV´àd8¹"nt•À–®5y-U1«,_5¶SÕWBŒáu=duâ<Ç*,,Rƒ¥?
vu"s±‡ŠJÎ8*Uþ=Cçá?3/,pót,ü¶tÉL²¾brgwå´nŒÂ1Ý·OùL'¨tt¸UuÈa îçCp×{cþä%¿ÀG¡BL³§"ÁÉ'²Ð0D]f ÙEó}S¡´ðŒñÆŸ2|¾b¼Ž
ìæžÉ~å‡8<7pjÈÐÂÔ$'šÁ{9yQ‹Ñ˜ÂxãÜáÝßüÁÚÛ­™Ý!C|£Ã[gŸ6³£:WâßkÒþ1Ñ?¸½8Çn*´‰Âzà(¼'"mb¼) €ñùB¹&<0âŽ`á ßÎHDÄœI;»lâ...Äý.*æA´ð8§Låß5ù!Å¡x_a
Bx,b¦<

I think that old hard drive has seen better days.

It's so fucking weird because all my arduino sketches and sqjpegs and stuff are fine, wtf happened to my ML files?

any advice for recovering these files?

Can we do this? I no longer have the laptop I was using for development a few years ago, but I DO have the test builds that I published at the time. Is there a way to extract the source from one of those test builds?

nope. Theres about a million conditions that are not allowing filters on hdmi......ughhhh

either set the camera to 2.39, or set your timeline in resolve to 2.39 then scale to fill screen. The advantage of leaving the camera on 16:9 and cropping in post is you have the ability to reframe if a boom mic drops into your shot

Is this:

Code Select Expand

if (lv_dispsize != 1) return;

the line that prevents magic zoom from drawing on HDMI ?

Code Select Expand

Draw Magic Zoom overlay
*/
static void draw_zoom_overlay(int dirty)
{   
    if (zoom_overlay_size == 3) return; // fullscreen zoom done via digic
   
    //~ if (vram_width > 720) return;
    if (!lv) return;
    if (!get_global_draw()) return;
    //~ if (gui_menu_shown()) return;
    if (!bmp_is_on()) return;
    if (lv_dispsize != 1) return;
    //~ if (get_halfshutter_pressed() && clearscreen != 2) return;
    if (RECORDING_H264_STARTING) return;

Definitely the code tries to pick a small number of output sizes to simplify things.  It's not quite true that we assume all cams have the same resolution, HDMI being bigger is sometimes managed via BMP_H_MINUS and related constants, and bmp.h defines these differently for VxWorks cams (digic 3 and earlier?) compared to everything else.  E.g.:

Code Select Expand


#define BMP_HDMI_OFFSET ((-BMP_H_MINUS)*BMPPITCH + (-BMP_W_MINUS))


In theory I guess you could define those constants per cam, or per digic gen, but it's not a simple change and testing it may be hard (does qemu emulate HDMI out resolution?).

Code Select Expand

#define BMP_W_PLUS 840
#define BMP_W_MINUS -120
#define BMP_H_PLUS 510
#define BMP_H_MINUS -30

#define BMPPITCH 960
#define BMP_VRAM_SIZE (960*540)

#define BMP_HDMI_OFFSET ((-BMP_H_MINUS)*BMPPITCH + (-BMP_W_MINUS))


Is this correct!?  H minus and W minus are already negative integers, this = 28,290 ?wtf?

The funny thing is I realized last night that these should not be drawn at all when hdmi is attached. I discovered this when I tried to enable them with the hdmi monitor connected, and they did not draw. Turns out the only way they show up on external display is if you enable them first the connect the display. So I guess I found a bug.... I supposed the intended behavior is they should be disabled when hdmi is connected, but this doesn't happen until you cycle ML menu. So I guess I have a different question now:

Why are display filters not drawn on hdmi output? It seems the zebras are properly working and aligned. Focus peaking is misaligned, Is it too much overhead? Were they disable because no one wanted to sort out the alignment issue? Does the peaking code need to be revised to adapt to the different resolution of external monitor? Anyone who has some knowledge about this please share.

Hey guys, can someone point me toward the line(s) in the source where the position of overlays (pertaining to HDMI output) is coded? I want to work on getting proper alignment of focus peaking and zebras on an external monitor

Are you grading and delivering in a a true HDR environment?

PS: I suggest you boost exposure by 1-2 EVs in order to have your mid tones roughly where they should be. This is not a destructive amplification, so your highlights will be safe!

I'm not sure what you mean by "True HDR environment" The output to my grading monitor is 10bit SRGB The first delivery for film projects is a DCP with an LUT I made for our local cheapie movie cinema's projection system (I did tests there when we premiered "The Refractor" and Rec.709 was way too dark so I made the LUT for the final output when rendering to DCP)

Streaming uses same grade, just different resolution and not LUT on output.

I agree with the exposure boost. If I expose skintones at 70% in camera they are coming through about 1 stop under after import. After playing around some more tonight, I realized p3 D60 is the most neutral colorspace option. Rec.709 shifts the skintones toward magenta, and BMDFILM makes them so muddy it takes a ton of extra work to get them back.

Regarding white balance. If auto(AWB) is applied you´ll get whatever kelvin temperature underlying since we are not calculationg auto wb into the dng file. I´d suggest selecting any other wb but auto to get better control over wb.

I balance the camera manually for the approximate color temperature of the lights, then finetune in post with the vectorscope. I was just curious as to why every clip defaults to 7.42 tint in resolve. Maybe MLVapp is adding it, maybe it's harcoded in .MLV maybe it's just a resolve quirk. No biggie, just odd....

Hey guys, I'm back!

Way back in 2016 We used adobe camera raw via After Effects and Visionlog to develop our MLV files. Nowadays I am exporting CDNG's from MLVapp and dragging the folders directly into Resolve.

Can someone advise the correct settings for the "camera raw" settings in davinci?

It seems that if "Cinema DNG Default" is selected in the (decode) drop-down it defaults to using rec.709 for the color space and gamma

If I choose "clip" in the decode field I have the options to choose between Rec.709, P3 D60, or Blackmagic Design in the color space.

If I choose blackmagic d.esign the only gamma available is BMD Film. If I choose Rec.709 the available gamma options are: 2.4, 2.6, Rec.709, SRBG, and Linear

What settings are you guys using?

Also, why does the camera metadata always have the tint set to 7.42 regardless of camera settings?

Has anyone notice that MLV files ignores the gain settings in canon audio menu? I recorded some clips at a concert saturday night and adjusted the gain in the canon menu, my .h264 files have the correct volume, but the raw videos I shot are all distorted.

About the focus pixel maps:
Launch MLV App while connected to the Internet. When you open your first EOS-M clip, the program will ask you if you want to download a map for the selected clip or all the maps. Those will be downloaded automatically once you make your choice.

'

This is not working on multiple computers

"Update of focus pixel maps failed"