Manual · Chapter 14
FAQ and Troubleshooting
Many unexpected results can be explained by the currently active project, an active filter, missing metadata or a deliberately selected export option. This chapter provides a systematic way to check common situations.
First steps when something looks wrong
If ViolaScope does not show the result you expect, begin by checking a few basic conditions.
- Check which project is currently active.
- Check whether a filter is active.
- Check the current photo selection.
- Check whether the affected photo resource is present in the project.
- For GPS or export issues, check the options used for that operation.
If the behavior cannot be explained by these checks, continue with the relevant troubleshooting section below.
Why can't I see all photos in my project?
An active filter is a common reason.
Filters in the left sidebar determine which photos from the active project are currently displayed in the workspace.
Check whether ViolaScope is filtering by star rating, color label, culling state or tag.
Clearing the active filter returns to the complete visible project set without changing ratings or other project information.
Why doesn't a filter change my photos?
This is intentional.
A filter does not change the original files, ratings, labels or other stored information.
It only controls which photos are currently visible in the workspace.
Why can a photo no longer be found?
If an image resource expected by the project was deleted, moved, renamed or replaced outside ViolaScope, the stored project association may no longer match the physical files.
First check whether the affected project resource can be restored from a backup of the project.
A different file with the same file name is not a reliable substitute for the missing resource.
The original photo folder is no longer available
The original source folder used when loading photos and the photo resources managed as part of the ViolaScope project are separate concepts.
Once a photo has been incorporated into the managed project state, the original source folder is not necessarily the ongoing working location for that project.
The important question is whether the managed project resources remain complete and available.
Why is metadata missing for a photo?
Not every image file contains the same metadata.
Available values depend on factors such as the camera, capture device, file format and previous metadata processing.
An empty field therefore does not automatically mean that something is wrong with ViolaScope.
ViolaScope displays the information that is actually available rather than inventing missing values.
Why doesn't a photo appear at a location on the map?
A geographic photo position requires usable location information.
If the file does not contain GPS coordinates and no location has been assigned within the ViolaScope project, there is initially no photo location to display.
A suitable GPX track can be used to determine a location for such photos.
The GPX locations are wrong
Check the time alignment first.
The clock in the camera and the time used by the device that recorded the GPX track may not match exactly.
An incorrect time offset can therefore cause a photo to be associated with the wrong point along the track.
Adjust the time offset and review the preview again before applying the proposed locations.
Can I check a GPX assignment before applying it?
Yes.
GPX-based location assignments are intentionally shown as a preview first.
Only when you choose Apply are the reviewed location assignments accepted into the ViolaScope project state.
Why didn't Vision Culling change my culling state?
This is intentional.
Vision Culling creates analysis results and suggestions, but it does not automatically overwrite your manual culling decisions.
You can inspect a suggestion and explicitly apply it to the selected photo when you agree with the result.
Why can Vision results differ after a new analysis?
Grouping and ranking depend on the photo set used for the individual analysis run.
If you analyze only a selection, that selection forms the comparison set.
An entire-project analysis can therefore produce different similarity groups or rankings than an analysis of a smaller selection.
Why is the previous Vision analysis no longer shown?
A new Vision Culling run creates a new current analysis result.
The new result replaces the previously stored Vision analysis result.
Your manual ratings and culling decisions are not automatically replaced by this process.
Why wasn't a photo exported?
Check the export rules first.
A photo may have been excluded because it did not meet the selected minimum rating.
The culling state can also matter when Rejects are not enabled for export.
The export summary helps you determine which photos were copied, filtered, already present or not successfully exported.
Where are exported Rejects stored?
When exporting Rejects is enabled, ViolaScope stores them separately from the regular export selection.
This keeps rejected images clearly separated from the main exported result.
Why didn't a repeated export create another image copy?
ViolaScope attempts to recognize identical image resources reliably.
If an existing destination resource is recognized as the same photo, another unnecessary image copy does not need to be created.
XMP or transfer-manifest information can still be updated when required.
Why are there two files with similar names?
An identical file name does not prove that two image files contain the same photo.
If the export destination already contains a different image resource with the requested name, ViolaScope uses a conflict-free destination name rather than overwriting the existing file.
Why do I see fewer photos after an export?
After a successful export, the exported result can become the active working state.
The filmstrip can then show the photos that were successfully exported as part of that working set.
Photos that were not included in the export are not automatically deleted from the overall ViolaScope catalog.
Why does the export folder contain more files than the filmstrip?
ViolaScope does not automatically remove older files from an existing export folder when a later export contains fewer photos.
The physical folder can therefore contain older images that are not part of the current exported working set shown in the filmstrip.
This avoids automatic deletion of files that may still be needed.
Does “Remove location data” remove GPS from the image file?
No.
The corresponding export option applies to XMP sidecars and transfer-manifest information generated or managed by ViolaScope.
GPS information already embedded directly in the exported image file, for example in EXIF metadata, can still remain in the copied image.
Which XMP profile should I use?
Choose the profile according to the application in which you plan to continue working.
- Neutral – general-purpose XMP output
- Adobe Lightroom – intended for transfer to Adobe Lightroom
- DxO PhotoLab – intended for transfer to DxO PhotoLab
Not every ViolaScope property can necessarily be represented in exactly the same way by every external application.
Why don't P, U, X or 0 to 5 work right now?
First check whether an editable text field or a dialog is active.
While entering text, ViolaScope intentionally does not treat letters, number keys, arrow keys or ⌘ + A as photo-management shortcuts.
When a sheet or dialog is open, keyboard input belongs to that active dialog instead of the main workspace.
Why do the number keys rate several photos at once?
Star ratings and culling states are applied to the current selection.
If several photos are selected, those photos therefore receive the selected rating or culling state together.
Check the current selection before applying a keyboard command when several photos are highlighted.
Why doesn't ⌘ + A select the entire project?
Select All refers to the currently displayed photo set.
If a filter is active, the command therefore selects the currently visible filtered photos rather than automatically selecting every photo in the entire project.
The normal photo-set Select All command is not used while comparison view is active.
Can I change managed project files outside ViolaScope?
The original external source folders and the managed ViolaScope project resources should be treated as separate things.
Files inside the managed project should normally not be manually deleted, renamed, replaced or moved.
Such changes can cause the physical project contents and the stored ViolaScope associations to no longer correspond.
Is an XMP export enough as a backup?
No.
XMP can transport important ratings and metadata, but it does not contain the complete state of a ViolaScope project.
A complete project backup should therefore include the managed project data together with the required image resources.
Is a catalog backup without the photos enough?
No.
A catalog backup can preserve important project and organizational information, but it does not replace the associated image resources.
Both parts must be considered if the project is to be fully recoverable.
What information should I include when reporting a problem?
A precise description makes technical investigation much easier.
Helpful information includes:
- the installed ViolaScope version and build number
- the macOS version
- a clear description of the problem
- the steps required to reproduce the behavior
- any error message that was displayed
A screenshot can also be useful when it clearly shows the problem.
Diagnostic information
ViolaScope provides additional diagnostic views that can help investigate reproducible problems.
⌘ + ⌥ + L opens the Interaction Log.
⌘ + ⌥ + P opens the Loading Performance view.
These views can provide useful technical information when investigating application behavior or performance.
Do I need to send original photos to support?
In many cases, no.
A precise description, reproduction steps and, when useful, a screenshot are often enough for an initial investigation.
If a specific problem genuinely requires an original image file, that can be clarified as part of the support request.
Contact support
If a problem cannot be explained or resolved using the checks described in this chapter, visit the ViolaScope support page for contact options.