WinBuilds 0.10.7 release

[GoogleCodeExporter]

New upstream releases are comming!
I'll take care of updating all the gstreamer modules in the next week.
We should start thinking on the next release :)

Original issue reported on code.google.com by ylatuya on 27 Jun 2010 at 8:30

[GoogleCodeExporter]

Sounds great - thanks for doing that.

I upgraded core/base/etc. to 0.10.29 already in the trunk, but it looks like 
there's a lot coming down the pike (good/bad/ffmpeg/python/etc.). At least one 
plugin has changed packages (I think it did so in the last good release 
actually), so please keep your eyes peeled for that.

I'll be on vacation all this week and half of next week, so I won't be around 
to help out much.

On an entirely different note, we need to catch up to VLC, MPlayer, etc. and 
get a direct3d plugin going. I've run into issues with the directshow stuff at 
work. I'm not sure why, but on certain machines with certain video cards, it 
looks like the number of open simultaneous directshow videos is limited. At 
least I get an internal data flow error after the 6th video is shown. I haven't 
gotten the equivalent error using the direct3d plugin and VLC. It warrants 
further investigation I know, but a direct3d plugin would be good to have 
regardless.

Original comment by david.g.hoyt on 27 Jun 2010 at 9:13

[GoogleCodeExporter]

I know Julien Moutte was is actually working on merging my patches upstream 
plus some improvements he has done too to the directshow plugin. One of them is 
including the new media fundation EVR renderer.

Original comment by ylatuya on 27 Jun 2010 at 10:02

[GoogleCodeExporter]

Original comment by ylatuya on 27 Jun 2010 at 10:03

• Changed state: Started

[GoogleCodeExporter]

I wrote a direct3d plugin that has been tested and retested and retested again 
for memory leaks and deadlocks and so far, so good. I need it tested on more 
systems, though. On the 1 ATI and 1 Nvidia card I've tested against, there've 
been no problems.

I'll be committing it upstream here soon, but it won't be in time for the next 
gst release. I would, however, like to include it in our release. You can find 
the source in gst-plugins-bad/sys/d3dvideosink/.

Original comment by david.g.hoyt on 15 Jul 2010 at 9:56

[GoogleCodeExporter]

Original comment by ylatuya on 18 Aug 2010 at 9:30

• Added labels: Type-Task
• Removed labels: Type-Defect

[GoogleCodeExporter]

I have rebase the udpsink patches. Will commit them this afternoon for the 
release. Anything else we should do except to test everything?

Original comment by ylatuya on 31 Aug 2010 at 1:59

[GoogleCodeExporter]

Original comment by ylatuya on 31 Aug 2010 at 8:12

• Changed title: WinBuilds 0.10.7 release

[GoogleCodeExporter]

as new upstream release, what's the plane for the ossbuild?
thanks.

Original comment by lfar...@gmail.com on 3 Sep 2010 at 10:32

[GoogleCodeExporter]

Sync with upstream and release ASAP :)

Original comment by ylatuya on 3 Sep 2010 at 11:34

[GoogleCodeExporter]

ylatuya: are all your commits in and ready to go?

I've completed my new build and am ready to post a new beta.

Original comment by david.g.hoyt on 25 Sep 2010 at 12:34

• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Users are reporting problems with the new build in win-xp, so I'll have to hold 
off until it's resolved.

Original comment by david.g.hoyt on 1 Oct 2010 at 2:11

[GoogleCodeExporter]

I'll be testing the release today. I'll let you know if I find any blocker.

Original comment by ylatuya on 3 Oct 2010 at 1:26

[GoogleCodeExporter]

Everything looks fine here :)
Can you upload a new installer to check that everything is correct in this side 
too?

Original comment by ylatuya on 3 Oct 2010 at 6:19

[GoogleCodeExporter]

I will once I get the new winxp-compatible build checked in.

Original comment by david.g.hoyt on 4 Oct 2010 at 4:48

[GoogleCodeExporter]

New build's committed, awaiting review for winxp compatibility.

Original comment by david.g.hoyt on 5 Oct 2010 at 12:42

[GoogleCodeExporter]

I need you to repatch the UDP and any other missing items that may have been 
overlooked.

Original comment by david.g.hoyt on 13 Oct 2010 at 11:31

[GoogleCodeExporter]

Any update on this?

Original comment by david.g.hoyt on 16 Oct 2010 at 1:14

[GoogleCodeExporter]

Sorry for not replying sooner. I'll update the patches this weekend. Should we 
release by then?

Original comment by ylatuya on 16 Oct 2010 at 2:31

[GoogleCodeExporter]

Well I don't know. I think another core/base/good release is due out very soon. 
We could just wait at this point. What do you think?

Original comment by david.g.hoyt on 16 Oct 2010 at 7:08

[GoogleCodeExporter]

Sure, the pre-releases are already up, so probably by the end of the next week

Original comment by ylatuya on 16 Oct 2010 at 9:02

[GoogleCodeExporter]

Can you please reapply the udp and/or any missing patches and double check the 
build before we do another release?

Original comment by david.g.hoyt on 25 Oct 2010 at 10:09

[GoogleCodeExporter]

I'm at the gstreamer conference in Cambridge :D
I'll have time to do it tomorrow, sorry for not having done it the past weekend

Original comment by ylatuya on 25 Oct 2010 at 10:29

[GoogleCodeExporter]

Awesome! I would've loved to go to that. (c:

I also need you to take a look at the python bindings and the installer. 
gst-python seems to have a couple new gst scripts, but I'm unsure.

The repo. is sync'ed w/ upstream now and pending any new commits between now 
and the next core/base/good/(python?) release, we're good to go. A new ffmpeg 
build w/ the h263p fix (issue 72) is also in.

Original comment by david.g.hoyt on 25 Oct 2010 at 10:48

[GoogleCodeExporter]

Did I mention that I can't wait until we have a jhbuild system going? The 
sync'ing is a real pain... (c:

Original comment by david.g.hoyt on 25 Oct 2010 at 10:50

[GoogleCodeExporter]

this means wont be a new release before 0.10.31 upstream? any beta?

Original comment by vitorl...@gmail.com on 26 Oct 2010 at 2:41

[GoogleCodeExporter]

0.10.31 should be out very soon. I can upload a new beta if the community 
wants, but it won't have ylatuya's UDP patches. I was going to do a new beta as 
soon as those patches were applied. But I don't mind doing 2 more beta releases 
instead of one.

Original comment by david.g.hoyt on 26 Oct 2010 at 4:11

[GoogleCodeExporter]

Just back from the conference. The patches will be applied this afternoon, once 
I get back home :) 
I have been talking about other windows developers and I have now a good idea 
on how to improve the build system to get more support from the community. One 
of them is Michael Smith, from Songbird, who mentioned us as an excellent 
project in his talk about cross-platform development of gstreamer apps :)
I'll open a new thread to discuss it in deep

Original comment by ylatuya on 27 Oct 2010 at 1:41

[GoogleCodeExporter]

I'm done with the bakport. I'll try to push hard to have them upstream, because 
it's a pain having to rebase them everytime.

Original comment by ylatuya on 27 Oct 2010 at 11:48

[GoogleCodeExporter]

ORC needs to be updated:
_orc_program_append_2 is missing

Original comment by ylatuya on 6 Nov 2010 at 7:55

[GoogleCodeExporter]

I'll update orc tonight. 
Should we plan the release after Christmas?

Original comment by ylatuya on 22 Dec 2010 at 12:41

[GoogleCodeExporter]

Orc should already be updated (dependency walker shows that 
orc_program_append_2 is there -- are you talking about orc-0.4.lib?) -- please 
double check before proceeding. 

The python installer changes still need to be done (if you have time and the 
inclination, feel free to give that a whack :p).

But yeah, it's time for a new release asap.

Original comment by david.g.hoyt on 22 Dec 2010 at 6:52

[GoogleCodeExporter]

I need you to review the farsight fix I committed the other day. I believe I 
deliberately caught and didn't overwrite the changes you mentioned in the 
farsight bug report. But you oughtta double check it just in case.

Original comment by david.g.hoyt on 22 Dec 2010 at 6:55

[GoogleCodeExporter]

It was just a couple of minor fixes to make the compiler happy, so if compiles 
that's ok :)

Original comment by ylatuya on 22 Dec 2010 at 7:13

[GoogleCodeExporter]

any progress with a new buidl?

Original comment by vitorl...@gmail.com on 9 Jan 2011 at 10:21

[GoogleCodeExporter]

Yes, it's getting closer, for sure. We need to make a couple of fixes to the 
installer and then it should be ready to go. It's basically 99.9% there. What's 
in the repo. right now in terms of gstreamer source will be what's tagged and 
in the release.

Original comment by david.g.hoyt on 10 Jan 2011 at 5:33

[GoogleCodeExporter]

could you build a new beta 3? the current beta is 3 months old. then we can 
test it with our app and if we found further problems than it can be fixed 
before the final release.
thanks in advance.
regards.

Original comment by lfar...@gmail.com on 14 Jan 2011 at 10:18

[GoogleCodeExporter]

ylatuya: what's the status on the new beta release?

Original comment by david.g.hoyt on 19 Jan 2011 at 7:37

[GoogleCodeExporter]

There's new beta 3 installs available for those interested.

Original comment by david.g.hoyt on 20 Jan 2011 at 1:51

[GoogleCodeExporter]

we test it. almost good (but now as new upstreamer release was released last 
week probably it'd be useful to update again).
anyway one old problem is that rtspsrc can't be teardown properly on windows.
should i open a separate issue for this or add it here?

Original comment by lfar...@gmail.com on 24 Jan 2011 at 11:37

[GoogleCodeExporter]

open a separate issue -- but really it needs to be tracked upstream. we'll 
release this and then do a very quick, short release cycle with the latest 
gstreamer release.

Original comment by david.g.hoyt on 24 Jan 2011 at 6:27

[GoogleCodeExporter]

I think we're ready to officially release 0.10.7. Anybody have any 
reservations/concerns on the issue?

Original comment by david.g.hoyt on 8 Feb 2011 at 6:16

[GoogleCodeExporter]

Fine for me.

Original comment by ylatuya on 8 Feb 2011 at 6:26

[GoogleCodeExporter]

:D

Original comment by ylatuya on 8 Feb 2011 at 6:26

[GoogleCodeExporter]

Regarding RTSPsrc, it also very slowly changes states in windows.
I've filed a bug upstream, but it still has no reaction.
https://bugzilla.gnome.org/show_bug.cgi?id=636893

Original comment by wl2776@gmail.com on 10 Feb 2011 at 1:16

[GoogleCodeExporter]

This bugs sucks... the tear down is extremely slow too. I'll to give a look, 
but I don't promise anything. Anyway it will have to wait for the next release

Original comment by ylatuya on 10 Feb 2011 at 2:06

[GoogleCodeExporter]

Hope the next gstreamer can play rmvb or rm video by adding necessary codecs.

Original comment by hsli...@gmail.com on 24 Feb 2011 at 7:51

[GoogleCodeExporter]

Has anyone tried running multiple pipelines in one application?  
I'm writing an application that handles multiple streams in C# with the .net 
bindings, I call gst.Application.Init() at program start, then create a new 
MainContext(), Mainloop, and Pipeline in a separate thread for each input 
stream.  It works for a while, then crashes.  Generally the crash info I get is:

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name: Lab Eye.exe
  Application Version:  1.0.0.0
  Application Timestamp:    4d658f1a
  Fault Module Name:    libglib-2.0-0.dll
  Fault Module Version: 2.26.1.0
  Fault Module Timestamp:   4cf826e0
  Exception Code:   c0000005
  Exception Offset: 00049317
  OS Version:   6.1.7600.2.0.0.256.48
  Locale ID:    1033
  Additional Information 1: 0a9e
  Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
  Additional Information 3: 0a9e
  Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Am I just trying to do something stupid?  Or am I just overflowing some stack 
somewhere?
Thanks

Original comment by mgrossl...@gmail.com on 24 Feb 2011 at 3:25

[GoogleCodeExporter]

I've run multiple pipelines in a java-based application without a problem, but 
I'm probably using different areas of gstreamer than you. What's causing your 
problem isn't likely to be answered by anyone here on the project -- you'll 
need to do some investigating and narrow it down. If it turns out it's a 
problem w/ our builds, we're happy to address and fix it. Often times, though, 
it's a problem upstream -- IOW, the project itself has poor or lacking Windows 
support and while we accept good patches, they should be submitted upstream so 
we can keep our patches to a minimum and the work kept where it belongs -- the 
project itself. The ultimate goal is for everything to build w/ zero 
Windows-specific patches. (c:

Original comment by david.g.hoyt on 24 Feb 2011 at 4:11

[GoogleCodeExporter]

the rtsp problems on windows is very serious for us since currently all of our 
program seg fault on windows (because of the these problems). i'm just check 
bugzilla and find these reports:
https://bugzilla.gnome.org/show_bug.cgi?id=610916 
https://bugzilla.gnome.org/show_bug.cgi?id=622588
https://bugzilla.gnome.org/show_bug.cgi?id=633831
https://bugzilla.gnome.org/show_bug.cgi?id=636893
https://bugzilla.gnome.org/show_bug.cgi?id=640416
is anybody working on these problems? or anybody has any kind of progress or 
tips about it? for where we should have to start etc..
thanks in advance.

Original comment by lfar...@gmail.com on 8 Mar 2011 at 1:16

[GoogleCodeExporter]

do you plan to sync with upstream release in the near future? afais the current 
git is a few version behind the upstream git or even the upstream release.

Original comment by lfar...@gmail.com on 23 Mar 2011 at 9:57