What does BYE identify your <CameraName> as ??

[s3igell]

I have a 60D which is identified as <cameraname> = "60D".

 

Then I also have a T2i which is identified as <cameraname> = "550DT2i".

(a rather longer and redundant double naming...)

 

I'm sure that these cameraname identifiers are coming from the DSLR via the SDK - meaning Canon specified that odd name.

 

But, I'm interested as to what other Canon DSLRs show for their <cameraname> data...

 

Chime in, so we can make a crowd-sourced list, if you have a DSLR not yet listed...

[admin]

I have a 60D which is identified as <cameraname> = "60D".

 

Then I also have a T2i which is identified as <cameraname> = "550DT2i".

(a rather longer and redundant double naming...)

 

I'm sure that these cameraname identifiers are coming from the DSLR via the SDK - meaning Canon specified that odd name.

 

But, I'm interested as to what other Canon DSLRs show for their <cameraname> data...

 

Chime in, so we can make a crowd-sourced list, if you have a DSLR not yet listed...

 

Actually BYE returns those values.  When a model has 2 different names for America and Europe both names are returned.

 

Regards,

[worcspaul]

FWIW, BYE logs my camera name as 1000D-XS

 

Paul

[s3igell]

Actually BYE returns those values.  When a model has 2 different names for America and Europe both names are returned.

 

My issue is a concern to manage the length of my Filenames while embedding sufficient Info to support my various workflows.  It might be minor, but the additional 3-4 chars start to add up. While Windows NTFS File System provides support for ridiculously long Filenames, some of the Imaging Apps fail to provide sufficient space in Listing and Search and Selection Tools.  Three less chars, times 10-15 selected files, sometimes is enough difference to allow a more restricted App to perform its function.

 

In general, all that we use the <camera-name> entry for is to differentiate between sources.  As owners of the Camera, we know of its multiple designations - actually at least 3 for each in the EOS Rebel line because of the "KISS x" naming scheme utilized in Asian Markets.  All that we look to the Filename to impart is sufficient data to differentiate between Cameras.

 

It's a relatively minor thing, but if given the choice between "550DT2i" / "550D" / "T2i" then I'd choose the shortest since each string imparts the same amount of Camera ID data and  the last saves a char (or 4) that can be used to impart some other piece of useful info which BYE makes available for our use.

[xdw]

Less experienced users prefer all the names and are not concerned with file name issues.

[admin]

Let me see if I can easily add 2 another property names to choose from with each camera name to choose from separately.

 

Regards,

[worcspaul]

Might I suggest an interim approach?

 

I have two 1000Ds, one modified, one not. Thanks to BYE's having two executables (and hence two user config files) I have one config file set to save everything under D:\backyardEOS\unmodified and the other to save under D:\BackyardEOS\modified (where D: is my external USB drive).  I've created shortcuts to the two BYE executables and named them modified and unmodified so it's then simply a matter of selecting the relevant shortcut depending on what camera I have connected.

 

You could do the same by saving images in separate folders BackyardEOS\550D and BackyardEOS\60D rather that including <cameraname> in the filename.

 

Paul

[s3igell]

I could do so, and actually do point the BackyardTEMP directories to separate locations when in 2 Camera Mode in order to avoid any potential for filename collisions during the interim processing.

 

But...

This suggested approach would come into issues later in the AP Processing Workflow, at points where my Post-Processing Apps had "standard output directories".  As well, the additional length of the subdirectory names will play to the same ultimate Filename Length issues.

 

As well, I don't always shoot Dual Camera, and one would simply be trading an automated Camera Identification for a Manual one...

 

Ni...  I'll make use of the functionality provided by BYE...  And if Guylain does see fit to add additional flexibility in a future release, I'll make the best of it...

[admin]

A quick dirty workaround would be to use the Filter field in the capture plan to identify the camera.  Not ideal but it would work.

[s3igell]

I use the <filter> field to identify my Filter use (if any)...  Which also leaves me without an Identifier for the Scope used...

 

I'll continue to use the <cameraname> field for its intended purpose.  And if additional functionality is added to BYE, I'll look to use that...

 

But, the Filter field is available for others who need it as an available user-definable field...

[admin]

I use the <filter> field to identify my Filter use (if any)...  Which also leaves me without an Identifier for the Scope used...

 

I'll continue to use the <cameraname> field for its intended purpose.  And if additional functionality is added to BYE, I'll look to use that...

 

But, the Filter field is available for others who need it as an available user-definable field...

 

The filter field is also a free-text field.  You can type whatever you what in that field, including your filter + camera + scope combination.

 

Regards,

[s3igell]

All true...

But that gets to be a rather big and messy "Filter List" when you have 4 Filters and 3 Cameras and at least 4 Imaging Scopes (4x3x4=48 Entries)...

 

I'll retain the Filter field for Filters, the Cameraname field for my DSLRs, and hope for a Scope field in the future...

[admin]

All true...

But that gets to be a rather big and messy "Filter List" when you have 4 Filters and 3 Cameras and at least 4 Imaging Scopes (4x3x4=48 Entries)...

 

I'll retain the Filter field for Filters, the Cameraname field for my DSLRs, and hope for a Scope field in the future...

 

Yes, but I meant the actual pulldown in the capture plan centre... there your can type anything even beyond what you entered in the Settings dialog.

 

It is not ideal, I realize that <_>

 

Regards,