yes... that what i meant with "differs from production server"... I try to fix it...
brb Am 04.03.2014 13:54, schrieb Maxim Solodovnik: > It seems like your ffmpeg has no x264 support :( > > both following commands are failed: > /usr/local/bin/ffmpeg -i > /home/worker/red5_3_0/red5/webapps/openmeetings/streams/hibernate/flvRecording_298.flv > -c:v libx264 -crf 24 -pix_fmt yuv420p -preset medium -profile:v baseline > -c:a libfaac -c:a libfdk_aac -b:a 32k -s 1440x800 > /home/worker/red5_3_0/red5/webapps/openmeetings/streams/hibernate/flvRecording_298.flv.mp4 > and > /usr/local/bin/ffmpeg -i > /home/worker/red5_3_0/red5/webapps/openmeetings/streams/hibernate/flvRecording_298.flv.mp4 > -vcodec libtheora -acodec libvorbis > /home/worker/red5_3_0/red5/webapps/openmeetings/streams/hibernate/flvRecording_298.flv.ogg > > Could you please run it from the console and check output? > Or check output via OM GUI? > > > On Tue, Mar 4, 2014 at 6:03 PM, Peter Dähn <[email protected]> wrote: > >> RC2 is compiled and deployed in a minute... I'll try it out... >> >> the former version was " 3.0.0-SNAPSHOT 1573484 3-March-2014" >> >> I'll attach the logs from yesterday... by now i saw a few errors.. i >> didn't had the time to investigate... :-( >> >> I'll check RC2 now.. >> >> cu >> >> >> Am 04.03.2014 11:50, schrieb Maxim Solodovnik: >>> Hello Peter, >>> >>> What version of OM were you using? >>> Could you retest using RC2? (it contains screen sharing fixes) >>> Were you able to record interview? >>> Can you try multiple resolutions/fps? >>> >>> >>> >>> On Tue, Mar 4, 2014 at 4:02 PM, Peter Dähn <[email protected]> wrote: >>> >>>> Hi there, >>>> >>>> i had the same problem, I couldn't get a valid record on my >>>> test-system. I use Linux. I thought it is a problem with my test-env, >>>> because it differs a bit from the production-server... >>>> >>>> so.. I think, recording should be fixed before release... sorry :-( >>>> >>>> Greetings Peter >>>> >>>> >>>> Am 04.03.2014 09:27, schrieb [email protected]: >>>>> "not ready status will be displayed after click on "!" icon in the >>>> popup." >>>>> I did not get a not ready status displayed. I see the icon on the left, >>>> but >>>>> neither by clicking on the icon nor on the recording anything happens. >>>>> >>>>> Can we make it that somehow that it will be displayed directly when you >>>>> click on the recording? >>>>> >>>>> Having links that you click and under some circumstances nothing >> happens >>>>> are just very hard to understand for end-users. Previously you did get >>>> the >>>>> pop warning 'not ready' directly on a click on the recording when it is >>>> not >>>>> yet ready for viewing. >>>>> >>>>> I tried to do three recordings on demo.dataved.ru, all failed. >> Possibly >>>>> because I am using Mac and/or bandwidth issues. >>>>> I was able to produce a recording at the 06th of February on that >> server >>>>> with a Mac, so it is not a general issue. >>>>> In the error log window I can see some ffmpeg command fails (see >> attached >>>>> on the bottom of the mail some example) >>>>> >>>>> But the screen sharer itself stayed at 50% of the CPU which is >> acceptable >>>>> for the first release of 3.x.x from my point of view. >>>>> Just to get some recordings produced with it would be something I would >>>> be >>>>> keen to verify. >>>>> >>>>> Another issues was that I cannot enter a room on demo.dataved.ruafter a >>>>> while. I just stuck in the screen when the loading bar in front of >>>> entering >>>>> the conference room is complete. I guess there is some null pointer >>>>> exception in the code but I cannot load the debug window on that >> server. >>>>> I was using the "remember me" cookie, after deleting the cookie and >>>>> re-login entering the room did work again. >>>>> >>>>> What about the attribute "length" of the recording in the UI, the field >>>>> seems to be simply not filled with any value yet, even if the recording >>>> was >>>>> successful. Is that not implemented yet? >>>>> >>>>> Btw the autocomplete box in the private message center and calendar is >>>>> a-w-e-s-o-m-e >>>>> I think we should leave it as is. Normally you can only send messages >> to >>>>> your contacts, but I think like that it is even better. The old one was >>>> too >>>>> restrictive to be intuitive. >>>>> When attaching a meeting request with a date/time to a private message >>>> ... >>>>> it did not show up in my calendar afterwards. Is that something that >>>> needs >>>>> to done still ? >>>>> >>>>> This is the FFMPEG error on all my recordings: >>>>> process: previewFullFLV command: ffmpeg -i >>>>> >> /opt/openmeetings-3.0.0.r1573575/webapps/openmeetings/streams/hibernate/flvRecording_210.flv >>>>> -vcodec mjpeg -vframes 1 -an -f rawvideo -s 1072x672 >>>>> >> /opt/openmeetings-3.0.0.r1573575/webapps/openmeetings/streams/hibernate/flvRecording_210.jpg >>>>> exception: null error: ffmpeg version git-2013-10-22-c68faca Copyright >>>> (c) >>>>> 2000-2013 the FFmpeg developers built on Oct 22 2013 12:58:25 with gcc >>>> 4.6 >>>>> (Ubuntu/Linaro 4.6.3-1ubuntu5) configuration: >> --prefix=/root/ffmpeg_build >>>>> --extra-cflags=-I/root/ffmpeg_build/include >>>>> --extra-ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin >>>>> --extra-libs=-ldl --enable-gpl --enable-libass --enable-libfdk-aac >>>>> --enable-libmp3lame --enable-libopus --enable-libtheora >>>> --enable-libvorbis >>>>> --enable-libvpx --enable-libx264 --enable-nonfree --enable-x11grab >>>>> libavutil 52. 47.101 / 52. 47.101 libavcodec 55. 37.102 / 55. 37.102 >>>>> libavformat 55. 19.103 / 55. 19.103 libavdevice 55. 4.100 / 55. 4.100 >>>>> libavfilter 3. 89.100 / 3. 89.100 libswscale 2. 5.101 / 2. 5.101 >>>>> libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 >>>> [flv >>>>> @ 0x3693900] Could not find codec parameters for stream 0 (Video: none, >>>> 200 >>>>> kb/s): unspecified size Consider increasing the value for the >>>>> 'analyzeduration' and 'probesize' options Input #0, flv, from >>>>> >> '/opt/openmeetings-3.0.0.r1573575/webapps/openmeetings/streams/hibernate/flvRecording_210.flv': >>>>> Metadata: noaudiocodec : 0 server : Red5 Server 1.0.0 RC3 Rev: 4393 >>>>> creationdate : Tue Mar 04 08:04:03 CET 2014 canSeekToEnd : true >> encoder : >>>>> Lavf55.19.103 Duration: 00:01:28.87, start: 0.000000, bitrate: 593 kb/s >>>>> Stream #0:0: Video: none, 200 kb/s, 1k tbr, 1k tbn, 1k tbc Stream #0:1: >>>>> Audio: mp3, 22050 Hz, mono, s16p, 32 kb/s Output #0, rawvideo, to >>>>> >> '/opt/openmeetings-3.0.0.r1573575/webapps/openmeetings/streams/hibernate/flvRecording_210.jpg': >>>>> Metadata: noaudiocodec : 0 server : Red5 Server 1.0.0 RC3 Rev: 4393 >>>>> creationdate : Tue Mar 04 08:04:03 CET 2014 canSeekToEnd : true >> encoder : >>>>> Lavf55.19.103 Output file #0 does not contain any stream exitValue: >> null >>>>> out: >>>>> >>>>> Sebastian >>>>> >>>>> >>>>> >>>>> 2014-03-04 20:18 GMT+13:00 Maxim Solodovnik <[email protected]>: >>>>> >>>>>> Currently "not ready" recordings are marked as "broken" (same "!" >> icon) >>>>>> not ready status will be displayed after click on "!" icon in the >> popup. >>>>>> interview recordings are now converted as fast as ordinary recordings. >>>>>> >>>>>> Icon can be changed, please suggest one :) (Do you feel it is blocker? >>>> or >>>>>> maybe we can release 3.0.1 will all such minor fixes?) >>>>>> >>>>>> >>>>>> http://demo.dataved.ru:5080/ contains the same SNAPSHOT >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Mar 4, 2014 at 2:12 PM, [email protected] < >>>>>> [email protected] >>>>>>> wrote: >>>>>>> I think there is still a slight glitch with the recordings UI. >>>>>>> >>>>>>> Previously, when a recording was not yet ready for viewing (because >> it >>>> is >>>>>>> still processing) there was a message in the UI telling you that. In >>>> the >>>>>>> case of interviews there was even a progress includes in percentages >> as >>>>>>> interviews take 1 minutes of processing time for the rendering of a 1 >>>>>>> minute of video. >>>>>>> >>>>>>> If you at the moment are too fast in switching to the UI and there >> was >>>>>> some >>>>>>> kind of error or its kind of simply not ready for viewing you click >> on >>>>>> the >>>>>>> video and just nothing happens. >>>>>>> >>>>>>> What is the current mechanism? Do we catch in the recordings UI if >> the >>>>>>> video is ready for viewing or not? >>>>>>> >>>>>>> Thanks, >>>>>>> Sebastian >>>>>>> >>>>>>> >>>>>>> 2014-03-04 19:54 GMT+13:00 [email protected] < >>>> [email protected] >>>>>>> : >>>>>>> >>>>>>>> Well if its just me I do not want to complain. >>>>>>>> I am using a Mac, probably that is part of the problem. >>>>>>>> >>>>>>>> Let me try to run a couple of tests. >>>>>>>> >>>>>>>> Btw: Is http://demo.dataved.ru:5080/ the same SNAPSHOT that is up >> for >>>>>> a >>>>>>>> vote? >>>>>>>> >>>>>>>> Thanks! >>>>>>>> Sebastian >>>>>>>> >>>>>>>> >>>>>>>> 2014-03-04 17:14 GMT+13:00 Maxim Solodovnik <[email protected]>: >>>>>>>> >>>>>>>> Hello Sebastian, >>>>>>>>> I was unable to fix high CPU usage because I can't see it :( >>>>>>>>> We have tried to reproduce it on our machines (me and Vasiliy, >>>> Vasiliy >>>>>>>>> provides you with his measurements), but it is not reproducible. >>>>>>>>> No additional comments were provided, so this issue have been >>>>>> postponed >>>>>>>>> >>>>>>>>> On Tue, Mar 4, 2014 at 11:08 AM, [email protected] < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Hi Maxim, >>>>>>>>>> >>>>>>>>>> Thanks, I think one of the major obstacles has been the CPU usage >> of >>>>>>> the >>>>>>>>>> screen sharing application. >>>>>>>>>> Did we reduce the CPU usage significantly? >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Sebastian >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2014-03-04 5:41 GMT+13:00 Alvaro <[email protected]>: >>>>>>>>>> >>>>>>>>>>> +1 >>>>>>>>>>> >>>>>>>>>>> ------------------- >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> El lun, 03-03-2014 a las 23:09 +0700, Maxim Solodovnik escribió: >>>>>>>>>>>> Dear OpenMeetings Community, >>>>>>>>>>>> >>>>>>>>>>>> I would like to start a vote about releasing Apache OpenMeetings >>>>>>>>> 3.0.0 >>>>>>>>>>> RC2 >>>>>>>>>>>> Main changes are covered in the >>>>>>>>>>>> Readme: >>>>>> https://svn.apache.org/repos/asf/openmeetings/tags/3.0.0RC2/README >>>>>>>>>>>> Full Changelog: >>>>>>>>>>>> >>>> https://svn.apache.org/repos/asf/openmeetings/tags/3.0.0RC2/CHANGELOG >>>>>>>>>>>> Release artefacts: >>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/openmeetings/3.0.0/rc2/ >>>>>>>>>>>> >>>>>>>>>>>> Tag: >>>>>> https://svn.apache.org/repos/asf/openmeetings/tags/3.0.0RC2/ >>>>>>>>>>>> PGP release keys (signed using >>>>>>>>>>>> C467526E): >>>>>> https://dist.apache.org/repos/dist/dev/openmeetings/3.0.0/rc2/KEYS >>>>>>>>>>>> Vote will be open for 72 hours. >>>>>>>>>>>> >>>>>>>>>>>> [ ] +1 approve >>>>>>>>>>>> [ ] +0 no opinion >>>>>>>>>>>> [ ] -1 disapprove (and reason why) >>>>>>>>>>>> >>>>>>>>>>>> My vote is +1. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Sebastian Wagner >>>>>>>>>> https://twitter.com/#!/dead_lock >>>>>>>>>> http://www.webbase-design.de >>>>>>>>>> http://www.wagner-sebastian.com >>>>>>>>>> [email protected] >>>>>>>>>> >>>>>>>>> -- >>>>>>>>> WBR >>>>>>>>> Maxim aka solomax >>>>>>>>> >>>>>>>> -- >>>>>>>> Sebastian Wagner >>>>>>>> https://twitter.com/#!/dead_lock >>>>>>>> http://www.webbase-design.de >>>>>>>> http://www.wagner-sebastian.com >>>>>>>> [email protected] >>>>>>>> >>>>>>> -- >>>>>>> Sebastian Wagner >>>>>>> https://twitter.com/#!/dead_lock >>>>>>> http://www.webbase-design.de >>>>>>> http://www.wagner-sebastian.com >>>>>>> [email protected] >>>>>>> >>>>>> -- >>>>>> WBR >>>>>> Maxim aka solomax >>>>>> >>>> -- >>>> B.Sc. Peter Dähn >>>> Virtueller Campus Rheinland-Pfalz <http://www.vcrp.de/> >>>> Postfach 3049 >>>> 67653 Kaiserslautern >>>> Tel: 0631/205-4944 >>>> Olat <https://olat.vcrp.de/> >>>> >>> > >
