Author Topic: crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView  (Read 368995 times)

timbytheriver

  • Member
  • ***
  • Posts: 176
Re: crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView
« Reply #1975 on: March 12, 2019, 10:29:51 AM »
Have updated the 16:9 graphic to show 2K(QHD).
5D3 1.2.3 
5D2 2.1.2

leozan

  • New to the forum
  • *
  • Posts: 10
Re: crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView
« Reply #1976 on: March 20, 2019, 06:57:11 PM »
ANY HOPE to see later long time update of :
ML Nightly Build and ML crop_rec_4k  for 5D3 (123)  ?
...with Latest Lua updates + fixes 2019-03-20 ?

no way to do alone , bad....sorry.
thanks

Walter Schulz

  • Hero Member
  • *****
  • Posts: 6578
Re: crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView
« Reply #1977 on: March 20, 2019, 07:10:01 PM »
Please tell us in detail which of the problems you are struggling with requires a merge of crop_rec_4k and lua_fix because it cannot be handled by either version alone?

Ceterum censeo experimental build page esse delendam!
Photogs and videographers: Assist in proof reading upcoming in-camera help!. Your input is wanted and needed!

jimiz

  • New to the forum
  • *
  • Posts: 44
Re: crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView
« Reply #1978 on: March 20, 2019, 07:25:47 PM »
Please tell us in detail which of the problems you are struggling with requires a merge of crop_rec_4k and lua_fix because it cannot be handled by either version alone?

Ceterum censeo experimental build page esse delendam!

 e98cf27: api_test.lua: test for all items from the Overlay menu
 (to make sure they can be safely turned on or off with menu.set)
 TODO: also check their submenu options

 4c6cde3: Waveform: fix crash when enabled outside ML menu
 (e.g. from Lua, https://www.magiclantern.fm/forum/index.php?topic=23673)
 Issue: initialization on first use + race condition.

 abdd1e2: api_test.lua: on EOS M, the INFO button may get us out of LiveView
 (fixes API test about ML overlay status)

 085b79c: EOS M: fixed display_idle() outside LiveView

 4aa1ba0: Zoom on HalfShutter: allow triggering when AF is enabled
 (only works when AF is not actually triggered by half-shutter, *, AF-ON etc)

 df8d088: Zoom tweaks: updated for recent models
 - option to disable the "x1" zoom (i.e. to go directly into x5/x10)
 - compatibility with touch-screen models (still rough)
 - api_test.lua updated (need to disable these tweaks in order to pass the zoom test)

 3a5bade: api_test.lua: skip checking for "Play mode actions"
 (feature not present on EOS M; requires serious cleanup)

 400d73f: EOS M: enabled rack focus and focus stacking
 (they appear to work, at least with regular EF lenses)

 0060b26: editor.lua: disabled debugging features
 (FIXME: they don't seem to work)

 252a4b7: EOS M, 100D: fix Q/SET short press outside ML menu
 (ETTR trigger and many others)

 3f5aa76: editor.lua: use the MENU key as primary method for triggering the menu
 (Q is still used, but it's not working on all models)

 b213791: EOS M: align long-press symbols for delete and Q/SET
 (minor)

 20628f1: EOS M, 100D: fix long-press symbol remaining visible after Q/SET
 https://www.magiclantern.fm/forum/index.php?topic=14828.msg210032#msg210032

 f40dacf: Arrow key shortcuts: minor cleanups
 - removed bogus ARROW_MODE_TOGGLE_KEY definition on EOS M
 - removed unused definitions on 650D and 1100D
 - require ARROW_MODE_TOGGLE_KEY if and only if FEATURE_ARROW_SHORTCUTS is defined

 9e54731: EOS M: fix PlayMain_handler stub
 7000D, 650D, 100D: comments for PlayMain_handler / PlayMovieGuideApp_handler

 7b7a9a3: Color scheme: fix conflict with fast zebras

 684ff6b: Menu: fix typo regarding FEATURE_JUNKIE_MENU
 (7469c34)

 91c84fd: exit_play_qr_menu_mode: wait until mode switch is finished
 (fixes GUI mode switching test in api_test.lua on EOS M, maybe others)

 7256e17: EOS M: fix GUIMODE_ML_MENU to allow operation outside LiveView
 (required for passing the Lua menu API tests outside LV)


sorry can't help you.
I don't know how update api_test.lua inside ML and recompile.
but seem most fox for EOS M I think....not 5d3, or meaby not...bhoooooo?!
the rest seem dead..

leozan

  • New to the forum
  • *
  • Posts: 10
Re: crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView
« Reply #1979 on: March 20, 2019, 07:27:54 PM »
Thanks , no problem , WAS only a question, no afraid.... ;)

jimiz

  • New to the forum
  • *
  • Posts: 44
Re: crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView
« Reply #1980 on: March 20, 2019, 07:29:33 PM »
if you like try something more "new" for 5d3 ,  look here...take time...  https://bitbucket.org/Dannephoto/magic-lantern/downloads/

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 12048
  • 5D Mark Free
Re: crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView
« Reply #1981 on: March 20, 2019, 08:54:53 PM »
Quoting dmilligan:

How about a 1000% refund of the purchase price of ML? I will pay that to you personally, let me know where to send the check.

FYI - 99% of my spare time (i.e. when I'm not at work and not with my family) already goes to ML. Lately I've been focusing on other areas, such as new ports, or just researching and documenting Canon internals. I don't record video, and the pictures I've been taking for myself are sitting in the waiting queue for years (guess why). Honestly, I don't know how to do better. OK, let's say I could focus more on the video side, or on some particular camera model, but that will be at the expense of neglecting other areas of ML (which unfortunately have their own share of trolls). FYI, there are areas in ML that did not get their fair "round robin" time slice (i.e. my attention) for years.

If you think the progress is too slow, the only way to speed it up is to join the development efforts. Trolling, like you are doing here, only serves to drive me away from this topic (can't speak for others, but for me it's not funny to read such things after an intensive debugging session, or after a full day at work). It's not the first time you are complaining for what you've got for free, so please take it as a warning. Be sure to check this guide before replying.

Yeah, I could have fixed another bug in ML instead of writing this.

Quote
Ceterum censeo experimental build page esse delendam!

OK, what to do with it? Let users build from source? Just include everything in mainline without testing? Other ideas?

Anyone who thinks they can do a better job is welcome to take over maintaining ML (release management, keeping stuff up to date, making sure things work on all supported models and so on), as it's already taking 110% of my time.

nikfreak

  • Developer
  • Hero Member
  • *****
  • Posts: 1114
Re: crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView
« Reply #1982 on: March 20, 2019, 10:05:58 PM »
... Other ideas?

Anyone who thinks they can do a better job is welcome to take over maintaining ML (release management, keeping stuff up to date, making sure things work on all supported models and so on), as it's already taking 110% of my time.

while we are offtopic and I am at 109% myself (just family and work not counting ML) I may just add my 2cents for those supported models you mentioned earlier as a proud owner of unsupported models (got it?)  ;D :P
As harsh as it may sound I would announce some kind of "code freeze":

  • Merge as much as possible of those open PRs (don't forget mine)
  • announce dropping support for Digic IV and older cameras (yes those oldie goldies like 7D, 5D2, 50D, 60D, 1x00D)
  • release a "final" build before dropping support for those cameras
  • Do some code cleanup afterwards (yes cleanup code so anyone wanting support for those cameras has to use a code freezed branch on btbucket / github or whatever). Just point them with links over there. Anyone's free to pick up work for it.
  • focus on digic 5/6/7/8 and onwards do exactly the same for digic V announcing to drop support for it but keep 5D3 because it has been built to survive. It's THE DIGIC V camera to keep / pick up.
  • Afterwards focus on digic 6/7/8

Nothing will be lost but official support will be simply discontinued to free up resources for future work on new cameras. I know it's a hard decision. You mention yourself being not able to handle more cameras yourself. I guess dust spreaded all over your cameras (i know what I am talking about) but you need to get rid off 'em in terms of developing / testing ML on 'em. Just use them as a photographer but don't develop / test them. I know it's hard. You have been spending thousands of countless hours with them but I think ML is nothing w/o you as the lead developer and if you don't make the first DIGIC 6 / 7 / 8 port no one else seems to be capable to do it but everyone is expecting it atm. Once accomplishing the first working digic 6/7/8 port others will be able to follow your work. I don't think "someone" will suddenly appear and do the first DIGIC 6 / 7 / 8 port for ML. You have been asking others to pick up work for it for so long already. Maybe later "someone" could appear but I personally think that chances are much higher that most users will just switch away and use their smartphones or whatever tool to take their stills and 8k videos.



At least think about it. Something like the 5D4 would fit everyone's need for the next years.
Now let's return back to topic please  :P
70D.112 & 100D.101

nikfreak

  • Developer
  • Hero Member
  • *****
  • Posts: 1114
Re: crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView
« Reply #1983 on: March 20, 2019, 10:28:51 PM »
forgot to mention: On April 1st please, as usual  ;D
70D.112 & 100D.101

leozan

  • New to the forum
  • *
  • Posts: 10
Re: crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView
« Reply #1984 on: March 22, 2019, 03:31:46 PM »
 :D well ... a little life on the topic ...   ;)