[Bug 771697] Develop media player with GStreamer. I have a few troubles.

[GStreamer (GNOME Bugzilla)]

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

Sebastian Dröge (slomo) <slomo at coaxion.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |slomo at coaxion.net
         Resolution|---                         |INCOMPLETE

--- Comment #1 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
Please file a few separate bugs about each of the individual issues, and for
support requests please ask on the mailing list instead:
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

(In reply to bamzunee from comment #0)

> 1. For Official App store from Apple release, I made a framework with
> wrapped GStreamer. For the release, currently, my framework calls GStreamer
> through absolute path (/Library/Frameworks/GStreamer.framework) However, I'd
> like to use this relative path down below.
>  - MyApp.app
>     : MyApp.app
>       /Contents
>          /Frameworks
>             /My.framework
>             /GStreamer.framework

You will have to relocate the .dylibs with otool and install_name_tool. Linking
on macOS is always done with absolute paths unless you manually change that
after the fact. This does not seem like a bug.

> 2. For Official App store from Apple release, I inputted the code sign in
> Terminal and these are the result below. I succeed the code sign and upload
> was also successful but with GStreamer framework, there is always code sign
> error.
> 
>  - Terminal input codesign command
>     : code sign -f —deep -s '3rd Party Mac Developer Application: My
> Developer ID' —entitlements "MyApp.entitlements" "MyApp.app"
>  - Output Message
>     : unsealed contents present in the root directory of an embedded
> framework
>       In subcomponent:
> MyPath/MayApp.app/Contents/Frameworks/GStreamer.framework

That sounds like a real problem and you should report a separate issue for
that, ideally with a small (minimal!) testcase that can reproduce the problem
directly.

> 3. my framework becomes deadlock when I change subtitle when I swap subtitle
> (subtitle URL change) makes my framework deadlock with glimagesink or
> osxvideosink on Windows and Mac, However, it works well with d3dvideosink on
> Windows. I referred totem-streamer and there are the codes below that I used 
> [...]

You said you were using 1.6.4. Please try again with 1.8.3 and if the problem
still exists, file a separate bug about this with a testcase to reproduce it.

> 4. When my framework plays a video file, the play screen rendering is always
> on the top of any other renderings such as layout, button, label, etc. What
> I want to do is the other renderings can be show/hide so that I can make
> play control, playlist as totem-Streamer.

You need to embed the video sink into your UI with the GstVideoOverlay
interface, or alternatively do closer integration like the caopengllayersink
does for macOS. This is not a bug.

> 5. I am currently using Delphi Berlin Firemonkey and the Delphi only
> supports OS X 32bit for build and currently, Streamer doesn't support since
> v1.5.1 came. so I built myself GStreamer v1.6.4 as Universal. I am wondering
> that GStreamer release higher version with Universal again.

Not sure if that makes any sense, because Apple does not support 32 bit either
anymore since 10.6, which is ancient by any means.

For applications it is still supported though, so if someone wants to put the
effort in making the universal build work and helps keeping it in shape, then
that would be possible. Please make another bug for this if you're interested
in working on that and want to provide patches, and help keeping it working.


I'm closing this bug here now as it's about too many independent issues, let's
continue discussions in separate bugs for any of these (or the mailing list).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.