After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 711190 - asfdemux: signal 3D video
asfdemux: signal 3D video
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-ugly
1.0.7
Other Linux
: Normal enhancement
: 1.5.2
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on: 611157
Blocks:
 
 
Reported: 2013-10-31 04:13 UTC by HyeJin Choi
Modified: 2015-06-11 02:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Add 3D parsing include dual stream 3D. (8.23 KB, patch)
2013-10-31 04:13 UTC, HyeJin Choi
needs-work Details | Review
asfdemux: Add support for stereoscopic video metadata. (10.58 KB, patch)
2015-06-10 04:38 UTC, Jan Schmidt
committed Details | Review

Description HyeJin Choi 2013-10-31 04:13:03 UTC
Created attachment 258628 [details] [review]
Add 3D parsing include dual stream 3D.

Add 3D parsing in Extend content descriptor object.
And bug fix in Advanced Mutual exclusion object parsing that is related with 3D dual stream.
Set as caps value to pass that 3D information to decoder.
Comment 1 Tim-Philipp Müller 2013-10-31 07:05:20 UTC
Thanks for the patch. I'm afraid this has to wait until we've agreed on API/conventions how to signal this stuff in general, instead of adding a custom "typeof3D" field.
Comment 2 Justin Kim 2013-10-31 13:21:35 UTC
@HyeJin, I always wonder that decoders have to know the type of 3D. Although I used typeof3D property as an indicator to deploy multiple decoders, I'm not sure whether the value of "typeof3D" has to be transferred into the decoders because I've seen only the value, "0x0d". Are there different values?
Comment 3 HyeJin Choi 2013-11-04 04:18:48 UTC
OK. If you decide how to send the signal, please let me know.
I'll improve my patch as your opinion.

(In reply to comment #1)
> Thanks for the patch. I'm afraid this has to wait until we've agreed on
> API/conventions how to signal this stuff in general, instead of adding a custom
> "typeof3D" field.
Comment 4 HyeJin Choi 2013-11-04 04:28:33 UTC
@Justin, Yes. Different values are exist.
"0x0d" is only for the dual stream 3D.
If you test with single stream 3D file, like have side by side half value, you can see the "0x01" or "0x02" value for "typeof3D".
  

(In reply to comment #2)
> @HyeJin, I always wonder that decoders have to know the type of 3D. Although I
> used typeof3D property as an indicator to deploy multiple decoders, I'm not
> sure whether the value of "typeof3D" has to be transferred into the decoders
> because I've seen only the value, "0x0d". Are there different values?
Comment 5 Justin Kim 2014-01-02 06:07:46 UTC
@Tim, could you share the progress of this issue? 
In my case, I defined "multipe-stream" property of caps to discern two cases, single or dual streams. 
It could be more general approach than using "typeof3d" because it doesn't have any meaning from specific demuxer logic. However, as you mentioned, it's not elegant. 
So If possible, I want to know the progress of your side discussion.
Comment 6 Tim-Philipp Müller 2014-01-02 09:52:48 UTC
There is no progress. It depends on a more generic solution that covers all container formats/codecs/layouts.
Comment 7 Jan Schmidt 2015-06-09 15:36:46 UTC
Does anyone have a sample file for testing?
Comment 8 Jan Schmidt 2015-06-10 04:38:20 UTC
Created attachment 304914 [details] [review]
asfdemux: Add support for stereoscopic video metadata.

Add parsing of stereoscopic metadata, and place into the caps to
the decoder.

Fix parsing of Advanced Mutual Exclustion objects.

https://bugzilla.gnome.org/show_bug.cgi?id=711190

Based on a patch by HyeJin Choi <meeshel78@hotmail.com>
Comment 9 Jan Schmidt 2015-06-10 04:38:59 UTC
For future reference, I found some test streams at http://www.3dtv.at/Movies/Index_en.aspx