-------- Original-Nachricht -------- > Datum: Fri, 27 Aug 2010 20:31:14 +0200 > Von: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> > An: haiku-commits@xxxxxxxxxxxxx > Betreff: [haiku-commits] Re: r38403 - in haiku/trunk: build/jam > src/add-ons/media/plugins src/add-ons/media/plugins/ffmpeg > superstippi@xxxxxx wrote: > > If there are regressions after this commit at all (I tested a lot of > > files), then I anticipate only that the ffmpeg plugin does not > > advertise > > support for files it could actually handle (i.e. easily fixable). In > > those cases hopefully a test stream can be made available. If the > > native mp4 reader is improved to the point that it works as well as > > the ffmpeg mp4 demuxer, we can easily switch it back, but for now, > > users > > will prefer reliable playback. > > Very welcomed changes, thanks! > Have you by any chance thought about how to properly support B-frames > in the decoder/encoder API? Since we define the API, and it's still not > considered stable, we could easily change that, at least. No, I haven't given it any thought and don't understand very much about it either. I am considering to import libx264 alongside the ffmpeg libs and perhaps even some more like theora and so on (which are already imported at a different place) to enable the support for these external libraries in the avcodec/avformat libs. Then one could most easily offer for example x264 encoding, and while doing so one could see what deficiencies are in the current API. On the other hand I wanted to look into rewriting the MediaPlayer playback backend (the node synchronization part), since I am not happy with it yet. It's somewhat too complicated on the one hand, and doesn't offer some other features at the same time. And while working on MediaPlayer I could make it more pleasant to use by fixing some of the many reported issues. Best regards, -Stephan