first of all, thanks for all the info about this issue!!
HTTP not working in windows is an ffmpeg limitation: network support cannot be built for this platform, thus HTTP (ans probably other network based protocols won't work). Sorry for this really bad piece of news!
AFAIK, HTTP works fine in both Linux and Mac OSX. I've tried it myself with success. However, some days ago we came across a video file (it was a QT movie) that ffmpeg had problems dealing with when playing via HTTP but will handle ok if in the local system.
That being said, HTTP support is included in this latest version, but as you can see it has some limitations. It's becoming really clear that the way to go will be to make Fobs' parser and codecs independent from the datasource. But that is some not straightforward work!
Thanks again.
Jose San Pedro
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Took some time, but I'm now able to compile everything under MinGW and network support in Windows is working. Some infos if anybody is interested:
- Cygwin provides network support under windows. Unfortunately, a bug in cygwin seems to make it impossible
to load to the generated fobs4jmf.dll within Java by calling System.loadLibrary(...). :-(
- It is possible to get network support in MinGW. Searching in Google for "mingw network support patch"
gives some example code. The patch has not been applied so far. Some minor modifications are needed
to work with the current SVN version. Moreover, "-lws2_32" (winsock api) is needed to create the fobs4jmf.dll.
- This way HTTP & Windows seem to work fine.
- I'm currently working on RTP (ignoring the JMF RTP implementation). For this purpose I simply use the HTTP
data source with a RTP url. Connecting to the stream works. But, so far I didn't managed to decode a MPEGTS/H.264
stream. There are a few error messages (due to the missing key frame):
but afterwards nothing happens. Help would be highly appreciated if someone knows by chance what it could be... :-)
- Fobs source, some minor bugs/improvements:
* The ffmpeg version within the resource directory cannot be used with the current fobs version and needs
to be replaced.
* At some places the method "free..." is used instead of "av_free...".
* Someone's home directory is included in the build script :-(
* Starting to play a file from HTTP takes about 10 seconds with Manager.createPlayer(...). Doing it manually
by instantiating the appropriate data sources & handlers saves about 9.5 seconds :-) Though, it could also be
a problem with my configuration.
* Would be nice if fobs could be used without JMF as JMF is pretty much dead
Remo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Help!!!
I'm loosing my mind right now!
I've working on adding HTTP support to FFMPEG and FOBS; but I have tons of problems;
I can compile FFMPEG smoothly (at head revision = 12864 {04 - Apr - 2008}) and in older revisions (way back to the 7215) but, when I try to build FOBS (with network support under Windows {MinGW 4.1.1, 3.1.0 or 3.0.0}) and FFMPEG revision 7760 or grater I can't.
I mean with all FFMPEG revisions under 7760 I can compile FOBS, but when I try to do that with a newer revision it wont build (it complains about an error while compiling stand_alone_codec.c)
I would like to know if it's possible to compile FOBS with the current version of FFMPEG and if not, which version of FFMPEG and how should I tweak it to have HTTP support under windows with FOBS.
PLEASE help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
first of all, thanks for all the info about this issue!!
HTTP not working in windows is an ffmpeg limitation: network support cannot be built for this platform, thus HTTP (ans probably other network based protocols won't work). Sorry for this really bad piece of news!
AFAIK, HTTP works fine in both Linux and Mac OSX. I've tried it myself with success. However, some days ago we came across a video file (it was a QT movie) that ffmpeg had problems dealing with when playing via HTTP but will handle ok if in the local system.
That being said, HTTP support is included in this latest version, but as you can see it has some limitations. It's becoming really clear that the way to go will be to make Fobs' parser and codecs independent from the datasource. But that is some not straightforward work!
Thanks again.
Jose San Pedro
Took some time, but I'm now able to compile everything under MinGW and network support in Windows is working. Some infos if anybody is interested:
- Cygwin provides network support under windows. Unfortunately, a bug in cygwin seems to make it impossible
to load to the generated fobs4jmf.dll within Java by calling System.loadLibrary(...). :-(
- It is possible to get network support in MinGW. Searching in Google for "mingw network support patch"
gives some example code. The patch has not been applied so far. Some minor modifications are needed
to work with the current SVN version. Moreover, "-lws2_32" (winsock api) is needed to create the fobs4jmf.dll.
- This way HTTP & Windows seem to work fine.
- I'm currently working on RTP (ignoring the JMF RTP implementation). For this purpose I simply use the HTTP
data source with a RTP url. Connecting to the stream works. But, so far I didn't managed to decode a MPEGTS/H.264
stream. There are a few error messages (due to the missing key frame):
[h264 @ 10330710]non existing PPS referenced
[h264 @ 10330710]decode_slice_header error
[h264 @ 10330710]no frame!
[h264 @ 10330710]non existing PPS referenced
[h264 @ 10330710]decode_slice_header error
[h264 @ 10330710]no frame!
[h264 @ 10330710]non existing PPS referenced
but afterwards nothing happens. Help would be highly appreciated if someone knows by chance what it could be... :-)
- Fobs source, some minor bugs/improvements:
* The ffmpeg version within the resource directory cannot be used with the current fobs version and needs
to be replaced.
* At some places the method "free..." is used instead of "av_free...".
* Someone's home directory is included in the build script :-(
* Starting to play a file from HTTP takes about 10 seconds with Manager.createPlayer(...). Doing it manually
by instantiating the appropriate data sources & handlers saves about 9.5 seconds :-) Though, it could also be
a problem with my configuration.
* Would be nice if fobs could be used without JMF as JMF is pretty much dead
Remo
Help!!!
I'm loosing my mind right now!
I've working on adding HTTP support to FFMPEG and FOBS; but I have tons of problems;
I can compile FFMPEG smoothly (at head revision = 12864 {04 - Apr - 2008}) and in older revisions (way back to the 7215) but, when I try to build FOBS (with network support under Windows {MinGW 4.1.1, 3.1.0 or 3.0.0}) and FFMPEG revision 7760 or grater I can't.
I mean with all FFMPEG revisions under 7760 I can compile FOBS, but when I try to do that with a newer revision it wont build (it complains about an error while compiling stand_alone_codec.c)
I would like to know if it's possible to compile FOBS with the current version of FFMPEG and if not, which version of FFMPEG and how should I tweak it to have HTTP support under windows with FOBS.
PLEASE help!