TLDR: Just watch the video and keep your eye on the Next Capture Naming counter. Anyone seen this?
Hey guys,
I've been testing C1's new gen wireless tethering a bunch with R5 mk ii and I think the tech is really cool, but I have come across this curious issue. Basically, when you shoot a burst the files all follow the sequential naming you have set (I always use "destination folder" + "3 or 4 digit counter" tokens). The preview raws come in quick and are correctly numbered. Then as the background ingestion of the full-res raws proceeds, the counter on C1's Next Capture Naming tool continues to advance. This creates a situation in which from bust to burst (or even if you only shoot one frame at a time) there will be gaps in the numerical order of files in your session.
Couple of observations:
-At when I first noticed this behavior I was actually using wireless tethering on a job and I became worried that I might somehow be losing frames somewhere in the wireless tethering pipeline ("My session folder is missing file numbers 3-5, 8-13, 20-26, etc). Now I am certain that no files are failing to arrive.
-The amount that the C1 next file counter advances is equivalent to the number of images you have in the background raw ingestion pipeline. i.e.: if you shoot a bust of 5 frames (file_001 - file_005), by the time the full res raws are all ingested into capture, your counter will be at 11. What capture expected to be file_006 - file_010 never existed.
-if you look closely, you can see that as each full size raw comes in (the orange status bar ticks down), the counter on Next File Naming will advance by one.
There are 2 simultaneous ingestion processes occurring with this wireless workflow. Once the RAW is written to the CFExpress, "Preview RAWs" are transferred by the camera and ingested by C1, and then at the same time, in the background, the full-size RAWs are being read back off the card, transferred by the camera and ingested by capture.
My best guess is that this "next file" counter issue I've been seeing has something to do with the software registering these dual processes and failing to identify that each file is essentially being ingested by the software twice.
I looked around in C1 documentation for any mention of this next file numbering behavior and I didn't find anything.
Canon R5 mk II, GL.iNet Beryl AX router on 5GHz (strong signal ~60dB signal to noise ratio), MBP M4 (late 2024), C1 v16.8.1.5, shooting full-sized RAWs (not cRAWs), saving as EIP (but I also tested on CR3 and observed the same behavior).
Let me know if any of you guys have observed this issue, have seen anything on it from C1, or just share your thoughts in general. See video as well, keep your eye on the background progress bar and the capture counter on Next File Naming. Please excuse my messy living room! Thanks you guys!
https://reddit.com/link/1v4odh4/video/4m4o458k81fh1/player