You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by le...@technomicssolutions.com on 2015/01/21 20:46:39 UTC
Concerns regarding OpenMeeting Recording feature.
Hi,
I am not sure if this is the right mailbox to request advise. However this what I got when checked from the Apache Openmeeting page.
Let me come to my concern directly.
I have installed OpenMeeting with following version.
Version 3.0.3-RELEASE
Revision 1621852
It's working fine but when I am using "recording" feature of OpenMeeting, I am having a glitch.
Steps I used to replicate:
1, Open up OpenMetting and go to "whiteboard" room.
2, Download the .jnlp file to record the session. I use "icedtea" for recording feature.
3, I started a session and once clicked "stop recording", it takes considerable time to stop the session, Like 2 minutes for 30 seconds actual session.
4, The problem is, when I play the above 30 seconds video + audio session, 2 minutes dead paused session is showing after the actual video.
How can I avoid this. Please advise. If this is not the right mail list, kindly forward to the apt maillist.
Thanks in advance,
Leo Prince.
Re: Concerns regarding OpenMeeting Recording feature.
Posted by Maxim Solodovnik <so...@gmail.com>.
Actually server is not an issue in this case, this problem is on the client
:(
We are planning to improve situation in 3.0.5 (currently working on 3.0.4)
On Fri, Jan 23, 2015 at 9:58 PM, <le...@technomicssolutions.com> wrote:
> Hi Maxim,
>
> Sorry for bothering you. Could you please advise.. I have few more
> outstanding concerns but not that complicated.
>
> 1, whether I needed to increase the resources of OM server machine to get
> 5FPM or 10FPM feeds without the dead paused time.
> 2, I am currently using IcedTea.. is there any other sharing client
> available ? Can you name them, so that I can try them as well..
> 3, I am using 3.0.3 now.. Does any better sharing client in mind for 3.0.4
> ? Can an app upgrade will help to improve the situation..
>
> Regards,
> Leo Prince.
>
> January 23 2015 12:46 AM, leo@technomicssolutions.com wrote:
>
>
> Yeah.. my local machine is having pretty good resources..What my recent
> concern was whether I needed to increase the resources of OM server machine
> to get 5FPM or 10FPM feeds without the dead paused time.
>
> I am currently using IcedTea.. is there any other sharing client available
> ? Can you name them, so that I can try them as well..
> I am using 3.0.3 now.. Does any better sharing client in mind for 3.0.4 ?
> Can an app upgrade will help to improve the situation..
>
> Leo Prince
>
> January 23 2015 12:34 AM, "Maxim Solodovnik" <solomax666@gmail.com
> <%22Maxim%20Solodovnik%22%20%3Csolomax666@gmail.com%3E>> wrote:
>
>
>
> actually client machine should be powerful enough to create better
> screen sharing
> We will try to improve screen sharing client
>
> On Fri, Jan 23, 2015 at 12:59 AM, <le...@technomicssolutions.com> wrote:
>
>
>
> Thanks Maxim.. That nearly worked out.. I was using the following specs
> before...
>
> Resolution : 1366x768
> Frame per second : 10
> Quality : High Quality
>
> It found worked out when I used the following specs..
>
> Resolution : 1050x768 ( of course it includes white board and camera feed )
> Quality : medium
> Frame Per Second : 2FPS
>
> However, medium quality is okay to visible when full screen ON but 2FPS is
> pretty slow.. When I used with 5FPS, it still having lag but obviously less
> compared when I used 10FPM earlier. What are your recommendations for
> server resources to use medium/high quality and 5/10 FPM..
>
> Currently it's a 4GB RAM server with 2 CPU.. Can this be sorted if we
> increase the CPU or any other resources ; As I think server can't handle
> processing tasks of 10 frames per second which caused the "dead lag"
> earlier which found fixed when used 2FPM..
>
> Please advise if this is an issue with the server resources or else..
>
> Regards,
> Leo Prince.
>
>
> January 22 2015 10:30 PM, "Maxim Solodovnik" <solomax666@gmail.com
> <%22Maxim%20Solodovnik%22%20%3Csolomax666@gmail.com%3E>> wrote:
>
>
> Actually when you stop recording all frames captured but not processed
> are being processed.
> I guess "dead paused session" is caused by stream lengths are differ: i.e.
> video captured by screen sharing is shorter than video captured by camera.
>
> I guess you set something like 30FPS full screen video
> can you try to decrease area being recorded and FPS
>
> On Thu, Jan 22, 2015 at 10:13 PM, <le...@technomicssolutions.com> wrote:
>
>
>
> Dear Maxim,
>
> Thank you for looking into this. We are not having any "exclamation" or
> "caution" symbol with the related recorded session. There are no errors any
> where but this issue is continue to go on.
>
> I have monitored the logs closely while performing a test recording
> session. When I started the recording session, the OM log shows plenty of
> lines and an example will be like this.
>
> =======================
>
> DEBUG 01-22 15:47:52.032 o.a.o.d.f.l.a.BaseStreamWriter:146 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream writer is still
> listening:: rec_64_stream_143_2015_01_22_15_45_45.flv
>
> =======================
>
> After I clicked on "stop recording", this sort of log entries continue to
> append to the log file with the status "Stream writer is still listening".
> After a while, it eventually stops and log entries changes. Please see the
> snippets of sample entries I observed.
>
> =======================
>
>
> DEBUG 01-22 15:47:52.562 o.a.o.r.FLVRecorderService:298
> [RTMPExecutor#TKDUJ1VLARWKE-1] - Stopping the stream :: New status ==
> STOPPING
>
>
>
> DEBUG 01-22 15:47:52.648 o.a.o.d.f.l.a.BaseStreamWriter:176 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream Status was:
> STOPPING has been written for: 142
>
>
>
> DEBUG 01-22 15:47:52.656 o.a.o.d.f.l.a.BaseStreamWriter:152 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: stream writer stopped
>
>
>
> DEBUG 01-22 15:47:52.663 o.a.o.r.FLVRecorderService:370
> [RTMPExecutor#TKDUJ1VLARWKE-1] - flvRecorderConverterTask
>
>
>
> DEBUG 01-22 15:47:52.728 o.a.o.c.BaseConverter:236 [taskExecutor-5] - ###
> processing metadata: 142
>
> DEBUG 01-22 15:47:52.740 o.a.o.c.BaseConverter:252 [taskExecutor-5] - FLV
> File Name: rec_64_stream_143_2015_01_22_15_45_45.flv Length: 997428
>
> DEBUG 01-22 15:47:52.752 o.a.o.u.p.ProcessHelper:104 [taskExecutor-5] -
> START stripAudioFromFLVs #################
>
> DEBUG 01-22 15:47:52.754 o.a.o.u.p.ProcessHelper:105 [taskExecutor-5] -
> /usr/local/bin/ffmpeg -y -i
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45.flv
> -af aresample=32k
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
>
>
>
> DEBUG 01-22 15:47:53.166 o.a.o.u9.p.ProcessHelper:105 [taskExecutor-5] -
> /usr/bin/sox
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_FULL_WAVE.wav
> pad 1.0 0.033
>
> DEBUG 01-22 15:47:53.166 o.a.o.u.p.ProcessHelper:106 [taskExecutor-5] -
> END addStartEndToAudio #################
>
> DEBUG 01-22 15:47:53.228 o.a.o.u.p.ProcessHelper:148 [taskExecutor-5] -
> exitVal: 0
>
> ==================================
>
> The above are just snippets only because entire log session is quite
> lengthy and nearly not affordable to send via mail. I observed the
> "Exitvalue" as 0. Does that makes any sense about our issue ?
>
> Please advise why our recording session actually stops after a while I
> clicked on "stop".. In addition to that, the "Stream Writer" is continue to
> listen until the "Stop" button in "IcedTea" turns to "Start" (Of course
> "stop" should have changed to "start" instantly when I clicked on it ).
>
> Is this an known issue with the OM 3.0.3.. can this be rectified with next
> upgrade or with latest build...
>
> Thanks in advance,
> Leo Prince.
>
> January 22 2015 9:29 AM, "Maxim Solodovnik" <solomax666@gmail.com
> <%22Maxim%20Solodovnik%22%20%3Csolomax666@gmail.com%3E>> wrote:
>
>
> this is correct mailing list :)
>
> do you have any errors in recording conversion? (small exclamation mark
> near recording in recordings tree)
> if yes what are the errors?
>
> On Thu, Jan 22, 2015 at 1:46 AM, <le...@technomicssolutions.com> wrote:
>
>
>
> Hi,
>
> I am not sure if this is the right mailbox to request advise. However this
> what I got when checked from the Apache Openmeeting page.
>
> Let me come to my concern directly.
>
> I have installed OpenMeeting with following version.
>
> Version 3.0.3-RELEASE
> Revision 1621852
>
> It's working fine but when I am using "recording" feature of OpenMeeting,
> I am having a glitch.
>
> Steps I used to replicate:
>
> 1, Open up OpenMetting and go to "whiteboard" room.
> 2, Download the .jnlp file to record the session. I use "icedtea" for
> recording feature.
> 3, I started a session and once clicked "stop recording", it takes
> considerable time to stop the session, Like 2 minutes for 30 seconds actual
> session.
> 4, The problem is, when I play the above 30 seconds video + audio session,
> 2 minutes dead paused session is showing after the actual video.
>
> How can I avoid this. Please advise. If this is not the right mail list,
> kindly forward to the apt maillist.
>
> Thanks in advance,
> Leo Prince.
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>
>
>
--
WBR
Maxim aka solomax
Re: Concerns regarding OpenMeeting Recording feature.
Posted by le...@technomicssolutions.com.
Hi Maxim,
Sorry for bothering you. Could you please advise.. I have few more outstanding concerns but not that complicated.
1, whether I needed to increase the resources of OM server machine to get 5FPM or 10FPM feeds without the dead paused time.
2, I am currently using IcedTea.. is there any other sharing client available ? Can you name them, so that I can try them as well..
3, I am using 3.0.3 now.. Does any better sharing client in mind for 3.0.4 ? Can an app upgrade will help to improve the situation..
Regards,
Leo Prince.
January 23 2015 12:46 AM, leo@technomicssolutions.com (mailto:leo@technomicssolutions.com) wrote:
Yeah.. my local machine is having pretty good resources..What my recent concern was whether I needed to increase the resources of OM server machine to get 5FPM or 10FPM feeds without the dead paused time.
I am currently using IcedTea.. is there any other sharing client available ? Can you name them, so that I can try them as well..
I am using 3.0.3 now.. Does any better sharing client in mind for 3.0.4 ? Can an app upgrade will help to improve the situation..
Leo Prince
January 23 2015 12:34 AM, "Maxim Solodovnik" wrote:
actually client machine should be powerful enough to create better screen sharing
We will try to improve screen sharing client
On Fri, Jan 23, 2015 at 12:59 AM, wrote:
Thanks Maxim.. That nearly worked out.. I was using the following specs before...
Resolution : 1366x768
Frame per second : 10
Quality : High Quality
It found worked out when I used the following specs..
Resolution : 1050x768 ( of course it includes white board and camera feed )
Quality : medium
Frame Per Second : 2FPS
However, medium quality is okay to visible when full screen ON but 2FPS is pretty slow.. When I used with 5FPS, it still having lag but obviously less compared when I used 10FPM earlier. What are your recommendations for server resources to use medium/high quality and 5/10 FPM..
Currently it's a 4GB RAM server with 2 CPU.. Can this be sorted if we increase the CPU or any other resources ; As I think server can't handle processing tasks of 10 frames per second which caused the "dead lag" earlier which found fixed when used 2FPM..
Please advise if this is an issue with the server resources or else..
Regards,
Leo Prince.
January 22 2015 10:30 PM, "Maxim Solodovnik" wrote:
Actually when you stop recording all frames captured but not processed are being processed.
I guess "dead paused session" is caused by stream lengths are differ: i.e. video captured by screen sharing is shorter than video captured by camera.
I guess you set something like 30FPS full screen video
can you try to decrease area being recorded and FPS
On Thu, Jan 22, 2015 at 10:13 PM, wrote:
Dear Maxim,
Thank you for looking into this. We are not having any "exclamation" or "caution" symbol with the related recorded session. There are no errors any where but this issue is continue to go on.
I have monitored the logs closely while performing a test recording session. When I started the recording session, the OM log shows plenty of lines and an example will be like this.
=======================
DEBUG 01-22 15:47:52.032 o.a.o.d.f.l.a.BaseStreamWriter:146 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream writer is still listening:: rec_64_stream_143_2015_01_22_15_45_45.flv
=======================
After I clicked on "stop recording", this sort of log entries continue to append to the log file with the status "Stream writer is still listening". After a while, it eventually stops and log entries changes. Please see the snippets of sample entries I observed.
=======================
DEBUG 01-22 15:47:52.562 o.a.o.r.FLVRecorderService:298 [RTMPExecutor#TKDUJ1VLARWKE-1] - Stopping the stream :: New status == STOPPING
DEBUG 01-22 15:47:52.648 o.a.o.d.f.l.a.BaseStreamWriter:176 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream Status was: STOPPING has been written for: 142
DEBUG 01-22 15:47:52.656 o.a.o.d.f.l.a.BaseStreamWriter:152 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: stream writer stopped
DEBUG 01-22 15:47:52.663 o.a.o.r.FLVRecorderService:370 [RTMPExecutor#TKDUJ1VLARWKE-1] - flvRecorderConverterTask
DEBUG 01-22 15:47:52.728 o.a.o.c.BaseConverter:236 [taskExecutor-5] - ### processing metadata: 142
DEBUG 01-22 15:47:52.740 o.a.o.c.BaseConverter:252 [taskExecutor-5] - FLV File Name: rec_64_stream_143_2015_01_22_15_45_45.flv Length: 997428
DEBUG 01-22 15:47:52.752 o.a.o.u.p.ProcessHelper:104 [taskExecutor-5] - START stripAudioFromFLVs #################
DEBUG 01-22 15:47:52.754 o.a.o.u.p.ProcessHelper:105 [taskExecutor-5] - /usr/local/bin/ffmpeg -y -i /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45.flv -af aresample=32k /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
DEBUG 01-22 15:47:53.166 o.a.o.u9.p.ProcessHelper:105 [taskExecutor-5] - /usr/bin/sox /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_FULL_WAVE.wav pad 1.0 0.033
DEBUG 01-22 15:47:53.166 o.a.o.u.p.ProcessHelper:106 [taskExecutor-5] - END addStartEndToAudio #################
DEBUG 01-22 15:47:53.228 o.a.o.u.p.ProcessHelper:148 [taskExecutor-5] - exitVal: 0
==================================
The above are just snippets only because entire log session is quite lengthy and nearly not affordable to send via mail. I observed the "Exitvalue" as 0. Does that makes any sense about our issue ?
Please advise why our recording session actually stops after a while I clicked on "stop".. In addition to that, the "Stream Writer" is continue to listen until the "Stop" button in "IcedTea" turns to "Start" (Of course "stop" should have changed to "start" instantly when I clicked on it ).
Is this an known issue with the OM 3.0.3.. can this be rectified with next upgrade or with latest build...
Thanks in advance,
Leo Prince.
January 22 2015 9:29 AM, "Maxim Solodovnik" wrote:
this is correct mailing list :)
do you have any errors in recording conversion? (small exclamation mark near recording in recordings tree)
if yes what are the errors?
On Thu, Jan 22, 2015 at 1:46 AM, wrote:
Hi,
I am not sure if this is the right mailbox to request advise. However this what I got when checked from the Apache Openmeeting page.
Let me come to my concern directly.
I have installed OpenMeeting with following version.
Version 3.0.3-RELEASE
Revision 1621852
It's working fine but when I am using "recording" feature of OpenMeeting, I am having a glitch.
Steps I used to replicate:
1, Open up OpenMetting and go to "whiteboard" room.
2, Download the .jnlp file to record the session. I use "icedtea" for recording feature.
3, I started a session and once clicked "stop recording", it takes considerable time to stop the session, Like 2 minutes for 30 seconds actual session.
4, The problem is, when I play the above 30 seconds video + audio session, 2 minutes dead paused session is showing after the actual video.
How can I avoid this. Please advise. If this is not the right mail list, kindly forward to the apt maillist.
Thanks in advance,
Leo Prince.
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
Re: Concerns regarding OpenMeeting Recording feature.
Posted by Maxim Solodovnik <so...@gmail.com>.
Actually server is not an issue in this case, this problem is on the client
:(
We are planning to improve situation in 3.0.5 (currently working on 3.0.4)
On Fri, Jan 23, 2015 at 1:16 AM, <le...@technomicssolutions.com> wrote:
> Yeah.. my local machine is having pretty good resources..What my recent
> concern was whether I needed to increase the resources of OM server machine
> to get 5FPM or 10FPM feeds without the dead paused time.
>
> I am currently using IcedTea.. is there any other sharing client available
> ? Can you name them, so that I can try them as well..
> I am using 3.0.3 now.. Does any better sharing client in mind for 3.0.4 ?
> Can an app upgrade will help to improve the situation..
>
> Leo Prince
>
> January 23 2015 12:34 AM, "Maxim Solodovnik" <solomax666@gmail.com
> <%22Maxim%20Solodovnik%22%20%3Csolomax666@gmail.com%3E>> wrote:
>
>
> actually client machine should be powerful enough to create better
> screen sharing
> We will try to improve screen sharing client
>
> On Fri, Jan 23, 2015 at 12:59 AM, <le...@technomicssolutions.com> wrote:
>
>
>
> Thanks Maxim.. That nearly worked out.. I was using the following specs
> before...
>
> Resolution : 1366x768
> Frame per second : 10
> Quality : High Quality
>
> It found worked out when I used the following specs..
>
> Resolution : 1050x768 ( of course it includes white board and camera feed )
> Quality : medium
> Frame Per Second : 2FPS
>
> However, medium quality is okay to visible when full screen ON but 2FPS is
> pretty slow.. When I used with 5FPS, it still having lag but obviously less
> compared when I used 10FPM earlier. What are your recommendations for
> server resources to use medium/high quality and 5/10 FPM..
>
> Currently it's a 4GB RAM server with 2 CPU.. Can this be sorted if we
> increase the CPU or any other resources ; As I think server can't handle
> processing tasks of 10 frames per second which caused the "dead lag"
> earlier which found fixed when used 2FPM..
>
> Please advise if this is an issue with the server resources or else..
>
> Regards,
> Leo Prince.
>
>
> January 22 2015 10:30 PM, "Maxim Solodovnik" <solomax666@gmail.com
> <%22Maxim%20Solodovnik%22%20%3Csolomax666@gmail.com%3E>> wrote:
>
>
> Actually when you stop recording all frames captured but not processed
> are being processed.
> I guess "dead paused session" is caused by stream lengths are differ: i.e.
> video captured by screen sharing is shorter than video captured by camera.
>
> I guess you set something like 30FPS full screen video
> can you try to decrease area being recorded and FPS
>
> On Thu, Jan 22, 2015 at 10:13 PM, <le...@technomicssolutions.com> wrote:
>
>
>
> Dear Maxim,
>
> Thank you for looking into this. We are not having any "exclamation" or
> "caution" symbol with the related recorded session. There are no errors any
> where but this issue is continue to go on.
>
> I have monitored the logs closely while performing a test recording
> session. When I started the recording session, the OM log shows plenty of
> lines and an example will be like this.
>
> =======================
>
> DEBUG 01-22 15:47:52.032 o.a.o.d.f.l.a.BaseStreamWriter:146 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream writer is still
> listening:: rec_64_stream_143_2015_01_22_15_45_45.flv
>
> =======================
>
> After I clicked on "stop recording", this sort of log entries continue to
> append to the log file with the status "Stream writer is still listening".
> After a while, it eventually stops and log entries changes. Please see the
> snippets of sample entries I observed.
>
> =======================
>
>
> DEBUG 01-22 15:47:52.562 o.a.o.r.FLVRecorderService:298
> [RTMPExecutor#TKDUJ1VLARWKE-1] - Stopping the stream :: New status ==
> STOPPING
>
>
>
> DEBUG 01-22 15:47:52.648 o.a.o.d.f.l.a.BaseStreamWriter:176 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream Status was:
> STOPPING has been written for: 142
>
>
>
> DEBUG 01-22 15:47:52.656 o.a.o.d.f.l.a.BaseStreamWriter:152 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: stream writer stopped
>
>
>
> DEBUG 01-22 15:47:52.663 o.a.o.r.FLVRecorderService:370
> [RTMPExecutor#TKDUJ1VLARWKE-1] - flvRecorderConverterTask
>
>
>
> DEBUG 01-22 15:47:52.728 o.a.o.c.BaseConverter:236 [taskExecutor-5] - ###
> processing metadata: 142
>
> DEBUG 01-22 15:47:52.740 o.a.o.c.BaseConverter:252 [taskExecutor-5] - FLV
> File Name: rec_64_stream_143_2015_01_22_15_45_45.flv Length: 997428
>
> DEBUG 01-22 15:47:52.752 o.a.o.u.p.ProcessHelper:104 [taskExecutor-5] -
> START stripAudioFromFLVs #################
>
> DEBUG 01-22 15:47:52.754 o.a.o.u.p.ProcessHelper:105 [taskExecutor-5] -
> /usr/local/bin/ffmpeg -y -i
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45.flv
> -af aresample=32k
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
>
>
>
> DEBUG 01-22 15:47:53.166 o.a.o.u9.p.ProcessHelper:105 [taskExecutor-5] -
> /usr/bin/sox
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_FULL_WAVE.wav
> pad 1.0 0.033
>
> DEBUG 01-22 15:47:53.166 o.a.o.u.p.ProcessHelper:106 [taskExecutor-5] -
> END addStartEndToAudio #################
>
> DEBUG 01-22 15:47:53.228 o.a.o.u.p.ProcessHelper:148 [taskExecutor-5] -
> exitVal: 0
>
> ==================================
>
> The above are just snippets only because entire log session is quite
> lengthy and nearly not affordable to send via mail. I observed the
> "Exitvalue" as 0. Does that makes any sense about our issue ?
>
> Please advise why our recording session actually stops after a while I
> clicked on "stop".. In addition to that, the "Stream Writer" is continue to
> listen until the "Stop" button in "IcedTea" turns to "Start" (Of course
> "stop" should have changed to "start" instantly when I clicked on it ).
>
> Is this an known issue with the OM 3.0.3.. can this be rectified with next
> upgrade or with latest build...
>
> Thanks in advance,
> Leo Prince.
>
> January 22 2015 9:29 AM, "Maxim Solodovnik" <solomax666@gmail.com
> <%22Maxim%20Solodovnik%22%20%3Csolomax666@gmail.com%3E>> wrote:
>
>
> this is correct mailing list :)
>
> do you have any errors in recording conversion? (small exclamation mark
> near recording in recordings tree)
> if yes what are the errors?
>
> On Thu, Jan 22, 2015 at 1:46 AM, <le...@technomicssolutions.com> wrote:
>
>
>
> Hi,
>
> I am not sure if this is the right mailbox to request advise. However this
> what I got when checked from the Apache Openmeeting page.
>
> Let me come to my concern directly.
>
> I have installed OpenMeeting with following version.
>
> Version 3.0.3-RELEASE
> Revision 1621852
>
> It's working fine but when I am using "recording" feature of OpenMeeting,
> I am having a glitch.
>
> Steps I used to replicate:
>
> 1, Open up OpenMetting and go to "whiteboard" room.
> 2, Download the .jnlp file to record the session. I use "icedtea" for
> recording feature.
> 3, I started a session and once clicked "stop recording", it takes
> considerable time to stop the session, Like 2 minutes for 30 seconds actual
> session.
> 4, The problem is, when I play the above 30 seconds video + audio session,
> 2 minutes dead paused session is showing after the actual video.
>
> How can I avoid this. Please advise. If this is not the right mail list,
> kindly forward to the apt maillist.
>
> Thanks in advance,
> Leo Prince.
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>
--
WBR
Maxim aka solomax
Re: Concerns regarding OpenMeeting Recording feature.
Posted by le...@technomicssolutions.com.
Yeah.. my local machine is having pretty good resources..What my recent concern was whether I needed to increase the resources of OM server machine to get 5FPM or 10FPM feeds without the dead paused time.
I am currently using IcedTea.. is there any other sharing client available ? Can you name them, so that I can try them as well..
I am using 3.0.3 now.. Does any better sharing client in mind for 3.0.4 ? Can an app upgrade will help to improve the situation..
Leo Prince
January 23 2015 12:34 AM, "Maxim Solodovnik" wrote:
actually client machine should be powerful enough to create better screen sharing
We will try to improve screen sharing client
On Fri, Jan 23, 2015 at 12:59 AM, wrote:
Thanks Maxim.. That nearly worked out.. I was using the following specs before...
Resolution : 1366x768
Frame per second : 10
Quality : High Quality
It found worked out when I used the following specs..
Resolution : 1050x768 ( of course it includes white board and camera feed )
Quality : medium
Frame Per Second : 2FPS
However, medium quality is okay to visible when full screen ON but 2FPS is pretty slow.. When I used with 5FPS, it still having lag but obviously less compared when I used 10FPM earlier. What are your recommendations for server resources to use medium/high quality and 5/10 FPM..
Currently it's a 4GB RAM server with 2 CPU.. Can this be sorted if we increase the CPU or any other resources ; As I think server can't handle processing tasks of 10 frames per second which caused the "dead lag" earlier which found fixed when used 2FPM..
Please advise if this is an issue with the server resources or else..
Regards,
Leo Prince.
January 22 2015 10:30 PM, "Maxim Solodovnik" wrote:
Actually when you stop recording all frames captured but not processed are being processed.
I guess "dead paused session" is caused by stream lengths are differ: i.e. video captured by screen sharing is shorter than video captured by camera.
I guess you set something like 30FPS full screen video
can you try to decrease area being recorded and FPS
On Thu, Jan 22, 2015 at 10:13 PM, wrote:
Dear Maxim,
Thank you for looking into this. We are not having any "exclamation" or "caution" symbol with the related recorded session. There are no errors any where but this issue is continue to go on.
I have monitored the logs closely while performing a test recording session. When I started the recording session, the OM log shows plenty of lines and an example will be like this.
=======================
DEBUG 01-22 15:47:52.032 o.a.o.d.f.l.a.BaseStreamWriter:146 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream writer is still listening:: rec_64_stream_143_2015_01_22_15_45_45.flv
=======================
After I clicked on "stop recording", this sort of log entries continue to append to the log file with the status "Stream writer is still listening". After a while, it eventually stops and log entries changes. Please see the snippets of sample entries I observed.
=======================
DEBUG 01-22 15:47:52.562 o.a.o.r.FLVRecorderService:298 [RTMPExecutor#TKDUJ1VLARWKE-1] - Stopping the stream :: New status == STOPPING
DEBUG 01-22 15:47:52.648 o.a.o.d.f.l.a.BaseStreamWriter:176 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream Status was: STOPPING has been written for: 142
DEBUG 01-22 15:47:52.656 o.a.o.d.f.l.a.BaseStreamWriter:152 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: stream writer stopped
DEBUG 01-22 15:47:52.663 o.a.o.r.FLVRecorderService:370 [RTMPExecutor#TKDUJ1VLARWKE-1] - flvRecorderConverterTask
DEBUG 01-22 15:47:52.728 o.a.o.c.BaseConverter:236 [taskExecutor-5] - ### processing metadata: 142
DEBUG 01-22 15:47:52.740 o.a.o.c.BaseConverter:252 [taskExecutor-5] - FLV File Name: rec_64_stream_143_2015_01_22_15_45_45.flv Length: 997428
DEBUG 01-22 15:47:52.752 o.a.o.u.p.ProcessHelper:104 [taskExecutor-5] - START stripAudioFromFLVs #################
DEBUG 01-22 15:47:52.754 o.a.o.u.p.ProcessHelper:105 [taskExecutor-5] - /usr/local/bin/ffmpeg -y -i /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45.flv -af aresample=32k /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
DEBUG 01-22 15:47:53.166 o.a.o.u9.p.ProcessHelper:105 [taskExecutor-5] - /usr/bin/sox /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_FULL_WAVE.wav pad 1.0 0.033
DEBUG 01-22 15:47:53.166 o.a.o.u.p.ProcessHelper:106 [taskExecutor-5] - END addStartEndToAudio #################
DEBUG 01-22 15:47:53.228 o.a.o.u.p.ProcessHelper:148 [taskExecutor-5] - exitVal: 0
==================================
The above are just snippets only because entire log session is quite lengthy and nearly not affordable to send via mail. I observed the "Exitvalue" as 0. Does that makes any sense about our issue ?
Please advise why our recording session actually stops after a while I clicked on "stop".. In addition to that, the "Stream Writer" is continue to listen until the "Stop" button in "IcedTea" turns to "Start" (Of course "stop" should have changed to "start" instantly when I clicked on it ).
Is this an known issue with the OM 3.0.3.. can this be rectified with next upgrade or with latest build...
Thanks in advance,
Leo Prince.
January 22 2015 9:29 AM, "Maxim Solodovnik" wrote:
this is correct mailing list :)
do you have any errors in recording conversion? (small exclamation mark near recording in recordings tree)
if yes what are the errors?
On Thu, Jan 22, 2015 at 1:46 AM, wrote:
Hi,
I am not sure if this is the right mailbox to request advise. However this what I got when checked from the Apache Openmeeting page.
Let me come to my concern directly.
I have installed OpenMeeting with following version.
Version 3.0.3-RELEASE
Revision 1621852
It's working fine but when I am using "recording" feature of OpenMeeting, I am having a glitch.
Steps I used to replicate:
1, Open up OpenMetting and go to "whiteboard" room.
2, Download the .jnlp file to record the session. I use "icedtea" for recording feature.
3, I started a session and once clicked "stop recording", it takes considerable time to stop the session, Like 2 minutes for 30 seconds actual session.
4, The problem is, when I play the above 30 seconds video + audio session, 2 minutes dead paused session is showing after the actual video.
How can I avoid this. Please advise. If this is not the right mail list, kindly forward to the apt maillist.
Thanks in advance,
Leo Prince.
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
Re: Concerns regarding OpenMeeting Recording feature.
Posted by Maxim Solodovnik <so...@gmail.com>.
actually client machine should be powerful enough to create better screen
sharing
We will try to improve screen sharing client
On Fri, Jan 23, 2015 at 12:59 AM, <le...@technomicssolutions.com> wrote:
> Thanks Maxim.. That nearly worked out.. I was using the following specs
> before...
>
> Resolution : 1366x768
> Frame per second : 10
> Quality : High Quality
>
> It found worked out when I used the following specs..
>
> Resolution : 1050x768 ( of course it includes white board and camera feed )
> Quality : medium
> Frame Per Second : 2FPS
>
> However, medium quality is okay to visible when full screen ON but 2FPS is
> pretty slow.. When I used with 5FPS, it still having lag but obviously less
> compared when I used 10FPM earlier. What are your recommendations for
> server resources to use medium/high quality and 5/10 FPM..
>
> Currently it's a 4GB RAM server with 2 CPU.. Can this be sorted if we
> increase the CPU or any other resources ; As I think server can't handle
> processing tasks of 10 frames per second which caused the "dead lag"
> earlier which found fixed when used 2FPM..
>
> Please advise if this is an issue with the server resources or else..
>
> Regards,
> Leo Prince.
>
>
> January 22 2015 10:30 PM, "Maxim Solodovnik" <solomax666@gmail.com
> <%22Maxim%20Solodovnik%22%20%3Csolomax666@gmail.com%3E>> wrote:
>
>
> Actually when you stop recording all frames captured but not processed
> are being processed.
> I guess "dead paused session" is caused by stream lengths are differ: i.e.
> video captured by screen sharing is shorter than video captured by camera.
>
> I guess you set something like 30FPS full screen video
> can you try to decrease area being recorded and FPS
>
> On Thu, Jan 22, 2015 at 10:13 PM, <le...@technomicssolutions.com> wrote:
>
>
>
> Dear Maxim,
>
> Thank you for looking into this. We are not having any "exclamation" or
> "caution" symbol with the related recorded session. There are no errors any
> where but this issue is continue to go on.
>
> I have monitored the logs closely while performing a test recording
> session. When I started the recording session, the OM log shows plenty of
> lines and an example will be like this.
>
> =======================
>
> DEBUG 01-22 15:47:52.032 o.a.o.d.f.l.a.BaseStreamWriter:146 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream writer is still
> listening:: rec_64_stream_143_2015_01_22_15_45_45.flv
>
> =======================
>
> After I clicked on "stop recording", this sort of log entries continue to
> append to the log file with the status "Stream writer is still listening".
> After a while, it eventually stops and log entries changes. Please see the
> snippets of sample entries I observed.
>
> =======================
>
>
> DEBUG 01-22 15:47:52.562 o.a.o.r.FLVRecorderService:298
> [RTMPExecutor#TKDUJ1VLARWKE-1] - Stopping the stream :: New status ==
> STOPPING
>
>
>
> DEBUG 01-22 15:47:52.648 o.a.o.d.f.l.a.BaseStreamWriter:176 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream Status was:
> STOPPING has been written for: 142
>
>
>
> DEBUG 01-22 15:47:52.656 o.a.o.d.f.l.a.BaseStreamWriter:152 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: stream writer stopped
>
>
>
> DEBUG 01-22 15:47:52.663 o.a.o.r.FLVRecorderService:370
> [RTMPExecutor#TKDUJ1VLARWKE-1] - flvRecorderConverterTask
>
>
>
> DEBUG 01-22 15:47:52.728 o.a.o.c.BaseConverter:236 [taskExecutor-5] - ###
> processing metadata: 142
>
> DEBUG 01-22 15:47:52.740 o.a.o.c.BaseConverter:252 [taskExecutor-5] - FLV
> File Name: rec_64_stream_143_2015_01_22_15_45_45.flv Length: 997428
>
> DEBUG 01-22 15:47:52.752 o.a.o.u.p.ProcessHelper:104 [taskExecutor-5] -
> START stripAudioFromFLVs #################
>
> DEBUG 01-22 15:47:52.754 o.a.o.u.p.ProcessHelper:105 [taskExecutor-5] -
> /usr/local/bin/ffmpeg -y -i
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45.flv
> -af aresample=32k
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
>
>
>
> DEBUG 01-22 15:47:53.166 o.a.o.u9.p.ProcessHelper:105 [taskExecutor-5] -
> /usr/bin/sox
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_FULL_WAVE.wav
> pad 1.0 0.033
>
> DEBUG 01-22 15:47:53.166 o.a.o.u.p.ProcessHelper:106 [taskExecutor-5] -
> END addStartEndToAudio #################
>
> DEBUG 01-22 15:47:53.228 o.a.o.u.p.ProcessHelper:148 [taskExecutor-5] -
> exitVal: 0
>
> ==================================
>
> The above are just snippets only because entire log session is quite
> lengthy and nearly not affordable to send via mail. I observed the
> "Exitvalue" as 0. Does that makes any sense about our issue ?
>
> Please advise why our recording session actually stops after a while I
> clicked on "stop".. In addition to that, the "Stream Writer" is continue to
> listen until the "Stop" button in "IcedTea" turns to "Start" (Of course
> "stop" should have changed to "start" instantly when I clicked on it ).
>
> Is this an known issue with the OM 3.0.3.. can this be rectified with next
> upgrade or with latest build...
>
> Thanks in advance,
> Leo Prince.
>
> January 22 2015 9:29 AM, "Maxim Solodovnik" <solomax666@gmail.com
> <%22Maxim%20Solodovnik%22%20%3Csolomax666@gmail.com%3E>> wrote:
>
>
> this is correct mailing list :)
>
> do you have any errors in recording conversion? (small exclamation mark
> near recording in recordings tree)
> if yes what are the errors?
>
> On Thu, Jan 22, 2015 at 1:46 AM, <le...@technomicssolutions.com> wrote:
>
>
>
> Hi,
>
> I am not sure if this is the right mailbox to request advise. However this
> what I got when checked from the Apache Openmeeting page.
>
> Let me come to my concern directly.
>
> I have installed OpenMeeting with following version.
>
> Version 3.0.3-RELEASE
> Revision 1621852
>
> It's working fine but when I am using "recording" feature of OpenMeeting,
> I am having a glitch.
>
> Steps I used to replicate:
>
> 1, Open up OpenMetting and go to "whiteboard" room.
> 2, Download the .jnlp file to record the session. I use "icedtea" for
> recording feature.
> 3, I started a session and once clicked "stop recording", it takes
> considerable time to stop the session, Like 2 minutes for 30 seconds actual
> session.
> 4, The problem is, when I play the above 30 seconds video + audio session,
> 2 minutes dead paused session is showing after the actual video.
>
> How can I avoid this. Please advise. If this is not the right mail list,
> kindly forward to the apt maillist.
>
> Thanks in advance,
> Leo Prince.
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>
--
WBR
Maxim aka solomax
Re: Concerns regarding OpenMeeting Recording feature.
Posted by le...@technomicssolutions.com.
Thanks Maxim.. That nearly worked out.. I was using the following specs before...
Resolution : 1366x768
Frame per second : 10
Quality : High Quality
It found worked out when I used the following specs..
Resolution : 1050x768 ( of course it includes white board and camera feed )
Quality : medium
Frame Per Second : 2FPS
However, medium quality is okay to visible when full screen ON but 2FPS is pretty slow.. When I used with 5FPS, it still having lag but obviously less compared when I used 10FPM earlier. What are your recommendations for server resources to use medium/high quality and 5/10 FPM..
Currently it's a 4GB RAM server with 2 CPU.. Can this be sorted if we increase the CPU or any other resources ; As I think server can't handle processing tasks of 10 frames per second which caused the "dead lag" earlier which found fixed when used 2FPM..
Please advise if this is an issue with the server resources or else..
Regards,
Leo Prince.
January 22 2015 10:30 PM, "Maxim Solodovnik" wrote:
Actually when you stop recording all frames captured but not processed are being processed.
I guess "dead paused session" is caused by stream lengths are differ: i.e. video captured by screen sharing is shorter than video captured by camera.
I guess you set something like 30FPS full screen video
can you try to decrease area being recorded and FPS
On Thu, Jan 22, 2015 at 10:13 PM, wrote:
Dear Maxim,
Thank you for looking into this. We are not having any "exclamation" or "caution" symbol with the related recorded session. There are no errors any where but this issue is continue to go on.
I have monitored the logs closely while performing a test recording session. When I started the recording session, the OM log shows plenty of lines and an example will be like this.
=======================
DEBUG 01-22 15:47:52.032 o.a.o.d.f.l.a.BaseStreamWriter:146 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream writer is still listening:: rec_64_stream_143_2015_01_22_15_45_45.flv
=======================
After I clicked on "stop recording", this sort of log entries continue to append to the log file with the status "Stream writer is still listening". After a while, it eventually stops and log entries changes. Please see the snippets of sample entries I observed.
=======================
DEBUG 01-22 15:47:52.562 o.a.o.r.FLVRecorderService:298 [RTMPExecutor#TKDUJ1VLARWKE-1] - Stopping the stream :: New status == STOPPING
DEBUG 01-22 15:47:52.648 o.a.o.d.f.l.a.BaseStreamWriter:176 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream Status was: STOPPING has been written for: 142
DEBUG 01-22 15:47:52.656 o.a.o.d.f.l.a.BaseStreamWriter:152 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: stream writer stopped
DEBUG 01-22 15:47:52.663 o.a.o.r.FLVRecorderService:370 [RTMPExecutor#TKDUJ1VLARWKE-1] - flvRecorderConverterTask
DEBUG 01-22 15:47:52.728 o.a.o.c.BaseConverter:236 [taskExecutor-5] - ### processing metadata: 142
DEBUG 01-22 15:47:52.740 o.a.o.c.BaseConverter:252 [taskExecutor-5] - FLV File Name: rec_64_stream_143_2015_01_22_15_45_45.flv Length: 997428
DEBUG 01-22 15:47:52.752 o.a.o.u.p.ProcessHelper:104 [taskExecutor-5] - START stripAudioFromFLVs #################
DEBUG 01-22 15:47:52.754 o.a.o.u.p.ProcessHelper:105 [taskExecutor-5] - /usr/local/bin/ffmpeg -y -i /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45.flv -af aresample=32k /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
DEBUG 01-22 15:47:53.166 o.a.o.u9.p.ProcessHelper:105 [taskExecutor-5] - /usr/bin/sox /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_FULL_WAVE.wav pad 1.0 0.033
DEBUG 01-22 15:47:53.166 o.a.o.u.p.ProcessHelper:106 [taskExecutor-5] - END addStartEndToAudio #################
DEBUG 01-22 15:47:53.228 o.a.o.u.p.ProcessHelper:148 [taskExecutor-5] - exitVal: 0
==================================
The above are just snippets only because entire log session is quite lengthy and nearly not affordable to send via mail. I observed the "Exitvalue" as 0. Does that makes any sense about our issue ?
Please advise why our recording session actually stops after a while I clicked on "stop".. In addition to that, the "Stream Writer" is continue to listen until the "Stop" button in "IcedTea" turns to "Start" (Of course "stop" should have changed to "start" instantly when I clicked on it ).
Is this an known issue with the OM 3.0.3.. can this be rectified with next upgrade or with latest build...
Thanks in advance,
Leo Prince.
January 22 2015 9:29 AM, "Maxim Solodovnik" wrote:
this is correct mailing list :)
do you have any errors in recording conversion? (small exclamation mark near recording in recordings tree)
if yes what are the errors?
On Thu, Jan 22, 2015 at 1:46 AM, wrote:
Hi,
I am not sure if this is the right mailbox to request advise. However this what I got when checked from the Apache Openmeeting page.
Let me come to my concern directly.
I have installed OpenMeeting with following version.
Version 3.0.3-RELEASE
Revision 1621852
It's working fine but when I am using "recording" feature of OpenMeeting, I am having a glitch.
Steps I used to replicate:
1, Open up OpenMetting and go to "whiteboard" room.
2, Download the .jnlp file to record the session. I use "icedtea" for recording feature.
3, I started a session and once clicked "stop recording", it takes considerable time to stop the session, Like 2 minutes for 30 seconds actual session.
4, The problem is, when I play the above 30 seconds video + audio session, 2 minutes dead paused session is showing after the actual video.
How can I avoid this. Please advise. If this is not the right mail list, kindly forward to the apt maillist.
Thanks in advance,
Leo Prince.
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
Re: Concerns regarding OpenMeeting Recording feature.
Posted by Maxim Solodovnik <so...@gmail.com>.
Actually when you stop recording all frames captured but not processed are
being processed.
I guess "dead paused session" is caused by stream lengths are differ: i.e.
video captured by screen sharing is shorter than video captured by camera.
I guess you set something like 30FPS full screen video
can you try to decrease area being recorded and FPS
On Thu, Jan 22, 2015 at 10:13 PM, <le...@technomicssolutions.com> wrote:
> Dear Maxim,
>
> Thank you for looking into this. We are not having any "exclamation" or
> "caution" symbol with the related recorded session. There are no errors any
> where but this issue is continue to go on.
>
> I have monitored the logs closely while performing a test recording
> session. When I started the recording session, the OM log shows plenty of
> lines and an example will be like this.
>
> =======================
>
> DEBUG 01-22 15:47:52.032 o.a.o.d.f.l.a.BaseStreamWriter:146 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream writer is still
> listening:: rec_64_stream_143_2015_01_22_15_45_45.flv
>
> =======================
>
> After I clicked on "stop recording", this sort of log entries continue to
> append to the log file with the status "Stream writer is still listening".
> After a while, it eventually stops and log entries changes. Please see the
> snippets of sample entries I observed.
>
> =======================
>
> DEBUG 01-22 15:47:52.562 o.a.o.r.FLVRecorderService:298
> [RTMPExecutor#TKDUJ1VLARWKE-1] - Stopping the stream :: New status ==
> STOPPING
>
>
>
> DEBUG 01-22 15:47:52.648 o.a.o.d.f.l.a.BaseStreamWriter:176 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream Status was:
> STOPPING has been written for: 142
>
>
>
> DEBUG 01-22 15:47:52.656 o.a.o.d.f.l.a.BaseStreamWriter:152 [Recording
> rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: stream writer stopped
>
>
>
> DEBUG 01-22 15:47:52.663 o.a.o.r.FLVRecorderService:370
> [RTMPExecutor#TKDUJ1VLARWKE-1] - flvRecorderConverterTask
>
>
>
> DEBUG 01-22 15:47:52.728 o.a.o.c.BaseConverter:236 [taskExecutor-5] - ###
> processing metadata: 142
>
> DEBUG 01-22 15:47:52.740 o.a.o.c.BaseConverter:252 [taskExecutor-5] - FLV
> File Name: rec_64_stream_143_2015_01_22_15_45_45.flv Length: 997428
>
> DEBUG 01-22 15:47:52.752 o.a.o.u.p.ProcessHelper:104 [taskExecutor-5] -
> START stripAudioFromFLVs #################
>
> DEBUG 01-22 15:47:52.754 o.a.o.u.p.ProcessHelper:105 [taskExecutor-5] -
> /usr/local/bin/ffmpeg -y -i
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45.flv
> -af aresample=32k
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
>
>
>
> DEBUG 01-22 15:47:53.166 o.a.o.u9.p.ProcessHelper:105 [taskExecutor-5] -
> /usr/bin/sox
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
> /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_FULL_WAVE.wav
> pad 1.0 0.033
>
> DEBUG 01-22 15:47:53.166 o.a.o.u.p.ProcessHelper:106 [taskExecutor-5] -
> END addStartEndToAudio #################
>
> DEBUG 01-22 15:47:53.228 o.a.o.u.p.ProcessHelper:148 [taskExecutor-5] -
> exitVal: 0
>
> ==================================
>
> The above are just snippets only because entire log session is quite
> lengthy and nearly not affordable to send via mail. I observed the
> "Exitvalue" as 0. Does that makes any sense about our issue ?
>
> Please advise why our recording session actually stops after a while I
> clicked on "stop".. In addition to that, the "Stream Writer" is continue to
> listen until the "Stop" button in "IcedTea" turns to "Start" (Of course
> "stop" should have changed to "start" instantly when I clicked on it ).
>
> Is this an known issue with the OM 3.0.3.. can this be rectified with next
> upgrade or with latest build...
>
> Thanks in advance,
> Leo Prince.
>
> January 22 2015 9:29 AM, "Maxim Solodovnik" <solomax666@gmail.com
> <%22Maxim%20Solodovnik%22%20%3Csolomax666@gmail.com%3E>> wrote:
>
>
> this is correct mailing list :)
>
> do you have any errors in recording conversion? (small exclamation mark
> near recording in recordings tree)
> if yes what are the errors?
>
> On Thu, Jan 22, 2015 at 1:46 AM, <le...@technomicssolutions.com> wrote:
>
>
>
> Hi,
>
> I am not sure if this is the right mailbox to request advise. However this
> what I got when checked from the Apache Openmeeting page.
>
> Let me come to my concern directly.
>
> I have installed OpenMeeting with following version.
>
> Version 3.0.3-RELEASE
> Revision 1621852
>
> It's working fine but when I am using "recording" feature of OpenMeeting,
> I am having a glitch.
>
> Steps I used to replicate:
>
> 1, Open up OpenMetting and go to "whiteboard" room.
> 2, Download the .jnlp file to record the session. I use "icedtea" for
> recording feature.
> 3, I started a session and once clicked "stop recording", it takes
> considerable time to stop the session, Like 2 minutes for 30 seconds actual
> session.
> 4, The problem is, when I play the above 30 seconds video + audio session,
> 2 minutes dead paused session is showing after the actual video.
>
> How can I avoid this. Please advise. If this is not the right mail list,
> kindly forward to the apt maillist.
>
> Thanks in advance,
> Leo Prince.
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>
--
WBR
Maxim aka solomax
Re: Concerns regarding OpenMeeting Recording feature.
Posted by le...@technomicssolutions.com.
Dear Maxim,
Thank you for looking into this. We are not having any "exclamation" or "caution" symbol with the related recorded session. There are no errors any where but this issue is continue to go on.
I have monitored the logs closely while performing a test recording session. When I started the recording session, the OM log shows plenty of lines and an example will be like this.
=======================
DEBUG 01-22 15:47:52.032 o.a.o.d.f.l.a.BaseStreamWriter:146 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream writer is still listening:: rec_64_stream_143_2015_01_22_15_45_45.flv
=======================
After I clicked on "stop recording", this sort of log entries continue to append to the log file with the status "Stream writer is still listening". After a while, it eventually stops and log entries changes. Please see the snippets of sample entries I observed.
=======================
DEBUG 01-22 15:47:52.562 o.a.o.r.FLVRecorderService:298 [RTMPExecutor#TKDUJ1VLARWKE-1] - Stopping the stream :: New status == STOPPING
DEBUG 01-22 15:47:52.648 o.a.o.d.f.l.a.BaseStreamWriter:176 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: Stream Status was: STOPPING has been written for: 142
DEBUG 01-22 15:47:52.656 o.a.o.d.f.l.a.BaseStreamWriter:152 [Recording rec_64_stream_143_2015_01_22_15_45_45.flv] - ##REC:: stream writer stopped
DEBUG 01-22 15:47:52.663 o.a.o.r.FLVRecorderService:370 [RTMPExecutor#TKDUJ1VLARWKE-1] - flvRecorderConverterTask
DEBUG 01-22 15:47:52.728 o.a.o.c.BaseConverter:236 [taskExecutor-5] - ### processing metadata: 142
DEBUG 01-22 15:47:52.740 o.a.o.c.BaseConverter:252 [taskExecutor-5] - FLV File Name: rec_64_stream_143_2015_01_22_15_45_45.flv Length: 997428
DEBUG 01-22 15:47:52.752 o.a.o.u.p.ProcessHelper:104 [taskExecutor-5] - START stripAudioFromFLVs #################
DEBUG 01-22 15:47:52.754 o.a.o.u.p.ProcessHelper:105 [taskExecutor-5] - /usr/local/bin/ffmpeg -y -i /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45.flv -af aresample=32k /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav
DEBUG 01-22 15:47:53.166 o.a.o.u9.p.ProcessHelper:105 [taskExecutor-5] - /usr/bin/sox /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_WAVE.wav /usr/lib/red5/webapps/openmeetings/streams/4/rec_64_stream_143_2015_01_22_15_45_45_FULL_WAVE.wav pad 1.0 0.033
DEBUG 01-22 15:47:53.166 o.a.o.u.p.ProcessHelper:106 [taskExecutor-5] - END addStartEndToAudio #################
DEBUG 01-22 15:47:53.228 o.a.o.u.p.ProcessHelper:148 [taskExecutor-5] - exitVal: 0
==================================
The above are just snippets only because entire log session is quite lengthy and nearly not affordable to send via mail. I observed the "Exitvalue" as 0. Does that makes any sense about our issue ?
Please advise why our recording session actually stops after a while I clicked on "stop".. In addition to that, the "Stream Writer" is continue to listen until the "Stop" button in "IcedTea" turns to "Start" (Of course "stop" should have changed to "start" instantly when I clicked on it ).
Is this an known issue with the OM 3.0.3.. can this be rectified with next upgrade or with latest build...
Thanks in advance,
Leo Prince.
January 22 2015 9:29 AM, "Maxim Solodovnik" wrote:
this is correct mailing list :)
do you have any errors in recording conversion? (small exclamation mark near recording in recordings tree)
if yes what are the errors?
On Thu, Jan 22, 2015 at 1:46 AM, wrote:
Hi,
I am not sure if this is the right mailbox to request advise. However this what I got when checked from the Apache Openmeeting page.
Let me come to my concern directly.
I have installed OpenMeeting with following version.
Version 3.0.3-RELEASE
Revision 1621852
It's working fine but when I am using "recording" feature of OpenMeeting, I am having a glitch.
Steps I used to replicate:
1, Open up OpenMetting and go to "whiteboard" room.
2, Download the .jnlp file to record the session. I use "icedtea" for recording feature.
3, I started a session and once clicked "stop recording", it takes considerable time to stop the session, Like 2 minutes for 30 seconds actual session.
4, The problem is, when I play the above 30 seconds video + audio session, 2 minutes dead paused session is showing after the actual video.
How can I avoid this. Please advise. If this is not the right mail list, kindly forward to the apt maillist.
Thanks in advance,
Leo Prince.
--
WBR
Maxim aka solomax
Re: Concerns regarding OpenMeeting Recording feature.
Posted by Maxim Solodovnik <so...@gmail.com>.
this is correct mailing list :)
do you have any errors in recording conversion? (small exclamation mark
near recording in recordings tree)
if yes what are the errors?
On Thu, Jan 22, 2015 at 1:46 AM, <le...@technomicssolutions.com> wrote:
> Hi,
>
> I am not sure if this is the right mailbox to request advise. However this
> what I got when checked from the Apache Openmeeting page.
>
> Let me come to my concern directly.
>
> I have installed OpenMeeting with following version.
>
> Version 3.0.3-RELEASE
> Revision 1621852
>
> It's working fine but when I am using "recording" feature of OpenMeeting,
> I am having a glitch.
>
> Steps I used to replicate:
>
> 1, Open up OpenMetting and go to "whiteboard" room.
> 2, Download the .jnlp file to record the session. I use "icedtea" for
> recording feature.
> 3, I started a session and once clicked "stop recording", it takes
> considerable time to stop the session, Like 2 minutes for 30 seconds actual
> session.
> 4, The problem is, when I play the above 30 seconds video + audio session,
> 2 minutes dead paused session is showing after the actual video.
>
> How can I avoid this. Please advise. If this is not the right mail list,
> kindly forward to the apt maillist.
>
> Thanks in advance,
> Leo Prince.
>
--
WBR
Maxim aka solomax