From: Roberto C. <rca...@lo...> - 2006-09-21 00:38:49
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey all, I'm having some random thread kills with this output: svr motion:[2] avcodec_open - could not open codec: file exists svr motion:[2] ffopen_open error creating (new) file [/PATH/OF/ VIDEO.AVI] : file exists ffmpeg version is: $ ffmpeg -version FFmpeg version CVS, Copyright (c) 2000-2004 Fabrice Bellard configuration: --prefix=/usr --enable-gpl --enable-mp3lame -- enable-libogg --enable-vorbis --enable-pp --enable-faac --enable-faad - --enable-a52 --enable-xvid --enable-dts --enable-pp --enable-shared -- enable-pthreads libavutil version: 49.0.0 libavcodec version: 51.9.0 libavformat version: 50.4.0 built on Jun 12 2006 14:19:26, gcc: 4.0.3 ffmpeg CVS libavutil 3211264 libavcodec 3344640 libavformat 3277824 motion version is: $ svn info Path: . URL: http://www.lavrsen.dk/svn/motion/trunk Repository Root: http://www.lavrsen.dk/svn/motion Repository UUID: 4132a67d-e308-0410-984c-893ed6249e5e Revision: 99 Node Kind: directory Schedule: normal Last Changed Author: AngelCarpintero Last Changed Rev: 99 Last Changed Date: 2006-07-02 21:23:18 -0400 (dom, 02 jul 2006) I would like to know if this is solved in newer svn versions or how I can help into resolving this. I'm getting this error totally random, sometimes happens often (during a day), sometimes just goes one week without problems.. it's very weird. I ran 4 threads and it happens randomly on all 4, one at a time, of course, restarting motion works fine, I would like to know wether is possible to detect this failure and restarting motion or the failed thread as a workaround. Any tips? Regards, r. - -- Roberto Carvajal LOKO IT Services rca...@lo... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFEd9Rhxx07QJWESMRArV6AKCtbiVwWukuGpSaOVfc9pHXS74ONQCcCwlK 5eMZVKgo8Uk6HQ8BZdYdsWo= =o0xG -----END PGP SIGNATURE----- |
From: Joerg W. <mo...@al...> - 2006-09-21 05:46:12
|
Hi Roberto, please update to the latest SVN snapshot of motion. This problem has been fixed a while ago. The function 'avcodec_open' in ffmpeg is not thread-safe. Brgds Joerg. Roberto Carvajal wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Hey all, > > > I'm having some random thread kills with this output: > > > svr motion:[2] avcodec_open - could not open codec: file exists svr > motion:[2] ffopen_open error creating (new) file [/PATH/OF/ > VIDEO.AVI] : > file exists > > > motion version is: $ svn info > Path: . > URL: http://www.lavrsen.dk/svn/motion/trunk > Repository Root: http://www.lavrsen.dk/svn/motion > Repository UUID: 4132a67d-e308-0410-984c-893ed6249e5e > Revision: 99 --=20 |
From: Kenneth L. <ke...@la...> - 2006-09-21 05:48:17
|
What is your movie_filename (earlier called ffmpeg_filename) defined as in motion.conf or in your thread file? Kenneth Roberto Carvajal wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hey all, > > I'm having some random thread kills with this output: > > svr motion:[2] avcodec_open - could not open codec: file exists > svr motion:[2] ffopen_open error creating (new) file [/PATH/OF/ > VIDEO.AVI] : > file exists > > ffmpeg version is: > > $ ffmpeg -version > FFmpeg version CVS, Copyright (c) 2000-2004 Fabrice Bellard > configuration: --prefix=/usr --enable-gpl --enable-mp3lame -- > enable-libogg --enable-vorbis --enable-pp --enable-faac --enable-faad > - --enable-a52 --enable-xvid --enable-dts --enable-pp --enable-shared -- > enable-pthreads > libavutil version: 49.0.0 > libavcodec version: 51.9.0 > libavformat version: 50.4.0 > built on Jun 12 2006 14:19:26, gcc: 4.0.3 > ffmpeg CVS > libavutil 3211264 > libavcodec 3344640 > libavformat 3277824 > > > motion version is: > $ svn info > Path: . > URL: http://www.lavrsen.dk/svn/motion/trunk > Repository Root: http://www.lavrsen.dk/svn/motion > Repository UUID: 4132a67d-e308-0410-984c-893ed6249e5e > Revision: 99 > Node Kind: directory > Schedule: normal > Last Changed Author: AngelCarpintero > Last Changed Rev: 99 > Last Changed Date: 2006-07-02 21:23:18 -0400 (dom, 02 jul 2006) > > I would like to know if this is solved in newer svn versions or how I > can help into resolving this. > > I'm getting this error totally random, sometimes happens often > (during a day), sometimes just goes one week without problems.. it's > very weird. > > I ran 4 threads and it happens randomly on all 4, one at a time, of > course, restarting motion works fine, I would like to know wether is > possible to detect this failure and restarting motion or the failed > thread as a workaround. > > Any tips? > > Regards, > > r. > - -- > Roberto Carvajal > LOKO IT Services > rca...@lo... > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > > iD8DBQFFEd9Rhxx07QJWESMRArV6AKCtbiVwWukuGpSaOVfc9pHXS74ONQCcCwlK > 5eMZVKgo8Uk6HQ8BZdYdsWo= > =o0xG > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Motion-user mailing list > Mot...@li... > https://lists.sourceforge.net/lists/listinfo/motion-user > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome > > > |
From: Roberto C. <rca...@lo...> - 2006-09-21 07:27:03
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thank you, I wonder if the ffmpeg version I'm using is safe. Should I update both motion and ffmpeg, or just updating motion is fine? PS: Kenneth, the file name is just a normal path like /home/user/=20 motion/2006/09/12/10/100023.avi - -- Roberto Carvajal LOKO IT Services rca...@lo... El 21-09-2006, a las 1:46, Joerg WEBER escribi=F3: > Hi Roberto, > > please update to the latest SVN snapshot of motion. This problem =20 > has been > fixed a while ago. The function 'avcodec_open' in ffmpeg is not > thread-safe. > > Brgds Joerg. > > > Roberto Carvajal wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> Hey all, >> >> >> I'm having some random thread kills with this output: >> >> >> svr motion:[2] avcodec_open - could not open codec: file exists svr >> motion:[2] ffopen_open error creating (new) file [/PATH/OF/ >> VIDEO.AVI] : >> file exists >> >> >> motion version is: $ svn info >> Path: . >> URL: http://www.lavrsen.dk/svn/motion/trunk >> Repository Root: http://www.lavrsen.dk/svn/motion >> Repository UUID: 4132a67d-e308-0410-984c-893ed6249e5e >> Revision: 99 > --=20 > > > > ----------------------------------------------------------------------=20= > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to =20 > share your > opinions on IT & business topics through brief surveys -- and earn =20 > cash > http://www.techsay.com/default.php?=20 > page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV > _______________________________________________ > Motion-user mailing list > Mot...@li... > https://lists.sourceforge.net/lists/listinfo/motion-user > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFEj8hhxx07QJWESMRAlgHAKCrfzZtFvKw+zgqiI65eIxMcAG+YACcCnOd qNHNLD/+hgeFIlZQBI8xyqc=3D =3Dr0Im -----END PGP SIGNATURE----- |
From: Joerg W. <mo...@al...> - 2006-09-21 07:33:21
|
Roberto, updating ffmpeg doesn't help. We have circumvented the problem in the motion code, so no need to change anything in ffmpeg anymore. To be on th= e safe side, you should use the motion codebase that Kenneth recommends: http://sourceforge.net/project/showfiles.php?group_id=3D13468&package_id=3D= 116390 Brgds Joerg. Roberto Carvajal wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Thank you, > > > I wonder if the ffmpeg version I'm using is safe. > > > Should I update both motion and ffmpeg, or just updating motion is fine= ? > --=20 |
From: Roberto C. <rca...@lo...> - 2006-09-21 07:40:27
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Great!, I'm going to test this and report back.. Thank you very much.. - -- Roberto Carvajal LOKO IT Services rca...@lo... El 21-09-2006, a las 3:33, Joerg WEBER escribi=F3: > Roberto, > > updating ffmpeg doesn't help. We have circumvented the problem in the > motion code, so no need to change anything in ffmpeg anymore. To be =20= > on the > safe side, you should use the motion codebase that Kenneth recommends: > > http://sourceforge.net/project/showfiles.php?=20 > group_id=3D13468&package_id=3D116390 > > > Brgds Joerg. > > > Roberto Carvajal wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> Thank you, >> >> >> I wonder if the ffmpeg version I'm using is safe. >> >> >> Should I update both motion and ffmpeg, or just updating motion is =20= >> fine? >> > > > --=20 > > > > ----------------------------------------------------------------------=20= > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to =20 > share your > opinions on IT & business topics through brief surveys -- and earn =20 > cash > http://www.techsay.com/default.php?=20 > page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV > _______________________________________________ > Motion-user mailing list > Mot...@li... > https://lists.sourceforge.net/lists/listinfo/motion-user > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFEkJEhxx07QJWESMRAjY5AJ4+LXRDmbaefecrWLiGgbFHeiN/mACgsMDd qS/iFaDfJMKOaV5I29g4xII=3D =3DVJ04 -----END PGP SIGNATURE----- |
From: Roberto C. <rca...@lo...> - 2006-09-21 16:08:43
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joerg, I updated motion to lastest SVN revision (110), this is the log: roberto$ svn update U video_freebsd.c U netcam_wget.h U netcam_jpeg.c U configure.in U motion.c U CHANGELOG U CREDITS U webhttpd.c U README.axis_2100 U netcam.c U netcam_wget.c Updated to revision 110. I see no ffmpeg.c changes nor at event.c, I was running revision 99 =20 before. I grep'ed for avcodec_open and ffopen_open and I found that I was =20 running the updated code. roberto$ grep -Fr ffopen_open * event.c: motion_log(LOG_ERR, 1, "ffopen_open =20 error creating (new) file [%s]",cnt->newfilename); event.c: motion_log(LOG_ERR, 1, "ffopen_open =20 error creating (motion) file [%s]", cnt->motionfilename); event.c: motion_log(LOG_ERR, 1, "ffopen_open =20 error creating (timelapse) file [%s]", cnt->timelapsefilename); roberto$ grep -Fr avcodec_open * ffmpeg.c: if (avcodec_open(c, codec) < 0) { ffmpeg.c: motion_log(LOG_ERR, 1, "avcodec_open - could =20 not open codec"); My guess is that I will have the same problem with lastest SVN rev, =20 since the code is the same. What do you think? Best Regards, - -- Roberto Carvajal LOKO IT Services rca...@lo... El 21-09-2006, a las 3:33, Joerg WEBER escribi=F3: > Roberto, > > updating ffmpeg doesn't help. We have circumvented the problem in the > motion code, so no need to change anything in ffmpeg anymore. To be =20= > on the > safe side, you should use the motion codebase that Kenneth recommends: > > http://sourceforge.net/project/showfiles.php?=20 > group_id=3D13468&package_id=3D116390 > > > Brgds Joerg. > > > Roberto Carvajal wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> Thank you, >> >> >> I wonder if the ffmpeg version I'm using is safe. >> >> >> Should I update both motion and ffmpeg, or just updating motion is =20= >> fine? >> > > > --=20 > > > > ----------------------------------------------------------------------=20= > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to =20 > share your > opinions on IT & business topics through brief surveys -- and earn =20 > cash > http://www.techsay.com/default.php?=20 > page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV > _______________________________________________ > Motion-user mailing list > Mot...@li... > https://lists.sourceforge.net/lists/listinfo/motion-user > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFErlbhxx07QJWESMRAjnzAJ9Tu9Scs4cfYZVqwVBmR7A9Q2JjDACaA29j sLlINeGmV6KznE9/AZcJecM=3D =3Dy5l/ -----END PGP SIGNATURE----- |
From: Joerg W. <mo...@al...> - 2006-09-21 19:25:53
|
Robert, the bug that was reported some time ago is this one: http://www.lavrsen.dk/twiki/bin/view/Motion/BugReport2006x04x07x164654 It looks simmilar to what I had experienced and what you reported. It was fixed in revision 76. Are you sure that the binary you were running is including the fix? I haven't seen this error anymore since I'm running the fixed version. Brgds Joerg. Am Donnerstag, 21. September 2006 18:10 schrieb Roberto Carvajal: > Joerg, > > I updated motion to lastest SVN revision (110), this is the log: > > roberto$ svn update > U video_freebsd.c > U netcam_wget.h > U netcam_jpeg.c > U configure.in > U motion.c > U CHANGELOG > U CREDITS > U webhttpd.c > U README.axis_2100 > U netcam.c > U netcam_wget.c > Updated to revision 110. > > I see no ffmpeg.c changes nor at event.c, I was running revision 99 > before. > > I grep'ed for avcodec_open and ffopen_open and I found that I was > running the updated code. > > roberto$ grep -Fr ffopen_open * > event.c: motion_log(LOG_ERR, 1, "ffopen_open > error creating (new) file [%s]",cnt->newfilename); > event.c: motion_log(LOG_ERR, 1, "ffopen_open > error creating (motion) file [%s]", cnt->motionfilename); > event.c: motion_log(LOG_ERR, 1, "ffopen_open > error creating (timelapse) file [%s]", cnt->timelapsefilename); > > roberto$ grep -Fr avcodec_open * > ffmpeg.c: if (avcodec_open(c, codec) < 0) { > ffmpeg.c: motion_log(LOG_ERR, 1, "avcodec_open - could > not open codec"); > > My guess is that I will have the same problem with lastest SVN rev, > since the code is the same. > > What do you think? > > Best Regards, -- Brgds Joerg. |
From: Roberto C. <rca...@lo...> - 2006-09-24 23:15:26
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm using the updated binary, motion -h reports 3.2.7 which is SVN code. Turns out that in the newest machines we use (P4 3.0Ghz HT) the =20 HyperThreading feature makes conflict with the kernel, which results =20 into random system locks (freeze) and it was kind of a hard bug to =20 resolve. Since I disabled HT on the machine, I haven't got any issues. I think linux HT support isn't mature enough or the Intel Motherboard =20= is buggy, either way I won't use that feature anymorme :) I still got some random thread kills on other machines, I will check =20 if HT is enabled on those, if not, then we have a situation :) Will report back as soon as I have confirmation. Thanks for the help! Best regards, - -- Roberto Carvajal LOKO IT Services rca...@lo... El 21-09-2006, a las 15:25, Joerg WEBER escribi=F3: > Robert, > > the bug that was reported some time ago is this one: > > http://www.lavrsen.dk/twiki/bin/view/Motion/BugReport2006x04x07x164654 > > It looks simmilar to what I had experienced and what you reported. =20 > It was > fixed in revision 76. Are you sure that the binary you were running is > including the fix? I haven't seen this error anymore since I'm =20 > running the > fixed version. > > Brgds Joerg. > > > Am Donnerstag, 21. September 2006 18:10 schrieb Roberto Carvajal: >> Joerg, >> >> I updated motion to lastest SVN revision (110), this is the log: >> >> roberto$ svn update >> U video_freebsd.c >> U netcam_wget.h >> U netcam_jpeg.c >> U configure.in >> U motion.c >> U CHANGELOG >> U CREDITS >> U webhttpd.c >> U README.axis_2100 >> U netcam.c >> U netcam_wget.c >> Updated to revision 110. >> >> I see no ffmpeg.c changes nor at event.c, I was running revision 99 >> before. >> >> I grep'ed for avcodec_open and ffopen_open and I found that I was >> running the updated code. >> >> roberto$ grep -Fr ffopen_open * >> event.c: motion_log(LOG_ERR, 1, "ffopen_open >> error creating (new) file [%s]",cnt->newfilename); >> event.c: motion_log(LOG_ERR, 1, "ffopen_open >> error creating (motion) file [%s]", cnt->motionfilename); >> event.c: motion_log(LOG_ERR, 1, "ffopen_open >> error creating (timelapse) file [%s]", cnt->timelapsefilename); >> >> roberto$ grep -Fr avcodec_open * >> ffmpeg.c: if (avcodec_open(c, codec) < 0) { >> ffmpeg.c: motion_log(LOG_ERR, 1, "avcodec_open - could >> not open codec"); >> >> My guess is that I will have the same problem with lastest SVN rev, >> since the code is the same. >> >> What do you think? >> >> Best Regards, > > --=20 > > > Brgds Joerg. > > ----------------------------------------------------------------------=20= > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to =20 > share your > opinions on IT & business topics through brief surveys -- and earn =20 > cash > http://www.techsay.com/default.php?=20 > page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV > _______________________________________________ > Motion-user mailing list > Mot...@li... > https://lists.sourceforge.net/lists/listinfo/motion-user > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFFxHphxx07QJWESMRAib6AJ4wryTmRWe2k0/ui6pGEmvmat+p1ACZASoh 5vW7j6l0YHmzqACHgS290VY=3D =3DLy8j -----END PGP SIGNATURE----- |
From: Roberto C. <rca...@lo...> - 2006-09-28 04:15:04
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It happens once a week with a non HT computer. In a HT enabled PC it happens way more often. It seems the bug is still there. You reported a fix for the netcam code, which happens to use the same =20= "create video" function, perhaps the ffmpeg code needs a little bit =20 more work in order to work as well as the netcam code regarding this =20 issue. Not sure how to fix this, any help would be great.. Thanks, - -- Roberto Carvajal LOKO IT Services rca...@lo... El 24-09-2006, a las 19:16, Roberto Carvajal escribi=F3: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I'm using the updated binary, motion -h reports 3.2.7 which is SVN =20 > code. > > Turns out that in the newest machines we use (P4 3.0Ghz HT) the > HyperThreading feature makes conflict with the kernel, which results > into random system locks (freeze) and it was kind of a hard bug to > resolve. > > Since I disabled HT on the machine, I haven't got any issues. > > I think linux HT support isn't mature enough or the Intel Motherboard > is buggy, either way I won't use that feature anymorme :) > > I still got some random thread kills on other machines, I will check > if HT is enabled on those, if not, then we have a situation :) > > Will report back as soon as I have confirmation. > > Thanks for the help! > > Best regards, > - -- > Roberto Carvajal > LOKO IT Services > rca...@lo... > > > El 21-09-2006, a las 15:25, Joerg WEBER escribi=F3: > >> Robert, >> >> the bug that was reported some time ago is this one: >> >> http://www.lavrsen.dk/twiki/bin/view/Motion/=20 >> BugReport2006x04x07x164654 >> >> It looks simmilar to what I had experienced and what you reported. >> It was >> fixed in revision 76. Are you sure that the binary you were =20 >> running is >> including the fix? I haven't seen this error anymore since I'm >> running the >> fixed version. >> >> Brgds Joerg. >> >> >> Am Donnerstag, 21. September 2006 18:10 schrieb Roberto Carvajal: >>> Joerg, >>> >>> I updated motion to lastest SVN revision (110), this is the log: >>> >>> roberto$ svn update >>> U video_freebsd.c >>> U netcam_wget.h >>> U netcam_jpeg.c >>> U configure.in >>> U motion.c >>> U CHANGELOG >>> U CREDITS >>> U webhttpd.c >>> U README.axis_2100 >>> U netcam.c >>> U netcam_wget.c >>> Updated to revision 110. >>> >>> I see no ffmpeg.c changes nor at event.c, I was running revision 99 >>> before. >>> >>> I grep'ed for avcodec_open and ffopen_open and I found that I was >>> running the updated code. >>> >>> roberto$ grep -Fr ffopen_open * >>> event.c: motion_log(LOG_ERR, 1, "ffopen_open >>> error creating (new) file [%s]",cnt->newfilename); >>> event.c: motion_log(LOG_ERR, 1, "ffopen_open >>> error creating (motion) file [%s]", cnt->motionfilename); >>> event.c: motion_log(LOG_ERR, 1, "ffopen_open >>> error creating (timelapse) file [%s]", cnt->timelapsefilename); >>> >>> roberto$ grep -Fr avcodec_open * >>> ffmpeg.c: if (avcodec_open(c, codec) < 0) { >>> ffmpeg.c: motion_log(LOG_ERR, 1, "avcodec_open - could >>> not open codec"); >>> >>> My guess is that I will have the same problem with lastest SVN rev, >>> since the code is the same. >>> >>> What do you think? >>> >>> Best Regards, >> >> --=20 >> >> >> Brgds Joerg. >> >> ---------------------------------------------------------------------=20= >> - >> --- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to >> share your >> opinions on IT & business topics through brief surveys -- and earn >> cash >> http://www.techsay.com/default.php? >> page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV >> _______________________________________________ >> Motion-user mailing list >> Mot...@li... >> https://lists.sourceforge.net/lists/listinfo/motion-user >> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome >> > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > > iD8DBQFFFxHphxx07QJWESMRAib6AJ4wryTmRWe2k0/ui6pGEmvmat+p1ACZASoh > 5vW7j6l0YHmzqACHgS290VY=3D > =3DLy8j > -----END PGP SIGNATURE----- > > ----------------------------------------------------------------------=20= > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to =20 > share your > opinions on IT & business topics through brief surveys -- and earn =20 > cash > http://www.techsay.com/default.php?=20 > page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV > _______________________________________________ > Motion-user mailing list > Mot...@li... > https://lists.sourceforge.net/lists/listinfo/motion-user > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFG0yZhxx07QJWESMRAtQ8AJ9My7qN2gtDBR5B6PFzvbX4QEN0bwCgkmWy j6p7fh7+gOzk4ffdCa2RfT8=3D =3DDhj8 -----END PGP SIGNATURE----- |
From: Joerg W. <mo...@al...> - 2006-10-02 22:53:50
|
Am Donnerstag, 28. September 2006 06:16 schrieb Roberto Carvajal: > It happens once a week with a non HT computer. > > In a HT enabled PC it happens way more often. > > It seems the bug is still there. > Hi Roberto, Angel has found another ffmpeg function that is not thread safe. He has just committed his patch to SVN. (version 111) Can you please try the lastest SVN version to see if it fixes your problem? -- Brgds Joerg. |
From: Roberto C. <rca...@lo...> - 2006-10-02 23:02:37
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Great!! I'll test this ASAP and report back!, will try for a week or two. Thank you guys.. rob. - -- Roberto Carvajal LOKO IT Services rca...@lo... El 02-10-2006, a las 18:53, Joerg WEBER escribi=F3: > Am Donnerstag, 28. September 2006 06:16 schrieb Roberto Carvajal: >> It happens once a week with a non HT computer. >> >> In a HT enabled PC it happens way more often. >> >> It seems the bug is still there. >> > > > Hi Roberto, > > Angel has found another ffmpeg function that is not thread safe. He =20= > has just > committed his patch to SVN. (version 111) > > Can you please try the lastest SVN version to see if it fixes your =20 > problem? > > --=20 > > > Brgds Joerg. > > ----------------------------------------------------------------------=20= > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to =20 > share your > opinions on IT & business topics through brief surveys -- and earn =20 > cash > http://www.techsay.com/default.php?=20 > page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV > _______________________________________________ > Motion-user mailing list > Mot...@li... > https://lists.sourceforge.net/lists/listinfo/motion-user > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFIZsIhxx07QJWESMRAtFTAJ9C6bUiUpvyudDW1aCrooafs3FktwCfSpG1 qNeDqMEhql/7RS3wS65tGOI=3D =3D4gZ5 -----END PGP SIGNATURE----- |
From: Roberto C. <rca...@lo...> - 2006-10-18 08:15:37
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, I updated motion and it's working without any issue for almost =20 2 weeks, seems fixed to me! Thanks guys, this problem was bugging me for a long time.. r. - -- Roberto Carvajal LOKO IT Services rca...@lo... El 02-10-2006, a las 19:04, Roberto Carvajal escribi=F3: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Great!! > > I'll test this ASAP and report back!, will try for a week or two. > > Thank you guys.. > > rob. > - -- > Roberto Carvajal > LOKO IT Services > rca...@lo... > > > El 02-10-2006, a las 18:53, Joerg WEBER escribi=F3: > >> Am Donnerstag, 28. September 2006 06:16 schrieb Roberto Carvajal: >>> It happens once a week with a non HT computer. >>> >>> In a HT enabled PC it happens way more often. >>> >>> It seems the bug is still there. >>> >> >> >> Hi Roberto, >> >> Angel has found another ffmpeg function that is not thread safe. He >> has just >> committed his patch to SVN. (version 111) >> >> Can you please try the lastest SVN version to see if it fixes your >> problem? >> >> --=20 >> >> >> Brgds Joerg. >> >> ---------------------------------------------------------------------=20= >> - >> --- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to >> share your >> opinions on IT & business topics through brief surveys -- and earn >> cash >> http://www.techsay.com/default.php? >> page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV >> _______________________________________________ >> Motion-user mailing list >> Mot...@li... >> https://lists.sourceforge.net/lists/listinfo/motion-user >> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome >> > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > > iD8DBQFFIZsIhxx07QJWESMRAtFTAJ9C6bUiUpvyudDW1aCrooafs3FktwCfSpG1 > qNeDqMEhql/7RS3wS65tGOI=3D > =3D4gZ5 > -----END PGP SIGNATURE----- > > ----------------------------------------------------------------------=20= > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to =20 > share your > opinions on IT & business topics through brief surveys -- and earn =20 > cash > http://www.techsay.com/default.php?=20 > page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV > _______________________________________________ > Motion-user mailing list > Mot...@li... > https://lists.sourceforge.net/lists/listinfo/motion-user > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFNeMjhxx07QJWESMRAk1gAKC57lR0P6p8tbb2FDrFjJcrmAfKoQCfd2EU vtoBp72bM+FzdFA9wlQju68=3D =3D6CY+ -----END PGP SIGNATURE----- |
From: Angel C. <ac...@te...> - 2006-10-18 08:31:51
|
El mi=C3=A9, 18-10-2006 a las 05:17 -0300, Roberto Carvajal escribi=C3=B3: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Well, I updated motion and it's working without any issue for almost =20 > 2 weeks, seems fixed to me! >=20 > Thanks guys, this problem was bugging me for a long time.. >=20 > r. > - -- > Roberto Carvajal > LOKO IT Services > rca...@lo... >=20 Great !! so seems that the problem was related to ffmpeg not thread safe functions :) That are fixed already. > > El 02-10-2006, a las 18:53, Joerg WEBER escribi=C3=B3: > > > >> Am Donnerstag, 28. September 2006 06:16 schrieb Roberto Carvajal: > >>> It happens once a week with a non HT computer. > >>> > >>> In a HT enabled PC it happens way more often. > >>> > >>> It seems the bug is still there. > >>> > >> > >> > >> Hi Roberto, > >> > >> Angel has found another ffmpeg function that is not thread safe. He > >> has just > >> committed his patch to SVN. (version 111) > >> > >> Can you please try the lastest SVN version to see if it fixes your > >> problem? > >> > >> --=20 > >> > >> > >> Brgds Joerg. Cheers, --=20 Angel Carpintero ack ( at ) telefonica ( dot ) net Key fingerprint =3D 3FD3 9C90 149E 7824 CECD 6BCF AC2C CA61 6EF1 B90D "No basta saber, hay que aplicar lo que se sabe;=20 no basta querer hacerlas cosas, hay que hacerlas". "Knowing is not enough; we must apply.=20 Willing is not enough; we must do" Johann Wolfgang von Goethe |