All Activity

Thanks

Welcome aboard! Ciao

yes, but apart from sunbursts, dynamic range I don't think is that useful under water, most shots I take I'm increasing contrast. Don't disagree there are certain situations where it will help. If you look at noise it seems to me the performance is closer than most people think. Here is one example comparing an EM-1 MkII with a Sony A7RV from DXO mark : You'll see the noise when the EM-1 is set to ISO200 is about the same as when the Sony is set ISO400. Effectively one stop better and shooting wide you may well want to have the Sony at 400 due to stopping down to f11-13, while the Olympus is happy at ISO200 at f8, but either way it's not a huge advantage. of course if you compare true ISO it's about a stop and half difference. The point is m43 can claw back quality by shooting at wider apertures and due to the smaller sensor they are less constrained by dome size. Here's a link to have a play with if you like: DXOMARKOlympus OM-D E-M1 Mark II vs Canon EOS R8 vs Sony A7R V |... The dynamic range curve is similar. In fact if you throw the Nikon Z8 or the Canon R8 into the pot they all very closely mimic the Sony curve. In fact DXO's most recent test results are from a camera released in 2023, it's like the curves are all so close there is little separate them and other shooting factors come into play like computational photography, AF, high frames/second etc. etc. to differentiate cameras today, making this sort of testing somewhat obsolete. Now I'm the first to admit these curves don't tell the whole story and certainly you shoot a bit higher ISO without noticeable penalty with full frame and there are other advantages for specific cases, but for general reef shooting and macro where you are shooting within a stop of base ISO it's close to a wash. I've linked in the past a shot taken on an OM-1 at ISO10,000 - it is surprisingly good. on the topic of large prints it seems to me we are talking A2 and above. If you look at physical prints in the big photo comps, I haven't looked lately but it seems they are mostly in A3 size range or the old 16x20.

Hello everyone I have been a lurker on WetPixel for years. I am mainly interested in video. I am very undecided between a cropped system and the enchanting sirens of full frame. Best regards

Pure manual triggers I believe rely upon the X-sync contacts within the shutter closing the circuit between the centre pin and the common edge contact, so to work they need the shutter to operate. E-Shutter needs the trigger to talk to the flash and establish communications so the sensor can trigger the flash. So a pure manual trigger doesn't tell the camera flash is even connected - this for example is how the Nauticam manual trigger can sync at 1/400 with the OM-1, the camera doesn't lock out the higher shutter speeds and the flash still fires regardless. Electronic shutter needs to co-ordinate with the sensor reading to fire the flash at the right time to fully illuminate the frame - on most camaeras unless they have very fast readout this means the sync speed for electronic shutter is lower. Out of interest why do you want to use e-shutter? Seems like it would be simpler to take advantage of the high mechanical sync speed in most circumstances?

Digi direct, DCW, Camera Pro among others have bricks and mortar stores, Digi has 4 in greater Sydney. What town are you in? If you come to the Go diving show ingreater Sydney there's quite a few stores still that you can visit. Apparently OM system is an exhibitor at Go Diving.

Bricks and mortar camera shops seem to have disappeared all over the place. I’ve lived in various major cities in the last few years and have seen them close the shutters and disappear. I guess online sales are largely to blame - and I have to own up to my share of guilt.

Sorry, Michi, I can’t really help you there. I doubt though that the trigger would be outpaced by the ability of the strobes to recharge.

Cheers - sounds good!

Christopher Frost is also worth viewing. Usefully he follows the same format for every review, and shows test charts separately for the centre and corners. If you open multiple browser windows, you can directly compare results for different lenses. However he doesn't measure field curvature - but then, who does?

Out of the curiosity - has anybody used GH7 with a silent/electronic shutter? Any ideas what is the max sync speed on this camera with the strobe trigger? As I do not seem to be able to find it anywhere.

Can you really Shoot in electronic shutter up to 1/400? I think it’s Limited in Electric to 1/200 (without HSS)?! With mechanical shutter it’s up to 1/400 (and with my Ikelite ds161, inon z330 And Marelux Apollo III and Nauticam trigger even Limited to 1/320…)?!

Hi Chip, thx! have you ever tried with electricic shutter to fire in serial mode? With the Backscatter strobe you have also a fast recycling one… Can the trigger / strobe keep up with a certain speed? I want to Use my new Marelux Apollo with my Sony a1 in serial Mode.

Hi Tim, thx! have you ever tried with electricic shutter to fire in serial mode? Can the trigger keep up with a certain speed? I want to Use my new Marelux Apollo with my Sony a1 in serial Mode.

Totally agree, unfortunately I don't have a local bricks & mortar camera store apart from a Harvey Norman (who are pretty clueless), don't even have a brick & mortar dive store either - can get a wetsuit at the surf store but that is about it.

I'm tending to use https://www.youtube.com/@DustinAbbottTWI/videos when I am looking for decent lens reviews - they are pretty thorough.

I look up best on-line prices then go straight to my local bricks and mortar store - Camera House in Geelong. They always match the best price if it's Australian stock and not some dodgy code discount. I reckon support your local store if you have one. It's the only place you can go to see some gear before buying.

Wide rectilinear shots is probably where FF has the most advantage.

Long time HW user. Great little boards.

I wanted to reply directly to this also, I am sorry it came across like I, or we, were dismissing the problem or putting it on you. That was not the intent. The reason I kept asking for the raw console errors is that I need them to debug this properly, and also to give Invision something specific if we need to submit it to them. A Copilot summary can be useful, but it is not enough on its own. Invision will need the actual error text, file name, line/function, browser, and the exact steps that trigger it. The error you sent is helpful because it gives us something real to trace. That said, the error appears to be coming from Invision's notification/checking script, not directly from the image uploader itself. So it may be related, or it may just be another JavaScript error happening on the same page. I do not want to claim either way until we know more. So I am not ignoring the issue, and I am not ruling out that something on the site is involved. I am also not ruling out that something local to your browser/profile could still be blocking part of the reply editor, since the same page is working for others. That could be cached site data, browser storage, an extension, a privacy/security setting, or something specific to that Edge profile. It is also possible that something is cached somewhere between the server and you. I am trying to separate what we know from what we do not know, so we can either fix it here or give Invision a proper report. I appreciate you sending the extra details. I know this has been aggravating, but the console output does help. Also, please remember that we all volunteer to run this site for free for you all. Time zones make things harder, and as the more technical admin I am fitting this around my normal work schedule, which is often 60 hours a week. Your patience is appreciated. It is being worked on, even if it cannot always move as quickly as either of us would like.

thanks.. good night ill research more..

[Violation] Forced reflow while executing JavaScript took 93ms [Violation] Forced reflow while executing JavaScript took 83ms root_front.js?v=4c29a2ba741785983349:258 Uncaught (in promise) TypeError: Cannot convert undefined or null to object at Object.assign (<anonymous>) at BaseControllerClone._updateTimestamp (root_front.js?v=4c29a2ba741785983349:258:449) at BaseControllerClone._doAjaxRequest (root_front.js?v=4c29a2ba741785983349:250:6) at BaseControllerClone._checkNotifications (root_front.js?v=4c29a2ba741785983349:249:6) updateTimestamp @ rootfront.js?v=4c29a2ba741785983349:258 doAjaxRequest @ rootfront.js?v=4c29a2ba741785983349:250 checkNotifications @ rootfront.js?v=4c29a2ba741785983349:249 setInterval setInterval @ rootfront.js?v=4c29a2ba741785983349:240 setup @ root_front.js?v=4c29a2ba741785983349:236 initialize @ root_front.js?v=4c29a2ba741785983349:233 initControllerOnElem @ root_framework.js?v=4c29a2ba741785983349:156 initializeControllers @ root_framework.js?v=4c29a2ba741785983349:126 init @ root_framework.js?v=4c29a2ba741785983349:122 (anonymous) @ root_library.js?v=4c29a2ba741785983349:70 e @ root_library.js?v=4c29a2ba741785983349:2 t @ root_library.js?v=4c29a2ba741785983349:2 setTimeout (anonymous) @ root_library.js?v=4c29a2ba741785983349:2 c @ root_library.js?v=4c29a2ba741785983349:2 fireWith @ root_library.js?v=4c29a2ba741785983349:2 fire @ root_library.js?v=4c29a2ba741785983349:2 c @ root_library.js?v=4c29a2ba741785983349:2 fireWith @ root_library.js?v=4c29a2ba741785983349:2 ready @ root_library.js?v=4c29a2ba741785983349:2 P @ root_library.js?v=4c29a2ba741785983349:2

When I click in this box after 10 or 15 sec this message main-mfr2DxeI.js?v=4c29a2ba741785983349:130 [Violation] 'setTimeout' handler took 71ms [Violation] Forced reflow while executing JavaScript took 57ms [NEW] Explain Console errors by using Copilot in Edge: click to explain an error. Learn moreDon't show again root_front.js?v=4c29a2ba741785983349:258 Uncaught (in promise) TypeError: Cannot convert undefined or null to object at Object.assign (<anonymous>) at BaseControllerClone._updateTimestamp (root_front.js?v=4c29a2ba741785983349:258:449) at BaseControllerClone._doAjaxRequest (root_front.js?v=4c29a2ba741785983349:250:6) at BaseControllerClone._checkNotifications (root_front.js?v=4c29a2ba741785983349:249:6) updateTimestamp @ rootfront.js?v=4c29a2ba741785983349:258 doAjaxRequest @ rootfront.js?v=4c29a2ba741785983349:250 checkNotifications @ rootfront.js?v=4c29a2ba741785983349:249 setInterval setInterval @ rootfront.js?v=4c29a2ba741785983349:240 setup @ root_front.js?v=4c29a2ba741785983349:236 initialize @ root_front.js?v=4c29a2ba741785983349:233 initControllerOnElem @ root_framework.js?v=4c29a2ba741785983349:156 initializeControllers @ root_framework.js?v=4c29a2ba741785983349:126 init @ root_framework.js?v=4c29a2ba741785983349:122 (anonymous) @ root_library.js?v=4c29a2ba741785983349:70 e @ root_library.js?v=4c29a2ba741785983349:2 t @ root_library.js?v=4c29a2ba741785983349:2 setTimeout (anonymous) @ root_library.js?v=4c29a2ba741785983349:2 c @ root_library.js?v=4c29a2ba741785983349:2 fireWith @ root_library.js?v=4c29a2ba741785983349:2 fire @ root_library.js?v=4c29a2ba741785983349:2 c @ root_library.js?v=4c29a2ba741785983349:2 fireWith @ root_library.js?v=4c29a2ba741785983349:2 ready @ root_library.js?v=4c29a2ba741785983349:2 P @ root_library.js?v=4c29a2ba741785983349:2 Good night... Need to go

Thanks. The Copilot summary is useful as a clue, but we need the raw browser console output, not Copilot’s interpretation of it. The reason is that Copilot may be summarizing, guessing, or connecting errors that are not actually the cause. To investigate this properly — and especially if we need to send it to Invision — we need the exact original error text, file name, and line number shown by Edge. When you have time tomorrow, please do this: 1. Open the page where reply upload/paste fails. 2. Press F12. 3. Go to the Console tab. 4. Clear the console. 5. Click into the reply editor. 6. Try to paste/upload an image. 7. Copy/paste the actual red console errors here, or send a screenshot. What we know so far is useful: - New topics/new messages work. - Editing an existing post/message works. - The initial reply composer fails on your affected machines. That points us toward the reply editor initialization, but we need the raw console error to confirm where it is failing.

Same reaction it doesn't work It's late I need to go to bed now. Wakup in 5 hour to go to work. I paste the console output to Copilot... (I know copilot is copilot ;) ) the result is what I gave you.