You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
|
Feb
(17) |
Mar
(5) |
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
(11) |
| 2007 |
Jan
(2) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(7) |
Jun
(3) |
Jul
(5) |
Aug
(21) |
Sep
(7) |
Oct
(4) |
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(5) |
Mar
(4) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(6) |
Dec
(3) |
| 2009 |
Jan
(3) |
Feb
(2) |
Mar
|
Apr
(3) |
May
(1) |
Jun
(8) |
Jul
(8) |
Aug
(19) |
Sep
(23) |
Oct
(20) |
Nov
(5) |
Dec
(9) |
| 2010 |
Jan
(16) |
Feb
(20) |
Mar
(5) |
Apr
(1) |
May
(2) |
Jun
(10) |
Jul
(5) |
Aug
(3) |
Sep
(1) |
Oct
(2) |
Nov
(8) |
Dec
(2) |
| 2011 |
Jan
(7) |
Feb
(1) |
Mar
(3) |
Apr
(4) |
May
(4) |
Jun
|
Jul
|
Aug
(15) |
Sep
(5) |
Oct
(4) |
Nov
(6) |
Dec
(2) |
| 2012 |
Jan
(4) |
Feb
(7) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
(3) |
Dec
|
| 2013 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
(5) |
May
(1) |
Jun
(6) |
Jul
|
Aug
(6) |
Sep
(5) |
Oct
(4) |
Nov
(4) |
Dec
(5) |
| 2014 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
(6) |
Oct
(5) |
Nov
(22) |
Dec
(5) |
| 2015 |
Jan
(5) |
Feb
(5) |
Mar
(1) |
Apr
(2) |
May
(5) |
Jun
(6) |
Jul
(5) |
Aug
|
Sep
(5) |
Oct
(2) |
Nov
(5) |
Dec
(1) |
| 2016 |
Jan
(1) |
Feb
(2) |
Mar
(6) |
Apr
(4) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
(4) |
Mar
(1) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(1) |
Dec
|
| 2018 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2021 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
|
2
|
3
|
4
|
5
|
6
|
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
|
21
(3) |
22
(2) |
23
|
24
|
25
|
26
|
27
|
|
28
|
29
|
30
|
31
|
|
|
|
|
From: Henri H. <he...@or...> - 2010-03-22 15:07:15
|
Gonzalo, This is now fixed in Svn. Thanks for reporting it. Henri _____ From: Gonzalo Brusella [mailto:gbr...@gm...] Sent: 02 February 2010 07:42 To: Henri Herscher Cc: it...@br...; ore...@li... Subject: Re: [Oreka-devel] audio device build errors Also found another bug on the SoundDevicePlugin: You need to change this: chunkRef->SetBuffer(rightBuffer, sizeof(short)*framesPerBuffer, details); for this: chunkRef->SetBuffer(rightBuffer, details, sizeof(short)*framesPerBuffer); on 3 places (The parameter order changes). Gonzalo A. Brusella go...@br... http://www.brusella.com.ar On Tue, Feb 2, 2010 at 09:40, Gonzalo Brusella <gbr...@gm...> wrote: I've sent to the list the fixes for those errors: Gonzalo A. Brusella go...@br... http://www.brusella.com.ar On Mon, Feb 1, 2010 at 12:53, Henri Herscher <he...@or...> wrote: . We will look at it at some point, send us a patch if you manage to compile it. You do not need the sound device plugin if all you want is VoIP recording. |
|
From: Henri H. <he...@or...> - 2010-03-22 15:02:43
|
Andrew, We have changed this because Oreka supports more than just VoIP recording, so TCP port number does not have any meaning for other technologies. We will soon reintroduce the ability to report on TCP port via the TapeFileNaming mechanism for more flexibility. Henri -----Original Message----- From: VG [mailto:vg...@ma...] Sent: 21 March 2010 09:57 To: oreka-devel Cc: oreka-user Subject: [Oreka-user] port number in Oreka 1.2 Hi all, I have just upgraded the Oreka from previous version to Oreka 1.2 CapturePort field in tapelist.log has changed It only shows 3 capital letters as follows: capturePort=GYY capturePort=MDF etc. The value of the `portName` column in table orksegment also contains the same 3 capital letters: GYY MDF etc. But I need to get port number in its native numeric form! Captureport in previous version was an IP address plus port number, e.g. 10.10.10.123:23456 and value of the `recPortName` column in table recPortName was an IP address plus port number, e.g. 10.10.10.123,23456 How can I get port number in in its native numeric form from Oreka 1.2? Thanks and regards, Andrew ---------------------------------------------------------------------------- -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Oreka-user mailing list Ore...@li... https://lists.sourceforge.net/lists/listinfo/oreka-user |
|
From: VG <vg...@ma...> - 2010-03-21 13:56:47
|
Hi all, I have just upgraded the Oreka from previous version to Oreka 1.2 CapturePort field in tapelist.log has changed It only shows 3 capital letters as follows: capturePort=GYY capturePort=MDF etc. The value of the `portName` column in table orksegment also contains the same 3 capital letters: GYY MDF etc. But I need to get port number in its native numeric form! Captureport in previous version was an IP address plus port number, e.g. 10.10.10.123:23456 and value of the `recPortName` column in table recPortName was an IP address plus port number, e.g. 10.10.10.123,23456 How can I get port number in in its native numeric form from Oreka 1.2? Thanks and regards, Andrew |
|
From: VG <vg...@ma...> - 2010-03-21 13:04:56
|
Hi all, I have just upgraded the Oreka from previous version to Oreka 1.2 CapturePort field in tapelist.log has changed It only shows 3 capital letters as follows: capturePort=GYY capturePort=MDF etc. The value of the `portName` column in table orksegment also contains the same 3 capital letters: GYY MDF etc. But I need to get port number in its native numeric form! Captureport in previous version was an IP address plus port number, e.g. 10.10.10.123:23456 and value of the `recPortName` column in table recPortName was an IP address plus port number, e.g. 10.10.10.123,23456 How can I get port number in in its native numeric form from Oreka 1.2? Thanks and regards, Andrew |
|
From: VG <vg...@ma...> - 2010-03-21 13:02:02
|
Hi all, I have just upgraded the Oreka from previous version to Oreka 1.2 CapturePort field in tapelist.log has changed It only shows 3 capital letters as follows: capturePort=GYY capturePort=MDF etc. The value of the `portName` column in table orksegment also contains the same 3 capital letters: GYY MDF etc. But I need to get port number in its native numeric form! Captureport in previous version was an IP address plus port number, e.g. 10.10.10.123:23456 and value of the `recPortName` column in table recPortName was an IP address plus port number, e.g. 10.10.10.123,23456 How can I get port number in in its native numeric form from Oreka 1.2? Thanks and regards, Andrew |