From owner-freebsd-multimedia@FreeBSD.ORG Tue May 3 06:44:19 2005 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6389D16A4CE for ; Tue, 3 May 2005 06:44:19 +0000 (GMT) Received: from mail231.csoft.net (resin.csoft.net [63.111.22.86]) by mx1.FreeBSD.org (Postfix) with SMTP id C9A7443D58 for ; Tue, 3 May 2005 06:44:18 +0000 (GMT) (envelope-from jakemsr@jakemsr.com) Received: (qmail 7232 invoked from network); 3 May 2005 06:50:25 -0000 Received: from unknown (HELO puff.jakemsr.gom) (63.111.27.87) by mail231.csoft.net with SMTP; 3 May 2005 06:50:25 -0000 Received: (from jakemsr@jakemsr.com) by puff.jakemsr.gom (mini_sendmail/1.3.5 16nov2003); Mon, 02 May 2005 23:44:17 PDT (sender jakemsr@puff.jakemsr.gom) Date: Mon, 2 May 2005 23:44:17 -0700 From: Jacob Meuser To: freebsd-multimedia@freebsd.org Message-ID: <20050503064417.GE11140@puff.jakemsr.gom> Mail-Followup-To: freebsd-multimedia@freebsd.org References: <20050502043610.51034.qmail@exxodus.fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050502043610.51034.qmail@exxodus.fedaykin.here> User-Agent: Mutt/1.4.2i Subject: Re: New ffmpeg CVS versions X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2005 06:44:19 -0000 On Mon, May 02, 2005 at 01:35:47AM -0300, Mario Sergio Fujikawa Ferreira wrote: > Hi, > > Latest ffmpeg official release happened a long time ago. > However, the CVS version has been evolving VERY fast. Lots of fixes > and brand new features. yeah, especially for amd64, and 64-bit archs in general as positive fallout. that's why the OpenBSD port is back to using snapshots ;) > I have just wrote a sample of the possible final ffmpeg-devel > CVS port. I would like feedback on what could be improved or if > there are some bugs left on the port. Specially from users of > architectures other than i386. > > Side effects, Michael Johnson has found > a few "drawbacks" which will be probably fixed by the time you read > this email. Both vlc and mplayer have some problems with a52 symbols > but probably adding -la52 to their build chains should work. That's > ahze's suggestion :) > > IPV6 support seems to be broken but I won't have a IPV6 > kernel box until tomorrow night so I hope someone has a fix before > that. > > Please, test the bktr(4) grabbing code if you can because > that's the main part I had no way to test it. > > Also, I did not test to the correct places to set fPIC and fPIE > so if some kind soul does it before I can reach my computer in > 19 hours; I'll really appreciate it. Please try submitting patches > alongside your suggestions but do not refrain just because you do > not have a patch handy. > > This is all about improving both the accuracy and the speed > of ffmpeg playback. > > There are 2 versions of the ffmpeg-devel port: > > 1 - build and works > port -> ffmpeg-cvs-20050427.tar.gz > distfile -> ffmpeg-devel-20050427.tar.gz > 2 - does not build, it breaks when trying to build the bktr(4) > grabbing code. I'll appreciate help fixing it > port -> ffmpeg-cvs-20050502.tar.gz > distfile -> ffmpeg-devel-20050502.tar.gz > > Instructions, fetch the distfiles and place them into > /usr/ports/distfiles. Then extract the ports at the place of your > convenience and try building them. > > Bear in mind, that installing these ports might compromise > the stability of vlc, mplayer and some other ports dependent > on ffmpeg. > > However, I might say that it is ALL working for me. > > ps: Try ffplay instead of mplayer and tell me what you think about > both of them. IMO, ffplay is always the preferred playback testing tool. i've seen mplayer stutter on stuff ffplay (an others) played smoothly. > pss: As long as we are here, what about adding ring buffering (video > and time) support to bktr(4) ffmpeg. It should automatically escalate > spinoffs like mplayer, xine, gstreamer, vlc... just to name a few. > Not a small thing to consider. also, try to convince the ffmpeg > "council" to add our grab code to the cvs once in for all. :) indeed, there should be bktr support in FFmpeg CVS. I was thinking about asking Steve for his OK, since it's his code, to submit it to ffmpeg-devel, along with the necessary configure/Makefile changes. I've been toying around with buffers, etc, in my bktr capture toys (http://www.jakemsr.com/bsdav/) but am still awaiting that moment of clarity when it all clicks together in a nice _simple_ manner. --