BTM_Pix

I don't remember Canon being particularly keen on a trusted journalist from the BBC getting a grip of them when they launched the EOS-R !

I suppose that technically you should report that to Canon as a bug 🙂

By the by but giving out advance copies of the firmware to YouTube "influencers" to make videos of them testing it who didn't lift a leg to test or raise any objection to this issue in the first place is not a good look for Canon.

DEVELOPMENT UPDATE AFX has five user selectable focus transition modes. When the transition mode is set to Off, no transition is applied and the AFX snaps immediately to the new focus point. When the mode is set to 1,2 or 3 then an increasing preset length of transition is applied from the current focus point to the new focus point. The final mode is called Natural and applies a transition that is based upon the distance between the current and new focus points meaning that the greater the distance the longer the transition. Focus transition mode is available in both AF-S and AF-C modes.

Cripple Hammer Live Cam when Canon read about people using workarounds for their cunning plan.

Shhhh.... I'm very much happy to be the Stuart Sutcliffe/Pete Best of this saga when you all get sued for inciting people to break their cameras 😉

It sounds like they've broken it in a very creative way then ! I think this update was for external control of the cameras by the ATEM Mini ? So it sounds like there might be a conflict there. They've acknowledged it publicly at least but I don't know what "ASAP" means in BM terms but I'm guessing it won't be too long in coming.

It certainly helps with the diagnosis if not the issue ! It appears that Blackmagic have broken Bluetooth in 6.9.5 and are doing a fix. If they had made changes then I'd sort out a firmware update but they've flat out broken it so the solution is to roll back or wait on them unfortunately.

So you don't mind having to format your cards in a PC, jamming a screw into the microswitch of the battery compartment, making a sacrificial recording while ejecting the battery and reconstructing the files on a PC later but you draw the line at switching the wifi on ? 😉 Only kidding. The entire process of getting around this is currently impractical but if it ultimately ends up with Canon stonewalling the issue and not fixing it with firmware then my point was that there is a method there to restore your settings if the only solution ends up being the data clearing internal battery reset process. Call it doomsday prepping if you will. Although, for what its worth, if it does prove necessary then I can use the same principle to do this with a small hardware box that plugs into the USB port and does it that way so at least we can take the wifi/smartphone step off the list.

There's no getting round the fact that the internal battery life is limited as well as unpredictable and so you are already into some sort of external solution for that. Obviously the ND situation will also need attending to, which will of course be per lens if they have different thread sizes or even if they have the same size you will likely still need it to be per lens if you are doing fast lens swaps. Or you could use a matte box which as you are already into some sort of rigged solution for the power would be a way to go. With audio you are down to one XLR channel with phantom but you can use an adapter to utilise the 3.5mm jack input for dynamic or non phantom condensers. So with all that you are losing the immediacy that you have with the C100 mkII which may not be such a big issue for the sit down interviews but will be for your run and gun stuff. The bigger elephant in the room though is the screen and having no EVF. It is next to useless outdoors and if it swivelled then that might mitigate it but it doesn't and this also makes it a pain for lower angle shooting too. This means that to work as you are now as a replacement for the C100 mkII then you are going to need to budget financially and form factor wise for some sort of external monitoring solution be that a monitor or EVF. If you don't mind doing all of that and ending up with it rigged (which you could leave it permanently like that if you wanted of course) then you'll be rewarded with a huge bang for the buck in terms of image quality. To keep your current way of working with the C100 mkII but get access to BM RAW then I think a used Ursa Mini Pro would be a more seamless transition but, of course, even used its still a considerable amount more than the Pocket cameras.

Yes, it has all the flexibility that you need in terms of routing inputs to channels and setting individual levels to do that. The 3.5mm jack is stereo so you can choose either channel to route to Channel 2 or a mono mix of the both.

Late.

Whilst the hope is that Canon will fix this properly, the probe app (which we made after the temperature monitoring one) can be used to restore the majority of user preferences, not a big deal to get it to chain them into one big faux preset to send back to the camera.

They are there in the SDK but not everything always works on all of their cameras so I'll have a quick poke at it and see what happens. We've built a custom PBC based rig for a customer who wants to do stop frame with their P4K to get around the stills function not being supported. To say its a sledgehammer to crack a nut solution would be an understatement !

You could likely do it on the one card and it would just lose the last recording on that one but if you try it with two first to just make sure it doesn't fuck the entire file table on the card.

Yes, thats how we would envisage it working. We potentially have a mechanism to swap between them too so you could flip between regular six and custom six live. The handheld controller that is included with the AFX gives more potential for easier control of things like levels due to the thumbstick and the controller will be supported in the next PBC firmware update for PBC irrespective of if you have an AFX.

Its what I would call "expected but annoying behaviour". There is a quirk with the HFR setting from the camera in that it doesn't provide frame rate it in its initial status until it you toggle it on the camera. As there is no specific function in the spec to indicate it is in HFR mode, we have to do it with a workaround. When we boot, the camera doesn't mention if it is in HFR mode and as we use the incoming frame rate value to do the workaround (to make sure you get the same ones back when you toggle it from the PBC) this is an issue. So what you need to do with the HFR then is to toggle it on the camera after the PBC is connected and then from that point on it will toggle properly from the PBC. Its a bit of a pain but its the only way to get the HFR to toggle remotely. There will be firmware updates for the PBC as they are needed to support new add ons such as the AFX and the mystery "other" AF adapter so other controls can be added. The audio functions are quite well supported in the API actually so adding a Phantom toggle, input type selector and levels wouldn't be an issue. If I don't run out of time before the AFX release then I'll certainly add them to that firmware update. The custom screen is under consideration anyway but might not make it into that one.

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.

Whoah..... Who had "It was the Japanese government" on their "Canon would never do this to us" bingo card ? Although I have to say that such a cartel may well have been behind the "Why the fuck do these manufacturers not put mic inputs on their compact cameras?" mystery.

That moment when you are appreciating the recognition but then you, of course, remember that in no way whatsoever did you ever advocate this at all yourself but merely suggested that other people might advocate this but not you. It was definitely other people m'lud 😉

"Silver haired click weasel" (C) Theoria Apophasis

It depends on which is the least amount of face to lose, having to unlock it and admit they'd locked it or canning it altogether to avoid having to admit that. You'd think they'd just go with the numbers, take it on the chin, just fix it and carry on selling it but you just never know. Although having said that its not even entirely certain whether they would actually get much backlash. People will let a lot of things slide to get the features a fully unrestricted version of this camera would give them and of course, in the modern world, as long as they tough out the first few days of any backlash then by and large everyone forgets anyway. Everything that I targeted from the API in the testing app was based on that premise as both @Andrew Reid and I knew it was unlikely to be strictly temperature based but the subsequent chase down was necessary to prove it as definitively as its likely going to be proven outside of Canon. I still don't think that will stop everyone talking about the temperatures though 😉 Canon muddied those waters with their original limit list when describing a specific temperature which set off all sorts of tangents with different anecdotal reports from differing environments. All of that was a red herring but even "60 jpegs in a fridge" doesn't quell the "I used it to shoot 300 RAW files in 12fps burst mode whilst pouring molten lava on it and it didn't overheat" reports. So I think it will go on for a while, particularly in the vacuum that Canon have left for it to do so by not making any sort of comment whatsoever. I'm starting to think those people who have experienced all these outlying run times and unhindered performance with their R5s might actually have faulty ones 🙂

So they've replaced the "Cripple Hammer" with the "Temporary Incapacitating Hammer" ? Its a possibility. Earlier on in this saga when the denial was high about the R5 I said we'd reached the "Pining for the fjords" stage of the Dead Parrot Sketch. I might have to revise that now and say we might only be at the "He's not dead...he's just stunned" stage 🙂

About having to manually put all your settings in... Imagine if someone had already written an app that uses Canon's API for testing this overheating and that could also reset all those settings in one go when you haven't used the battery reset workaround that I certainly never advocated using?

That is certainly in line with the sort of thing I'm not talking about. It's likely a smaller battery in the R5 so it would likely require a smaller version of what I'm sure we can all agree that I'm absolutely not talking about.