Apparently, Superlab keeps two paths in its scenario file for each external stimulus file or folder, one an absolute path from the filesystem root, the other a relative path from the last place that the scenario was saved. If you move the scenario file and/or the stimuli somewhere else, if either the absolute or the relative path still works, the other is updated to the new location both while running and also if the scenario is saved. If neither works, you have to specify the new location.
Based on some testing, plus on how the experiment package feature works, it looks like superlab tries the relative path first, then the absolute path. What I’d like to know is whether this is always true. Can I count on the relative path being used first, so that if I copy an experiment hierarchy (scenario and stimuli) to another location, it will use the stimuli in the copy (relative path), not the stimuli in the original location (absolute path)? (Assume that both paths point to stimuli with the same file names, but different contents.)
I ask because I want to make copies of an experiment and then modify some of the stimuli in the copy while using the same file names, to avoid having to alter each scenario.
If not, I see two workarounds: I could make sure the original location is not there when running experiments, or I could use a binary editor like bbe to scribble x’s over all the absolute paths in the scenario before copying it. However, it would be more convenient not to do this.