similar to: Ogg encapsulation...

FYI, the Ogg Opus encapsulation is now RFC 7845: https://tools.ietf.org/html/rfc7845 -------- Forwarded Message -------- Subject: [codec] RFC 7845 on Ogg Encapsulation for the Opus Audio Codec Date: Fri, 29 Apr 2016 19:47:28 -0700 (PDT) From: rfc-editor at rfc-editor.org To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org CC: drafts-update-ref at iana.org, codec at ietf.org, rfc-editor at

When pass :cache param to ActionDispatch::Session::MemCacheStore, it should be removed from options, otherwise it remains "published". This violates the OOP encapsulation principle. I created a LH ticket with a patch http://bit.ly/cGDaWs Luca -- lucaguidi.com twitter.com/jodosha -- You received this message because you are subscribed to the Google Groups "Ruby on Rails:

Hi, as some IPSec users might be worried about the "BSD derived RFC3173 IPComp encapsulation will expand arbitrarily nested payload" from http://seclists.org/fulldisclosure/2011/Apr/0 , here's some braindump: To be affected it's believed that you need to 1) manually compile in IPSEC (not done in GENERIC or the release), 2) have an entry for ipcomp in your security

Has there been any discussion of ICMP encapsulation in cases where UDP fails? -------------- next part -------------- A non-text attachment was scrubbed... Name: rhammond.vcf Type: text/x-vcard Size: 234 bytes Desc: not available URL: <http://www.tinc-vpn.org/pipermail/tinc-devel/attachments/20150619/6ba98a4d/attachment.vcf>

Hi everyone, Has someone tried the new GENEVE protocol ? http://datatracker.ietf.org/doc/draft-gross-geneve/ It is included in last kernel versions. May it be a "replacement" of Tinc ? What are the advantages/drawbacks of each ?

Hi All, I'm new to R from a C and Octave/Matlab background. I am trying to construct some classes in R to which I want to attach pieces of data. First, is attr(obj, 'member name') <- data the accepted way of doing this? Second, having attached member data with attr is there anything wrong with accessing it by the asperand (@), i.e. > t = "" > attr(t,

(sending this publicly so the discussion about this is in the open) Hi OggK, all, OggK, you've probably seen that the bug in Firefox for adding Kate support has been closed as WONTFIX: https://bugzilla.mozilla.org/show_bug.cgi?id=481529 I've just posted a reply there mentioning how I envisage in-band WebVTT support to be provided through Kate. I want to ask your opinion. In case you

it's good you brought this up, I want to finalize the Ogg FLAC bitstream mapping and add it to the docs. currently the way it is done in flac 1.1.0 is not ideal and probably should change. --- Arc Riley <arc@Xiph.org> wrote: > I've been implementing Ogg FLAC support in an editor I'm working on, > and > I must admit to being frustrated by the lack of support for the

?Hello everybody, I'm working on the "Use difftime for time comparison" bug (#313634). Charles directed me to the other one "Use monotonic clock for monitoring" attended to by Baruch; I believe that's very good idea, however I'd use a bit more encapsulated & general approach: 1/ I'd create an opaque timer type and its get/set/cmp/inc/dec etc interface

Dear R users, I have two related questions about scoping and data encapsulation. One is fairly specific - I am looking at "scoping.R" which is used in demo(scoping) - it's an example of lexical scoping and encapsulation. Where is the 'total' stored? It is not an attribute in 'ross' or 'robert' however, functions like balance() have access to it. Is it more

I have been developing some directshow filters for ogg, and vorbis and speex... currently i have an ogg demux filter and a speex/vorbis decoding filter. In this pre-release only vorbis is operational... but the speex decoder is pretty much done... i jsut need to tweak the demux filter so that it can negotiate a speex connection with the other filter. Just though some people might find them useful

I've been implementing Ogg FLAC support in an editor I'm working on, and I must admit to being frustrated by the lack of support for the codec on the Ogg layer... and this is more than lacking granulepos. The codec's I've worked with, and my own (Writ), use Page 0 for general information about the codec. Specifically, the samplerate, bitrate, quality, number of channels, all

i'm trying to build ices0.4 and vorbis-tools 1.0.1 with flac 1.1.1. Neither seems happy, hence the crossposting (sorry). ICES0.4 --- ices refuses to see the libFLAC library, even if i specify --with-flac=/usr/local/lib (or even just --with-flac=/usr/local/, as the configure script seems to look in the lib and include subdirectories of the specified path?). i get a configure error:

i'm trying to build ices0.4 and vorbis-tools 1.0.1 with flac 1.1.1. Neither seems happy, hence the crossposting (sorry). ICES0.4 --- ices refuses to see the libFLAC library, even if i specify --with-flac=/usr/local/lib (or even just --with-flac=/usr/local/, as the configure script seems to look in the lib and include subdirectories of the specified path?). i get a configure error:

Hi, We needed a vorbis decoder that operated differently from the approach taken libvorbisfile. So I sat down, looked through the docs, and the sample decoder that come with libvorbis and wrote our own. Since I couldn't find any docs for the API for libvorbis itself, I've written some. It details all the steps you need to go through to write a _basic_ reusable decoder library using

/usr/bin/ld: bad -rpath option collect2: ld returned 1 exit status make[4]: *** [libFLAC.la] Error 1 --- flac-1.1.2/src/libFLAC/Makefile.in.orig 2005-02-04 21:23:37.000000000 -0500 +++ flac-1.1.2/src/libFLAC/Makefile.in 2006-04-30 20:30:00.000000000 -0400 @@ -399,7 +399,7 @@ rm -f "$${dir}/so_locations"; \ done libFLAC.la: $(libFLAC_la_OBJECTS)

On Mon, 10 Jan 2005, Ralph Giles wrote: > As such it's an incompatible change, for which you should also > zero the 'age' field. So 1.1.1-beta1 should have been 2:0:0, > not 2:0:1. [...] > Yes, I agree. The numbering is all about coexisting installs of the > various versions. Ok. I need to know what to do about this... is 1.1.2 with fixed sonames just around the

On Mon, Jan 10, 2005 at 09:37:18PM -0800, Josh Coalson wrote: > as far as I can piece together, the last releases went like: > > FLAC release libOggFLAC went to > ------------- ------------------------------------------ > 1.1.0 1:2:0 from 1:1:0 (code changes only I think) > 1.1.1-beta1 2:0:1 from 1:2:0 (some i'faces added, some changed) > 1.1.1

Hi, I'm in the process of switching over to Asterisk from Alchemy kit and have hit a stumbling block. We're in the UK and use ISDN. At the moment we don't accept calls from withheld numbers (we just play them a message), but do accept calls from unavailable numbers. There doesn't seem to be any way for me to differentiate between the two number types in Asterisk (chan_CAPI) -

On a BT line, how do I determine whether the number on an incoming call has been deliberately withheld (by dialling 141) or is merely unavailable (e.g. because it originated from overseas or passed through some ancient switching equipment) ? In the first case, I want the caller to be played a message to the effect that we are not at home to anonymous cowards but if their business is