similar to: Clipping problem

I noticed that clipping occurs in lossy audio compression even if there is no clipping in the original file (though the original file has peaks that are just below the maximum). I know that this happens due to all the filtering involved during compression, but I'm wondering just how audible this clipping is because I don't hear anything wrong. I mean, as things are now, is it safe to say

Check this clip (it's small, 373kb) http://www.geocities.com/jdxss/udialwav.zip It left oggenc, lame and MP+ encoders choking in dust. -- Vorbis Xtreme | http://solair.eunet.yu/~aldov/ Ogg Vorbis is the free, open source alternative to MP3 --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a

Hello everyone, ff123 compiled Monty's branch of the RC1 encoder, see his post on r3mix.net forum: http://66.96.216.160/cgi-bin/YaBB.pl?board=c&action=display&num=994299736&start=30 Anyway it only supports ~128kbps mode, so I did a quick listening test with some files that bugged vorbis beta4. grace.wav - the right channel is still a bit watery, and I think this can be seen

Monkey's Audio lossless compressor (currently win32 only, free but not open-source except decoder) author is thinking to implement a kind of audiophile-quality lossy compression which would filter "noise bits" that are hard to encode lossless but which are (or should be) inaudible and thus improve lossless compression (avg. 300-450kbps). I think that implementing something like this

Hi folks, Warning: I don't know if the result I am getting makes sense, so this may be a statistics question. The fitted values from my binomial lmer mixed model seem to consistently overestimate the cell means, and I don't know why. I assume I am doing something stupid. Below I include code, and a binary image of the data is available at this link:

Hi, with the Lame MP3 encoder I reduce the amplitude of the input signal prior to encoding with the --scale option to prevent clipping that can be introduced due to resampling errors. Is Vorbis prone to this sort of clipping? <p>Headless --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a

Hi. Since I'm new to this mailing list, I don't know whether this was discussed in this mailing list, or if it is already fixed. Anyway, the problem is that all audio encoders out there add a small amount of silence to the start/end of the encoded file. This is usually a small amount, around 0.03 seconds. Most of the time it goes unnoticed, BUT when you have tracks that flow into one

> On 21 Apr 2016, at 17:15, Chris Matthews <chris.matthews at apple.com> wrote: > > I love D3. This is a great idea. Maybe we can finally kill flot! > > We are going to have to start using the html data attributes more; but that is a good thing IMO. > > D3 would greatly simply some of our CSS/templates too. I am regularly surprised how hard it is to make a cell

Dear all, I would like to make a large scatter plot created with R available as an interactive web graphic, in combination with additional text-annotations for each data point in the plot. The idea is to present the text-annotations in an HTML-table and inter-link the data points in the plot with their corresponding entries in the table, i.e. when clicking on a data point in the plot, the

---- "Aleksandar Dovnikovic" <aldov@EUnet.yu> wrote: > I think that AAC wasn't developed to be used as 'another' > MP3, it's usage is focused towards companies that sell audio > over the internet, for portable players, satellite communications... A-ha! That explains a lot. There used to be a project called FAAC but I presume it's gone. After seeing

I was doing some testing with RC2 and I noticed that RC2 doesn't encode past 19kHz with this clip (-b256 and -b350). There are no problems with this clip like it was before, but this clip contains signal past 19kHz which is audible as a faint high-frequency hiss - and that hiss is gone in the encoded file since RC2 cuts off at 19kHz. I think that -b256 and -b350 should encode at least up to

I couldn't catch Monty on IRC, so I'll ask here... how's RC3 coming along? Can we expect RC3 anytime soon, and what are the main improvements over RC2? -- Vorbis Xtreme | http://solair.eunet.yu/~aldov/ Ogg Vorbis - free, open source audio __________________________________________________ Do You Yahoo!? Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com ---

There seems to be an error in the X11 display code: try: plot(c(-30000,-1,0,1,30000),c(30000,1,0,1,30000),type="l") points(c(-30000,-1,0,1,30000),c(30000,1,0,1,30000)) it gives a big "V" as expexted. Now zoom in using small xlim and ylim: plot(c(-30000,-1,0,1,30000),c(30000,1,0,1,30000),type="l", xlim=c(-5,5),ylim=c(0,5))

Hi. Winamp version 3.0 has been announced. There will be no public beta and final version is expected for Christmas. Winamp 3.0 will be completely re-written version, but current plug-ins and skins (for winamp 2.x) will NOT be compatible with Winamp 3 (though this will be addressed in later winamp 3 versions). More info: http://www.winamp.com/nsdn/winamp3x/ Anyway, the reason I'm sending

Comments? ---------------------------------------- "Mark Taylor" <mt@sulaco.org> wrote: [...] > This is related to one minor objection I have to vector quantization > based codecs like Vorbis and the MPEG4 VQ codec: they do not compute > the quantization noise during the encoding process. The choice of > codebooks (use a big codebook: low quantization noise, use a

Hi, I've been working on further improving the perf profile view in LNT that James added recently. I've got a series of patches ready that reconstruct the control flow graph from the perf profiles, which helps a lot in quickly finding the codegen differences that cause performance deltas. I've used the D3 javascript library (https://d3js.org/) to implement the visualization. My

In case you missed it, RC2 is on slashdot.org too: http://slashdot.org/article.pl?sid=01/08/13/1811241 BTW Gian-Carlo Pascutto wrote on /. that RC3 should appear very soon (in a week or so)? Also, it looks like Wall Street Journal article is not available on-line (at least to non-registered persons). If someone is registered or have a paper edition, please post this article somewhere so that we

a comparison between the two formats can be read at http://www.digit-life.com/articles/oggvslame/index.html . i first heard of this from Vorbis Extreme ( http://solair.eunet.yu/~aldov/ ). anyone see any problems with the review? -- noodlez: Karol Pietrzak GPG/PGP-KeyID: 0x3A1446A0 --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To

I am plotting subsets of my data, using ylim. This works fine, but the outer margin line widths of the plot are thin, due to clipping. If I include > trellis.par.set(clip=list(panel = "off")) then the outer margin line widths are fine, but the outlying data is visible. Is there any way of achieving both correct margin line widths and clipping of outlying data? Thanks, Dan Bebber

This is only a minor annoyance, but mouse wheel zooming on LNT graphs is pretty broken on at least OSX. It does not work correctly on Chrome, Safari or Firefox. On Safari and Chrome the zoom is way to sensitive, on Firefox, the page scrolls while mouse wheel zooming. This appears to be a limitation of the flot graphing package we use. Does LNT’s mouse wheel zooming work better for people Linux