i use GPSgate too!!
i use GPSgate too!!
I think capture now depends on curiosity's GPS filter as a way to get the overlay working. I do agree it should not depend on xPort for GPS data but read the values from a COM port (that can be a port from xPort).
I guess the priority was to get overlay working and depending on GPS filter is not that bad while a better solution is found. Nothing wrong with combining programs together, thats how stuff gets done in linux. If GPSfilter does not interfere with your GPSGate it should work for you
Exactly. I just wanted to mention to keep the compatibility and usability for different CarPC-setups in mind while developing Capture!. As, for example, the new button layout is great for only one Capture!-window it is not practical for DualCapture! with two windows.Quote:
I guess the priority was to get overlay working and depending on GPS filter is not that bad while a better solution is found.
But for now, just keep going, we can discuss all the changes after everything works ;-)
But they all have one common interface, like a pipe for text-based data. For GPS this is NMEA and COM-Ports.Quote:
Nothing wrong with combining programs together, thats how stuff gets done in linux.
Not to worry. I'm sure the filter won't interfere with anything and Cameleon has it as an option that can be disabled.
Prefect: Pipes are great, serial is outdated and sloppy, and bad for time-critical processes. :) But I'm not writing for Linux. I'm using shared memory. Sort of like pointers that get passed around in DirectX.
Well good and bad news I guess.
I have the overlay working but its seems quite flaky. It wasnt displaying the data but seeing the post from Curiosity it seems I need to update my old version of xPort.
With the original Capture! it was very generic, with one call to RenderStream for capture or preview as it could link the capture, compression and render filters in one command. Now we are introducing this optional filter, the generic CaptureGraphBuilder does quite a bad job of guessing how it should build the graph. And I am no good at doing manual graph building (yet!). So I am having to make multiple RenderStream calls to get all the filter joined up. The downside at the moment, is although preivew and capture work, capture with preview does not. I think the capture class needs a major rework to build the graph properly from the start so that it can be used for preview or capture, instead of what it does at the moment of creating a graph whenever preview or capture is called.
With regard to dependancy on certain products I think you are right. I think that the GPS overlay should work off any COM port but I use xPort personally so I am happy. If we want it to be perfect then its up to Curiosity to work into the filter the option to use either xPort or a noraml COM port. That is not something I can change. I definately wont be using RR or CF interfaces to get the data either, unless it is ported to a proper plug in for them (which wont be done for a long time).
With regard to the buttons, this was just a new layout I was testing. I'm sure we can still come up with a layout that allows for the dual capture, or maybe we need to make a fork which just has a different interface for that? Shouldnt be difficult once we get it stable.
I've had a couple of busy days at work and havent been able to work on it recently, but will get back on it tonight. I hope to release a working version with overlay quickly, but "preview when capturing" will most likely not work. I think to get that working properly will require a rework of the capture class which will take some time. Ideally we could use someone with DirectShow experience that can help us link the filters properly rather than let the RenderStream take a guess at it.
For those asking for the Beta versions, please be patient as I try to make it work. I only have 2 PCs and one cam to test with so want to make sure its stable(ish) for you so to avoid dissapointment :) The latest version was linked a few posts back but thats without overlay which is very much in the Beta stage atm.
Oh yes, I had 2 versions of XPort with the interface but they were formatted differently so there were version compatibility issues. 1.31 is final.
Don't take shortcuts with the graph. DirectShow helper objects are of little help I know, but I'm positive you're going to get it working. :)
Don't think of XPort as a product. XPort actually works fine with GPSGate. Being the filter is somewhat of a dll called by a child process, it has limited resources and functionality, and really shouldn't have file I/O in it. Even registry, windows and other functions are different in it. Timing is important. Just calling OpenFile is quite slow and even more fun, a bluetooth GPS would set it back 5-10 seconds on the first frame and boom. So it must have an external process feeding it data. It also has a public interface for displaying anything you want, so it's not limited to XPort or GPS specific data.
Right, well this will keep you guys happy! (maybe)
You need to download xport and the GPS filter from Curiosity's site to get the GPS filter installed. Not sure what it will do if its not installed, I havent tried it! I though I would just get this out there so people can see what can be done. I am not a professional coder so dont expect any or all bugs to be fixed. I will try my best, but we may have to stick it on SourceForge or something to keep it moving. I have had problems when testing it going from preview to no preview to capture to no capture etc (trying to break it, it did break!). This mainly happens with preview with capture. Also to get turn off audio on preview, you need to click the setting and restart. Need to sort that really.
Have fun :)
I'm getting lots of errors. It really needs to be done proper but I don't know C# or have a compiler to play with. If anyone could help out it would be appreciated. Here's as close as I can get it. I just modified the Capture.cs file.
that is veeery promising...
it is quiet unstable a bit..but works nice..
too soon but, is there a way to change the speed to km/h? :D