AVbin 9 Released

[Nathan]

I just released AVbin 9. Unfortunately, I believe that most pyglet
users should stick to version 8.1 for now. Basically, I improved the
build process quite a bit, generated test sounds and videos, and
switched from FFmpeg to Libav, but the actual end product is more
buggy due to the Libav branch that I used for this release.

See the links below for more details:

Announcement - http://goo.gl/cA2dB

Known Issues - http://avbin.github.com/AVbin/Testing.html

~ Nathan

[anatoly techtonik]

-DEPRECATED avbin_get_ffmpeg_revision()

-ADDED avbin_get_libav_commit()

-ADDED avbin_get_libav_version()

If it is not clear which lib are you going to stick with, maybe it's better to use avbin_get_backend_type() and avbin_get_backend_version()?

[Richard Jones]

Indeed - the whole point of avbin though is ABI stability. Perhaps you could even stick with the old API and just include a reference to libav in the version info?

Sent from my portable device, please excuse the brevity.

--
You received this message because you are subscribed to the Google Groups "pyglet-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/pyglet-users/-/1nv1_Xi2M1cJ.
To post to this group, send email to pyglet...@googlegroups.com.
To unsubscribe from this group, send email to pyglet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.

[Nathan]

On Sat, Jul 7, 2012 at 1:36 AM, Richard Jones <r1char...@gmail.com> wrote:
> Indeed - the whole point of avbin though is ABI stability. Perhaps you could
> even stick with the old API and just include a reference to libav in the
> version info?

Unfortunately, sticking with the old API isn't possible in this case.
The old API returns an integer which used to represent SVN revision
number. Any sane representation of release version number (0.6.6) or
git commit (123abc456...) requires returning a string. 6 years
without an API change...that's pretty awesome. :-)

On Fri, Jul 6, 2012 at 11:02 PM, anatoly techtonik <tech...@gmail.com> wrote:
> If it is not clear which lib are you going to stick with, maybe it's better
> to use avbin_get_backend_type() and avbin_get_backend_version()?

That's an excellent idea. I think we can even take that a bit further!

How about this set of functions?

+ avbin_get_backend_name() ("Libav")
+ avbin_get_backend_version() ("0.6.6")
+ avbin_get_backend_repo() ("https://github.com/AVbin/libav.git")
+ avbin_get_backend_commit() ("123abc456def...")

Those functions would be pretty flexible and not require future renaming.

I added that as issue 24:

https://github.com/AVbin/AVbin/issues/24

~ Nathan

[Richard Jones]

On 9 July 2012 09:40, Nathan <nathan...@gmail.com> wrote:
> On Sat, Jul 7, 2012 at 1:36 AM, Richard Jones <r1char...@gmail.com> wrote:
>> Indeed - the whole point of avbin though is ABI stability. Perhaps you could
>> even stick with the old API and just include a reference to libav in the
>> version info?
>
> Unfortunately, sticking with the old API isn't possible in this case.
> The old API returns an integer which used to represent SVN revision
> number.

Ah, ok. Please excuse my speaking from ignorance :-)



Richard

[Nathan]

Don't worry about it! I actually planned to just modify that function
myself, until I got into it and discovered it returned an integer...

~ Nathan

[anatoly techtonik]

On Mon, Jul 9, 2012 at 2:40 AM, Nathan <nathan...@gmail.com> wrote:
> On Sat, Jul 7, 2012 at 1:36 AM, Richard Jones <r1char...@gmail.com> wrote:
>> Indeed - the whole point of avbin though is ABI stability. Perhaps you could
>> even stick with the old API and just include a reference to libav in the
>> version info?
>
> Unfortunately, sticking with the old API isn't possible in this case.
> The old API returns an integer which used to represent SVN revision
> number. Any sane representation of release version number (0.6.6) or
> git commit (123abc456...) requires returning a string. 6 years
> without an API change...that's pretty awesome. :-)
>
> On Fri, Jul 6, 2012 at 11:02 PM, anatoly techtonik <tech...@gmail.com> wrote:
>> If it is not clear which lib are you going to stick with, maybe it's better
>> to use avbin_get_backend_type() and avbin_get_backend_version()?
>
> That's an excellent idea. I think we can even take that a bit further!
>
> How about this set of functions?
>
> + avbin_get_backend_name() ("Libav")
> + avbin_get_backend_version() ("0.6.6")
> + avbin_get_backend_repo() ("https://github.com/AVbin/libav.git")
> + avbin_get_backend_commit() ("123abc456def...")

The last two are too excessive - will needlessly bloat the API.
avbin_get_backend_version(details=True) can return "%s %s %s %s" with
all this information.

[Nathan]

On Mon, Jul 9, 2012 at 1:59 AM, anatoly techtonik <tech...@gmail.com> wrote:
>> How about this set of functions?
>>
>> + avbin_get_backend_name() ("Libav")
>> + avbin_get_backend_version() ("0.6.6")
>> + avbin_get_backend_repo() ("https://github.com/AVbin/libav.git")
>> + avbin_get_backend_commit() ("123abc456def...")
>
> The last two are too excessive - will needlessly bloat the API.
> avbin_get_backend_version(details=True) can return "%s %s %s %s" with
> all this information.

Hmm. I don't like the idea of requiring parsing to make sense of a
response, but I do like the idea of not adding tons of functions.

Perhaps I should consolidate it into one function call, maybe
avbin_get_info() which returns a struct with all of this sort of
version metadata. I could include AVbin-specific information like the
release number as well, and then the calling function can simply
access whichever information it is interested in.

~ Nathan

[anatoly techtonik]

If AVbin version info is not present anywhere then avbin_get_info()
looks like is a way to go to me.
--
anatoly t.