Displaying 4 results from an estimated 4 matches for "46kb".
Did you mean:
16kb
2005 Feb 05
2
Problem installing Hmisc
What am I doing wrong?
> install.packages("Hmisc")
trying URL `http://cran.r-project.org/src/contrib/PACKAGES'
Content type `text/plain; charset=iso-8859-1' length 47565 bytes
opened URL
==================================================
downloaded 46Kb
trying URL `http://cran.r-project.org/src/contrib/Hmisc_3.0-1.tar.gz'
Content type `application/x-tar' length 453567 bytes
opened URL
==================================================
downloaded 442Kb
Delete downloaded files (y/N)?
The packages are in /tmp/Rtmp1911/Rinstdir77a4044d
Warn...
2005 Feb 05
2
Problem installing Hmisc (more info)
...hen I try to install:
> > install.packages("Hmisc")
> trying URL `http://cran.r-project.org/src/contrib/PACKAGES'
> Content type `text/plain; charset=iso-8859-1' length 47565 bytes
> opened URL
> ==================================================
> downloaded 46Kb
>
> trying URL `http://cran.r-project.org/src/contrib/Hmisc_3.0-1.tar.gz'
> Content type `application/x-tar' length 453567 bytes
> opened URL
> ==================================================
> downloaded 442Kb
>
> Delete downloaded files (y/N)?
>
> The pack...
2018 May 16
0
GlobalAddress lowering strategy
...or GlobalAddress values.
I was wondering whether anybody has looked into this sort of issue for
an in-tree or out-of-tree backend, or had any thoughts on addressing
it. The numbers for introducing performDAGCombine to the AArch64
backend certainly indicate that performing the combine is a net win
(46KB reduction in .text size of chromium), but it would interesting
to look at addressing cases where the combine is counterproductive.
## Appendix: example 1
For the following code snippet, folding the offset into the global is
ideal and AArch64 will choose to do so:
@foo = global [6 x i16] [i16 1, i...
2016 May 10
3
Opus encoding rate for very quiet noisefloor
...If you encode 10s of loud noise, you get similar bitrates.
As you encode quieter and quieter noise, the extra cost of using _AUDIO mode vs _VOIP goes up.
At the extreme, a 10s signal of white noise with amplitude of only 2 (16bit, 16kHz), I see a near doubling. The _VOIP encoded file is size 46KB, the _AUDIO encoded file is 69K.
Now this does make sense -- in an audio mode, you want faithful reproduction of very quiet signals (reverb tails, etc).
However, I wanted to ask the list if this is expected/known behaviour. I wonder if it is possible to engineer a scenario (using existing apis...