You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
thanks for this add-on. Recently, I wanted to send a link to an opus audio file (with ending .opus). For testing, this directory of opus audio streams should be sufficient.
m4b (identical to m4a, but other file ending, for audio books)
ape
webp
opus
which are understood by Kodi, but "unsupported" by this add-on.
I did not exhaustively search for other missing file formats. Instead I want to ask if it is a good idea filtering links by file endings. Some URLs may contain no file ending and instead define the type with the MIME-Type HTTP header. On the other hand, Kodi does support almost any media format there is, adding more as available. Therefore, simply trying to send any file may be more reasonable. To avoid sending no-media web site content, HTML, JavaScript, JSON, CSS,... may be filtered out, ideally by MIME-Type.
The text was updated successfully, but these errors were encountered:
Hi,
thanks for this add-on. Recently, I wanted to send a link to an opus audio file (with ending
.opus
). For testing, this directory of opus audio streams should be sufficient.After some research, I found this list of supported formats and after comparison with the regex of this add-on, I can identify at least
which are understood by Kodi, but "unsupported" by this add-on.
I did not exhaustively search for other missing file formats. Instead I want to ask if it is a good idea filtering links by file endings. Some URLs may contain no file ending and instead define the type with the MIME-Type HTTP header. On the other hand, Kodi does support almost any media format there is, adding more as available. Therefore, simply trying to send any file may be more reasonable. To avoid sending no-media web site content, HTML, JavaScript, JSON, CSS,... may be filtered out, ideally by MIME-Type.
The text was updated successfully, but these errors were encountered: