Displaying 20 results from an estimated 100 matches similar to: "Legal sample rates"
2004 Nov 10
0
Legal sample rates
--- Erik de Castro Lopo <erikd-flac@mega-nerd.com> wrote:
> Hi all,
>
> I'm trying to use the FLAC C libraries to encode audio.
>
> I'm doing something like:
>
> FLAC__seekable_stream_encoder_set_channels(pflac->fse, 1);
> FLAC__seekable_stream_encoder_set_sample_rate(pflac->fse, 11025);
>
2004 Nov 11
3
Legal sample rates
On Wed, 10 Nov 2004 16:08:21 -0800 (PST)
Josh Coalson <xflac@yahoo.com> wrote:
> > Is there someway of figuring out if a sample rate is valid?
>
> that's the right way.
But it doesn't tell me that the sample rate is invalid it tells
me FLAC__SEEKABLE_STREAM_ENCODER_STREAM_ENCODER_ERROR or
FLAC__STREAM_ENCODER_NOT_STREAMABLE.
> the reason it's being rejected is
2004 Nov 11
0
Legal sample rates
--- Erik de Castro Lopo <erikd-flac@mega-nerd.com> wrote:
> On Wed, 10 Nov 2004 16:08:21 -0800 (PST)
> Josh Coalson <xflac@yahoo.com> wrote:
>
> > > Is there someway of figuring out if a sample rate is valid?
> >
> > that's the right way.
>
> But it doesn't tell me that the sample rate is invalid it tells
> me
2004 Nov 11
3
Legal sample rates
On Thu, 11 Nov 2004 13:33:42 -0800 (PST)
Josh Coalson <xflac@yahoo.com> wrote:
> --- Erik de Castro Lopo <erikd-flac@mega-nerd.com> wrote:
> > On Wed, 10 Nov 2004 16:08:21 -0800 (PST)
> > Josh Coalson <xflac@yahoo.com> wrote:
> >
> > > > Is there someway of figuring out if a sample rate is valid?
> > >
> > > that's the
2004 Sep 10
3
Non-audio applications
Hi,
I work for a company which makes meteor and wind radar
(http://www.gsoft.com.au).
On occasion (ie during meteor showers such as the Leonids) we configure
the system to save raw data as it comes out of the acquisition system,
the data rate for this varies (depends on acquisition parameters and
number of coherent integrations etc), but usually it is around
600kb/sec.
The data consists of 16
2006 May 11
2
C++ Set_Metadata Problem
I refer to a problem that appeared on the flac list last August that was
either solved off-list or abandoned.
(http://lists.xiph.org/pipermail/flac/2005-August/000468.html)
The problem is with using the C++ encoder classes, particularly the
FLAC::Encoder::File:set_metadata
function. JC said that the developers version of how to add a simple
metadata block looked right, but it did not work for
2008 May 06
2
Flac-dev Digest, Vol 45, Issue 2
Along the same line as Frederick, myself and another university student were able to implement a multi threaded FLAC
encoder, but using Intel's Threading Building Blocks (TBB) package. We saw similar near-linear speedup.
Our solution is a bit more convoluted since we were learning the API, TBB and writing the encoder all in one 6 week
period. We used a pipeline model on the input stream, and
2004 Sep 10
5
[Flac-users] Re: settings for tighter compression than -8?
Early this past week, Miroslav Lichvar suggested for me:
> Ok, you need 0.04% improvement, that should not be a problem. Try
> flac --lax -e -p -l 32 -r 10 --no-padding
Thank you again, Miroslav. I tried that, and it took almost two full
days (surprisingly, Windows ME stayed up that long without crashing) to
re-encode the entire set on my 266-MHz machine. After all, in the help
file
2004 Sep 10
0
Re: Bug#196556: flac: FLAC__STREAM_ENCODER_NOT_STREAMABLE
Hi Matt!
On Sat, Jun 07, 2003 at 10:09:20PM -0400, Matt Zimmerman wrote:
> Run file(1) on the .wav file and send the output. Particularly, what are the
> sampling rates of the input files?
>
"RIFF (little-endian) data, WAVE audio, Microsoft PCM, 8 bit, mono 11025 Hz"
All the WAV files i tried before have been the ones shipped with the
openwebmail Debian package, showing
2004 Sep 10
2
Re: Bug#196556: flac: FLAC__STREAM_ENCODER_NOT_STREAMABLE
On Sun, Jun 08, 2003 at 02:06:18AM +0200, Paul Seelig wrote:
> This is what i get when trying to encode a WAV file:
>
> ------------- snip -----------------
> [pseelig]/tmp > flac -o YouGotMail.flac YouGotMail.wav
>
> flac 1.1.0, Copyright (C) 2000,2001,2002,2003 Josh Coalson
> flac comes with ABSOLUTELY NO WARRANTY. This is free software, and you
> are welcome to
2004 Sep 10
1
Re: Bug#196556: flac: FLAC__STREAM_ENCODER_NOT_STREAMABLE
severity 196556 minor
thanks
On Sun, Jun 08, 2003 at 12:06:56PM +0200, Paul Seelig wrote:
> On Sat, Jun 07, 2003 at 10:09:20PM -0400, Matt Zimmerman wrote:
> > I ran a simple test to try to reproduce your problem, and I happened to grab
> > one wav file which had a sampling rate of 4660 and was able to reproduce
> > your problem. flac works fine on the other files, which
2004 Nov 16
0
Legal sample rates
--- Erik de Castro Lopo <erikd-flac@mega-nerd.com> wrote:
> On Thu, 11 Nov 2004 13:33:42 -0800 (PST)
> Josh Coalson <xflac@yahoo.com> wrote:
> > 11025 is a valid sample rate, but 9 channels is not a valid
> > # of channels.
> >
> > the FLAC__STREAM_ENCODER_NOT_STREAMABLE error means you are
> > violating the "set streamable subset" setting
2013 Oct 18
4
[LLVMdev] Contribute a new precise pointer analysis to LLVM
Hi All,
This is Lian Li from Oracle Labs in Brisbane Australia.
We have developed a precise and highly efficient pointer analysis
framework on top of LLVM, The approach is flow, context, and field
sensitive, details are described in the two papers below:
"Boosting the performance of flow-sensitive points-to analysis using
value flow" (in ESEC-FSE 2011), and
"Precise and
2013 Oct 18
3
[LLVMdev] Contribute a new precise pointer analysis to LLVM
Thanks, Chris.
We are interested in contributing it to LLVM itself. Our manager
agrees to commit resources for maintenance needs if it is accepted by
the community.
Regards,
Lian
On Fri, Oct 18, 2013 at 3:43 PM, Chris Lattner <clattner at apple.com> wrote:
>
> On Oct 17, 2013, at 5:20 PM, lian li <lianli at gmail.com> wrote:
>
> Hi All,
>
> This is Lian Li from
2013 Oct 18
0
[LLVMdev] Contribute a new precise pointer analysis to LLVM
On Oct 17, 2013, at 5:20 PM, lian li <lianli at gmail.com> wrote:
> Hi All,
>
> This is Lian Li from Oracle Labs in Brisbane Australia.
>
> We have developed a precise and highly efficient pointer analysis
> framework on top of LLVM, The approach is flow, context, and field
> sensitive, details are described in the two papers below:
>
> "Boosting the
2013 Oct 18
0
[LLVMdev] Contribute a new precise pointer analysis to LLVM
On Oct 17, 2013, at 10:51 PM, lian li <lianli at gmail.com> wrote:
> Thanks, Chris.
>
> We are interested in contributing it to LLVM itself. Our manager
> agrees to commit resources for maintenance needs if it is accepted by
> the community.
This is great. Please make sure Oracle legal sign off on explicitly granting LLVM the use of the patents associated with the work.
On
2013 Oct 18
0
[LLVMdev] Contribute a new precise pointer analysis to LLVM
Hi Lian,
I am certainly interested in seeing this; do you have performance numbers (compile time)? Also, can you share more information about the promising optimization results you mentioned?
Thanks,
Hal
----- Original Message -----
> Hi All,
>
> This is Lian Li from Oracle Labs in Brisbane Australia.
>
> We have developed a precise and highly efficient pointer analysis
>
2020 Nov 06
3
How to find the root causes of compiler bugs in practice?
Hi, developers,
Recently, I read two papers [1], [2] about finding the root causes of compiler bugs. However, I do not find any information in these paper about how compiler developers find the root causes of compiler bugs in practice. So I am curious whether these techniques are useful in practice. For my experience, the outputs of compilers are always used to isolate the causes of compiler
2005 Aug 01
1
Application Metadata
Hi,
I'm sorry to say that I've found the libFLAC++ interface and
documentation pretty slim and baffling.
What I need to do is add some application-specific metadata to a FLAC
file (i'm using the FLAC++ fileencoder). It is currently just a string
of characters, which doesn't need to be null-terminated.
I've looked through the docs, i've looked through the tests, and
2013 Oct 22
2
[LLVMdev] Contribute a new precise pointer analysis to LLVM
Hi Evan,
We did an experiment using the LLVM test suite: we compare the
overhead of using our analysis to the LLVM default, both with -O2
option.
The overall overhead of compiling the whole test suite using our
analysis is 36.5%.
The biggest overhead is observed in
"SingleSource/Benchmarks/Misc/flops-5", where we are 5 times slower:
0.07s (with our analysis) compared to