Menu
I'm running Windows 7 x64, and I had those same problems, and so some of the requirement checks are done because of that. Both problems that you describe are a result of bugs in the GStreamer SDK.
The first problem you mention sounds very much like the following, but as far as I can tell it is only present on GStreamer.com SDK 2012.7:. It's possible that they have another DLL missing. Hindi dub english movies free direct download. The second problem occurs on 2012.9: Because you installed the x64 version yourself, you ran into the libssp-0.dll problem. Exaile is actually bundled with libssp-0.dll, and tries to install it into the GStreamer SDK directory. Though, only for x86.
I think there will be a second RC soon, delaying the release. I'll add support for x64 in the launcher script in time for that, but I don't anticipate releasing an x64 installer unless there's a lot of demand for it. Yeah, ideally for Exaile I want an install to work out of the box, so we include libssp-0.dll. At the moment, I'm hesitant to support both an x64 and x86 installation, considering we're just starting to support windows and that increases the complexity. Of course, what I really need to do is put a README.Windows that has some of these things in it so people installing Exaile manually know what the possible problems are. I'm interested in trying to diagnose the first problem you had (32-bit GStreamer, specified procedure cannot be found)? There are a couple of things I can think of that might be the cause: - You have a GTK living somewhere else that isn't compatible with the GStreamer.com SDK.
This happens if you have GStreamer SDK and PyGTK installed on the same machine. You may have MinGW installed someone else that isn't compatible with the GStreamer.com SDK What you can do to diagnose the problem: - Get depends.exe: - Modify exaile.bat to launch depends instead of exaile (that way the environment is identical) - Load%GSTREAMER SDKROOT x86% lib python2. 7 site- packages gst-0.10 gst gst.
Pyd in depends (the pyd file is really a DLL), and see what errors it reports. Should be able to tell you what DLL is conflicting, and what its path is. I believe the exaile.bat launcher should now support the GStreamer.com 64-bit SDK as well. Pushed to trunk in r4279, and in in r4262. A windows-specific readme file was added in r4277/r4260 If you have time, I'd still like to see if we could diagnose your 32-bit GStreamer.com SDK problem, as others may be affected. As part of changing the launcher, I've moved the GST SDK to the beginning of the PATH, so that may fix that problem as well since Windows will now search for the necessary DLLs in the GST directory first. I suppose next time I look at this I'll actually install the 64-bit SDK.
Sorry about that, I just assumed they would do something consistent. It should still work though if the environment variable is setup correctly - which it should be for the user that installed the SDK. I don't think exaile.bat should work that way. In particular, I noted that python 32-bit and python 64-bit install in the same directory with the same executable file names.
You.can. run a python script to do the detection, but that isn't necessary in most cases: - We look for python (regardless of version) on your path. If we find it, we use it. If your path is setup correctly for GST and GTK, we'll take that too - If not, we try to detect the environment variables, which should be valid most of the time.
Gstreamer
If not, then we do the raw detection. The only time this will fail is if you have a mismatched version of the GST SDK and python, or if you have both the 32-bit and the 64-bit GST SDK installed. In any of those cases, I don't know if we'd be able to reliably detect what the user wants anyways. Additionally, we can't assume that a 64-bit system has a 64-bit python installed. I don't really want to support a 64-bit version at the moment either, so if you want to use the 64-bit build then the user is on their own.
Presumably such a user that isn't using our installer is technically inclined anyways, and should be able to deal with any such problems. I made more tests using Windows 8 x64.
Still with Exaile 3.3.0-dev:. Using Python x86 and gstreamer x86, I still have the bug described in my first message. This time, I used Dependency Walker within the launch script to check gst.pyd as asked, and you can find the result attached (can be opened with DW). Using Python x86 and gstreamer x64, or using Python x64 and gstreamer x86, I have the following error: - ImportError: DLL load failed:%1 is not a valid Win32 application. Using Python x64 and gstreamer x64 it works. Your decision seems fine:). Make sure that the Windows user is warned concerning these dependency issues, and that would be a begining.
Do you plan to provide someday an all-inclusive Windows installer that embed all the dependencies? That is quite dirty, but brings many new users that are not able to handle these dependency issues by themselves. Thanks for the DW output file - it's quite clear here what's happening for you. You have Inkscape installed, which has a copy of libglib-2.0-0.dll installed in it. I bet that it's older than what GST uses, and thus why the DLL cannot be loaded. DLL hell at its finest. Try this then.
There's a line in exaile.bat, that looks like this: set PATH=%GST SDK% bin;%PATH% Change that to the following: set PATH=%GSTSDK% bin I think that might make your x86 version work correctly. Though, I'm confused as to why sticking the GST directory first didn't fix it. Quod Libet has an installer that has all the dependencies packed with it, so if we decided to do something like that then that would be something to work from as an example. However, I was hoping that the GST SDK would.just work., and then we wouldn't need to do all that packaging. Well, this bug report isn't useless - if someone else runs into this problem, then they might know how to fix it. However, I think that this situation should still be fixable by our launcher - I don't think the average user is going to even know what a PATH is, never mind keeping it clean.
Borderlands 1 modded shield download. Finally, where are you in the game itself? We have our own thanks to We also have a thanks to Co-op reddits:| SHiFT Codes Previous SHiFT codes:| Partner reddits accepts non-text posts. Timezone (for schedule) and geographical location (for lag) can also be significant. PC players may join our. 400% more link karma!
Presumably other installers might add themselves to the PATH, and then break us. I think I'll just have to erase the path if we have to do detection of GST.
So, see if I can import gst without changing the environment, and if it doesn't work then clean the path up. I can't help but wonder if that will break things though.
As talked about in our, the MJPG-Streamer video rate using the Pi's Camera module was definitely not acceptable for our project. The maximum speed (with dropped frames)of raspistill was far below the video quality needed for our project. After researching multiple different streaming methods we settled on using, an open source visual and audio streaming platform. This method is faster as the software opens up a direct network pipeline between the Raspberry Pi and the OCU (in this case a Windows 7 machine). This tutorial is Windows 7 specific, but will work on Mac and Linux. The tutorials for Mac and Linux are actually much easier as GStreamer was originally created for those platforms. First prime the Pi by adding the follow to /etc/apt/sources.list.
Stefan Thanks, finally got it to work on Windows 7. It took me a while to figure out that the IP in the Raspberry Pi command should be the IP of the Windows machine, because I confused UDP with the TCP commands I used earlier.
Here are the commands of which you made screenshots (easier to copy): On the Raspberry Pi: raspivid -t 999999 -w 1280 -h 720 -fps 10 -rot 270 -b 2000000 -o - gst-launch-1.0 -e -vvv fdsrc! Rtph264pay pt=96 config-interval=5! Udpsink host=IP-OF-WINDOWS-MACHINE port=5000 On the Windows machine (find the IP with ipconfig): gst-launch-1.0 udpsrc port=5000! Application/x-rtp, payload=96! Fpsdisplaysink sync=false text-overlay=false. An easy way to record the Pi's video stream is by using netcat.
Install netcat on the Pi (apt-get install netcat) and then on your windows machine (- might have to download using Internet Explorer as Chrome views the netcat download as a virus). After downloading netcat, run this command on the Pi: raspivid -t 999999 -o - nc 5001 In the directory where you installed Netcat on your laptop: netcat -p -l 5001 video.h264 Recording video through GStreamer is also very easy (GStreamer ONLY records video up until 10s before you end the program. Lean on me the best of bill withers rar files.
Keep GStreamer running well after the event you would like to record has passed.). Run the same command from the Pi as mentioned above. On your laptop run this: gst-launch-1.0 -e -v udpsrc port=5000! Application/x-rtp, payload=96! File sink=movie.avi As for the green lines, it seems you might have an encoding issue.
Are you using the Pi camera or different hardware? GStreamer encoding (and decoding) h264 video, but if your camera does not stream h264 then the setup above will not work. If you are using the Pi Camera and the green lines are still there, comment again and we can help you out. Thanks for the comment.
OpenCV and ffmpeg are great tools especially if you're wanting to do any type of image/video analysis or manipulation. But installing these tools isn't exactly the easiest thing to do either. I went through the pain and here's what I discovered.
Installing ffmpeg Since opening most video files require a codec in OpenCV installing ffmpeg was the first thing that I did. Download the and then extract the files. You may need 7zip to extract.
Create a folder in C: called ffmpeg. Copy the contents of the extracted files into C: ffmpeg. Edit your PATH environment variable to append at the end the following entry.
Ffmpeg -version Installing OpenCV These steps are similar to installing ffmpeg however the OpenCV download comes with a self-extracting executable. Download the self-extracting executable from the. Run the Executable which will in turn extract the executable.
Create a folder in C: called opencv. Copy the contents of the extracted files into opencv. Edit your PATH environment variable.
This will be dependent on the version you want installed (i.e. 32 or 64 bit) and also the version of visual studio you have installed (express editions are fine). Definition - x86 32 bit x64 64 bit Definition - vc10 VS 2010 vc11 VS 2012 vc12 VS 2013 C: opencv build in to the site-packages folder. Note: that currently OpenCV is ONLY supported on Python 2.7. OpenCV also requires that numpy be installed as well. Matplolib is also recommended to be installed.
To test it out open a python console and enter the following.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |