similar to: RC2 artifacts

After doing an informal (128k) listening test, I have concluded that I prefer Beta4 over RC2. The 16kHz low-pass on the RC2 encoder makes it sound like FM radio. Both encoders SEEM to have a couple of dB bump at 10kHz. JT --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to

When I use on my Win98 box: for %%1 in (*.wav) do oggenc.exe -q3.0 %%1 it truncates all the filenames to 8.3 format (e.g., YES-RE~1.ogg, YES-RE~2.ogg, etc.) I checked the --h, but missed instructions on keeping the long filenames. Anyone? -- Ciao for now, --EdB <edb@earthling.net> http://www.geocities.com/endered <p><p>--- >8 ---- List archives:

---- "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

Hello. That's what I've got from ld: /usr/lib/libxenguest.a(xg_private.o): In function `unlock_pages': (.text+0x490): multiple definition of `unlock_pages' /usr/lib/libxenctrl.a(xc_private.o):(.text+0x6a0): first defined here /usr/lib/libxenguest.a(xg_private.o): In function `lock_pages': (.text+0x4d0): multiple definition of `lock_pages'

I came across an interesting test sample the other day while trying to compress some of my music and trying out different encoders. You can grab the sample in question from here: http://www.animus-facticius.org drone_clip.zip is a 9 second clip of the track where the artifact is most apparent, drone_short.pac is a 1 minute clip of track. The sample is from the song "Drone" from

On 20/10/12 03:15, Michael Spencer wrote: > On Fri, Oct 19, 2012 at 2:55 AM, r4start <r4start at gmail.com> wrote: >> Hi all. >> >> While compiling next code >> @A = weak unnamed_addr constant { i32, i32, i32 } { i32 0, i32 0, i32 0 }, >> section ".data" >> was discovered that llc ignores weak linkage if we emit it in COFF object. >>

Getting closer... When emitting symbols, how do I set the symbol's value to the address of the current instruction? Do I need to emit a label in the current section and another that uses the former to point to the latter? If possible, a code sample would be very helpful. And probably questions for Tim, are these "section-relative" mapping symbols, as defined in 4.6.5.1 of the

Dear R community, I am a newbie to R and I am using lme() to analyzed a two way repeated measures ANCOVA on some data I have gathered. In producing some graphs based on the fixed effects I noticed that I get vary different results depending on how I order my levels in my factor statement (see code below). Now, I have read that different models treat data from the factor class

hi have problems to get an samba server up that offers shares for all without a password heres my smb.conf file located under /usr/local/samba/lib/smb.conf [global] netbios name = DEATHB server string = Samba %v on (%L) workgroup = LANSTRIKE encrypt passwords = yes security = share [homes] browseable = no [mp3] comment = lmh path = /var/glftpd/site/mp3/lame.r3mix/ browseable = yes read only =

Hi All, I know this must have been discussed around here a million times, but I really didn't find this info anywhere else and I'm on a deadline here. I already have an FC1 server with a working LDAP directory in production. The same server runs a Samba PDC, but not with LDAP functionality yet. All I need to know right now is if I have to include some standard user and group

Hi David, On Thu, Jun 7, 2012 at 10:17 AM, Fan Dawei <fandawei.s at gmail.com> wrote: > Could you please tell me more about $a, $t and $d symbols? How these symbols > are used to define different regions? Where I can find this symbols in ELF > object file? At the start of each range of ARM code, an assembler or compiler should produce a "$a" symbol with that address, and

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

> From: Jack Moffitt [mailto:jack@icecast.org] > > So in the very near future, I don't think that there will be any > non-vorbis capable players. And for the most part, I think Vorbis will > be included in most players, though I have little hope that Microsoft > will allow Vorbis to stand side-by-side with WMA. There is a big difference between having a codec available for

Hello All, As you can see below I am having a problem checking for updates. This happens repeatedly. I have to kill the process then rerun. I have tried "yum clean all" but no joy - the process hangs again on "extras" - see second listing below. Suggestions? Dave [root at cserver ~]# yum check-update Loaded plugins: fastestmirror, priorities Loading mirror speeds from

On Jun 7, 2012, at 7:53 AM, Fan Dawei <fandawei.s at gmail.com> wrote: > Hi Tim, > > Thanks a lot for your help! I'm very grateful. > > libc.so is a prelinked library, I'll build a non-prelinked one and have another try. > > I'm now at the start of a binary translation project. I want to convert ARM binary code [*] to llvm ir, which is then translated to

Hi Tim, Thanks a lot for your help! I'm very grateful. libc.so is a prelinked library, I'll build a non-prelinked one and have another try. I'm now at the start of a binary translation project. I want to convert ARM binary code [*] to llvm ir, which is then translated to binary for our mips like architecture. That's why I'm looking for a decoder for ARM binary. The

Compiling llvm on a linux/amd64 box produces: home/rafael/dev/llvm/build/Debug/lib/LLVMX86.o: In function `_X86CompilationCallback': (.text+0x316fe): undefined reference to `_X86CompilationCallback2' /home/rafael/dev/llvm/build/Debug/lib/LLVMX86.o: In function `llvm::X86JITInfo::getLazyResolverFunction(void* (*)(void*))': /home/rafael/dev/llvm/cvs/lib/Target/X86/X86JITInfo.cpp:219:

That depends on how you define "one ARM instruction." It's not a clear cut thing. For example, is "add r1, r2, r3" the same ARM instruction as "add r1, r2, #4"? What is a distinct instruction and what's a variant encoding of the same instruction is often entirely a matter of convenience. -Jim On Jun 8, 2012, at 6:40 AM, Fan Dawei <fandawei.s at

Hi Jim, Thanks for reply. I'm sorry I didn't make myself clear enough. The MCInst created by MCDisassembler depends on the instructions defined in td files. These instructions do not have a one to one mapping to ARM instructions. There are usually one or more instructions defined in the td file correspond to one actual ARM instruction. Thanks, David On Thu, Jun 7, 2012 at 1:27 PM, Jim

Hi all, I just came across the following page: http://r3mix.net In the "News" section there is a fairly negative critique of Vorbis; especially it is mentioned that Vorbis "has terrible masking problems". There is also a Vorbis-encoded frequency sweep which shows strong deficiencies at high frequencies, but I suppose this is due to the quite low bitrate of the distributed