similar to: FLAC 1.1.2 released

Displaying 20 results from an estimated 4000 matches similar to: "FLAC 1.1.2 released"

2005 Mar 01
1
Re: FLAC 1.1.2 released
--- Christian Weisgerber <naddy@mips.inka.de> wrote: > Josh Coalson <xflac@yahoo.com> wrote: > > > FLAC 1.1.2 has been released. See the news item for full details: > > In doc/html, the api documentation is only installed if doxygen is > installed. Is this correct? I thought, doxygen was only required > to _build_ the api docs, but the package already comes
2004 Sep 10
9
FLAC 1.0.4 released
I uploaded the source tarball and binary releases for win32 and redhat 7. Solaris package should be ready tomorrow. See the news item for all the improvements from 1.0.3: http://flac.sourceforge.net/news.html#20020924 Developers, see the new Doxygen-based API docs: http://flac.sourceforge.net/api/index.html Thanks again to all the contributors and testers. Josh
2004 Sep 10
5
Re: beta 10 candidate checked in
Christian Weisgerber <naddy@mips.inka.de> wrote: > | # nasm build rule: > | %.lo: %.s Even with gmake, this really works only by accident. Automake generates a competing suffix rule, and gmake apparently gives the rule above a higher priority than the suffix rule (or that just happens to be the evaluation order). Matt, since you seem to understand automake, can you come up with
2004 Sep 10
6
beta 10 candidate checked in
I have checked in all the latest into CVS and am going to start the test suite again. if all goes well I will probably release this as beta 10. this one should have all the configure stuff working with the new assembly infrastructure. I have tried to make it as easy as possible to port routines to assembly. all that's really needed now is to write the corresponding routine for a specific
2004 Sep 10
4
FLAC 1.0.1 source release out
The source release for 1.0.1 is finally up on sourceforge. If you are compiling for x86 make sure to read the note in in the README about automake 1.5. Josh __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com
2004 Sep 10
3
FLAC 1.0.3 is out
Yes, it's finally here. See the homepage for details, but here's a summary: - 10-15% decoder speedup - 24-bit input support restored - more robust plugins - new metadata block for Vorbis-style tags - vastly improved metadata editor - fixed bug with pipes and Windows - new libFLAC++, a C++ object wrapper around libFLAC - new metadata editing interface in libFLAC and libFLAC++ - and
2004 Sep 10
5
detecting host machine in configure.in?
I am trying to set up a flexible infrastructure for the assembly code. Basically what I want is configure.in determination of basic machine type (intel/compatible, alpha, ppc), then within that (say intel) the code will detect variants like MMX, SSE, and use the right routines. I know how to do the second, but what is a good way to do the first? Linux/Cygwin/Solaris seem to support the MACHTYPE
2007 Sep 01
2
Re: 1.2.0: Test suite failures on LP64 archs?
Christian Weisgerber <naddy@mips.inka.de> wrote: > #0 0x0000000040d18810 in FLAC__lpc_compute_residual_from_qlp_coefficients_wide > (data=0x49e4c014, data_len=110, qlp_coeff=0x7f7ffffece70, order=1, > lp_quantization=14, residual=0x4fced000) at lpc.c:745 > 745 residual[i] = > data[i] - (FLAC__int32)((qlp_coeff[0] *
2004 Sep 10
5
Re: beta 10 candidate checked in
> > > $ aclocal && autoconf && automake -c -a -i > > > aclocal: configure.in: 45: macro `AM_PATH_XMMS' not found in > library > > > > my hunch is that your version of either automake or possibly > > autoconf is not recent enough. > > No. He simply doesn't have xmms installed. That's what I mentioned > a while ago:
2007 Aug 31
2
1.2.0: Test suite failures on LP64 archs?
Running the basic (--disable-thorough-tests) test suite, I get these failures round-trip test (rt-1-24-111.raw) encode... Segmentation fault (core dumped) ERROR FAIL: ./test_flac.sh fsd24-01 (--channels=1 --bps=24 -0 -l 16 --lax -m -e -p): encode...ERROR during encode of fsd24-01 FAIL: ./test_streams.sh on alpha and amd64. By contrast, i386 is fine. (All OpenBSD/4.2.) Could be a generic LP64
2004 Sep 10
1
Re: FLAC 1.0.4 released
--- Christian Weisgerber <naddy@mips.inka.de> wrote: > Josh Coalson <xflac@yahoo.com> wrote: > > > I uploaded the source tarball and binary releases for win32 and > > redhat 7. Solaris package should be ready tomorrow. > > There seem to be various problems with the included configure script: > > (1) > checking for shared library run path origin...
2005 Feb 01
3
FLAC 1.1.2-beta: attn package maintainers
The FLAC 1.1.2 release candidate is now available at http://prdownloads.sourceforge.net/flac/flac-1.1.2-beta.tar.gz?download Only the source tarball is available. I am putting out the beta first so that package maintainers and others can smoke test the build/install/check process before the official one goes out, since we've had problems before. Everyone that can, please download and try:
2004 Sep 10
3
Re: 0.9 problems
Matt Zimmerman <mdz@debian.org> wrote: > Aha. In FLAC__fixed_restore_signal, the index variable 'i' is declared > unsigned, then used like so: [...] With the following trivial patch applied, > everything works on Alpha, at least with my test sample. Against 0.9 or CVS? While this clearly fixes a bug, 0.9 still dies for me. #0 0x1600692a8 in
2002 Jul 28
2
IPv4/v6 socket problem on BSD
Currently, if IPv6-enabled rsync is run as --daemon, it will perform a wildcard bind(2) on an AF_INET6 socket and expect that IPv4 traffic will be forwarded to the v6 socket (IPv4 mapped address, RFC2553). This has never worked on OpenBSD which disallows IPv4 mapped addresses for security reasons. On FreeBSD 5.0-CURRENT, where the behavior is subject to configuration, the default was switched to
2004 Sep 10
5
0.9 problems
Problems in FLAC 0.9: - On alpha, flac immediately dumps core for both encoding and decoding (FreeBSD/alpha). - The distribution Makefile.in files haven't been generated with "automake --include-deps". The resulting Makefiles aren't fully portable; in particular they break with BSD make. In the future, care should be taken to use "--include-deps". - What is
2020 Jan 02
2
u2f seed
That sounds like the application param is still used as part of the process though? Would allowing the user to specify the application work in the Solokey case? What is stored in the private keyfile? The documentation says no private key is stored there. So is it just information used to reseed the public/private key? Thanks, Kevin ________________________________________ From: openssh-unix-dev
2004 Sep 10
2
Re: : flac and pipes problems (was: Possible bug)
> A minor point. Would it not be better if flac defaulted to .wav input > rather than raw samples. I think it's going to get wav input an order > of > magnitude more than raw samples? It saves always having to put the > -fw in > there, on these: > > $ flac -fw - mj.flac < mj.wav > $ cat mj.wav | flac -fw - mj.flac > > For that matter it should be able to
2004 Sep 10
2
0.10 released
Well, it's finally here. 0.10 has a lot of improvements. See the news page for the full list but here's a summary: * both encoder and decoder are significantly faster * flac now has gzip-like command-line usage (should be more intuitive) * the -# options have been tweaked for efficiency; -5 is the new default * flac now autodetects WAVE input * flac now ignores (with warning)
2004 Sep 10
2
object format detection
Last night I checked in code to enable changing the object file format passed to nasm. But I don't have many examples to draw from so if anyone could submit patches against configure.in for any of nasm's supported formats I'll put them in. Right now the relevant snippet just looks like: AC_CANONICAL_HOST case "$host" in *) OBJ_FORMAT=elf ;; esac Any patterns for
2020 Jan 10
4
u2f / libfido2 version
Hi, So I finally have time to test the u2f support but so far I haven't been very successful, Specifically, current HEAD has SSH_SK_VERSION_MAJOR 0x00040000 and I can't seem to find a matching libfido2 version, current HEAD of Yubico/libfido2 is 0x00020000 Is there a more up to date libfido2 or a particular commit of openssh-portable I should be using? thanks Sean