To 'activate' resources/images, ... they have to be 'imported' fom original location into oe resources.

If you use those resources from outside of oe, they are not known to oe. Not transferred and not updated, just unknown.

That condition of oe is by far not known. But it's an important key for the usage of oe.

So,

whenever you'd need a resource/image/sound/clip to be implemented on oe, it is required to transport/invoke that to the resource(s).

The further advantage is, that the original of that image is kept anwhere, it will never be touched (just  copied to oe).

The access will always be through oe internally. It is 'embedded'. Oe could not find it else, because it is also not transferred to the server.

Don't be scared, it's simple.
When you see the symbol for implementing a resource
(screen shot 1), that button leads you to the resources part of oe.

You select a resource (image) from there only. That makes that image known to oe.
And it includes that particular resource into the optimization process (manually triggered), but leaves the original(s) untouched (Preferences ... Maintenance, ...).

If you do not yet have such resource there, you may add it
(screen shot 2).

Pull that wanted symbol/image from the original place, add it to the resources. It's just copied.
That leaves the original intact. Only oe has internal access to it via the resources. Very nice. You may even delete that resource/mage at the original location, it is still known to oe.

One thing else, you might consider

(screen shot 3).
To keep an order to find resources already existing in oe's resources,
I urge you to create some correspondingly named *Folders*.

You may easily create any *folder* (New Folder).
There are exceptions. Some entities/resources have to go to the *Other* ... folder(s), you'll find out
(screen shot 4).
Be careful to give meaningful names, because it's not so simple to change the folder names.

Be acquainted with the resource handling, that helps alot.
Usually it is not required to manually coding in oe for resources.

I made the same mistake, referenced the resources from original location only.

But I was not really happy.

It is a pretty simple process - once you know the beef.

Recently I put my sample project online for free usage.
That might give you more info. It might help you.
https://forum.openelement.com/en/forum_posts.asp?TID=1622&title=sample-website

OpenElement creates some sort of databases that list the elements to include into the export.

When you use code block to include a file into your pages OE doesn't know it.

If you use Project=>Resources to import these files into OE, you can also use Project=>Resources then select files and use the publish button to export them.

You can download it here: https://denislafrance.net/Element/Audio.en-us.htm

Built from HTML5 standards for OpenElement, if you use it, OE will know the audio file and export it

Currently it is minimum, It allows for MP3 and OGG and is limited to full controls, I will add options later today.

Procedure:

I'll give your new element a try, thanks.

If I do not use that I'll just associate the audio files with a hidden element. Then they will seamlessly go along for the ride.

Thanks again to you both for your help.

Thanks much.

(Guess I should learn how to add elements but I'm not big into the web side of things. )