Xiph.Org issueshttps://gitlab.xiph.org/groups/xiph/-/issues2017-11-01T04:49:44Zhttps://gitlab.xiph.org/xiph/vorbis/-/issues/1945[PATCH] configure script should honour --docdir option2017-11-01T04:49:44ZKarl Lindén[PATCH] configure script should honour --docdir optionThe configure script should honour the --docdir option as this is the autotools standard. The build system currently overrides that the docdir variable with its own but that is not very clean. Honouring docdir gives a more standardized a...The configure script should honour the --docdir option as this is the autotools standard. The build system currently overrides that the docdir variable with its own but that is not very clean. Honouring docdir gives a more standardized and flexible behaviour that the user can control.
I'm attaching a patch that fixes the issue.Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/icecast-libshout/-/issues/2313ezstream hangs with libshout2019-11-18T08:44:49Zzygmundezstream hangs with libshoutHi,
Some time ago I was reported ezstream hangs with version of libshout 2.4.3 but problem still exists even with master branch, after few houres stream stops and I need to kill -9 ezstream.
When I downgraded to 2.4.1 everything is perf...Hi,
Some time ago I was reported ezstream hangs with version of libshout 2.4.3 but problem still exists even with master branch, after few houres stream stops and I need to kill -9 ezstream.
When I downgraded to 2.4.1 everything is perfect.https://gitlab.xiph.org/xiph/vorbis-tools/-/issues/639ogg123: remote .m3u playlist files2018-01-22T04:18:37ZGitlab Botogg123: remote .m3u playlist filesIt seems silly to me that Icecast will generate .m3u files dynamically for.ogg mountpoints but ogg123 can't make use of them.It seems silly to me that Icecast will generate .m3u files dynamically for.ogg mountpoints but ogg123 can't make use of them.Gitlab BotGitlab Bothttps://gitlab.xiph.org/xiph/vorbis-tools/-/issues/1678oggdec manpage error: oggdec - doesn't write to stdout2018-01-22T04:18:37ZJohn Ferlitooggdec manpage error: oggdec - doesn't write to stdoutReported by anton repko at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=263762
The man page says:
If the input file is specified as ‐ , then oggdec will read
from stdin, and write to stdout unless an output filename i...Reported by anton repko at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=263762
The man page says:
If the input file is specified as ‐ , then oggdec will read
from stdin, and write to stdout unless an output filename is
specified.
This doesn't seem to be true. It writes to "-.wav" if no filename is
specified, e.g. for
oggdec - < foo.ogg
Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/vorbis-tools/-/issues/1790The channel order for oggdec is wrong.2018-01-22T04:18:37ZGitlab BotThe channel order for oggdec is wrong.It is necessary to revise oggdec like oggenc.
== patch for oggdec==
```
diff -crN vorbis-tools-1.4.0/oggdec/oggdec.c vorbis-tools-1.4.0m/oggdec/oggdec.c
*** vorbis-tools-1.4.0/oggdec/oggdec.c Fri Jan 22 15:01:46 2010
--- vorbis-tools-1...It is necessary to revise oggdec like oggenc.
== patch for oggdec==
```
diff -crN vorbis-tools-1.4.0/oggdec/oggdec.c vorbis-tools-1.4.0m/oggdec/oggdec.c
*** vorbis-tools-1.4.0/oggdec/oggdec.c Fri Jan 22 15:01:46 2010
--- vorbis-tools-1.4.0m/oggdec/oggdec.c Sun May 01 23:57:57 2011
***************
*** 225,237 ****
static void
permute_channels(char *in, char *out, int len, int channels, int bytespersample)
{
! int permute[6][6] = {{0}, {0,1}, {0,2,1}, {0,1,2,3}, {0,1,2,3,4},
! {0,2,1,5,3,4}};
int i,j,k;
int samples = len/channels/bytespersample;
/* Can't handle, don't try */
! if (channels > 6)
return;
for (i=0; i < samples; i++) {
--- 225,245 ----
static void
permute_channels(char *in, char *out, int len, int channels, int bytespersample)
{
! int permute[8][8] = {
! {0},
! {0,1},
! {0,2,1},
! {0,1,2,3},
! {0,2,1,3,4},
! {0,2,1,4,5,3},
! {0,2,1,5,6,4,3},
! {0,2,1,6,7,4,5,3}
! };
int i,j,k;
int samples = len/channels/bytespersample;
/* Can't handle, don't try */
! if (channels > 8)
return;
for (i=0; i < samples; i++) {
```
Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/xiph-qt/-/issues/1622XiphQT 0.1.5 (windows) does not support files with .oga file extension2018-04-29T09:16:11ZqubitXiphQT 0.1.5 (windows) does not support files with .oga file extensionI was recently testing playback of various files in iTunes.
On a WinXP machine I'm able to playback a set of .mp3, .ogg, and .oga files using Songbird.
On a Windows Vista machine + iTunes + XiphQT 0.1.5 I'm able to playback the .ogg fi...I was recently testing playback of various files in iTunes.
On a WinXP machine I'm able to playback a set of .mp3, .ogg, and .oga files using Songbird.
On a Windows Vista machine + iTunes + XiphQT 0.1.5 I'm able to playback the .ogg files, but the .oga files don't appear to be recognized or imported in iTunes.Arek KorbikArek Korbikhttps://gitlab.xiph.org/xiph/oggdsf/-/issues/1653FLAC will not play from library on Win7 642018-04-29T07:18:12ZGitlab BotFLAC will not play from library on Win7 64Platform is Windows 7 64 bit. After installing latest (22nd Feb) build, I could double-click and play FLACs fine. However, there are two scenarios where FLACs will not play:
1. When streamed from a UPNP media server (e.g. try mediatomb f...Platform is Windows 7 64 bit. After installing latest (22nd Feb) build, I could double-click and play FLACs fine. However, there are two scenarios where FLACs will not play:
1. When streamed from a UPNP media server (e.g. try mediatomb from Linux). The server works fine, I tested FLAC streaming with a hardware streamer. MP3s also work fine. FLACs do not.
2. When double clicked from library after adding FLACS using WMTagPlus (http://bmproductions.fixnum.org/wmptagplus/)
In both scenarios you see WM display "media changing" several times and it skips several tracks before finally giving up and saying it doesn't know how to play them.Cristian AdamCristian Adamhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2167Icecast should expose the YP listing status to the public status pages2018-06-16T22:44:16ZThomas B. RückerIcecast should expose the YP listing status to the public status pagesThere are hundreds if not thousands of streams that fail to list properly in dir.xiph.org and it's obvious that nobody notices.
/admin/stats should expose a per mount status field if the given mount is set public and directory listings ...There are hundreds if not thousands of streams that fail to list properly in dir.xiph.org and it's obvious that nobody notices.
/admin/stats should expose a per mount status field if the given mount is set public and directory listings are enabled for the server.
Logic could be as follows:
* *OK* - No known errors for this mount
* *WARN* - During the last n yp-touches at least one error was received
* *FAIL* - No successful listing/touch for this mount
Further information, including verbatim messages from YP should be available through the admin interface. Covered in a separate ticket.Icecast 2.5.0Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2189Event triggers for Icecast 2.52019-01-22T06:35:22ZThomas B. RückerEvent triggers for Icecast 2.5We are introducing event triggers and need to decide what we trigger on. Currently already supported:
* source-connect
* source-disconnect
* icecast-start
* icecast-stop
Proposed additional triggers:
* client-connect (all connectio...We are introducing event triggers and need to decide what we trigger on. Currently already supported:
* source-connect
* source-disconnect
* icecast-start
* icecast-stop
Proposed additional triggers:
* client-connect (all connections that are !SOURCE|!PUT)
* client-disconnect (all connections that are !SOURCE|!PUT)
* icecast-reload (configuration reload as caused SIGHUP or web request)
* yp-failure
* metadata-change (Both in container and side-channel triggered, with differentiating field)
* various admin commands (Including authentication management)
* critical errors or even general logging (this needs to be thought through)Icecast 2.5.0Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/vorbis/-/issues/1920todB () function correction2017-11-01T04:49:44ZAniket BtodB () function correctionIn the mapping0_forward () function in the file mapping0.c file, while converting fft values to dB scale, a local maximum calculations are performed. In the first iteration, the max value is initialized to fft[0] (magnitude of signal) wh...In the mapping0_forward () function in the file mapping0.c file, while converting fft values to dB scale, a local maximum calculations are performed. In the first iteration, the max value is initialized to fft[0] (magnitude of signal) while in later on iterations, the maximum value is initialized to magnitude^2. In dB conversion of these values, a constant is subtracted in the todB () function. However, in the first iteration the constant is subtracted from the magnitude value, while in the further iterations the value is subtracted from magnitude^2.
logfft[0]=scale_dB+todB(pcm) + .345; /* + .345 is a hack; the
original todB estimation used on
IEEE 754 compliant machines had a
bug that returned dB values about
a third of a decibel too high.
The bug was harmless because
tunings implicitly took that into
account. However, fixing the bug
in the estimator requires
changing all the tunings as well.
For now, it's easier to sync
things back up here, and
recalibrate the tunings in the
next major model upgrade. */
local_ampmax[i]=logfft[0];
for(j=1;j<n-1;j+=2){
float temp=pcm[j]*pcm[j]+pcm[j+1]*pcm[j+1]; //magnitude square calculation
temp=logfft[(j+1)>>1]=scale_dB+.5f*todB(&temp) + .345; /* +
.345 is a hack; the original todB
estimation used on IEEE 754
compliant machines had a bug that
returned dB values about a third
of a decibel too high. The bug
was harmless because tunings
implicitly took that into
account. However, fixing the bug
in the estimator requires
changing all the tunings as well.
For now, it's easier to sync
things back up here, and
recalibrate the tunings in the
next major model upgrade. */
if(temp>local_ampmax[i])local_ampmax[i]=temp;
}
if(local_ampmax[i]>0.f)local_ampmax[i]=0.f;
if(local_ampmax[i]>global_ampmax)global_ampmax=local_ampmax[i];
//todB () function definition.
static inline float todB(const float *x){
union {
ogg_uint32_t i;
float f;
} ix;
ix.f = *x;
ix.i = ix.i&0x7fffffff;
return (float)(ix.i * 7.17711438e-7f -764.6161886f);
//764.6161886 is subtracted from fft[0] as well as amp^2.
//The constant subtraction is not consistent over the max calculations
}Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/icecast-libshout/-/issues/2314Allow disabling installation of ckport database2020-02-11T08:40:50ZPetr PisarAllow disabling installation of ckport databaseI found out that libshout-2.4.3 installs libshout.ckport file although I have no use for it. An attached patch adds --disable-ckport configure option that allows users to disable the installation.
[libshout-2.4.3-Allow-disabling-ckport-...I found out that libshout-2.4.3 installs libshout.ckport file although I have no use for it. An attached patch adds --disable-ckport configure option that allows users to disable the installation.
[libshout-2.4.3-Allow-disabling-ckport-database-installation.patch](/uploads/18b0544b437ccba7c9dd352e25175354/libshout-2.4.3-Allow-disabling-ckport-database-installation.patch)https://gitlab.xiph.org/xiph/vorbis-tools/-/issues/1677/usr/bin/ogg123: ogg123 status filling the console2018-01-22T04:18:37ZJohn Ferlito/usr/bin/ogg123: ogg123 status filling the consoleOriginally reported by matthieu castet at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=239073
If the terminal width is shorter than the ogg status line
Time: 00:20.61 [03:09.31] of 03:29.92 (219.6 kbps) Output
and it wraps then...Originally reported by matthieu castet at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=239073
If the terminal width is shorter than the ogg status line
Time: 00:20.61 [03:09.31] of 03:29.92 (219.6 kbps) Output
and it wraps then it starts scrolling instead of just updating itself.
Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/vorbis-tools/-/issues/1789Access violation problem of oggenc (windows mingw build)2018-01-22T04:18:37ZGitlab BotAccess violation problem of oggenc (windows mingw build)When I encode by standard input, a problem happened.
I changed "oggenc.c" as follows. Thus the problem disappears.
-------------------------------------------------------------------------------------------
```
diff -crN vorbis-tools-1....When I encode by standard input, a problem happened.
I changed "oggenc.c" as follows. Thus the problem disappears.
-------------------------------------------------------------------------------------------
```
diff -crN vorbis-tools-1.4.0/oggenc/oggenc.c vorbis-tools-1.4.0m/oggenc/oggenc.c
*** vorbis-tools-1.4.0/oggenc/oggenc.c Fri Mar 26 16:07:08 2010
--- vorbis-tools-1.4.0m/oggenc/oggenc.c Sun May 01 05:30:28 2011
***************
*** 366,372 ****
enc_opts.filename = NULL;
enc_opts.infilename = NULL;
utf8_decode(out_fn, &enc_opts.filename);
! utf8_decode(infiles[i], &enc_opts.infilename);
} else {
enc_opts.filename = strdup(out_fn);
enc_opts.infilename = strdup(infiles[i]);
--- 366,373 ----
enc_opts.filename = NULL;
enc_opts.infilename = NULL;
utf8_decode(out_fn, &enc_opts.filename);
! if(infiles[i]!=NULL)
! utf8_decode(infiles[i], &enc_opts.infilename);
} else {
enc_opts.filename = strdup(out_fn);
enc_opts.infilename = strdup(infiles[i]);
```Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/xiph-qt/-/issues/1610Trouble with a specific video file2018-04-29T09:16:11ZShaneTrouble with a specific video fileSystem - dual G4 1.25Ghz 2GB RAM Mac OSX 10.4.11 - Quicktime 7.6.4 - xiphqt plugin
I have used this plugin (v0.1.8 until today) to play many files without issue.
Using this video - http://edgyu.excess.org/git-tutorial/2008-07-09/git2.og...System - dual G4 1.25Ghz 2GB RAM Mac OSX 10.4.11 - Quicktime 7.6.4 - xiphqt plugin
I have used this plugin (v0.1.8 until today) to play many files without issue.
Using this video - http://edgyu.excess.org/git-tutorial/2008-07-09/git2.ogv there appears to be a problem.
I have re-downloaded a second copy of the video and have the same problems.
with v0.1.8 about 15:23 - you can start playing from 15:00
Crash reporter notifies of a crash - interface stays up until you click report or cancel. video stops, audio continues.
Relevant part of crash log v0.1.8
```
Thread 12 Crashed:
0 <<00000000>> 0xffff8ad8 __memcpy + 824 (cpu_capabilities.h:189)
1 org.xiph.xiph-qt.xiphqt 0x06448278 Theora_ImageCodecDecodeBand + 432
2 ...ple.CoreServices.CarbonCore 0x90bdef80 CallComponentFunctionCommon + 1076
3 ...ple.CoreServices.CarbonCore 0x90bdeae8 CallComponent + 260
4 ...ickTimeComponents.component 0x99197f7c ImageCodecDecodeBand + 44
5 ...ickTimeComponents.component 0x98c8eb2c BaseCodec_ImageCodecDecodeBand_VideoDecodeThread + 44
6 ...ple.CoreServices.CarbonCore 0x90bfb46c InvokeDeferredTaskUPP + 24
7 com.apple.QuickTime 0x94907ea4 VideoDecodeThread + 148
8 libSystem.B.dylib 0x9002b908 _pthread_body + 96
```
with v0.1.9 about 18:30 - start playing about 17:00
Video stops and audio continues. Seems to continue with audio ok after that.
If you jump to about 20:00 to start playing it happens again just past 21:20
It would appear to be after a certain point in the file you can only play a short amount of video before it messes up the plugin.
Arek KorbikArek Korbikhttps://gitlab.xiph.org/xiph/oggdsf/-/issues/1637DirectShow Installer does not provide an option to select the directshow filt...2018-04-29T07:18:12ZCristian AdamDirectShow Installer does not provide an option to select the directshow filters to be installedWindows DirectShow Installer (version 0.81.15562) does not provide an option to select which directshow filters are going to be installed, it installs all of them.
It has only an option to select the file associations, but no option for...Windows DirectShow Installer (version 0.81.15562) does not provide an option to select which directshow filters are going to be installed, it installs all of them.
It has only an option to select the file associations, but no option for the actual filters, which, if not needed, will "bloat" the registry settings of the computer.Cristian AdamCristian Adamhttps://gitlab.xiph.org/xiph/vorbis-tools/-/issues/638Better handling of invalid/missing streams in OGG1232018-01-22T04:18:37ZGitlab BotBetter handling of invalid/missing streams in OGG123I'd like to see better handling of error messages for streams. Right
now the user has no idea why it failed, only that it did.
If it was an HTTP error, printing this should be sufficient. If it wasn't
an ogg vorbis file, the MIME type...I'd like to see better handling of error messages for streams. Right
now the user has no idea why it failed, only that it did.
If it was an HTTP error, printing this should be sufficient. If it wasn't
an ogg vorbis file, the MIME type really should say so (assuming it's
being checked) and ogg123 shouldn't ever have to try opening it, unless we
want to try streams regardless of mime type.Gitlab BotGitlab Bothttps://gitlab.xiph.org/xiph/vorbis-tools/-/issues/1782Ignoring metadata comments in ogg1232018-01-22T04:18:37ZnhollandIgnoring metadata comments in ogg123I've made some changes to ogg123 (from vorbis-tools 1.4.0) that allows arbitrary metadata comments to be ignored (=not printed to the screen) when playing files. For example, when a file contains binary album artwork in a comment, this w...I've made some changes to ogg123 (from vorbis-tools 1.4.0) that allows arbitrary metadata comments to be ignored (=not printed to the screen) when playing files. For example, when a file contains binary album artwork in a comment, this would normally result in a lot of garbage to be printed to the screen (in addition to a delay until the playback actually starts). Of course, this can be suppressed with the -q option, but when using that option no comments whatsoever and no playback progress / statistics at all would be printed, which isn't nice either.
As a result, I introduced a new command line switch (-i, --ignore-comments) as well as a new parameter in .ogg123rc (ignore-comments=...) that takes a comma-separated list of comment tags identifying those tags whose comments should not be printed (ignored) upon starting playback. The result is that only the comments specified are ignored, and all other comments as well as any playback statistics are printed as always.
The attached diff contains all the necessary changes to the ogg123 source.Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/xiph-qt/-/issues/1592Audio compressor settings button in QuickTime doesn't do anything at all2018-04-29T09:16:11ZDavid GatwoodAudio compressor settings button in QuickTime doesn't do anything at allOpen an AIFF file or other audio-only file in QuickTime Player.
Choose File > Export
Select "Movie to Ogg" in the Export pop-up
Click Options
Click the Settings button beside Audio
You should see some sort of pane for configuring bi...Open an AIFF file or other audio-only file in QuickTime Player.
Choose File > Export
Select "Movie to Ogg" in the Export pop-up
Click Options
Click the Settings button beside Audio
You should see some sort of pane for configuring bit rate and other compressor settings. Instead, the button does nothing as though it weren't hooked up correctly. The result is that there is no way to encode audio except at the default 128 kbps!
Platform: Mac OS X 10.5.8 (Intel)
XiphQT 0.1.9
Arek KorbikArek Korbikhttps://gitlab.xiph.org/xiph/oggdsf/-/issues/1612Windows 7.0 64 bit Issues2018-04-29T07:18:12ZMartin ErdmannWindows 7.0 64 bit IssuesInstalled 64bit stable in Windows 7/64bit op sys, 4Gb ram,
media player worked fine,however after I shut system down and after restart system would come up but explorer stopped working, system just locked up. Had to force shutdown and d...Installed 64bit stable in Windows 7/64bit op sys, 4Gb ram,
media player worked fine,however after I shut system down and after restart system would come up but explorer stopped working, system just locked up. Had to force shutdown and do system restore to use PC .Cristian AdamCristian Adamhttps://gitlab.xiph.org/xiph/vorbis/-/issues/1848Warnings in libvorbis/libvorbisfile2017-11-01T04:49:44ZAndrew ChurchWarnings in libvorbis/libvorbisfileThe attached patch against SVN r18145 corrects a number of compiler warnings with "gcc -Wall -Wempty-body -Wmissing-declarations -Wpointer-arith -Wsign-compare -Wstrict-prototypes" on GCC 4.6.1:
- Adds a new header lib/block.h to hold t...The attached patch against SVN r18145 corrects a number of compiler warnings with "gcc -Wall -Wempty-body -Wmissing-declarations -Wpointer-arith -Wsign-compare -Wstrict-prototypes" on GCC 4.6.1:
- Adds a new header lib/block.h to hold the declaration of vorbis_window(), #includes it in block.c and vorbisfile.c, and removes the declaration of that function from vorbisfile.c.
- Adds "static" to internal functions which don't have it: res[012]_*() in res012.c and _make_words() and run_test() in sharedbook.c.
- Changes () to (void) in function definitions so they are proper prototypes: main() (for tests) in sharedbook.c and host_is_big_endian() in vorbisfile.c.
- Deletes the unused function _vi_gpsy_free() from psy.c.
- Deletes the unused variable lastdelta from Laguerre_With_Deflation() in lsp.c.
- Propagates "const" up from the vwin64/vwin128 arrays in window.c through _vorbis_window_get() to its callers (and onward).
- Fixes a constant in info.c which was one digit too long (0x7ffffffff).
I can split this out into separate patches if desired, but I've bundled the changes together since they don't change any functionality.Monty MontgomeryMonty Montgomery