GPAC offers the possibility to create unregistered properties using a string identifier. This opens great possibilities but GPAC doesn't handle collisions at all.

There is only one property with a given name per packet. This is an issue for example when a stream of packet carry the property and the packet rate is diminished: some of these properties are lost.

Another example (related to https://github.com/gpac/gpac/pull/2748) is id3 metadata. When carried in MPEG-TS PES streams they may not have any PTS. We then assign them to the next (audio) packet. However if we get several of them at once they are not merged but silently lost ; the mpeg2-ts demuxer could merge them but the current API doesn't allow it.

Just triggering the discussion at this point on what to do.
Question about unregistered packet properties
This is a GitHub Issue
repo:gpac
owner:gpac
Title : Question about unregistered packet properties
Issue date:

--- start body ---
GPAC offers the possibility to create unregistered properties using a string identifier. This opens great possibilities but GPAC doesn't handle collisions at all.

There is only one property with a given name per packet. This is an issue for example when a stream of packet carry the property and the packet rate is diminished: some of these properties are lost.

Another example (related to https://github.com/gpac/gpac/pull/2748) is id3 metadata. When carried in MPEG-TS PES streams they may not have any PTS. We then assign them to the next (audio) packet. However if we get several of them at once they are not merged but silently lost ; the mpeg2-ts demuxer could merge them but the current API doesn't allow it.

Just triggering the discussion at this point on what to do.
--- end body ---
