similar to: bitrtate peeling and lossless compression (UU2509787)

I just read some of the discussion on the list about 'bitrate peeling' and remembered an interview of Monty that I have read recently. In it he says that Vorbis uses MCDTs <sp> and that these are theoretically reversable. And now, I learn that theoretically we can use bitrate peeling to make smaller files from larger ones, and that leads to my question. Could I theoretically

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Fraunhoffer claims patents on other formats") and forwarded it to the appropriate personnel for processing.

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("[vorbis] Improve your stepfamily life") and forwarded it to the appropriate personnel for processing. To help us provide

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Announce: VCE v0.1.2") and forwarded it to the appropriate personnel for processing. To help us provide you

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Announce: VCE v0.1.2") and forwarded it to the appropriate personnel for processing. To help us provide you

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Announce: VCE v0.1.2") and forwarded it to the appropriate personnel for processing. To help us provide you

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Announce: VCE v0.1.2") and forwarded it to the appropriate personnel for processing. To help us provide you

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("[vorbis] VCE 0.1.3") and forwarded it to the appropriate personnel for processing. To help us provide you with the best

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Experimental info editor for winamp") and forwarded it to the appropriate personnel for processing. To help

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] OpenML, Khronos, and dmSDK") and forwarded it to the appropriate personnel for processing. To help us provide

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("[vorbis] INCREDIBLE MEGA EXPERIENCE!") and forwarded it to the appropriate personnel for processing. To help us provide

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("[vorbis] VorbisExt prerelease") and forwarded it to the appropriate personnel for processing. To help us provide you with

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] VorbisExt prerelease") and forwarded it to the appropriate personnel for processing. To help us provide you

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("[vorbis] VorbisExt 0.2.0") and forwarded it to the appropriate personnel for processing. To help us provide you with the

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] VorbisExt 0.2.0") and forwarded it to the appropriate personnel for processing. To help us provide you with

Hi, all; I'm new to R. Have been a SAS developer for over 20 years. Whenever I create a new table - you call them dataFrame objects - or modify an existing one, I like to open the table in a grid with horizontal and vertical sliders so that I can scan across the table and (especially) look at all four corners. If I made a gross error, it often shows up when I look at the corners of

I bought this UPS to use with NUT. I've used Belkin, APC, CyberPower, Best, Powerware upses with NUT on dozens of servers beginning with RHEL3. http://www.amazon.com/Tripp-Lite-Display-Protection-SMART1500LCDT/dp/B009TZTGWK Since this was advertised as USB HID, I didn't expect any problems. Bad idea (should have gotten the Cyberware with somewhat less runtime). Initially, it seems to

On 10/06/2016 07:26 PM, Lane Russell wrote: > ?? > Syslog after server loses sight of UPS: > Oct 6 17:29:01 kvm usbhid-ups[3529]: libusb_get_string: error sending > control message: Broken pipe > Oct 6 17:30:53 kvm upsd[3533]: Data for UPS [ups] is stale - check driver > Oct 6 17:30:57 kvm upsmon[3548]: Poll UPS [ups at localhost] failed - > Data stale > Oct 6 17:30:57

I have some things I'd like someone brighter than me to explain. #1. Add xxxx scripts. Everyone seems to put these scripts in their smb.conf. The add user and add machine make sense, and they work, but explain to me how the other scripts, such as add user to group, are supposed to work? When do they get called, etc.? I guess most of these involve the smbldap tools. #2. Here's my

This morning I see this in the syslog on our primary public DNS host. internal_send: 142.77.1.1#33950: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#35153: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#35644: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#49394: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#49816: Connection timed