In my first try with fobs4jmf, I got the "can't realize processor" error. I was trying to transmit RTP in H.263-198 format from fobs-jmstudio, using input from a webcam.
With fobs4JMF, is it possible to capture from a web cam and transmit in H.263-1998 format?
Then, is it possible to receive H.263-1998 with fobs components and then display with the new opengl renderer?
Thanks,
S
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
if I understand well what you want to do, I would say it's just not possible. Mainly because Fobs can only accept input from a file (there's a prevous discussion in the forum that explains why). Besides, enconding plugins have not been coded yet though it's a possible enhancement for the future.
Sorry for the bad news. Fobs is still a young project and I'm coding it by myself (except for some recent submissions of code).
Cheers.
Jose San Pedro
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Fobs has no decoder of its own, but is uses ffmpeg to do the decoding stuff. AFAIK ffmpeg seems to have h263 decoding support (h263, h263i, h263p). Anyway, I will try to make a file to test if it works or not.
This has been extracted from the 'ffmpeg -formats' command:
DEVSDT h263
D VSD h263i
EV h263p
It means that Encoding/Decoding is available for h263, but for h263i only decoding is available and for h263p only encoding is available.
So codec support is already there, in the ffmpeg library. The only thing missing is the link to JMF. This would need an encoding JMF plugin (i.e. Video encoder + muxer, i would say). There's no need to deal only with h263 as ffmpeg offers the same interface for any codec.
In addition, if you want to receive video through RTP using Fobs, some major modification to the code architecture have to be made. Maybe, the easiest way to do it would be to use ffmpeg rtp support and build a DataSource that uses it to get the necessary packages (looking at the current File DataSource will help). Right now Fobs kind of bypass JMF when it comes to pass file segments to the parser (ffmpeg takes care of it all).
Tell me what you think!
Cheers.
Jose San Pedro
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
In my first try with fobs4jmf, I got the "can't realize processor" error. I was trying to transmit RTP in H.263-198 format from fobs-jmstudio, using input from a webcam.
With fobs4JMF, is it possible to capture from a web cam and transmit in H.263-1998 format?
Then, is it possible to receive H.263-1998 with fobs components and then display with the new opengl renderer?
Thanks,
S
Hi,
if I understand well what you want to do, I would say it's just not possible. Mainly because Fobs can only accept input from a file (there's a prevous discussion in the forum that explains why). Besides, enconding plugins have not been coded yet though it's a possible enhancement for the future.
Sorry for the bad news. Fobs is still a young project and I'm coding it by myself (except for some recent submissions of code).
Cheers.
Jose San Pedro
Jose:
I would like to contribute the missing components to Fobs for my intended use. Are the following components missing now?
1. H.263-1998 encoder
2. H.263-1998 packetizer
3. H.263-1998 depacketizer
Is there anything else that is required? I assume that Fobs has H.263-1998 decoder - is that correct?
Regards,
S
Hi S,
Fobs has no decoder of its own, but is uses ffmpeg to do the decoding stuff. AFAIK ffmpeg seems to have h263 decoding support (h263, h263i, h263p). Anyway, I will try to make a file to test if it works or not.
This has been extracted from the 'ffmpeg -formats' command:
DEVSDT h263
D VSD h263i
EV h263p
It means that Encoding/Decoding is available for h263, but for h263i only decoding is available and for h263p only encoding is available.
So codec support is already there, in the ffmpeg library. The only thing missing is the link to JMF. This would need an encoding JMF plugin (i.e. Video encoder + muxer, i would say). There's no need to deal only with h263 as ffmpeg offers the same interface for any codec.
In addition, if you want to receive video through RTP using Fobs, some major modification to the code architecture have to be made. Maybe, the easiest way to do it would be to use ffmpeg rtp support and build a DataSource that uses it to get the necessary packages (looking at the current File DataSource will help). Right now Fobs kind of bypass JMF when it comes to pass file segments to the parser (ffmpeg takes care of it all).
Tell me what you think!
Cheers.
Jose San Pedro