GStreamer issueshttps://gitlab.freedesktop.org/groups/gstreamer/-/issues2023-05-18T16:10:52Zhttps://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2581[2.0] encoder elements should all use bits/sec as the unit for bitrate proper...2023-05-18T16:10:52ZBugzilla Migration User[2.0] encoder elements should all use bits/sec as the unit for bitrate properties## Submitted by Thomas Vander Stichele `@thomasvs`
**[Link to original bug (#337409)](https://bugzilla.gnome.org/show_bug.cgi?id=337409)**
## Description
theoraenc for example uses kbit/sec
it's an ABI change so we have to do i...## Submitted by Thomas Vander Stichele `@thomasvs`
**[Link to original bug (#337409)](https://bugzilla.gnome.org/show_bug.cgi?id=337409)**
## Description
theoraenc for example uses kbit/sec
it's an ABI change so we have to do it in 0.112.xhttps://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/453structure/caps: cleaner nested serialization2021-09-24T11:09:03ZHenry Wilkesstructure/caps: cleaner nested serializationThis is a suggestion for tidying up the serialization of nested GstStructures/GstCaps (or any type that needs to include the serialization of other types as part of its own serialization) to make them more readable.
E.g. currently, if y...This is a suggestion for tidying up the serialization of nested GstStructures/GstCaps (or any type that needs to include the serialization of other types as part of its own serialization) to make them more readable.
E.g. currently, if you have three nested structures `si`, for `i=1,2,3`, where `si` contains the GstStructure value `ni=s(i+1)` when `i=1,2` and the string value `vi="i "`, then calling `gst_structure_to_string(s1)` will produce the string:
```
s1, v1=(string)"1\ ", n1=(structure)"s2\,\ v2\=\(string\)\"2\\\ \"\,\ n2\=\(structure\)\"s3\\\,\\\ v3\\\=\\\(string\\\)\\\"3\\\\\\\ \\\"\\\;\"\;";
```
So, `s(i+1)`'s string is escaped before inserting it into `si`, which means that `s3` ends up being doubly escaped.
It seems that the primary reason all these levels of escaping are needed are because the character `"` is used as both the opening and closing delimiter for the value, so each `"` needs to be escaped several times so we don't confuse it with the end delimiter, but it also results in all escape sequences becoming very long!
I would suggest that the serialization process should use different delimiters for opening and closing a value which may well contain other serialized values. This because you can read in such a string and count every time you reach an unescaped open delimiter, and every time you reach an unescaped closing delimiter, and once they cancel out you have the end of the field. And this would only require that any other appearances of the delimiter characters are escaped _once_, regardless of how many levels of nesting are present.
One choice would be to use backtick and apostrophe. As far as I'm aware, the only basic type that will serialize to include a backtick or apostrophe would be a string, but these characters are already escaped (there is a potential issue with apostrophes and backticks being used in field names, but that is a separate bigger issue https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/433). I'm used to using backtick and apostrophe from writing in LaTeX, where they are used to open and close quotes, but I know people can be averse to the backtick. Note, all the bracket delimiters are already used for types, ranges, arrays and lists. The other option would be to use some sequence of characters.
So, for example, the above structure would instead become
```
s1, v1=(string)"1\ ", n1=(structure)`s2, v2=(string)"2\ ", n2=(structure)`s3, v3=(string)"3\ ";';';
```
the nested structure can easily be picked out as
```
s2, v2=(string)"2\ ", n2=(structure)`s3, v3=(string)"3\ ";';
```
and the next as
```
s3, v3=(string)"3\ ";
```
and no unescaping process is required.2.xhttps://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/issues/63[2.0] qtdemux/qtmux: merge image/x-j2c and image/x-jpc and drop non-standard ...2021-09-24T13:30:04ZBugzilla Migration User[2.0] qtdemux/qtmux: merge image/x-j2c and image/x-jpc and drop non-standard boxing in the jpeg2000 elements## Submitted by Tim Müller `@tpm`
**[Link to original bug (#677754)](https://bugzilla.gnome.org/show_bug.cgi?id=677754)**
## Description
From commit message:
From 426b2db2cba849ab4f64a6ba91047380ff338837 Mon Sep 17 00:00:00 200...## Submitted by Tim Müller `@tpm`
**[Link to original bug (#677754)](https://bugzilla.gnome.org/show_bug.cgi?id=677754)**
## Description
From commit message:
From 426b2db2cba849ab4f64a6ba91047380ff338837 Mon Sep 17 00:00:00 2001
From: Sebastian Dröge <slomo@circular-chaos.org>
Date: Mon, 01 Dec 2008 15:48:13 +0000
Subject: ext/jp2k/: Add image/x-jpc caps name for real, raw JPEG2000 codestream data.
Original commit message from CVS:
* ext/jp2k/gstjasperdec.c: (gst_jasper_dec_sink_setcaps):
* ext/jp2k/gstjasperenc.c: (gst_jasper_enc_reset),
(gst_jasper_enc_set_src_caps), (gst_jasper_enc_init_encoder),
(gst_jasper_enc_sink_setcaps), (gst_jasper_enc_get_data):
* ext/jp2k/gstjasperenc.h:
Add image/x-jpc caps name for real, raw JPEG2000 codestream data.
In 0.11 we should merge image/x-j2c and image/x-jpc and simply drop
the non-standard boxing in the jasper elements and handle it in
qtmux/qtdemux.
image/x-jpc will be used by mxfdemux later.
Also add support for JP2 output in jp2kenc.2.xhttps://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/issues/30[2.0] qtdemux: mpeg audio version 2 is reported as version 12021-09-24T13:29:51ZBugzilla Migration User[2.0] qtdemux: mpeg audio version 2 is reported as version 1## Submitted by Josep Torra `@adn770`
**[Link to original bug (#619300)](https://bugzilla.gnome.org/show_bug.cgi?id=619300)**
## Description
The demuxer generate caps with version 1 for mpeg audio in both cases.
Version: 2.x## Submitted by Josep Torra `@adn770`
**[Link to original bug (#619300)](https://bugzilla.gnome.org/show_bug.cgi?id=619300)**
## Description
The demuxer generate caps with version 1 for mpeg audio in both cases.
Version: 2.x2.xhttps://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/74debug logging: Print the GstTask name as well as the thread pointer in the de...2022-11-10T09:21:00ZBugzilla Migration Userdebug logging: Print the GstTask name as well as the thread pointer in the debugs## Submitted by Thibault Saunier `@thiblahute`
**[Link to original bug (#736402)](https://bugzilla.gnome.org/show_bug.cgi?id=736402)**
## Description
Currently the debug looks like:
0:00:00.487023893 31989 0x1294590 DEBUG ca...## Submitted by Thibault Saunier `@thiblahute`
**[Link to original bug (#736402)](https://bugzilla.gnome.org/show_bug.cgi?id=736402)**
## Description
Currently the debug looks like:
0:00:00.487023893 31989 0x1294590 DEBUG category ...
where 0x1294590 is the thread as return by g_thread_self. It would be pretty useful to use the name of the GstTask associated when there is one, leading to something like:
0:00:00.487023893 31989 videotestsrc0:src_0x1294590 DEBUG category ...
What do you think?2.xhttps://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/34gstobject: re-enable "notify::parent"2022-11-10T09:20:44ZBugzilla Migration Usergstobject: re-enable "notify::parent"## Submitted by Stefan Kost `@ensonic`
**[Link to original bug (#693281)](https://bugzilla.gnome.org/show_bug.cgi?id=693281)**
## Description
Two attempts to make it possible to listen to changes in parentage.## Submitted by Stefan Kost `@ensonic`
**[Link to original bug (#693281)](https://bugzilla.gnome.org/show_bug.cgi?id=693281)**
## Description
Two attempts to make it possible to listen to changes in parentage.2.xhttps://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/7GstBus should auto-flush on a failed NULL->READY state change2024-01-10T10:54:54ZBugzilla Migration UserGstBus should auto-flush on a failed NULL->READY state change## Submitted by Jan Schmidt `@thaytan`
Assigned to **Jan Schmidt `@thaytan`**
**[Link to original bug (#381603)](https://bugzilla.gnome.org/show_bug.cgi?id=381603)**
## Description
A failure to change state to READY in the pipelin...## Submitted by Jan Schmidt `@thaytan`
Assigned to **Jan Schmidt `@thaytan`**
**[Link to original bug (#381603)](https://bugzilla.gnome.org/show_bug.cgi?id=381603)**
## Description
A failure to change state to READY in the pipeline should be handled like a NULL->READY->NULL transition and set the bus to auto-flushing, so that default pipelines don't end up with refcount loops due to messages on the bus.2.xhttps://gitlab.freedesktop.org/gstreamer/gst-plugins-base/-/issues/2[2.0] encoder elements should all use bits/sec as the unit for bitrate proper...2023-05-18T16:10:59ZBugzilla Migration User[2.0] encoder elements should all use bits/sec as the unit for bitrate properties## Submitted by Thomas Vander Stichele `@thomasvs`
**[Link to original bug (#337409)](https://bugzilla.gnome.org/show_bug.cgi?id=337409)**
## Description
theoraenc for example uses kbit/sec
it's an ABI change so we have to do i...## Submitted by Thomas Vander Stichele `@thomasvs`
**[Link to original bug (#337409)](https://bugzilla.gnome.org/show_bug.cgi?id=337409)**
## Description
theoraenc for example uses kbit/sec
it's an ABI change so we have to do it in 0.112.x