search for: sonusnet

I downloaded test vectors from opus-codec.org site. The site indicated that the test files are intended for verifying that the Opus decoders are operating properly. I assume I could also use them to verify my encoder implementation, right? For example, use testvector01.dec as input to my encoder and compare its output bitstream with the corresponding testvector01.bit bitstream file. Any idea

...enjamin.m.schwartz at gmail.com [mailto:benjamin.m.schwartz at gmail.com] On Behalf Of Benjamin Schwartz Sent: Sunday, November 10, 2013 1:53 PM To: Wang, Chris Cc: opus at xiph.org Subject: Re: [opus] Questions Regarding Opus Test Vectors On Sun, Nov 10, 2013 at 10:41 AM, Wang, Chris <cwang at sonusnet.com<mailto:cwang at sonusnet.com>> wrote: I downloaded test vectors from opus-codec.org<http://opus-codec.org> site. The site indicated that the test files are intended for verifying that the Opus decoders are operating properly. I assume I could also use them to verify my encoder...

Set in to aumix rec from lin in Saludos -----Mensaje original----- De: Todd Goodman [mailto:tgoodman@sonusnet.com] Enviado el: jueves 29 de marzo de 2001 16:31 Para: icecast@xiph.org Asunto: Re: [icecast] Little Liveice Help Make sure you select line-in as the record source with aumix. This is different from the record levels. Todd * Abhijit Joshi <jabhice@hotmail.com> [010329 13:19]: > Hi, &g...

On Sun, Nov 10, 2013 at 10:41 AM, Wang, Chris <cwang at sonusnet.com> wrote: > I downloaded test vectors from opus-codec.org site. The site indicated > that the test files are intended for verifying that the Opus decoders are > operating properly. I assume I could also use them to verify my encoder > implementation, right? For example, use te...

Previously I mentioned some problems I was having getting LiveIce and Icecast working. Everything is working so I wanted to get the archives updated with the solutions. The first was just my player I was streaming to needed a much larger buffer configured (stupid, but I'm just starting up with streaming). The problem I had with LiveIce streams being unlistenable was due to the wrong input

Tested DTX feature in Opus 1.0.2 and 1.1 for 20, 40, and 60ms frame size. They all generated only one encoded frame every 400ms during silence period as expected. However, for 10 ms frame size, the DTX period was 200ms instead. Has anyone else experienced the same? Thanks, Chris Wang -------------- next part -------------- An HTML attachment was scrubbed... URL:

* Andrew M. Wu <andrewwu@Princeton.EDU> [010419 03:49]: > Hi all, > > I've been trying to compile and re-compile ices-0.0.1beta5 with lame > support. > > I've downloaded the source to lame-3.88beta and compiled it and installed > it. The configure script allows for the compilation of a libmp3lame.a > and libmp3lame.la, but not libmp3lame.so (in the INSTALL

Thanks Jean-Marc and Benjamin for the answers. One follow-up question. If I use a repacketizer as Jean-Marc suggested by combining two 60ms frames to form a 120ms frame, without extracting individual frames and using a new TOC, I would need to have a "de-packetizer" that does the exact opposite of repacketizer. De-packetizer would need to separate this 120ms frame into two 60ms frames

I'm having a couple problems trying to get Icecast and LiveIce set up on a Linux 7.0 system. I'm running Icecast 1.3.10 without a config file (using all defaults). I can use shout to stream to it and connect to it from a windows machine running WinAmp. It works OK except winamp stops every few seconds and tells me that it's buffering. It buffers for a few seconds and then plays a

Hi Jean-Marc, A simpler question. How does opus_encode() generate packets of 20ms (SILK-only or Hybrid)? Concatenating two 10ms frames or doing it straight with just one 20ms frame?

I'm sorry, I meant RedHat 7.0 of course. That machine is running kernel 2.2.14-5.0. I've tried the XMMS LiveIce plugin and XMMS cores as soon as it's enabled. Thanks for the info on buffering. Todd * David S. Geirsson <andmann@andmann.eu.org> [010320 09:49]: > First of all, please define "Linux 7.0", since the last time I knew linux > was only up to 2.4. It