Hi Oliver,

Make a simple test. Create a new page with only one addon inside. Just add "Raw HTML addon"

and inside put HTML5 player > Apply > Save & Close.

<audio controls preload="metadata" aria-label="Audio player">
<source src="/images/audio/Kapitel 1.mp3" type="audio/mp3">
Ihr Browser unterstützt das Audio-Element nicht.</audio>

then test that page on your smartphone. Und Ja, Our Audio addon - Verwenden Sie fast denselben Code.

There could be also problem with filename that you used, in general is NOT recommended to have space inside filename "Kapitel 1.mp3" > "Kapitel_1.mp3"

Hello Paul. This one works fine...

But it doesn't inside the Accordion addon... I changed the filename, but still.

Does raw html addon with that code works in Accordion addon? Please check.

what you see on iPhone, empty space ???

No, it is not visible, I'm afraid. Here is the screenshot - but it is no iPhone, but an Android Phone (I don't know, whether this info might be relevant). https://prnt.sc/XxCiWNuuBgfR

Hmm. Please ping me tomorrow morning, I will ask our developer what it might be. I have no idea.

Maybe the new Helix version, I just updated? But yes, I will ping you :-)

You set Casiopea template as default for testing, but I don't think so.

Good morning. Set Casiopea as default ... ? Not that I know of.

Here is my ping :-)

I mean, Audio worked in Accordion on Casiopea template on Smartphone ?

No, it doesn't work in Accordion - I tried it in Casiopea and in Podcasta template.

Well, thanx for coming back on that one. Since it is a confirmed bug, I hope, there will be a fix in the future ;-)

I see the same problem with Tabs...

I tried with the Audio Layouts addon and it works.

I investigated further and found out that the Audio Layouts addon doesn't work on mobile phone either. So I tried to be very clever and build a Popup as a workaround and - tadaaaaa - it also doesn't work. Seem to me that there is a big bug in that thing.

By the way, I use an Android phone - for reproduction. Double checked it on my tablet, Android as well, and it doesn't work either. Seems like an incompatability with Android to me (just a wild gues).

do you mean it doesn't work inside accordion and tabs addon, right.

But why, I don't have idea, it's so simple html5 code.

Now my confusion is complete. I upgraded to Podcasta template version 2.2.0 - all audio stuff didn't work, even if I remove the code from file custom.css. So I restored the backup with version 2.1.0. Audio works again, but HTML5 player doesn't work in Accordion and Tabs addon. I put in this into custom.css

.article-details-top-wrapper, .podcast-audio-player, .article-can-edit {display: none !important;}

in order to get rid of the header section in the article, NO audio works on the entire site. This

.podcast-audio-player

seems to switch it off all together. If I put it into the pages custom css only, nothing happens at all.

Looks like css code is not the answer here.

I also tried to place the HTML5 player into a Popup and call it via a button - it doesn't work either.

This is by the way related to these threads... https://www.joomshaper.com/forum/question/42842 https://www.joomshaper.com/forum/question/42934

Oh, I restored under another domain...

Just for info: Meanwhile, I changed the templates default.php file to get my result. But the incompatability problem remains...

Happy new year!

Yet another test and ... oops - audio player doesn't work at all. HTML5 version as well as the addon in PageBuilder... Even not outside an addon. It just doesn't. Creates a line of free space, but no player visible.

But I checked it on another site, running with Podcasta template as well, and I don't have the problem.

Well, we found the problem. It is a conflict of css. I use RSFormPro! and it brings its own css. This prevents the audio player to be displayed on an Android phone (only, why ever). If I switch off this form based css, it works fine.

Sometimes, I don't know, where to get enough phantasy for all these possible trouble sources from ... ;-) Happy new year.

Thanks for the info, indeed, it was weird case, that's why we couldn't reproduce the issue on clean Joomla site with SPPB only.