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

Pages: [1]
1
Camera-specific discussion / Canon 80D vs 5D IV
« on: October 04, 2018, 08:05:12 PM »
80D has a DIGIC 6, the 5D IV has a DIGIC 6+, i do not know if either has been shown to be multi-core, but then why should that matter.

I believe i saw that typically the '+' DIGICs were just faster clock speeds, maybe something diff about them, don't know.

The 5DIV has only a sinlge DIGIC, & the 80D.

It appears that the 5DIV is progressing well in its port.

So why does not some/most/all of the 80D port (besides addresses) not benefit from the 5DIV effort and success ?

Just wondering since I have used ML on my old orig M model and do see lovely benefits, ML is nice and would love to see some of its benefits on my 80D as we all would.

Happy porting and much success !!

2
Camera-specific discussion / Shutter Count from Canon 80D - How ?
« on: October 26, 2017, 01:33:29 AM »
Generally ML can retrieve the shutter count from all ported cams, and is view-able via ML on cam.

Currently the ONLY method to get the 80D shutter/mirror count is to PAY $$ ($6 for winblows, $3.81 for mac - 2 diff apps), neither APT astronomy app, nor gphoto2 (linux) show it either - both free.  And no the jpeg does not show the shutter count either using a jpeg meta editor.

It appears ONLY via a usb conn and knowing specifically where the data is located, and dumping it and interpreting it correctly, is the only way to get this data.

So has anyone seen via a usb conn, some way or the place that the shutter count is stored, (maybe someone decompiling the rom dump, while trying to port ML, might have seen something like this or some hint to where ??)


TIA !

3
But like many Canon cams, the SD writer is likely a very limiting factor, at least for raw video.

The M3 is certainly a step forward, but honestly, the ML team should wait (maybe?) for the obvious very needed f/w update from Canon for the M3, it has several important issues for some, and until fixed many/some are NOT buying it.

That said, the M3 is fine for most now, just not as good as a f/w fix and ML could make it, and unlike  other makes has a nice touch screen - once you have one, hard to NOT want one for any/all cams IMO !!

4
Camera-specific discussion / Re: Canon EOS M
« on: April 16, 2015, 01:03:00 PM »
Are the pink dots/patterns the Phase Detect &/or the Contrast Detect sensor locations - anyone really know ?  They certainly do not cover as much of sensor (total coverage area) as I would have thought.

5
magiclantern-Nightly.2015Jan15.EOSM202

Saw the posts about CBR and this must be a build issue. I certainly was seeing up to 235mbps bit rates for 2kHD using a TragicLantern load a while back. I recently did some video w/ latest ML, set to 2.5CBR, and the resulting vids were peaking at 114mbps rates, some at same setting only show around 99mbps.

Just performed a 2.9CBR vid out the window and it shows - peaks to 155mbps, mostly 135mbps peaks. I then upped it to 3.0CBR and got - crash/stop - 4-5 secs only - peak around 160mps!

I loaded in the 'last' TL build - tragiclantern-v31337.TRAGIC.2014Dec19.EOSM202 - at 3.5CBR it crashed - <10secs only (saw a peak of 168mbps), went down to 3.2CBR and got peaks of 133mpbs.

Put in my old TL load (used for audio remote trigger) which I believe was where I saw 235mbps peaks and - only saw 150mbps peaks - and 3.5CBR crashed after 10 secs, whereas 3.2 worked fine - about 133mbps.

So either I am GREATLY MISremembering getting peaks of 235mbps (saw when SD card was new) OR since my card has been useds LOTS, a reformat and so forth may show those higher results - which I think some ppl have seen when attempting RAW video.

So, 133mbps = 133/8 is ~16mBps, FAR from the 30mBps M SD writer speed capability (30mBps * 8 = 240mbps) of M (once again I think we think that is the speed limit of the writer ?).

So something has changed in the year or so I saw 235mbps peak, and the only change was/is the fairly heavy use of my SD card and NO reformat or conditioning !! (Sandisk  UHS-II 80mBps read, 60mBps write or some such)

So maybe reformat/condition your fast SD card before doing critical video - test and see !!

On the other hand, I do not think using the Canon encoder algorithm, that a 200mbps recording is any usefully better than is a 133mbps or maybe lower.

Most of the above testing was done in 'crop' mode, both TL & ML so a higher bit rate and crop mode will give you the 'BESTEST' Canon video, maybe as good as RAW via ML/TL or better !! 

PS: But honestly Canon 1080p 2kHD video is so soft that it barely looks better than other makes 720p !!  This really is a shortcoming of Canon at the moment - IMO ! And 4kHD blows it away even via an iPhone 4kHD !!

Good Luck ALL !!

6
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: July 05, 2014, 02:11:20 AM »
I had a 4.1 Gb h.264 file come out of my eos-m as a .dat file today?
I've read something about this coming from going over 4 gb, or something I may not have had set right?
Anyway, can that file be retrieved, salvaged, or is it toast?
Thanks.

Have you simply tried to change the file type to .MOV, .mov or .mp4 ?  A diff file extension/type means NOTHING to the content (many times) just the 'packaging' of the contents!  Do not erase until you check a few things!

ex. - .3gp is just .mp4/H.264, aac audio, etc contents in a file wrapper.

Good Luck!

7
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: July 04, 2014, 10:35:28 AM »
It increases noise. It is true, I have tested it. Crop mode reduces aliasing and moire. because there is no lineskipping.

I do not see increased noise, actually next to none, but then I use higher bit rates, usually 2.0x CBR. 1 example of this was taking a still of the same shot of same scene of crop vid, the video was much better in shadows (details & low noise) and less geometric distortion.

I do hope the 'next' M (M3? or Pro model) will address the fairly poor H.264 encoder used by Canon (or Texas Instruments - their DSP (DIGIC) suppliers - I assume f/w encoders as well?)

The M3 could be a BMPCC fighter but it has to have much more attention to the video, if not 4k at least state of the art H.264 encoding with higher bit rates and true raw &/or HDMI output & 4:4:2 as well ?

8
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: May 11, 2014, 11:33:22 AM »
Anyone know if any effort to enable 'Remote Shooting' via USB & EOS Util. via ML/TL ??

Its incredible that Canon gave us no way to remote control shooting w/ the M !?

If I have missed this capability via ML/TL &/or EOS Utility, plz let me know.

Thx!!

9
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: May 11, 2014, 08:59:50 AM »
Class 6 card is too slow now for magic lantern? My recording stops itself after a couple seconds depends how complicated scene is.

You need to specify more info - are you using a CBR of 1.0, for example or RAW video or .....

10
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 06, 2014, 07:26:52 AM »
I am now trying the new ML, Jan 5, for the M 2.02 and it makes the shutterbug come back on my cam. When I use any of the TL versions, I do not have the shutterbug (after I do my reformat workaround that I explained a few times so far on here).

IIRC, the person porting TL to ML was mostly concerned with 'picture taking' changes to TL, NOT video. So this is of importance to him, I think !!  I am sure it is not easy getting all the code deltas correct, assuming his tools are not so great, shame there is not a 'versioning' code repository to keep each code 'effort/changes' independent by 1% & others.

I do get the shutterbug occasionally, but I seem to get out of it via changing modes (this may be a general freeze problem not the shutterbug), but another one (shutterbug I believe - less often), I have to take out battery. Very annoying as there is NO prediction when this can occur.

Good Luck.

11
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 06, 2014, 12:13:26 AM »
You only need a 45 or 60 mB/s card because as you stated the writer is only capable of 40mB/s.

On the other hand that h264 video was probably in megabits not megabytes and hence it was 17.5 megabytes per second.

Yep, thats why I put the 'mb' in lower case! Me knows the diff!! Me use to be an Electrical Engineer. Me are used to bits/nibbles/bytes/words/double words/etc. Me be cognizant of the diff. Me prefers 'MB or mb' rather than 'mB or mb', for the emphasis, as well that is what is shown on ML screens - 'MB/s'.

The statement of compressed video is that it will NEVER likely be able to be written at the speed of raw or M SD writer, as the H.264 encoding does take time and the encoder chip is likely processing limited, or I would see a higher bps, wouldn't I?

Also, I can set CBR to higher than 2.9x (4x is where I quit) with my card, just the output NEVER gets higher than about 140mb/s (saw peaks of 150+mb/s), so VERY likely processor/encoder/bus speed limited.

Also, the ultimate speed of compressed seems to a degree dependent on ISO, maybe - limited use/testing of this.

Thanks anyhow.

PS: It is going to be interesting when UHS-II (240MB/s writes) SD writers are in cams, and also when H.265 encoders are in cams, then the Digic engines (dual/triple Digics?) will have some REAL work to do & will be so capable !! 

BTW, FYI: Canon works (has work done by?) with Texas Instruments (TI) on their Digic processors - Nikon has FujiFilm do their h/w work & firmware work!

12
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 05, 2014, 11:24:04 PM »
I can shoot Raw ONLY? when using the 12/31 TL !!

I was able to get Raw in both crop and non crop modes !  1280x434 non, 1280x720 crop modes !!
(must put Canon video in 2kHD 24fps mode for crop to work BTW!)

So I believe NO TL or ML builds beyond the 2013/12/31 TL build works, I have tried a couple newer ML as well as older TL builds !!

Note: non crop is writing at about 27 MB/s, whereas crop is writing at about 35 MB/s !  (this means likely the fastest/highest resolution possible for M SD writer !!)  Sad!  :-[

This is with a Sandisk Extreme Plus UHS-I 32gb card - 60/80 MB/s.

So I A$$ume this means not ALL fixes/etc are in the ML stream yet or those for video at least !

Thanks for the help!

PS: Now the question is, is it worth the huge trouble processing raw 720p when the world wants 2kHD or even 4kHD !?  Especially considering the ability to get high bit rate compressed H.264, would anyone notice the diff for a huge amount of situations? Maybe only for high ISO situs?

13
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 05, 2014, 05:02:11 AM »
I played around with the 12/31 build for a while. While continuous raw recording at 720p worked pretty consistently in TL, with this build, I couldn't get a raw recording more than a few seconds.

So you think maybe not all the 'fixes' in the last TL has been migrated into ML builds?

What card did you use for 720p in TL?

TIA!

14
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 05, 2014, 04:51:55 AM »
140mb/s is 140/8 = 17.5mB/s. Raw video requires a lot of speed.

Its compressed video, maybe slowed down by ACTUAL processing - who would imagine?

So what card?  M only has a 40mBps SD writer, my card is a 60mBps card, so How much is required ? Plz answer the question, not show math skills !! ;)

15
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 04, 2014, 07:17:41 AM »

I have a 60/80 MBps SDHC UHS-I card, I can get up to 140mbps compressed video with this card - CBR 2.9x.

BUT, I can NOT get any more than the buffer's worth of RAW video.

I have tried both TL (Nov 30 & Dec 26 zips) and ML (Jan 02 zip) builds.

What exact settings, loaded modules are needed, and ANY other advice to help solve this - PLEASE !!

OR does RAW not work at all yet ?

TIA!

Pages: [1]