Home / GitHub Page

Is audio not playable with html5?

#1

Hi,

when I import two sound-files, I can hear the sound from an external player.
Jan Delay - Large.mp3
Jan Delay - Large.ogg

But when I use this code, the shown html-player is grey (both sound files are imported to joplin):

<audio controls autoplay>
  <source src="Jan Delay - Large.ogg" type="audio/ogg">
  <source src="Jan Delay - Large.mp3" type="audio/mpeg">
Your browser does not support the audio element.
</audio>

Is it possible to run the sound-file with the html-player?

Greetings,

Uwe

0 Likes

#2

This has 2 reasons:

  • you are not referencing the correct local files
  • Joplin does not know how to use it’s own local files for the source tag

There has been a similar change for the <img> tag, which could be used as a template to create a PR for the <source> tag as well.

This would be a nice PR for Hacktoberfest :jack_o_lantern: !!!

Btw, it works, if you reference an external file. Try something like:

<audio controls autoplay>
  <source src="https://upload.wikimedia.org/wikipedia/commons/c/c8/Example.ogg" type="audio/ogg">
</audio>
0 Likes

#3

As a general rule, HTML support is there mostly for layout, color, styling, etc. but more advanced features such as sound, video or JavaScript handling are not officially supported (though in some cases it’s possible it will work).

0 Likes

#4

Thank’s for your workaround, but I’d prefer a (local) solution similar to the tag.

An other open source tool for notes tiddlywiki supports these features (audio, video, image) since many years and I like both, Tiddlywiki and Joplin.

So my hope is on the Hacktoberfest. :wink:

Greetings and many thanks for this great piece of software!

0 Likes

#5

Yes, they are easily done !

0 Likes

#6

Öh - what is easily done? The access to locally stored audio-files is still not possible in 1.0.142. (Or did I something wrong?)

0 Likes

#7

Isn’t there a markdown-it plugin for this?

0 Likes

#8

Yes, indeed, there are two audio plugins:

https://www.npmjs.com/search?q=keywords%3Amarkdown-it-plugin%20audio

0 Likes

#9

The problem is not with the audio itself, but the fact that the link is not recognized. Playing audio works perfectly with valid links. But HTML does not understand a link that looks like :/b98bd768c35644389f498e4abf7eaf05

So we don’t need a plugin, but a way to make HTML able to understand the above Joplin link.

0 Likes

#10

Maybe a solution could be to add ‘support’ for resource filename extensions into Joplin?

I.e. you’d type :/b98bd768c35644389f498e4abf7eaf05.mp3, Joplin would discard the ‘.mp3’ bit on navigation and handle everything as it always did, and the HTML component is happy that it has an extension available?
Yes, of course, I have no idea how difficult this would be to implement, or if it’s possible at all. :stuck_out_tongue:

0 Likes