Menu

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

#76
worked for me. Thx Walter
#77
Yeah we discuss about Digic 6/7/8 like 5D4, EOS R, EOS RP and such. There's need for some serious amount of $$ to let a1ex hold these real hardware in his hands. Not only QEMU stuff. Then there's the bills - family needs to be satisfied, not just by words. There's all these sleepless nights a1ex spends for ML project. That's not for free. It was for the last years. But in my opinion it's time for some funding to keep ML ongoing. ML is not about discussing for the next years about Digic 4 and 5. As harsh as it may sound I still vote for a code freeze and drop support for these old cameras when time comes. You a1ex need all of your free time for the new stuff - not for supporting the old cameras. I even can't believe how you try to spend your free time to reflash those peoples' broken cameras. That's not your job.
Set up that Patreon page or announce some other donation phase. Then wait some weeks for the income. Is it hundreds, thousands, maybe ten thousands or even hundred thousand or maybe more???

Afterwards decide if the income meets your requirements.

Oh btw and don't forget about Walter Schulz. He deserves that medal of honor.
#78
set up that Patreon page @a1ex. Just do it!

Quote from: a1ex on April 06, 2019, 06:19:55 PM
..may demotivate other developers, and that's exactly what I want to avoid. Of course, me being unable to integrate their contributions in a timely manner... is not going to motivate them either...

Don't think about others. As I said earlier. It's you, your famous name and you doing 99,9% of all reverse enginering at the moment. Think about it like this. If a Patreon page can pay the bills and motivate you to do more for ML then the end result for ML could be better support in Digic 6/7/8 etc. That again will lead to more traffic to the community site and again to more followers and again to more reputation and that again will motivate new developers to join the community.

A win-win situation for all.
#79
Oh btw regarding Android. people just make 'nuff money only by cherry-picking kernel commits and releasing a kernel and additionaly paid kernel app to manage it. Ever heard about Francisco Franco? Check the amount of installations:

https://play.google.com/store/apps/details?id=com.franco.kernel&hl=de
#80
Let's sum it up. If you ever do a D6+ port on real hardware I promise to do another one too (read: I don't give an ETA)
#81
maybe this one???
Quote from: nikfreak on July 20, 2017, 12:29:56 PM
If all goes wrong you can use Canon sensors together with a1ex's qemu work and a raspbi and call it A1EXIOM  :P
#82
okay okay let's use the unbricking service but make it a converting service for existing cameras: replace sdcard / CF card with flash / UFS storage. Some EOSM / 5D3 with ulrafast 512GB or 1TB flash storage would be nice.
#83
In my opinion we should invest into those SONY IMX sensors used in smartphones and team up to do what Google does but use AI (read: a1ex intelligence not artificial intelligence  :D ;D :D). Let's put a dozen of those sensors into a small body and chime in a snapdragon cpu use Android as a base, do some RE on Pixel devices and let's forget about apertus, canon, nikon and whomever and make our own camera. Google will win ofc because they know better and prove that single lens setup beats all those triple / quadrouple camera setups with Google AI but hey we can place 2nd after Google, right?
everyone's after a GCAM port on his smartphone. Why not announce an "A1ex app" trying to bring revolutionary features like dualiso from ML to smartphones etc..?? Millions would buy it later in Play Store. Lots of people would support only the idea - that announcement.
a1ex just your name would bring you enough $$ to do whatever you want to do as a full time job if you would announce something like above. Don't be shy. No risk no fun and thousands of people would spend a whole lot of money onto any kickstarter project you would anounce. I am not talking about an unbricking service for cameras. You got THAT famous name and are freaky enough to spend another thousands sleepless nights to do whatever magic you have in your mind.

This community alone has enough people willing to help in anything you decide to do.
#84

  • something qemu related  like Liveview / Movie
  • Eeko processing (dualiso, noise, blending ...)
  • sd_uhs
  • unifying of crop_rec / lua / 70D / 100D and other branches
  • maybe some fake news like nikfreak has been banned or we can do 8k 8bit recording on 1300D and such ;D
#85
forgot to mention: On April 1st please, as usual  ;D
#86
Quote from: a1ex on March 20, 2019, 08:54:53 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
#87
Camera-specific Development / Re: Canon 70D
March 09, 2019, 12:45:49 PM
DPAF is stubborn. I guess it has something to do with https://twitter.com/autoexec_bin/status/1038866055278538753
#88
Camera-specific Development / Re: Canon 100D / SL1
January 13, 2019, 09:16:09 PM
I bet you got a dozen modules loaded, stuff like raw_twk.mo and such  :P
#89
Camera-specific Development / Re: Canon 100D / SL1
January 13, 2019, 09:37:03 AM
@OlRivrRat please try another sdcard...
#91
Canon PowerShot G1 X Mark III

:D
#92
No twitter either over here:

7D Mark II
EOS M3

#93
Camera-specific Development / Re: Canon 80D
January 05, 2019, 04:42:02 PM
Quote from: whoreable on January 05, 2019, 11:18:01 AM
Lets start the GoFundMe and someone surely will take the challenge...


Quote from: g3gg0
magic lantern: 1Magic9991E1eWbGvrsx186GovYCXFbppY, server expenses: [email protected]
ONLY donate for things we have done, not for things you expect!

Here's the official forum site and the place where developers (new and old) can connect and talk. You need patience. "Someday" "someone" will announce ML for 80D or 5d Mark IV or any other unsupported cam. But that will happen here and not on external funding sites
#94
This proves again I'm no videographer and not using any related builds / features  :o
#95
could fit into this PR by "greying it out" for not supported cams (I still vote for hiding as discussed in PR):

https://bitbucket.org/hudson/magic-lantern/pull-requests/730/menu-proper-handling-of-raw-jpg-h264/diff

One could also think about adding mlv_snd options as a submenu into "Movie" tab
#96
Quote from: Walter Schulz on January 03, 2019, 04:03:01 PM

Is it possible to rename Debug into Utils (avoiding creating another tab/tab icon) and use an "Debug options ..." or "Advanced settings ..." menu item to make all debug entries visible?

+1 for avoiding to add another tab. Name the existing one Utils / Tools and use a "Debug options ..." submenu. Maybe make a debug module which adds that "Debug options ..." submenu
#97
Quote from: a1ex on November 28, 2018, 10:50:56 AM
...

- ISO optimizations to maximize dynamic range (still working on them)
- full-resolution silent pictures without exposure time restrictions:
   - with burst options (e.g. start/end trigger with half-shutter; currently doable, to some extent, from mlv_lite)
   - auto-selection of best images (currently done for 1080p LiveView frames)
   - in-camera blending to get long exposures or higher dynamic range (possibly fully- or semi-automatic)

these are enough and exactly what I was thinking of when hearing about Google's Night Sight. Go google for examples. I'm amazed.

C'mon give it to me  ;D
No, don't say to achieve it in post on my PC.
#98
fps_timer_a_orig
fps_timer_b_orig
#99
Unsure if it could help but you might try to define  timer A+B to it's orig value. Maybe my customisations interfere somehow.
#100
Camera is rather old but entry level. Porting ML onto it should be straight forward once you've already done a port. I several times was thinking about doing EOS 2000D port but would never invest or buy that cam on my own. It's identical to the EOS 1300D. Even the sdcard is still crippled and will only do 20MB/s (forget raw video!!!)  but it has 24Mpx sensor which got my interest (seems to be on par with 750D). So would be useful for stills photography.