Thanks for your detailed response. I have taken a closer look at the source code for osxvideosink and found that it supports an "embed" property (which is FALSE by default). I can tell that when TRUE it will emit a message called "have-ns-view", where it passes a GstGLView object to the callback. This object is an NSView (part of the Apple Cocoa framework). I have learned that I am supposed to attach that to a NSWindow. Unfortunately I am pretty new to programming on the Mac. Thus far I have been using OS abstraction libraries such as Qt to avoid dealing with different windowing systems. Qt gives me back a window handle, which turns out to be integer but I have no idea how to retrieve a NSWindow object from that. So if anyone has done this before on the Mac (with or without Qt) I would greatly appreciate your input. Thanks, Andreas <div class="gmail_quote">On Wed, Jun 25, 2008 at 5:26 PM, Michael Smith <<a href="mailto:msmith@xiph.org" target="_blank">msmith@xiph.org</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div>On Wed, Jun 25, 2008 at 3:16 PM, Andreas Schuler <<a href="mailto:andreas@neokast.com" target="_blank">andreas@neokast.com</a>> wrote: > Hi all, > > I am trying to get an application to run on a Max OSX <a href="http://10.5.2." target="_blank">10.5.2.</a> I have > downloaded and built the latest tar balls and everything seems to be running > fine when I use gst-launch. > > >From within my app, which also runs on Windows, I am doing the following to > set the id of the window I want the video to be rendered on: > > - get_bus_set_sync_handler to setup my callback > - The callback function looks as follows: </div>That looks good for Win32 and linux. On linux the 'window handle' will need to be the XID for the window, but that's just a matter of different platform-specific types, not a big problem. On OSX, you're presumably using osxvideosink (well, you say you're using autovideosink, but that'll be selecting osxvideosink internally). osxvideosink doesn't implement GstXOverlay, so you can't do this with it. Because of this it won't ever even emit the prepare-xwindow-id signal, which is what you're seeing. osxvideosink has some other interface to set this up, but I don't know the details of how it works. You may find looking at the output of "gst-inspect-0.10 osxvideosink" to be helpful - it'll tell you what signals exist, etc. If possible, it would be best to make osxvideosink implement the GstXOverlay interface - that would let people use more common code across different platforms. Looking into whether that's possible is on my TODO list, but pretty far down right now - I probably won't get to it for a month or two. If you manage to do that sooner, that'd be great - patches would be very welcome. Mike </blockquote></div>