<div dir="ltr"><span style="font-size:12.727272033691406px;font-family:arial,sans-serif">Dear Christian van Bijleveld,</span><div><font face="arial, sans-serif"><br></font></div><div><span style="font-family:arial,sans-serif">You can use any of the below DSPs of Texas Instruments</span><font face="arial, sans-serif"><br>
</font></div><div><font face="arial, sans-serif">1. TMS320C674x - This supports floating point implementation of opus</font></div><div><span style="font-family:arial,sans-serif">2. TMS320C66x - This supports both floating and fixed point implementations</span></div>
<div><font face="arial, sans-serif">3. </font><span style="font-family:arial,sans-serif">TMS320C64x - This supports only fixed point implementation</span></div><div><br></div><div><img src="https://app.yesware.com/t/892cff5bd6ead7a3ef0e24a1a392aa4d078aeaaf/5f0dcb7a59c94d3ede28a0463559e1fe/spacer.gif" style="border: 0px; width: 1px; height: 1px;"><img src="http://app.yesware.com/t/892cff5bd6ead7a3ef0e24a1a392aa4d078aeaaf/5f0dcb7a59c94d3ede28a0463559e1fe/spacer.gif" style="border: 0px; width: 1px; height: 1px;"></div>
<div>Regards,</div><div>Mahantesh</div><img src="https://app.yesware.com/t/892cff5bd6ead7a3ef0e24a1a392aa4d078aeaaf/fc4c51c293fa8ed63c4b807b7f087f26/spacer.gif" style="border: 0px; width: 1px; height: 1px;"><img src="http://app.yesware.com/t/892cff5bd6ead7a3ef0e24a1a392aa4d078aeaaf/fc4c51c293fa8ed63c4b807b7f087f26/spacer.gif" style="border: 0px; width: 1px; height: 1px;"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, May 13, 2013 at 10:12 PM, <span dir="ltr"><<a href="mailto:opus-request@xiph.org" target="_blank">opus-request@xiph.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Send opus mailing list submissions to<br>
<a href="mailto:opus@xiph.org">opus@xiph.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.xiph.org/mailman/listinfo/opus" target="_blank">http://lists.xiph.org/mailman/listinfo/opus</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:opus-request@xiph.org">opus-request@xiph.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:opus-owner@xiph.org">opus-owner@xiph.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of opus digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. opus_demo produces garbage (Hermann Weber)<br>
2. Re: opus_demo produces garbage (Jean-Marc Valin)<br>
3. Re: opus_demo produces garbage (Hermann Weber)<br>
4. Exact audio position (Hermann Weber)<br>
5. Quality difference between opus_demo.exe and opusenc.exe<br>
(Hermann Weber)<br>
6. OPUS in embedded platform (van Bijleveld Christian (ST-CO/ENG1.3))<br>
7. Re: opus file trimming/clipping (Matt Ruck)<br>
8. Re: Exact audio position (Ian Malone)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 13 May 2013 07:43:55 +0200<br>
From: Hermann Weber <<a href="mailto:hermie.weber@gmx.de">hermie.weber@gmx.de</a>><br>
Subject: [opus] opus_demo produces garbage<br>
To: <a href="mailto:opus@xiph.org">opus@xiph.org</a><br>
Message-ID: <<a href="mailto:51907D9B.50803@gmx.de">51907D9B.50803@gmx.de</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hello!<br>
<br>
I am running opus_demo.exe with the following cmds:<br>
<br>
-e audio 48000 1 16 -cbr m:\test\test1.raw m:\test\test1.opus<br>
<br>
When I open the .opus file with a hex editor, I see only<br>
<br>
00000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000<br>
<br>
This pattern repeats over and over again.<br>
<br>
What might go wrong here?<br>
<br>
Greetings,<br>
Hermann<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 13 May 2013 02:04:42 -0400<br>
From: Jean-Marc Valin <<a href="mailto:jmvalin@jmvalin.ca">jmvalin@jmvalin.ca</a>><br>
Subject: Re: [opus] opus_demo produces garbage<br>
To: Hermann Weber <<a href="mailto:hermie.weber@gmx.de">hermie.weber@gmx.de</a>><br>
Cc: <a href="mailto:opus@xiph.org">opus@xiph.org</a><br>
Message-ID: <<a href="mailto:5190827A.1090305@jmvalin.ca">5190827A.1090305@jmvalin.ca</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
What you're looking at is the compressed result of trying to encode your<br>
file at 16 *bits* per second (0.016 kbit/s).<br>
<br>
Jean-Marc<br>
<br>
On 05/13/2013 01:43 AM, Hermann Weber wrote:<br>
> Hello!<br>
><br>
> I am running opus_demo.exe with the following cmds:<br>
><br>
> -e audio 48000 1 16 -cbr m:\test\test1.raw m:\test\test1.opus<br>
><br>
> When I open the .opus file with a hex editor, I see only<br>
><br>
> 00000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000<br>
><br>
> This pattern repeats over and over again.<br>
><br>
> What might go wrong here?<br>
><br>
> Greetings,<br>
> Hermann<br>
><br>
> _______________________________________________<br>
> opus mailing list<br>
> <a href="mailto:opus@xiph.org">opus@xiph.org</a><br>
> <a href="http://lists.xiph.org/mailman/listinfo/opus" target="_blank">http://lists.xiph.org/mailman/listinfo/opus</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 13 May 2013 08:16:59 +0200<br>
From: Hermann Weber <<a href="mailto:hermie.weber@gmx.de">hermie.weber@gmx.de</a>><br>
Subject: Re: [opus] opus_demo produces garbage<br>
To: Jean-Marc Valin <<a href="mailto:jmvalin@jmvalin.ca">jmvalin@jmvalin.ca</a>><br>
Cc: <a href="mailto:opus@xiph.org">opus@xiph.org</a><br>
Message-ID: <<a href="mailto:5190855B.8060304@gmx.de">5190855B.8060304@gmx.de</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Okay, got it, thanks.<br>
<br>
opus_demo.exe solved all my problems, I think.<br>
Good sample code.<br>
<br>
Thanks.<br>
Hermie<br>
<br>
Am 13.05.2013 08:04, schrieb Jean-Marc Valin:<br>
> What you're looking at is the compressed result of trying to encode your<br>
> file at 16 *bits* per second (0.016 kbit/s).<br>
><br>
> Jean-Marc<br>
><br>
> On 05/13/2013 01:43 AM, Hermann Weber wrote:<br>
>> Hello!<br>
>><br>
>> I am running opus_demo.exe with the following cmds:<br>
>><br>
>> -e audio 48000 1 16 -cbr m:\test\test1.raw m:\test\test1.opus<br>
>><br>
>> When I open the .opus file with a hex editor, I see only<br>
>><br>
>> 00000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000007800000001000000<br>
>><br>
>> This pattern repeats over and over again.<br>
>><br>
>> What might go wrong here?<br>
>><br>
>> Greetings,<br>
>> Hermann<br>
>><br>
>> _______________________________________________<br>
>> opus mailing list<br>
>> <a href="mailto:opus@xiph.org">opus@xiph.org</a><br>
>> <a href="http://lists.xiph.org/mailman/listinfo/opus" target="_blank">http://lists.xiph.org/mailman/listinfo/opus</a><br>
>><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Mon, 13 May 2013 10:45:00 +0200<br>
From: Hermann Weber <<a href="mailto:hermie.weber@gmx.de">hermie.weber@gmx.de</a>><br>
Subject: [opus] Exact audio position<br>
To: <a href="mailto:opus@xiph.org">opus@xiph.org</a><br>
Message-ID: <<a href="mailto:5190A80C.6020201@gmx.de">5190A80C.6020201@gmx.de</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hello!<br>
<br>
I need to extract audio data at a certain position in respect to the<br>
original audio data.<br>
<br>
Is the "-cbr" switch meant to ensure that data can be found on a<br>
specific position?<br>
<br>
I want to be able to predict where certain audio can be found in the<br>
encoded data.<br>
<br>
An example:<br>
If you put 10 apples into a box and then compress the box, you will not<br>
be able to predict where apple C can be found in the box.<br>
Perhaps apple B could be compressed more than apple C, and now the<br>
"position" of apple C is not predictable anymore.<br>
This is exactely NOT what I want :-)<br>
<br>
Greetings,<br>
Hermann<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 13 May 2013 13:24:06 +0200<br>
From: Hermann Weber <<a href="mailto:hermie.weber@gmx.de">hermie.weber@gmx.de</a>><br>
Subject: [opus] Quality difference between opus_demo.exe and<br>
opusenc.exe<br>
To: <a href="mailto:opus@xiph.org">opus@xiph.org</a><br>
Message-ID: <<a href="mailto:5190CD56.80103@gmx.de">5190CD56.80103@gmx.de</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hello!<br>
<br>
I encoded a voice file (48kHz) with opusbin\opusenc.exe with the<br>
standard settings and decoded it.<br>
The output was amazing. I could not hear any loss at all.<br>
<br>
Then i encoded the same file with opus_demo.exe and standard settings<br>
and then decoded it.<br>
The output had a sizzling noise, even when I used full bandwidth.<br>
<br>
I think I have played around with any of the settings in opus_demo.exe,<br>
but I just can not get these amazing results as with opusbin\opusenc.exe.<br>
<br>
What may I have missed?<br>
<br>
Thank you.<br>
<br>
Hermann<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Mon, 13 May 2013 14:57:55 +0200<br>
From: "van Bijleveld Christian (ST-CO/ENG1.3)"<br>
<<a href="mailto:Christian.vanBijleveld@nl.bosch.com">Christian.vanBijleveld@nl.bosch.com</a>><br>
Subject: [opus] OPUS in embedded platform<br>
To: "<a href="mailto:opus@xiph.org">opus@xiph.org</a>" <<a href="mailto:opus@xiph.org">opus@xiph.org</a>><br>
Message-ID:<br>
<<a href="mailto:8E99D2CE27782C4BA15262EE04CE7AA37952CEC3E9@SI-MBX18.de.bosch.com">8E99D2CE27782C4BA15262EE04CE7AA37952CEC3E9@SI-MBX18.de.bosch.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hello,<br>
<br>
<br>
I am interested in porting OPUS to an embedded platform. The idea is that the encoder and decoder will run on different processors. In order to choose the proper platform, I need an estimate of the resources which are needed for OPUS.<br>
<br>
I read the following in the OPUS wiki:<br>
<br>
"The Opus code base is written in C89 and should run on the vast majority of recent (and not so recent) CPUs. A few of the platforms on which Opus has been tested and is known to run include x86, x86-64, ARM, Itanium, Blackfin, and SPARC."<br>
Are there, or is it known, figures regarding the resources needed for OPUS to run on an embedded platform such as DSP or microprocessor? If exact figures are not available, but if anyone can give an indication about which type of platform is required at least, I would appreciate very much. I can image that the amount of resources for the encoder and the decoder may be different.<br>
<br>
Another question: does OPUS need the support of an Operating System or Real Time Kernel (ie; threads,...)?<br>
<br>
<br>
Met vriendelijke groeten | Best Regards,<br>
Christian van Bijleveld<br>
<br>
Bosch Security Systems BV<br>
Bosch Communications Systems, BL Public Address and Conference Systems (ST-CO/ENG1.3)<br>
P.O. Box 80 002<br>
5600 JB Eindhoven<br>
The Netherlands<br>
<a href="http://www.boschsecurity.com" target="_blank">www.boschsecurity.com</a><<a href="http://www.boschsecurity.com" target="_blank">http://www.boschsecurity.com</a>><br>
T. +31 (0)40 257 7076<br>
F. +31 (0)40 257 7091<br>
<a href="mailto:christian.vanbijleveld@nl.bosch.com">christian.vanbijleveld@nl.bosch.com</a><mailto:<a href="mailto:christian.vanbijleveld@nl.bosch.com">christian.vanbijleveld@nl.bosch.com</a>><br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.xiph.org/pipermail/opus/attachments/20130513/1e31aa21/attachment-0001.htm" target="_blank">http://lists.xiph.org/pipermail/opus/attachments/20130513/1e31aa21/attachment-0001.htm</a><br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Mon, 13 May 2013 09:17:45 -0400<br>
From: Matt Ruck <<a href="mailto:ultymatt@gmail.com">ultymatt@gmail.com</a>><br>
Subject: Re: [opus] opus file trimming/clipping<br>
To: Ralph Giles <<a href="mailto:giles@thaumas.net">giles@thaumas.net</a>><br>
Cc: opus <<a href="mailto:opus@xiph.org">opus@xiph.org</a>><br>
Message-ID:<br>
<CAPNsZ0wLhOjdZKPakGKqMKRop_=07TnWfKEBzcOk=<a href="mailto:e8XKJfmNg@mail.gmail.com">e8XKJfmNg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Thanks for your responses. I am potentially interested in developing a<br>
simple tool to trim a section of an Opus file, similar to the functionality<br>
of vcut or sox. What I would need to know is an estimate of how involved<br>
(difficulty and time commitment ) it would be for someone like me, with<br>
very little experience working with audio or programming in C (although I<br>
am much more comfortable with higher level languages). I have the source<br>
code for vcut for reference -- assuming that a similar tool for Opus could<br>
be based on this, could most of this be reused?<br>
<br>
<br>
On Thu, May 9, 2013 at 7:17 PM, Ralph Giles <<a href="mailto:giles@thaumas.net">giles@thaumas.net</a>> wrote:<br>
<br>
> On 13-05-09 2:06 PM, Matt Ruck wrote:<br>
><br>
> > Would trimming in another format like WAV or Ogg using existing tools,<br>
> > and then encoding to Opus be a good way accomplish trimming a sound<br>
> > track for Opus, and if so, what tools might be best (e.g., vcut was<br>
> > previously mentioned)?<br>
><br>
> Trimming WAV and then encoding to Opus would give you equivalent quality<br>
> and is something which can be done with existing tools. You can trim a<br>
> wave file with the command-line sox tool, or e.g. Audacity, a graphical<br>
> audio editor.<br>
><br>
> Something like 'sox in.wav trim 12:53.6 30 out.wav' will cut out 30<br>
> seconds of audio starting at 12 minutes 53.6 seconds into the file.<br>
><br>
> That said, if you want to try writing a lossless Opus trimmer, we'd be<br>
> happy to help. That' something the Ogg Opus draft which hasn't seen any<br>
> implementation feedback on.<br>
><br>
> -r<br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.xiph.org/pipermail/opus/attachments/20130513/7ce5d621/attachment-0001.htm" target="_blank">http://lists.xiph.org/pipermail/opus/attachments/20130513/7ce5d621/attachment-0001.htm</a><br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Mon, 13 May 2013 17:42:26 +0100<br>
From: Ian Malone <<a href="mailto:ibmalone@gmail.com">ibmalone@gmail.com</a>><br>
Subject: Re: [opus] Exact audio position<br>
To: <a href="mailto:opus@xiph.org">opus@xiph.org</a><br>
Message-ID:<br>
<<a href="mailto:CAL3-7MqRv-Ku-uHYTfH0%2Bqt3KZyK3_bP1hHt5mW5O--rCfP_WQ@mail.gmail.com">CAL3-7MqRv-Ku-uHYTfH0+qt3KZyK3_bP1hHt5mW5O--rCfP_WQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On 13 May 2013 09:45, Hermann Weber <<a href="mailto:hermie.weber@gmx.de">hermie.weber@gmx.de</a>> wrote:<br>
<br>
> Hello!<br>
><br>
> I need to extract audio data at a certain position in respect to the<br>
> original audio data.<br>
><br>
> Is the "-cbr" switch meant to ensure that data can be found on a<br>
> specific position?<br>
><br>
> I want to be able to predict where certain audio can be found in the<br>
> encoded data.<br>
><br>
> An example:<br>
> If you put 10 apples into a box and then compress the box, you will not<br>
> be able to predict where apple C can be found in the box.<br>
> Perhaps apple B could be compressed more than apple C, and now the<br>
> "position" of apple C is not predictable anymore.<br>
> This is exactely NOT what I want :-)<br>
><br>
><br>
><br>
(Oops, replied off-list by mistake)<br>
<br>
The encapsulation records this information, for Opus in Ogg you want<br>
'granule position':<br>
<a href="http://tools.ietf.org/html/draft-ietf-codec-oggopus-00#section-4" target="_blank">http://tools.ietf.org/html/draft-ietf-codec-oggopus-00#section-4</a><br>
<a href="https://wiki.xiph.org/GranulePosAndSeeking" target="_blank">https://wiki.xiph.org/GranulePosAndSeeking</a><br>
<br>
I'm less familiar with RTP, but I think the RTP timestamp is probably the<br>
equivalent thing:<br>
<a href="http://tools.ietf.org/html/draft-spittka-payload-rtp-opus-03" target="_blank">http://tools.ietf.org/html/draft-spittka-payload-rtp-opus-03</a><br>
<br>
<br>
<br>
--<br>
imalone<br>
<a href="http://ibmalone.blogspot.co.uk" target="_blank">http://ibmalone.blogspot.co.uk</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.xiph.org/pipermail/opus/attachments/20130513/4a30dc2e/attachment.htm" target="_blank">http://lists.xiph.org/pipermail/opus/attachments/20130513/4a30dc2e/attachment.htm</a><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
opus mailing list<br>
<a href="mailto:opus@xiph.org">opus@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/opus" target="_blank">http://lists.xiph.org/mailman/listinfo/opus</a><br>
<br>
<br>
End of opus Digest, Vol 52, Issue 12<br>
************************************<br>
</blockquote></div><br></div><font face="yw-892cff5bd6ead7a3ef0e24a1a392aa4d078aeaaf-9a1b315e516fd340b932f2a8d3362c94--tom"></font></div>