search for: libmatroska

...Requires: libebml.so.2()(64bit) Removing: libebml-1.0.0-1.el6.rf.x86_64 (@rpmforge) libebml.so.2()(64bit) Updated By: libebml-1.2.1-1.el6.x86_64 (epel) Not found Error: Package: vlc-1.1.13-1.el6.rf.x86_64 (@rpmforge) Requires: libmatroska.so.2()(64bit) Removing: libmatroska-1.0.0-1.el6.rf.x86_64 (@rpmforge) libmatroska.so.2()(64bit) Updated By: libmatroska-1.2.0-1.el6.x86_64 (epel) Not found Error: Package: vlc-1.1.13-1.el6.rf.x86_64 (@rpmforge) Requires: libmodplug...

On 6/5/2015 10:05 AM, Michael Hennebry wrote: > > ... audacity... > > I just got it from an epel repository, > but it caused problems with yum. what sort of problems? -- john r pierce, recycling bits in santa cruz

https://bugs.freedesktop.org/show_bug.cgi?id=86006 Bug ID: 86006 Summary: [NV84] Nvidia GeForce 8600 GT VDPAU h264 hardware acceleration Product: xorg Version: 7.6 (2010.12) Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

...d.so.0 is needed by vlc-0.8.6a-2.el4.rf.i386 libid3tag.so.0 is needed by vlc-0.8.6a-2.el4.rf.i386 libiso9660.so.5 is needed by vlc-0.8.6a-2.el4.rf.i386 liblirc_client.so.0 is needed by vlc-0.8.6a-2.el4.rf.i386 libmad.so.0 is needed by vlc-0.8.6a-2.el4.rf.i386 libmatroska.so.0 is needed by vlc-0.8.6a-2.el4.rf.i386 libmodplug.so.0 is needed by vlc-0.8.6a-2.el4.rf.i386 libmp3lame.so.0 is needed by vlc-0.8.6a-2.el4.rf.i386 libmpcdec.so.3 is needed by vlc-0.8.6a-2.el4.rf.i386 libmpeg2.so.0 is needed by vlc-0.8.6a-2.el4.rf.i386 lib...

...om various other opensource projects in the multimedia environment, we were able to come up with a working specification for the container end of 2002. From this spec our chief developer and project administrator, Steve 'robux4' Lhomme, could code a working basic I/O library called 'libmatroska', which was released in alpha version to interested OSS developers beginning of this year. Since then all efforts were undertaken to make file creation and playback possible, and in the meantime the main library was steadily developed further to its actual status. The matroska container is...

...e MCF project because of incompatibilities of our work with the project goals defined by the founder of MCF ( TMF ), Lasse 'Tronic' Karkainen, especially with respect to the latest specs Steve had been writing and documenting here http://matroska.sourceforge.net/specs/ ( replace libmcf with libmatroska, will be updated soon ) . Tronic himself could not be actively participating on the project lately, due to the fact that his courses at university didnt leave him much time to do so. Steve and myself have been developing the project further, and now we find ourselves in the situation that the resu...

...e MCF project because of incompatibilities of our work with the project goals defined by the founder of MCF ( TMF ), Lasse 'Tronic' Karkainen, especially with respect to the latest specs Steve had been writing and documenting here http://matroska.sourceforge.net/specs/ ( replace libmcf with libmatroska, will be updated soon ) . Tronic himself could not be actively participating on the project lately, due to the fact that his courses at university didnt leave him much time to do so. Steve and myself have been developing the project further, and now we find ourselves in the situation that the resu...

...worked on. And since I consider it fills all past missing gaps in the specs and is far superior in expandability, I don't want that format to die. There is also a libmcf library already existing that I coded 90% a while back. And since MCF and Matroska are twins this code will be used for libmatroska, and I think we'll be able to parse/create Matroska files quite fast (we're only missing UCI then). > "Step one: Achieve something. Step two: toot horn" I strongly agree with this. But Christian's announcement wasn't to announce that the format is final and the code...

...worked on. And since I consider it fills all past missing gaps in the specs and is far superior in expandability, I don't want that format to die. There is also a libmcf library already existing that I coded 90% a while back. And since MCF and Matroska are twins this code will be used for libmatroska, and I think we'll be able to parse/create Matroska files quite fast (we're only missing UCI then). > "Step one: Achieve something. Step two: toot horn" I strongly agree with this. But Christian's announcement wasn't to announce that the format is final and the code...