Leaderboard

Canon engineers reading this thread.

A1ex is a legend I swear. That guy should replace the current CEO at canon

Hello everyone, I'm Dilara and I'm student. I really like take amazing photos that is my hobi. I found this great forum and want to meet some good people,who know some tricks to take amazing macrophotography and take sunset and etc. Thanks in advance!

The thought of spending $4,000 on a camera and having to deal with all this nonsense, just to get the features Canon markets on the box...it's appalling. What's even more tragic is the people still making excuses. Canon could have delivered the goods and made everyone happy but they botched it.

On Friday, I received a message from the lead developer at Magic Lantern. An interesting theory was being put forward by one of their open source contributors, which he believed could defeat the so-called overheat timer on the Canon EOS R5. Initially I was skeptical as to whether it would work! Mainly because the initial real-world tests on my own EOS R5 did not reset the timer. But then, a break-through. Magic Lantern just became Magic Screw! Read the full blog post here: https://www.eoshd.com/news/canon-eos-r5-so-called-overheat-timer-defeated-by-a-single-screw-in-battery-door/

Thanks for the files. Tried two separate automated MP4 repair programs/scripts, both of which support reading the headers/metdata from the "good" file and attempt to graft that data over those missing elements in the bad file, specifically the missing moov atom in the corrupt file. No joy so far. Oddly when I examine the "good" file the moov atom is actually at the beginning of the file - I expected it to be at the end since that's what's missing from the corrupt file. It might be that Canon relocates the moov atom to the front after a successful recording end. It's usually placed at the beginning of files to facilitate better streaming as the file is being downloaded. Or it might be that IsoBuster didn't recover the file correctly. I'll keep digging. Here's the Atom data from the good file, obtained from AtomicParsley <filename> -T Atom ftyp @ 0 of size: 28, ends @ 28 Atom moov @ 28 of size: 262116, ends @ 262144 Atom uuid=85c0b687-820f-11e0-8111-f4ce462b6a48 @ 36 of size: 65750, ends @ 65786 Atom udta @ 65786 of size: 2056, ends @ 67842 Atom manu @ 65794 of size: 20, ends @ 65814 ~ Atom modl @ 65814 of size: 38, ends @ 65852 ~ Atom urat @ 65852 of size: 16, ends @ 65868 ~ Atom free @ 65868 of size: 1974, ends @ 67842 Atom mvhd @ 67842 of size: 108, ends @ 67950 Atom trak @ 67950 of size: 16328, ends @ 84278 Atom tkhd @ 67958 of size: 92, ends @ 68050 Atom edts @ 68050 of size: 36, ends @ 68086 Atom elst @ 68058 of size: 28, ends @ 68086 Atom mdia @ 68086 of size: 16192, ends @ 84278 Atom mdhd @ 68094 of size: 32, ends @ 68126 Atom hdlr @ 68126 of size: 33, ends @ 68159 Atom minf @ 68159 of size: 16119, ends @ 84278 Atom vmhd @ 68167 of size: 20, ends @ 68187 Atom dinf @ 68187 of size: 36, ends @ 68223 Atom dref @ 68195 of size: 28, ends @ 68223 Atom stbl @ 68223 of size: 16055, ends @ 84278 Atom stsd @ 68231 of size: 311, ends @ 68542 Atom hvc1 @ 68247 of size: 295, ends @ 68542 ~ Atom stts @ 68542 of size: 24, ends @ 68566 Atom stss @ 68566 of size: 296, ends @ 68862 Atom ctts @ 68862 of size: 4472, ends @ 73334 Atom stsc @ 73334 of size: 28, ends @ 73362 Atom stsz @ 73362 of size: 3364, ends @ 76726 Atom co64 @ 76726 of size: 6704, ends @ 83430 Atom sdtp @ 83430 of size: 848, ends @ 84278 Atom trak @ 84278 of size: 8276, ends @ 92554 Atom tkhd @ 84286 of size: 92, ends @ 84378 Atom edts @ 84378 of size: 36, ends @ 84414 Atom elst @ 84386 of size: 28, ends @ 84414 Atom mdia @ 84414 of size: 8140, ends @ 92554 Atom mdhd @ 84422 of size: 32, ends @ 84454 Atom hdlr @ 84454 of size: 33, ends @ 84487 Atom minf @ 84487 of size: 8067, ends @ 92554 Atom smhd @ 84495 of size: 16, ends @ 84511 Atom dinf @ 84511 of size: 36, ends @ 84547 Atom dref @ 84519 of size: 28, ends @ 84547 Atom stbl @ 84547 of size: 8007, ends @ 92554 Atom stsd @ 84555 of size: 103, ends @ 84658 Atom mp4a @ 84571 of size: 87, ends @ 84658 Atom esds @ 84607 of size: 51, ends @ 84658 Atom stts @ 84658 of size: 24, ends @ 84682 Atom stsc @ 84682 of size: 748, ends @ 85430 Atom stsz @ 85430 of size: 6548, ends @ 91978 Atom co64 @ 91978 of size: 576, ends @ 92554 Atom trak @ 92554 of size: 947, ends @ 93501 Atom tkhd @ 92562 of size: 92, ends @ 92654 Atom mdia @ 92654 of size: 847, ends @ 93501 Atom mdhd @ 92662 of size: 32, ends @ 92694 Atom hdlr @ 92694 of size: 33, ends @ 92727 Atom minf @ 92727 of size: 774, ends @ 93501 Atom nmhd @ 92735 of size: 12, ends @ 92747 Atom dinf @ 92747 of size: 36, ends @ 92783 Atom dref @ 92755 of size: 28, ends @ 92783 Atom stbl @ 92783 of size: 718, ends @ 93501 Atom stsd @ 92791 of size: 50, ends @ 92841 Atom tmcd @ 92807 of size: 34, ends @ 92841 Atom stts @ 92841 of size: 24, ends @ 92865 Atom stsc @ 92865 of size: 40, ends @ 92905 Atom stsz @ 92905 of size: 20, ends @ 92925 Atom co64 @ 92925 of size: 576, ends @ 93501 Atom free @ 93501 of size: 168643, ends @ 262144 Atom mdat @ 262144 of size: 730194240 (^), ends @ 0 (^)denotes a 64-bit atom length ~ denotes an unknown atom ------------------------------------------------------ Total size: 730456384 bytes; 66 atoms total. AtomicParsley version: 0.9.0 (utf16) Media data: 730194240 bytes; 262144 bytes all other atoms (0.036% atom overhead). Total free atom space: 170617 bytes; 0.023% waste. Padding available: 1974 bytes. ------------------------------------------------------

Ah Sony are just another bunch of opportunists really, using the suffering of a rival to drum up some more sales - I'm no great fan of the A7S III. I think this is a watershed moment, and I hope it encourages people to spend their money differently. Maybe buy more from Sigma, who are family owned. Let's put business ethics in the spotlight. Let's see what really goes on behind closed doors and what they try to hide from their customers.

Might give IsoBuster a try ... I have recovered a ton of stuff when the FAT was completely corrupted ... mainly from DVD/CDs It will dump any information it finds and is usually able to tell the type of file from the structure.

I looked into what it might take to recover the lost/missing video file after a battery pull. I reproduced the R5 hack scenario on my Canon RP by recording a minute of video on a freshly-formatted SD card and then pulling the battery while the door-sensor was inhibited. Like what Andrew discovered on his R5 the file is not corrupt but actually completely missing, both when attempting to play the video on the camera and when mounting the card on a computer. I then tried running SanDisk's RescuePro Deluxe and after scanning the entire card it didn't find the video. Here's what I think is happening. Obviously Canon has to write the video data to the card while recording, since it has no other place to retain it beyond the internal SDRAM buffer capacity. You can see easy evidence of this by watching the card access light continuously flicker. The strategy Canon is likely employing is to defer the writing of the official FAT metadata until the recording is orderly stopped. This would include elements such as the FAT directory entry, which anchors the file, and possibly also the linked FAT allocation tables. This would explain why RescuePro couldn't find the file, since there isn't enough or any recognizable metadata to reconstruct the orphaned data sectors associated with the video. Canon is either caching that information in memory until the file is closed or is writing it somewhere on the card that isn't linked to the official FAT structures. The benefit of this strategy, assuming they're using it, is that it prevents any potential filesystem-level corruption from incomplete metadata updates, since none of the official metadata structures are updated to link to the file until it's closed. The downside of this strategy is that it orphans all the data from the file and makes recovery more complicated. There are a few strategies in devising a recovery app for this situation. The first would be to reverse-engineer exactly what if any metadata Canon is writing during the recording and to where. If that orphaned metadata is in the same format as actual FAT structures then it should be relatively straightforward to create a placeholder directory entry and link to it. If the format of that metadata is proprietary to Canon then the process of reverse-engineering its structure would be much more complex. This would all be done by using a sector editor and block-based search tools to compare a freshly-formatted card to one which has a missing video after recording. And lots of effort. I was actually an embedded firmware storage engineer for most of my professional career so this would be in my wheelhouse. I'll see how much demand there might be for this before I spent any serious amount of time on it. In the meantime I'll also try some other recovery apps to see if they have better luck...in case SanDisk's utility is not doing the job it's supposed to. I recommend others try the same so we don't unnecessarily reinvent the wheel 🙂

If you can bang that sledgehammer 24 times a second, then you'll essentially bring cDNG back to the camera. That really would be nuts!

Som years ago it came out that a famous car company has manipulated the control system of their cars, so when measuring how pollutive the exhaust is, the software adjusted the engine management, so very low values were registered. The company did advertise the cars with these impossible to archive values, so actually were misleading, cheating the customers. Investigations showed that also other car manufacturers made use of this ingenious trick… Since these firms have paid billions as penalty, have “reengineered” the control software, have recalled millions of cars, the responsible ones have faced serious sanctions and most of the CEO-s are not seeeous anymore. Most people find all this rightful. I really hope that in some of the most important countries, markets for Canon, where customers are not willing to be defrauded and the legal system is grown up to such situations, Canon is going to be punished for this absurd dishonesty. It will also be an important message for the whole high-tech/IT industry, where shiny marketing brochures often promise values, never archivable in real world.

there's probably a million of them out there. My other two russian lenses are modded i think, to get infinity. One the helicoid is worn out and there's a real loose spot in the middle the other dosn't quite reach infinity. i have 3 different brands i think, been trying them out but i think i'm done with russians, not real interested int the helioses , not a fan of the swirly bokeh thing. Might just save up for a modern next like a voightlander 17.5 mm or a proper tripod. Yesterday on sunset i noticed the moon is back but 60km an hour winds straight of bass straight aren't really exciting me to go outside.

Here is a VFX heavy short film I shot on the Samsung NX1 years ago, finally decided to finish it and get it online so here it is! The last scene is the canon T3i all lenses used are the rokinon 24mm f1.4 and Canon 50mm f1.4 Watching in 4k is strongly recommended as YouTube loves compressing things

Designed for super8 cameras....the smallest 2x scope out there. And believe it or not? This thing is superior to the much-drooled-over baby hypergonar. Significantly so. I own two baby kowa 2x's, and one baby hypergonar....all of them are in near-new condition. The hypergonar was practically "New Old Stock" shape. Anyway, here's a couple pics of it mounted tucked inside a Rapido FVD8a, along with a screengrab of fellas on the porch talking. Also some pics from around the net of what the baby kowa looks like by itself (since mine are mounted in rapido FMJ, dont feel like removing right now) Shot not lit or anything...just stuck a camera there and recorded a bit; GH5 was on Natural profile, in 4:3 "4k anamorphic" mode (3328x2496), ISO 800. Taking lens is a Canon nFD 50mm f1.8, mounted on a 0.71x Zhongyi speedbooster. Aperture was set at 2.8 (on the lens). Yup...the baby Kowa is able to cover 50mm at around APS-C/S35, with no real vignetting/portholing on corners/sides. The sides have been cropped to achieve 2.35, but the cropped portions were fully visible. Of course...such coverage requires careful choice of taking lens, with a small front element that is very far forward so kowa rear lens can be very close. The flares are soft, understated, and beautiful...pinkish purple. I'll upload a test clip showing that off as soon as I get a moment today.

"Math Class" on Baidu now has extensive infrared thermometer readings of the camera's mainboard with the back off, showing they correspond closely to the temperature reported in the EXIF data and don't rise above 64C. His next finding is that if you remove the internal battery it resets the so-called overheating limitations. So who is telling the truth now, Canon? You can view the most recent findings here by the user "Math Class" (Google translated) Read the full article on EOSHD: https://www.eoshd.com/8k/removing-internal-battery-resets-eos-r5-overheat-timer-are-canons-pants-now-completely-down/

Just ran a short clip on my 1DXIII pulled the battery and extracted the DAT file to my desktop. ISObuster attempted to convert it to mpg but the resulting file was unplayable in VLC, unrecognized by FF:Works and Davinci Resolve Studio. The conversion in ISObuster was at 2.1MB/s ... so even if it were readable the length of time to convert would be untenable.

Samsung had (atleast) one paper on the organic sensor. They did test it, on paper (maybe in a few versions). I read somewhere that the Panasonic organic camera is quite power hungry, so that may be one of the reasons (among a host if other reasons), for it's slow development. I am expecting the announcement in a few weeks, and the GH6 to release by year end or very early 2021. The GH6 just needs to do 6k at 60fps. And 4k at 120fps. If the quality if the 6k of 4k is good enough, you could easily upres with great results to 8k. Maybe even good 12k. They need to work on the autofocus and the dynamic range. Everything else is pretty respectable. And I suspect rhs S5 will have mu h improved autofocus. They should just install Laser and ToF for autofocus and it will be damn close to PDAF.

The R5 Is not a camera, it looks like a smartphone where you are working around custom ROMs LMAO It is anyway unbelievable as no one in Canon still drop 2 lines... and meanwhile the camera is on the market. How that could be possible?

Nice and sharp! I have one on the way but the shape isn't as good as yours. These are really nice gems!

There is no way a GH6 is not coming. There are too many lenses and m43 users around, and they are perfectly happy with their cameras. They do not even have to split the sales with Olympus now. I could guess that 2019-2020 was the years of S cameras, 2021 will be the year of m43, in no way they are going to release another full frame camera any time soon (I mean, after the S5 will be officially announced and everything) and that would be...at least weird, if not straight negative. Already too many S1 owners feel a little "betrayed". I am expecting a GH6 announcement in early 2021, and probably a release soon after. GH5 and the rest are good enough for another 8-10 months, then I will be expecting a slow (normal maybe) release of 2-3 years. Maybe just 2 or 3 models are enough for m43. I am one of those that believe that 8K is too soon, I wouldn't say no to 5K or 6K for re-framing/downscaling/stabilizing purposes, just to be safe for the next few years.

Good call @docmoore. Just downloaded IsoBuster and it found the .mp4. It wont let me attempt to extract it without buying a license. I'll search out a few other free/open-source solutions first before biting the bullet on the purchase. Here's a screenshot of the recovery:

If I owned an ARRI M18 I'd be bragging about using it in every IG post I make!

That's actually not true, if you upload in 4K youtube uses a different compression method for 1080p as well (VP9 vs H264) making it look much better.

Interesting point. I'll see if I can give it a go. First I need to work on a YouTube video showing it going for 1 hour in 8K. That should shut some people up.

On topic please people.

IMO I bag you pardon, maybe it would be better to involve some more time to really investigate where all of this one and thousands similar cases are proved to be pure sad true? If you have a will, I can provide it to you, but not here to further contaminate thread already polluted with superficial news level. I think, It's surely not at all about someone's favorite side (dirty and immoral ones are everywhere the same) - which you introduced with something that has to be a provocative joke and default fact - but about favorite and really independent state of mind. And of course, my big apologize to you and all others - it is always my dilemma weather to answer to something I feel as superficial provocations that sometimes arise at inappropriate place. Maybe just only to remind all of us (with me as so sadly often first-place-candidate!) and add suggestion at called-out level of picture-to-picture answer

I can see Foneh Thornrup frantically conjuring up a video where he somehow finds all the solutions and saves the day for all R5 owners, of which there are 126 internationally.

So there we have it. Proven without doubt Canon lied. Over at Canon fan boy HQ, dpreview, it's thing of beauty to watch the fan boys react to this news. The mental gymnastics required to defend Canon in light of this are really quite something.

https://lists.bcn.mythic-beasts.com/pipermail/bitlist/2008-October/000400.html

Someone else did it with a dummy AC battery as well:

It looks like, hacking is even simpler with a battery grip: https://www.youtube.com/watch?v=b-qeqNY2Nog

If you have two cards, it might be worth testing recording clips on the first one until you get close to the limit then inserting the second and doing the battery pull while its recording to that one. If it resets the clock if its shut down in a disorderly way while recording as has been observed then you'll only have lost that recording and not your real ones from the first card. Ifit turns out that this sacrficial recording on the second card only needs to be for 30 seconds or whatever then that might be a viable practical workaround. On a £4K camera.

Being able to save the clip is the critical next step but definitely looks/sounds more like a timer than true communication and limitations from a thermometer. Since we know the internals do heat up to 65C/150F, it'll be interesting to see who pushes this to the limit and the resulting damage (if there is any) after prolonged use. Perhaps with a timer exploit + proper thermal management via hardware mod, you'd actually have the functional camera Canon should have delivered in the first place.

It's worth another look. Quite a few variables and ways to do it. I haven't had the time try everything to be honest. The guy on YouTube has tried pulling the battery during a recording, and got 5 mins remaining. I also got 5 minutes remaining, but stopped the recording first. I thought at this point, if the timer is in RAM then it should go up to 20 mins in 8K not 5. Then I went out and had an ice cream with the girlfriend. So tomorrow maybe I should put more effort in!?

Perhaps with the delay of the Summer Olympics to July 2021 gave some breathing room for Panasonic to re-evaluate the capabilities. When they launched the S camera’s the official company line was “Panasonic is on track for 8K by 2020”. I assumed we would have seen it in a FF S series camera, but with the release of the S5 and the past 24MP S1H release it hasn’t come to pass. The spirit of the GH MFT cameras has always been “the first with 4K...the first with 4K 60p...”. Or in more broad terms to push the limits. However, we have see a gigantic leap in FF technology. We have 8K, we have 4K120p, all offered in 10-bit 420 or better, with excellent rolling shutter performance. At this point I would rather see the first internal ND solution in a mirrorless camera than 8K from a MFT sensor. I would rather see a very solid 6K60p and 4K120p. I would rather have internal RAW or ProRes HQ straight from the camera. Give us dual gain ISO from GH5S with IBIS. Give us some more absolutely unique 1.7 prime zooms like the 10-25 f/1.7 A 25-50 f/1.7 would pair nicely indeed and give us a native mount lens with AF that would compete with the classic speedbooster Sigma 18-35 and 50-100 f/1.8 setups. Besides, we have all the other focal lengths and aperture combinations already covered in the extensive MFT lens ecosystem. People that complain about these big and heavy MFT lenses don’t need yet another 12-35 f2.8 standard zoom! All of those features above actually improve the shooting experience with the camera. 6K is a nice middle ground, offering excellent 4K delivery and makes a “8K” anamorphic headline grabber still possible, while also offering a high resolution HFR not seen in any other mirrorless camera. Besides, I could shoot 6K60p and use a superscaler from BM Resolve or Topaz and essential get a 8K60p video and very few people would be the wiser. All the new “hybrid” cameras aren’t really hybrids at all. The R5/R6 are photo first cameras. They shit the bed for video. The Sony A7SIII is an excellent video mirrorless camera but its 12MP sensor hampers it for mixed photo work. Besides, I think Blackmagic is more of a threat they now have a S35 12K sensor shooting at 60p! Imagine something similar in a new pocket 6K camera with modular mount...ouch! The A7IV will be a true hybrid but will probably max out at 4K60p video and still have a 24MP sensor, which is well within the competing range for 20MP+ MFT sensors for photo work. And they don’t even have to use a 4:3 sensor if that don’t want to. JVC has proved that (although for photo I really like the 4:3 aspect ratio vs 3:2 a lot)! Anyway, long rambling post.

@Anaconda_ @newfoundmass YT is pretty much a brick wall when it comes to quality. You can give it higher quality files, but the quality bump is almost negligible. I haven't done exhaustive testing because it's been covered pretty well in this thread (look for the posts by Bryan Worsley): https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=85016

I can't remember if I already posted this, but we shot this with mostly S1. Couldn't believe the quality of the image. Truly amazing.

At least you don’t have to explain to your wife that you are about to spend thousands and thousands of dollars on audio equipment in this current economic environment. Its good but not great. It tends to be slightly off, much better when you use the zoom function and peaking enabled but we can’t do that when live recording ;-(

Apart from the artificial crippling, the consensus is the camera doesn’t actually overheat? What voodoo is in there that the S1H doesn’t have? (which needs a huge vent). Thing is, if Canon didn’t do this I would of been a customer of 2 bodies and a bunch of RF lenses. Plus I would of likely picked up an RF cine cam in the future. Just doesn’t make much business sense to me.