Base filename number incrementing

10 views
Skip to first unread message

Alan Davis

unread,
Mar 17, 2024, 3:46:44 AM3/17/24
to Entangle Development
Hello:

I do not understand why sometimes, capturing with a Canon EOS camera, the jpeg and raw files have identical base filename numbers. 

What can I do to make the numbers identical for the same shot?  Like this:
  1. capture-000007.jpg
  2. capture-000007.cr3
Sometimes this happens, but other times it looks like this, or so:\

  1. capture-000000.jpg
  2. capture-000001.cr3
Or visa versa.

Thank you for any clarification. 

Alan Davis
 

d...@berrange.com

unread,
Mar 28, 2024, 8:32:40 AM3/28/24
to Alan Davis, Entangle Development
On Sunday, March 17, 2024 08:46 CET, Alan Davis <alan3...@gmail.com> wrote:

> Hello:
>
> I do not understand why sometimes, capturing with a Canon EOS camera, the
> jpeg and raw files have identical base filename numbers.
>
> What can I do to make the numbers identical for the same shot? Like this:
>
> 1. capture-000007.jpg
> 2. capture-000007.cr3

Right this is the expected behaviour we aim to provide. Essentially we look
at the filename prefix as provided by the camera, and compare it to the
last filename prefix we saw. If they are the same, then we don't increment
the digits.

That happens in this method:

https://gitlab.com/entangle/entangle/-/blob/master/src/backend/entangle-session.c?ref_type=heads#L403

> Sometimes this happens, but other times it looks like this, or so:
>
>
> 1. capture-000000.jpg
> 2. capture-000001.cr3

This suggests that the two filenames received from the camera had different
name prefixes already, which caused entangle to increment the digit when
applying its local naming pattern. Or our entangle naming code has a bug.

Running with --debug-entangle will record the log files from that method
I link to above, and would diagnose what we're seeing from the camera that
causes us to mistakenly change the digit.

Daniel

Reply all
Reply to author
Forward
0 new messages