First of all, there is one thing here that needs to be explained:
# PATH should never be off/false. By default, it is set to "mp3" ... Even if you are using use_imagefolder, the PATH should point to somewhere, because the path specifies the audio folder fallback. In your examples, you mostly have "false" and in some you have "content" ...
If you are using "content" as path for audio (which is a bit obscure), you won't be able to combine that with use_imagefolder properly.
mwr wrote:>Why not use the default "mp3" folder for this?<
What is that? I don't see anything like that in the list of
You have deleted your MP3 folder from the original Imagevue. This is not a problem, but we made it like that to recommend normal users to simply use this folder for mp3 audio files. In the admin interface it is set to HIDDEN, so that it does not display in the imagevue menu, but simply acts as a folder strictly for audio.
I am not 100% sure what you are trying to achieve, but perhaps I can recommend this - You obviously want separate tracks to be played from separate folders:
# Create a folder "mp3" or "audio" in your admin. In settings, point your audio path to this folder. There is no reason to set your path to "content" or "false" no matter if you are using use_audiofolder or not ...
# If you are using use_audiofolder, place your tracks in each specific imagefolder. There is no reason again here why you should be placing your tracks in the main "content" folder.
There are also some other issues which may cause problems when testing: 1. Imagevue uses a flash "cookie" to determine the visitors last state of the audioplayer (if its playing or not). This outweighs the autostart setting and may of course have effects when testing.
Now, I won't insist there are no flaws with Imagevue and the audioplayer, but it would be easier to diagnose if we could work out from standard integrations. Feel free to post back here ...