BTM_Pix

Don't worry, it will be quite an easy multiple choice one like this. Q. Assuming an ISO value of 800 and a shutter speed of 1/48th of a second, what is the correct aperture setting for the scene below ? f10 The other f10

The official cable pack finally showed up. The barrel connector adapter works fine with the cheap SmallRig Sony battery adapter that many people may have from the original Pocket and BMCC days. There are a myriad ways to mount the adapter to any sort of rig you have or even directly onto the 1/4" 20 mount on the top of the camera as I've done here. Tested the Dtap with a V mount battery and that is fine too for anyone looking for that type of solution. The only thing I would say is that I'm probably going to put some heat shrink on the cables as on my ones at least the cables aren't a particularly snug fit into the connector and I'm not sure how they would get on long term with repeated insertion and removal.

I'll give you an example of each of the three main MFT manufacturer's native lenses and three speed boosted ones from different manufacturers, listing the apertures at which they have repeats. NATIVE LENSES Panasonic 14mm f2.5 f11 f14 f16 f21 Sigma 30mm f1.4 f1.4 f1.7 f10 f11 f14 f15 Olympus 45mm f1.8 f10 f11 f14 f15 f16 f21 ADAPTED LENSES (using Metabones T Ultra 0.71x) Canon 50mm f1.8 f1.3 f1.7 f10 f11 f14 f15 Sigma 18-35mm ART f1.8 f1.3 f1.4 f1.7 f10 f11 Tamron SP 17-50mm f2.8 f10 f11 f14 f15 f16 The Metabones has the latest firmware and from the responses by the other two users in the thread, the same behaviour is also happening with Viltrox adapters. Obviously, none of these native lenses or adapted lens combinations shows the same issues when tested on either a "regular" MFT hybrid camera (Panasonic G7 and GX80) or my other MFT mount camera the JVC LS300. With regard to the steps to reproduce, just turn the aperture wheel one step at a time (or you can do it on the app as its the same behaviour) and you will see the points at which the indicated value does not change and these points will remain consistent in either direction. As f10 and f11 are two of the common points of repetition across all lenses, you should also these two byte arrays for each version of f10 and f11 being returned from UUID: B864E140-76A0-416A-BF30-5876504537D9 in any logs you capture in nRF Connect whilst doing this. f10 (0x) FF-06-00-00-00-02-80-02-26-35 (0x) FF-06-00-00-00-02-80-02-40-36 f11 (0x) FF-06-00-00-00-02-80-02-59-37 (0x) FF-06-00-00-00-02-80-02-5A-38 This shows that the parameter value itself is not a repetition (0x3526 and 0x3640 for f10 / 0x3759 and 385A for f11) but the interpretation of it is. So if you write those arrays to UUID: 5DD3465F-1AEE-4299-8493-D2ECA2F8E1BB you will see that you will also get two versions of f10 and f11 respectively.

As per the orginal post it is happening with native (both Panasonic and Sigma that I've tested) as well as adapted lenses. I'll be back from this job later this evening so I can have a look at an Olympus lens for completeness but I'm not expecting it to be any different. If you connect to the camera with something like nRF Connect and register for a callback on UUID: B864E140-76A0-416A-BF30-5876504537D9 and turn the aperture wheel (or use the app) you will see the values for parameter 2 of group 0 change on every increment and should then see the instances where the value has changed but the indicated f stop hasn't.

I'm going to go out on a limb and say that there aren't many topics on here about anything to do with RED because not many people on here own them. Oddly enough, I do though and have had an EPIC X for seven years and I'm not sure I follow when you say its got the same problem ? It reports those same Canon lenses just fine on its adapter and reflects the actual aperture values (rather than the 64 'send it and we'll let the lens work it out' routine) correctly for the same lenses, with no repeats. It also reports the aperture back correctly from the suitably equipped PL lenses I've got as well so its not an issue I have come across or can reproduce. The design of the product has an MFT mount integral to it though so it was obvious that they would use a selection of those lenses. What they shouldn't have done is say that those lenses are fully compatible because they patently aren't. That's got nothing to do with it being 'dirt cheap' or who they are selling it to. Anyhoo, for what it's worth, my Android remote app fixes the problem so that it will only send the values that each particular lens has a valid matching aperture for. So if a low rent whining prick like me can resolve it then hopefully the $400M corporation can do the same at some point.

What do you mean 'update every camera lens out there' ? They just have to profile them to make sure they go to where they should go to. Tell you what, how about they compromise and just profile the ones (80% of which it will affect) they use in their advertising for the camera ? I'm not being funny but if any other camera company had an issue where they had inaccurate aperture control like this (which isn't just a cosmetic issue either) there would be an absolute shitstorm on here but weirdly, as with a few other issues, BM somehow seem to get a pass. Anyway, thanks for those with the cameras that have chimed in to confirm it on their lenses and I suppose just view it as an FYI for everyone who hasn't yet got one.

Thanks for checking. I suppose its at the wide end of the aperture that its going to have to be borne in mind as there may be a bit more there that people won't discover - as with the nifty fifty - unless they go one step further than what it is reporting as the maximum aperture. So the rule of thumb is that when you think you've reached the maximum, turn it one more step. It a bit of a reverse Nigel Tufnel from Spinal Tap really as these go to -1 rather than 11.

Thanks These are the histograms from my "two" f1.3 settings on the nifty fifty and I can definitely see from the shift that they are two distinct settings on mine at least. I know what you mean but I'm not sure its ideal that depending on which direction you approach some particular f stops will decide whether you get the "real" setting or the one that doesn't do anything, particularly if you are exposing via an external light meter? And that even that inconsistency is in itself inconsistent depending on which lens you are using. In the case of my lens above, I had a little bit extra in hand when I went down to the "second" f1.3 that I wouldn't have been aware of if I'd not gone past the first one. It also has implications for anyone trying to match more than one camera as well in that you'd have to agree that both were on the same version of the f stop. It also causes sync issues with their own app where to add to the fun you can have one setting displayed on the app and another on the camera, which again has implications for anyone such as a gimbal manufacturer making a viable remote control for it. The root of the problem is that the camera doesn't profile the lens so the interpretation by the lens of the value that they use for the aperture ends up being a bit of a crap shoot depending on whether the lens actually has a physical setting that matches it.

I'm finding what might be described as "interesting" behaviour when changing aperture values. Aside from the unusually high degree of granularity (there are 66 different positions between f1.3 and f22 for example), I'm finding that there are a number of repeats within these positions. For example, there are two f1.3s, so when you have it on f1.3 then step up to the next value it is also f1.3. This is repeated at several other positions and is the same, for me at least, on both native MFT and adapted lenses. At some positions, there is no difference in exposure (so if you move from the "first" f11 to the "second" f11 it appears the same) but worryingly that is not always the case. On a Canon nifty fifty on a speedbooster for example there is a very clear exposure difference between the two f1.3 settings. The quirkiness of it having that many steps and some repeats is something I can live with if it was consistent between lenses and was only an indication foible in terms of the repeats but its neither of those things unfortunately. I have an understanding of why it is happening based on the BM protocol and messages I'm reading back from the camera over bluetooth but I have a limited range of lenses so obviously, it would be appreciated if any of you could check behaviour of a couple of lenses and see what happens with yours and I'd be particularly interested if anyone can try it with lenses with a wider aperture than f1.3 to see if there is a similar issue there.

As I say, they've recently updated it in the past few weeks to fix issues they had with Mojave so a lot of it will be related to those previous problems. I have not switched to Mojave so can't comment but I'm on High Sierra 10.13.5 and it works fine for me with the latest version installed. It even gives me a Touch Bar emulation at a cheaper price than upgrading my MBP With regard to price, it is a one off price for the regular version ($20-ish) and a subscription add on for the pro version which lets you use the iPad as a digitiser. I use it in a few different ways, depending on what I'm up to. In FCP-X I have the iPad Pro handling the interface and the MBP full screen as the picture monitor. For work, I will be editing pictures on the MBP and use the iPad Pro to view and control the FTP application so I can keep an eye on the transmission of the pictures to the agency without having to swap applications. As Duet works with any iOS device (and the one off payment covers you to use it on all the devices linked to your Apple account) then I tend to use an iPhone more than an iPad for that as it saves space and is an appropriate screen size for a smaller application. There are other similar products out there though so have a look around.

Oh that that where the only bug in that project. Have a look at Duet. I use mine with the Mountie clip system that attaches it to the side of the laptop screen but any old stand will do. They have recently fixed the issues they had with Mojave.

The original poster didn't come back with a resolution but I suspect this thread from DVXUser is the same person. Judging by that, the solution did seem to be sending it back to Panasonic for a repair (or replacement in his case as it was under warranty). There is an interesting post further down in that thread from someone saying that their one didn't AF unless it was actually recording so that might be worth a try to at least try and see if it makes a difference. http://www.dvxuser.com/V6/showthread.php?356676-12-35mm-2-8-NO-FOCUS-past-12mm

Just pondering whether if you attached something like this to the 1/4-20 mount on the top of the camera you could then have an adjustable way to mount some additional weight to the camera itself to try and balance it for the additional weight of the 18-35mm (Its about 140g difference looking at the specs of the lenses) without having to move it back too far ?

I'm not sure I follow what you mean about buying all the options? If you are talking about the different resolution options, then if you buy the €90 Multi Rez Stock Kit then you get all of them included. Or are you talking about the overall cost when you add the controller? As even with the more expensive option (the Arturia) its about €180, which is less than a fifth of the price of another option such as the BM Mini controller. Having said that, the BM Mini controller is a very, very nice looking piece of kit. I previously couldn't justify the cost of the available ones based on how much I did it but these and other lower cost solutions have given me pause for thought and I possibly will in the near future. I'm very much in favour of anything that offers a tactile interface to applications, so I use numerous different MIDI controllers for controlling DAWs and synths and even Lightroom via the LrControl plugin. And, of course, who can forget my very own custom real time Panasonic picture profile tweaker Maybe I should revive that for Resolve ! For keyboard shortcuts for Resolve and other applications like FCP-X, Logic and Lightroom I use silicon keyboard covers like these They are about £5 each on eBay and just lift on and off when you swap applications. I also have a generic one for when I'm working as it keeps the elements out of the keyboard. The other thing I've used for editing for years is the Contour ShuttleXpress. I used to use the original one but the more compact one is enough for what I need for jog/shuttle and marking in and out points etc. I'm not a colourist so I can't speak about it with any authority or insight whatsoever but I can definitely see where the wheels and trackballs would be a big boon, analogous as they are to the controls inside the software. If you want to dip a toe in then Tangent (who make a series of lower cost hardware controllers for Resolve) have an app that can turn an android or iOS tablet into a virtual version. The full price is £80 but they do a free version which you can use for an hour a day to see if its something that works for you. I wasn't actually aware of it before myself so I think I might have a go as well. Video about it here

With it being Bluetooth LE, I suspect this will be related to the F8n not allowing multiple client devices being registered for notification and/or write on the same service characteristic(s). However....whilst not a single button button option I think this will provide you with a solution.... If you go into the Ipad settings screen and tell it to forget the F8n then it will remove the bonding from the F8n which will then make it available to the iPod. Then when you want to swap back you would do the same on the Ipod to break the bond and make it available to the iPad. As I say, its not an instant single button solution but shouldn't take more than 10-15 seconds.

Nce find. If anyone is interested in a hardware controller for Resolve then Tachyon also have a 40% off sale running on their interface software to run with affordable MIDI controllers. The Arturia Beatstep version is ideal for keeping the footprint small and the Akai APC40 version has a ton of direct access controls. You have to source the controller yourself, the Arturia is roughly £75 and the Akai APC40 (which has to be the Mark I) is about £40 used. With the current sale on the software, the total solution is about £135 for the Arturia and £100 for the Akai. https://posttools.tachyon-consulting.com/davinci-resolve-controllers/beatstep-resolve-edition/ This is a run through of it and at 06:00 there is a very cool feature to control curves.

For the love of God, he needs to take the music off that video. Difficult to hear the lens noise he's talking about or any of his other observations when its drowned out by a soft porn soundtrack. That aside, I thought the Z6 did pretty well with the face tracking, especially with the 85mm adapted lens. However, it was definitely struggling and doing an overshoot with that lens when he was on the right hand side of the frame. It also seemed to struggle even with its native lens when he moved out of the frame completely and it had no face to track as, unlike the Sony, it was very inconsistent in then subsequently acquiring focus on the Leica/Billingham bag cabinet at the rear centre of the frame. Without knowing what all of his additional fine tune AF settings were set to (which are many with Nikon of course and can also include individual lens tuning), its difficult to call it a problem but the inconsistency is a bit concerning. As it stands though, the fast acquisition of focus on the face appearing from beneath the frame certainly makes the Z6 another solid choice for coverage of weightlifting.

I'm a bit confused about the apparent incredulity of Sony releasing an 8K camera sooner rather than later as well. We have already had this video on here before but here is an interview from the BBC with a Sony Senior Manager at Photokina where he clearly states that they already have it but will just decide the timing for the customer. And the little smirk at the end of the interview doesn't exactly hint at this 'correct timing' being several years away. (Ignore the hero frame, the link will start the video at the start of the interview. BTW If you haven't seen this video before it is worth rewinding it to about 4:06 to watch Canon's European Vice President being somewhat disarmed by the direct questioning of the BBC journalist)

They refer to as "Non-CPU Lens Data" and its found in Menu>SETUP This will let you profile the lens for the camera to understand for IBIS etc Obviously, you also have to be in Manual mode for the shutter release to work.

All that is, is a brief summary of the official Photokina announcement. https://news.panasonic.co.uk/panasonic-lumix-announces-development-of-its-first-full-frame-mirrorless-cameras/ Sorry but you'll have to forgive me a wry smile here. For someone who was saying this thread was going nowhere, I do have to applaud your contribution in taking it somewhere. Well, back in time by 2 months and 10 pages does count as taking it somewhere I guess

..

..

..

..

..