Dikirim dari ponsel cerdas BlackBerry 10 saya dengan jaringan XL. Pesan Asli Dari: [email protected] Terkirim: Minggu, 11 Januari 2015 03.02 Ke: [email protected] Balas Ke: [email protected] Perihal: Lives-users Digest, Vol 69, Issue 4
Send Lives-users mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/lives-users or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Lives-users digest..." Today's Topics: 1. Re: unable to read audio while encoding (Kyle) 2. Re: unable to read audio while encoding (salsaman) 3. Re: unable to read audio while encoding (Kyle) 4. undefined reference to `lives_widget_ensure_style' (Chris) 5. Re: unable to read audio while encoding (salsaman) 6. Re: unable to read audio while encoding (salsaman) ---------------------------------------------------------------------- Message: 1 Date: Thu, 08 Jan 2015 19:15:19 -0500 From: Kyle <[email protected]> Subject: Re: [Lives-users] unable to read audio while encoding To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=UTF-8; format=flowed Try this link instead. http://kyle.tk/LiVES%20Screenshot.png Hope it helps. -- "Don't judge my disability until you are able to see my ability." ~Kyle: https://kyle.tk/ My chunk of the internet: https://chunkhost.com/r/Kyle ------------------------------ Message: 2 Date: Thu, 8 Jan 2015 21:27:19 -0300 From: salsaman <[email protected]> Subject: Re: [Lives-users] unable to read audio while encoding To: LiVES users list <[email protected]> Message-ID: <CAA74=eudrnevze8p+_lxkhes2nh3d7xdw046ypnvgh8vhgr...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Thanks, that is quite useful. I noticed there was a parenthesis missing in x264_encoder, which must have been there since I added mplayer2 support in version 2.2.5. Anyway if you update svn and re install then that may fix the problem. Otherwise please send me the text of the encoder log using one of the methods I mentioned earlier. Regards, Gabriel. http://lives.sourceforge.net https://www.openhub.net/accounts/salsaman On Thu, Jan 8, 2015 at 9:15 PM, Kyle <[email protected]> wrote: > Try this link instead. > http://kyle.tk/LiVES%20Screenshot.png > Hope it helps. > -- > "Don't judge my disability until you are able to see my ability." > ~Kyle: https://kyle.tk/ > My chunk of the internet: https://chunkhost.com/r/Kyle > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > Lives-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lives-users > -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 3 Date: Thu, 08 Jan 2015 20:47:44 -0500 From: Kyle <[email protected]> Subject: Re: [Lives-users] unable to read audio while encoding To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=UTF-8; format=flowed I'm still seeing the same error message, but this time, clicking "show details" crashed LiVES again, but this time with very little information of any use except the possibly useful lines: GLib-GObject Critical error: g_object_unref: assertion 'G_IS_OBJECT (object)' failed LiVES error: Unable to read from the file /run/media/kyle/USB3HDD/livestmp//199705230/audio It appears that LiVES did save the encoder log this time, as the file has previously been empty, so there was nothing to send you. I have the file at http://kyle.tk/encoder_log_1000_100.txt I see all kinds of funny things in here, which may indicate that I'm doing something rather abnormal or unexpected with the encoder options, but I'm having difficulty decrypting the messages I see, so I'm not finding anything that I know for sure could be causing the inability to read the audio data, only indicators that my ffv1 video may not be any good once it gets encoded. The problem is that ffv1 is the only video encoding I can see in the encoder options that is supposed to be lossless, which will allow me to do further editing once the clip has been encoded, e.g. incorporating the clip into other clips and/or applying other effects, without losing video or audio quality each time I perform further actions on the clips. If you have any further ideas about how I can do this that may work better, please do let me know, although I have used these same options several years ago, and I recall everything working perfectly. Thanks again for all your help. -- "Don't judge my disability until you are able to see my ability." ~Kyle: https://kyle.tk/ My chunk of the internet: https://chunkhost.com/r/Kyle ------------------------------ Message: 4 Date: Thu, 08 Jan 2015 20:21:22 -0600 From: Chris <[email protected]> Subject: [Lives-users] undefined reference to `lives_widget_ensure_style' To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset="UTF-8" I asked this a week ago or so and it's like no one ever saw it. So, I'll try again. Trying to build Lives 2.2.7. Configure seems to run ok at least I don't see any errors. When running make it runs for a few seconds then stops with: In function `create_LiVES': /home/chris/lives-2.2.7/src/gui.c:317: undefined reference to `lives_widget_ensure_style' collect2: error: ld returned 1 exit status make[1]: *** [lives-exe] Error 1 make[1]: Leaving directory `/home/chris/lives-2.2.7/src' make: *** [all-recursive] Error 1 Does anyone have any idea what may be causing this? Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11?N 97.89?W (Elev. 1092 ft) 20:18:20 up 10:27, 2 users, load average: 0.23, 0.27, 0.37 Ubuntu 14.04.1 LTS, kernel 3.14.0-031400-generic ------------------------------ Message: 5 Date: Fri, 9 Jan 2015 00:29:43 -0300 From: salsaman <[email protected]> Subject: Re: [Lives-users] unable to read audio while encoding To: LiVES users list <[email protected]> Message-ID: <CAA74=euyblf_-ykndnq_d2wzmafheubwwf3hrm207nuz7ji...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" OK, making progress ! I was able to reproduce the errors here. I have fixed the crash in "Show Details" after the encoding fails. I'll take a look at the encoder plugin failures next. Regards, Gabriel. http://lives.sourceforge.net https://www.openhub.net/accounts/salsaman On Thu, Jan 8, 2015 at 10:47 PM, Kyle <[email protected]> wrote: > I'm still seeing the same error message, but this time, clicking "show > details" > crashed LiVES again, but this time with very little information of any use > except the possibly useful lines: > > GLib-GObject Critical error: g_object_unref: assertion 'G_IS_OBJECT > (object)' failed > LiVES error: Unable to read from the file > /run/media/kyle/USB3HDD/livestmp//199705230/audio > > It appears that LiVES did save the encoder log this time, as the file has > previously been empty, so there was nothing to send you. I have the file at > http://kyle.tk/encoder_log_1000_100.txt > I see all kinds of funny things in here, which may indicate that I'm doing > something rather abnormal or unexpected with the encoder options, but I'm > having > difficulty decrypting the messages I see, so I'm not finding anything that > I > know for sure could be causing the inability to read the audio data, only > indicators that my ffv1 video may not be any good once it gets encoded. The > problem is that ffv1 is the only video encoding I can see in the encoder > options > that is supposed to be lossless, which will allow me to do further editing > once > the clip has been encoded, e.g. incorporating the clip into other clips > and/or > applying other effects, without losing video or audio quality each time I > perform further actions on the clips. If you have any further ideas about > how I > can do this that may work better, please do let me know, although I have > used > these same options several years ago, and I recall everything working > perfectly. > Thanks again for all your help. > -- > "Don't judge my disability until you are able to see my ability." > ~Kyle: https://kyle.tk/ > My chunk of the internet: https://chunkhost.com/r/Kyle > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > Lives-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lives-users > -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 6 Date: Sat, 10 Jan 2015 17:01:22 -0300 From: salsaman <[email protected]> Subject: Re: [Lives-users] unable to read audio while encoding To: LiVES users list <[email protected]> Message-ID: <CAA74=eWr22-bwdS0CJ_-pvUzoSWgYLPFjpxHz=otfz_bgkj...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Kyle, I had a look at your screenshot and I noticed that you were using mencoder_encoder with the ffv1 codec. I reproduced this at home and noticed a minor error with the mencoder_encoder (it was using mp3 audio encoding instead of pcm). Fixed that and checked it in to svn. After this I was able to encode a clip succesfully with mencoder_encoder / ffv1. I did not encounter any problems with the audio file permissions. To summarise, unfortunately you encountered 4 bugs, 3 of which have now been fixed in svn. 1) avcodec_close_input_file deprecated from libav. This has now been fixed by substituting avformat_close_input when available. 2) a crash when clicking on "Show Details" after encoding fails. This has been fixed in svn. 3) a problem with audio encoding format in the mencoder_encoder, affecting ffv1 format. Fixed in subversion. Thanks for your assistance with reporting these ! 4) final issue: permissions problem accessing audio file during encoding. I was not able to reproduce this so far. To reiterate, with the latest svn version I followed the steps in your screenshot, and succesfully encoded a clip. I was also able to do it manually by going into one of the clip directories with .png files. I entered the command from your encoder log: mencoder -mf fps=29.97002983:type=png -vc mpng -o "tmpvid" -ovc lavc -lavcopts vcodec=ffv1:vhq:format=BGR32 -noskip mf://*.png -frames 80 This worked and I was able to play back tmpvid with mplayer. I noticed one difference however, in your log there are many lines that read: "[ffv1 @ 0x7f8e029af000]Provided packet is too small, needs to be 48400384". I did not get this error myself. So in this case it could be a bug in your version of libav. Finally, I noticed that you seem to be running with livestmp on an external drive. I believe this may be the cause of the permissions problems as you may be using a vfat or fat32 partition. I have just checked in a patch which I hope will fix this. If you can update once more from subversion and test it out it would be great. Regards, Gabriel. http://lives.sourceforge.net https://www.openhub.net/accounts/salsaman On Fri, Jan 9, 2015 at 12:29 AM, salsaman <[email protected]> wrote: > OK, making progress ! I was able to reproduce the errors here. I have > fixed the crash in "Show Details" after the encoding fails. > > I'll take a look at the encoder plugin failures next. > > Regards, > Gabriel. > > > > http://lives.sourceforge.net > https://www.openhub.net/accounts/salsaman > > On Thu, Jan 8, 2015 at 10:47 PM, Kyle <[email protected]> wrote: > >> I'm still seeing the same error message, but this time, clicking "show >> details" >> crashed LiVES again, but this time with very little information of any use >> except the possibly useful lines: >> >> GLib-GObject Critical error: g_object_unref: assertion 'G_IS_OBJECT >> (object)' failed >> LiVES error: Unable to read from the file >> /run/media/kyle/USB3HDD/livestmp//199705230/audio >> >> It appears that LiVES did save the encoder log this time, as the file has >> previously been empty, so there was nothing to send you. I have the file >> at >> http://kyle.tk/encoder_log_1000_100.txt >> I see all kinds of funny things in here, which may indicate that I'm doing >> something rather abnormal or unexpected with the encoder options, but I'm >> having >> difficulty decrypting the messages I see, so I'm not finding anything >> that I >> know for sure could be causing the inability to read the audio data, only >> indicators that my ffv1 video may not be any good once it gets encoded. >> The >> problem is that ffv1 is the only video encoding I can see in the encoder >> options >> that is supposed to be lossless, which will allow me to do further >> editing once >> the clip has been encoded, e.g. incorporating the clip into other clips >> and/or >> applying other effects, without losing video or audio quality each time I >> perform further actions on the clips. If you have any further ideas about >> how I >> can do this that may work better, please do let me know, although I have >> used >> these same options several years ago, and I recall everything working >> perfectly. >> Thanks again for all your help. >> -- >> "Don't judge my disability until you are able to see my ability." >> ~Kyle: https://kyle.tk/ >> My chunk of the internet: https://chunkhost.com/r/Kyle >> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming! The Go Parallel Website, >> sponsored by Intel and developed in partnership with Slashdot Media, is >> your >> hub for all things parallel software development, from weekly thought >> leadership blogs to news, videos, case studies, tutorials and more. Take a >> look and join the conversation now. http://goparallel.sourceforge.net >> _______________________________________________ >> Lives-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/lives-users >> > > -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ------------------------------ _______________________________________________ Lives-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lives-users End of Lives-users Digest, Vol 69, Issue 4 ****************************************** ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ Lives-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lives-users
