Xiph.Org issueshttps://gitlab.xiph.org/groups/xiph/-/issues2011-02-22T16:30:00Zhttps://gitlab.xiph.org/xiph/libao/-/issues/1735add libffado support2011-02-22T16:30:00ZGitlab Botadd libffado supportin order to play on firewire audio devices on linux, one has to use ffado ( http://www.ffado.org/ )
It would be nice if libao supported that. in order to play on firewire audio devices on linux, one has to use ffado ( http://www.ffado.org/ )
It would be nice if libao supported that. Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/speex/-/issues/2041Add library.json2023-11-09T05:56:18ZIhorNehrutsaAdd library.jsonAdd library.json for VS Code PlatformIO
```
{
"name": "speex",
"version": "1.2.1",
"headers": "speex.h",
"build": {
"srcDir": "./libspeex"
},
"homepage": "https://www.speex.org/",
"repository":
{
"type": "git",
...Add library.json for VS Code PlatformIO
```
{
"name": "speex",
"version": "1.2.1",
"headers": "speex.h",
"build": {
"srcDir": "./libspeex"
},
"homepage": "https://www.speex.org/",
"repository":
{
"type": "git",
"url": "https://gitlab.xiph.org/xiph/speex.git"
}
}
```https://gitlab.xiph.org/xiph/opus/-/issues/2253Add license header to autogen.sh2017-10-21T19:37:04ZGhost UserAdd license header to autogen.shI am updating Opus in Chromium and one of the checks highlighted that autogen.sh doesn't have a license header. Is it possible to add this? Thanks!I am updating Opus in Chromium and one of the checks highlighted that autogen.sh doesn't have a license header. Is it possible to add this? Thanks!Jean-Marc ValinJean-Marc Valinhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2263Add mime.types paths for other distros2020-10-11T14:45:20ZMarvin ScholzAdd mime.types paths for other distrosWe should add some more mime.types paths, seems the current one we have does not work on FreeBSD
and OS X uses a different one.
See [this](https://groups.google.com/forum/#!topic/golang-codereviews/fIw6mRzai4U) for some more paths that ...We should add some more mime.types paths, seems the current one we have does not work on FreeBSD
and OS X uses a different one.
See [this](https://groups.google.com/forum/#!topic/golang-codereviews/fIw6mRzai4U) for some more paths that seems to be usual.Icecast 2.5.0Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2457add MPTCP support2023-04-06T12:41:42ZBjoern Jackeadd MPTCP supportMPTCP allows clients to switch from one network to another network without the TCP connection to break. So a client can be in a WIFI network and move to a LAN or a mobile data connection and the TCP connection stays alive. This is ideal ...MPTCP allows clients to switch from one network to another network without the TCP connection to break. So a client can be in a WIFI network and move to a LAN or a mobile data connection and the TCP connection stays alive. This is ideal for streaming applications and this would be perfect for Icecast. MPTCP v1 support was added to the Linux kernel in the early 5.x releases. Adding support for it for server applications is simple. MPTCP support is also transparent for non-MPTCP-aware devices.
All that being said, please add support for MPTCP to Icecast and have it enable it by default.Philipp SchafftPhilipp Schaffthttps://gitlab.xiph.org/xiph/vorbis-tools/-/issues/1106add output directory option to oggenc2009-04-18T05:19:08ZGitlab Botadd output directory option to oggencCurrently oggenc produces the output ogg file in the same directory where the input file is. I would like to have a option to specify an output directory e.g. "." or in the longer term even with formatstrings to create an output director...Currently oggenc produces the output ogg file in the same directory where the input file is. I would like to have a option to specify an output directory e.g. "." or in the longer term even with formatstrings to create an output directory with the artist's and album's name in it or with the path or latest directory from the input files.
Examples:
this one would be nice to have soon:
oggenc /tmp/artist-album/01-artist-title.flac -O . # outpufile: ./01-artist-title.ogg
these ones would be nice to have in the long term: (%P describes here the last directory from the path of the input file, alternatively %1p for the last directory and %2p for the last but one and the last directory would be a nice feature, too)
oggenc /tmp/artist-album/01-artist-title.flac -O "./%p" # outpufile: ./tmp/Artist-Album/01-artist-title.ogg
oggenc /tmp/artist-album/01-artist-title.flac -O "./%P" # outpufile: ./Artist-Album/01-artist-title.ogg
oggenc /tmp/artist-album/01-artist-title.flac -O "./%a" # outpufile: ./artist/01-artist-title.ogg
Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/XiphDirectory/-/issues/1Add Pagination for Genre/Codec/Search pages2023-06-23T22:30:19ZMarvin ScholzAdd Pagination for Genre/Codec/Search pagesPagination is needed, as on the real dataset there will be thousands of streams and outputting all on one page
is not going to perform well.
Either do a cursor-based pagination or an offset based one. Likely cursor based is going to wor...Pagination is needed, as on the real dataset there will be thousands of streams and outputting all on one page
is not going to perform well.
Either do a cursor-based pagination or an offset based one. Likely cursor based is going to work better performance wise
and additionally is better for consistency for things like the search where the dataset can change before the next
request is made and just using an offset would lead to confusing results.1.0.0Andreas MiekeAndreas Miekehttps://gitlab.xiph.org/xiph/rav1e/-/issues/44Add partition splitting to RDO2018-09-23T17:20:12ZThomas DaedeAdd partition splitting to RDO*Created by: tmatth*
Currently in `encode_tile` for every superblock, we search for the intra mode with the best RD (based on a 64x64 SSE), for PARTITION_NONE. We should extend this search to one-level of split.*Created by: tmatth*
Currently in `encode_tile` for every superblock, we search for the intra mode with the best RD (based on a 64x64 SSE), for PARTITION_NONE. We should extend this search to one-level of split.https://gitlab.xiph.org/xiph/Infrastructure/-/issues/2228Add per ip cooldown to media.xiph.org captcha2020-05-26T03:38:32ZRalph GilesAdd per ip cooldown to media.xiph.org captchaI noticed this week on https://media.xiph.org/ the same ip address managed to download *through the captcha* the same 89G file 11 times in the same day. That's counting complete transfers, not the POST request or a handful of truncated o...I noticed this week on https://media.xiph.org/ the same ip address managed to download *through the captcha* the same 89G file 11 times in the same day. That's counting complete transfers, not the POST request or a handful of truncated or Range-request downloads.
If possible, I'd like to add a filter to block repeated downloads. Ideally one download per file per ip address, but something less specific would be helpful too. That seems to best way to limit waste like this without slowing down people who actually need multiple resources.Marvin ScholzMarvin Scholzhttps://gitlab.xiph.org/xiph/theora/-/issues/512add pkgconfig support2009-04-19T20:41:41Zin7y118add pkgconfig support```
the attached patch adds pkgconfig support to libtheora.
``````
the attached patch adds pkgconfig support to libtheora.
```https://gitlab.xiph.org/xiph/icecast-server/-/issues/2130Add POST support to admin requests2018-10-04T10:42:35ZMarvin ScholzAdd POST support to admin requestsDue to how web stuff works and the web interface handles things (auth managements for instance) it is mandatory that we support POST, for properly sending data to the server.
(Just one downside of GET that already should be enough is th...Due to how web stuff works and the web interface handles things (auth managements for instance) it is mandatory that we support POST, for properly sending data to the server.
(Just one downside of GET that already should be enough is that the password would be in cleartext in the browser history)Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/xiph-qt/-/issues/1487Add steps to configure iTunes and QT to play FLAC and OGG files2009-04-19T20:46:52Zgary.johnsonAdd steps to configure iTunes and QT to play FLAC and OGG filesWhen I click on a flac file and open with QT I get the message, not a valid movie file.
When I open with iTunes, I get no action. I have the latest versions of iTunes and quicktime on OS X 10.4 as of DEC 28 08. It might be a nice idea ...When I click on a flac file and open with QT I get the message, not a valid movie file.
When I open with iTunes, I get no action. I have the latest versions of iTunes and quicktime on OS X 10.4 as of DEC 28 08. It might be a nice idea to have a page of instructions and a few test files so that we could declare victory on a successful install. Ditto for FirefoxArek KorbikArek Korbikhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2084Add support for ANSI streaming2021-10-26T09:40:29ZPhilipp SchafftAdd support for ANSI streamingStreaming in Text+ANSI Codes should be added to icecast. This would allow to to send shows of e.g. text adventures or other text games and applications.Streaming in Text+ANSI Codes should be added to icecast. This would allow to to send shows of e.g. text adventures or other text games and applications.Icecast 2.6https://gitlab.xiph.org/xiph/icecast-libshout/-/issues/2311Add support for JWT tokens2023-03-18T10:25:44ZThiago SantosAdd support for JWT tokensAdds support for setting a JWT authorization token (or any opaque token) to libshout. It will be used as an "Authorization: Bearer <token>" header instead of the usual user/password header for HTTP requests.Adds support for setting a JWT authorization token (or any opaque token) to libshout. It will be used as an "Authorization: Bearer <token>" header instead of the usual user/password header for HTTP requests.Philipp SchafftPhilipp Schaffthttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2465Add support for RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token...2023-03-18T10:25:42ZPhilipp SchafftAdd support for RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token UsageSupport for RFC 6750 should be added. In a first iteration this only needs to be supported by the `url` and the `enforce-auth` backend.
See also: xiph/icecast-libshout#2311Support for RFC 6750 should be added. In a first iteration this only needs to be supported by the `url` and the `enforce-auth` backend.
See also: xiph/icecast-libshout#2311Philipp SchafftPhilipp Schaffthttps://gitlab.xiph.org/xiph/theora/-/issues/1081Add user-lockable frame memory to theora2017-08-20T01:57:18ZGitlab BotAdd user-lockable frame memory to theora
## SUMMARY
Currently it is not generally possible to display ('play') theora content without
copying decoded frames at least twice - once from libtheora memory to user memory, and once from user memory to display memory.
This proposal...
## SUMMARY
Currently it is not generally possible to display ('play') theora content without
copying decoded frames at least twice - once from libtheora memory to user memory, and once from user memory to display memory.
This proposal suggests the addition of two API calls that add the concept of a "shared" buffer, allocated and freed by the user but lockable by libtheora. With such a buffer, one of these copies can be eliminated.
## THE PROBLEM
libtheora provides decoded frames in memory allocated and owned by libtheora (through the theora_yuv_out function call). libtheora does not guarantee that this memory is valid following subsequent theora_packet_in calls. Hence, the player application must either copy the decoded frame directly to the screen, or copy it to a buffer for later display.
However, it is undesirable to copy the frame directly to the screen, as this will lead either to unpredictable display times or an inefficient use of available time (the player must either display the frame as soon as it is ready or wait until the display time of the frame arrives). Hence, players must in general incur the cost of copying the frame to a temporary buffer owned by the player application.
## THREE PROPOSED SOLUTIONS
(1) One solution would be to add a single API call to libtheora:
```
theora_unlock_yuv_buffer(theora *, buffer *)
```
libtheora would then avoid freeing frames that have not been explicitly unlocked by the user. This approach has disadvantages:
* the behaviour of the library changes (legacy applications will stop working due to memory leaks)
* an additional function call per frame is required for normal operation of the library
(2) These disadvantages can be mitigated by requiring the user to lock buffers
first:
```
theora_lock_yuv_buffer(theora_state *, yuv_buffer *)
theora_unlock_yuv_buffer(theora_state *, yuv_buffer *)
```
libtheora would exhibit the same behaviour in the absence of these functions being
called, but would not free frames that have been locked by the user until subsequently unlocked.
(3) Another approach is to allow user-allocation of buffers:
```
theora_user_yuv_out(theora_state *, yuv_buffer *)
int theora_user_buffer_is_freeable(theora_state *, yuv_buffer *)
```
In this case, the user can provide user-allocated memory into which theora decodes the frame, and theora can indicate that a user-allocated frame should not be freed (for example, if the frame is a reference frame). Normal operation of the library is unchanged.
This approach has the additional advantage that the user can tailor memory use to the application and environment - restricted-memory embedded systems can avoid malloc and free, while directX-based systems can provide memory already allocated as a directX texture.
## RECOMMENDATION
Given that this problem exists, and is fixable with minimal API modification and no perceived change for existing applications, I would suggest that we consider fixing it. I currently favour approach 3, as it is more flexible, however this approach also means more work for the application designer that wishes to use the new feature.
https://gitlab.xiph.org/xiph/vorbis-tools/-/issues/1286add vinfo to vorbis-tools2008-02-17T16:20:46ZGitlab Botadd vinfo to vorbis-toolsAoyoumi released vinfo, a tool for displaying the information in an OggVorbis file (including an option to print bitrate). This is licensed under 3-clause BSD. The tool can be found here:
http://www.geocities.jp/aoyoume/oggtool/index.htm...Aoyoumi released vinfo, a tool for displaying the information in an OggVorbis file (including an option to print bitrate). This is licensed under 3-clause BSD. The tool can be found here:
http://www.geocities.jp/aoyoume/oggtool/index.html
Note that the source code is included with the windows executable.
Woul be nice if that will be added to next release of vorbis-tools (maybe after asking Aoyumi if the tool is considered ready to be merged).Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/vorbis-tools/-/issues/317Add warning when -M is below average for a specific -q2018-01-22T04:18:38ZjazAdd warning when -M is below average for a specific -q```
Using -q x -M y (for streaming purposes), when y is below the average of -q,
it is ignored, although oggenc says " using constrained VBR ( ... , max br
y ) ".
It might be useful to add a warning about this, because if not, it simp...```
Using -q x -M y (for streaming purposes), when y is below the average of -q,
it is ignored, although oggenc says " using constrained VBR ( ... , max br
y ) ".
It might be useful to add a warning about this, because if not, it simply
looks like it doesn't work.
```Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/opus/-/issues/2364Added the OPUS_SET_INBAND_FEC(2) option2023-07-27T04:04:32Zhua yanAdded the OPUS_SET_INBAND_FEC(2) optionWhat are the benefits of adding the OPUS_SET_INBAND_FEC(2) option? How does it affect audio quality? How does it affect audio quality compared to OPUS_SET_INBAND_FEC(1)?What are the benefits of adding the OPUS_SET_INBAND_FEC(2) option? How does it affect audio quality? How does it affect audio quality compared to OPUS_SET_INBAND_FEC(1)?https://gitlab.xiph.org/xiph/icecast-server/-/issues/2226Adding <mount-title> for mountpoints2018-11-10T15:54:39ZvtangerAdding <mount-title> for mountpointsAs there are a number of semi-defective clients which do not transmit a description/title as well as people out there who cannot reliably enter the display title into their client configuration, such an override-option in the configurat...As there are a number of semi-defective clients which do not transmit a description/title as well as people out there who cannot reliably enter the display title into their client configuration, such an override-option in the configuration would come handy. Thomas B. RückerThomas B. Rücker