OK, got the new 4.0 firmware installed and things seem to have improved with the crosshatching issue with one exception.
First, here's my testing methodology (empirical as it is). YMMV
1) For Prores, load file into Quicktime player. Turn looping on, start player and then scale player from very small to very large. Previously it would be simple to see the crosshatching pattern when you scaled through smaller multiples of the source resolution, such as 1/16, 1/8 and 1/4.
2) Then load file into your NLE of choice (in my case FCPX) and scale to various resolutions, zoom way in, play the file, etc. All empirical, but in previous firmware it was obvious to see a regular pattern when investigating this way.
First I wanted to see if the 4.6k on a 4.6k timeline crosshatching issue was fixed. Unfortunately it's not, but fortunately the drx workaround from BM USA (Veronica) still works. This first test is of Raw lossless 4.6k (full sensor) on a 4.6k timeline. Here's a zip file of the original sequence:
https://www.dropbox.com/s/xwr1nqenrfiv9p0/A002_08161324_C001%20Raw%20lossless%204point6k%20on%20a%204point6k%20timeline.zip?dl=0Dropbox transcoded prores of the original sequence with no drx applied:
https://www.dropbox.com/s/wu4ak5yqy8wyilg/prores%204point6k%20on%204point6k%20timeline%20no%20drx%2001158780.mov?dl=0Dropbox transcoded prores of the original sequence with the drx workaround applied:
https://www.dropbox.com/s/6ql9os8nwiv4fcp/prores%204point6k%20on%204point6k%20timeline%20with%20drx%2001158780.mov?dl=0Screen capture of transcoded prores output of above file, rendered to 4.6k on 4.6k timeline WITHOUT the drx fix from BM USA and then viewed in the quicktime player and scaled down to a 1/8 multiple of the original file. I can clearly see the artifacts of the crosshatching here.
https://www.dropbox.com/s/y6y6p317hkypc9i/screenshot%204point6k%20on%204point6k%20timeline%20no%20drx%20-%20scaled%20in%20quicktime.jpg?dl=0Screen capture of transcoded prores output of above file, rendered to 4.6k on 4.6k timeline WITH the drx fix from BM USA and then viewed in the quicktime player and scaled down to a 1/8 multiple of the original file. I cannot see any artifacts of the crosshatching here.
https://www.dropbox.com/s/8ut0y0d0wabql4z/screenshot%204point6k%20on%204point6k%20timeline%20with%20drx%20-%20scaled%20in%20quicktime.jpg?dl=0Note that I get exactly the same results (with artifacts as above) if I shoot in the new Prores 4.6k format. Here's a copy of the Prores 4.6k files Straight Out Of Camera (SOOC):
https://www.dropbox.com/s/hngnlatzkb4x4cf/Prores%204point6k%20SOOC%20A002_08161326_C004.mov?dl=0Load that into the Quicktime player (or any player) and scale it down to a smaller multiple and the crosshatching/screen artifact will appear.
----------------
The second test is of Prores422 UHD full sensor SOOC. This seems to be fixed!
Here's the file... You can load this and try rescaling it and you won't get the artifact.
https://www.dropbox.com/s/2189896i6nus1ei/Prores%20UHD%20SOOC%20A002_08161326_C005.mov?dl=0Same thing with full sensor HD. Also no weirdness that I can see.
https://www.dropbox.com/s/eeg0m1jmdfeggfh/Prores%20HD%20SOOC%20A002_08161326_C006.mov?dl=0I have not tried all the other new formats, nor have I tried windowed sensor. Will keep testing, but for now it looks like 4.6k on a 4.6k timeline is the main issue, and for me I'm ok with it using the drx workaround.
The biggest major bug I've seen is that if you're in the menus and initiate a recording without leaving menu mode, there'll be a few seconds of black-screen latency and then the recording will initiate. But the file will be corrupted. Either it needs to be fixed so that we can initiate recordings correctly without latency and corruption from menu mode, or we should be required to exit menu mode to start recording. I've posted a bug report about that one.
I'll keep testing, but I suggest that y'all do also and we'll compare notes.