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 771882 - GstPlayer on Android with RTSP stream reports width x height= 0 x 0 in "video-dimensions-changed" event
GstPlayer on Android with RTSP stream reports width x height= 0 x 0 in "video...
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
1.9.2
Other other
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-09-23 15:19 UTC by Predrag Manojlovic
Modified: 2016-11-21 07:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Predrag Manojlovic 2016-09-23 15:19:28 UTC
When playing RTSP stream "video-dimensions-changed" event is triggered only once reporting dimensions of 0 x 0. No further events triggered.

Following streams (and any other I've tried) can be used to reproduce the problem:

rtsp://mpv.cdn3.bigCDN.com:554/bigCDN/definst/mp4:bigbuckbunnyiphone_400.mp4

This was used as base code:

https://github.com/sdroege/gst-player/blob/master/android/app/src/main/jni/player.c


with none modification, and call back was set with:

            mGstMediaPlayer = new Player(); 
            mGstMediaPlayer.setVideoDimensionsChangedListener(new Player.VideoDimensionsChangedListener() { 
                public void videoDimensionsChanged(Player player, final int width, final int height) { 
                    Log.d(TAG, "videoDimensionsChanged: width=" + width + " height=" + height); 
                } 
            }); 


which reports dimensions of 0 x 0.
Comment 1 Sebastian Dröge (slomo) 2016-09-26 06:30:02 UTC
Can you attach a full debug log, and another one with gst-player:6 here? Thanks!
Comment 2 Sebastian Dröge (slomo) 2016-11-21 07:02:29 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!