The muxer is still at an early 'draft state', but what concerns me more at this point is creating the MPEG4 Atoms hierarchy to be used by the muxer. This hierarchy will last during the whole project and it could cause some headaches later.
I thought of two main options:
- Create a gobject class hierarchy: it is better organized and we could have some common interfaces, but it would be probably too much of a overhead
- Create a 'struct hierarchy': composing structs is pretty easy and straightforward to do. Having common structs at the top place might also provide some common methods, but probably difficult to maintain
Other than that, I'll be starting a repository to put the code in the following days, so that interested people might take a look at it.
1 comment:
For the internal atom representation, you don't need all the extra gobject bling (introspection, properties, methods, etc...), so I would recommend just going with the struct solution.
Post a Comment