jffmpeg-devel

Re: [Jffmpeg-devel] project direction?

[David S. <da...@si...>]

Hi Bill,

What are your changes like? Perhaps we could make them to the existing 
source before we proceed with my larger update. Then I could try to do 
the merge carefully to keep the MPEG support.


Bill Snyder wrote:

>Hi David,
>
>With some minor tweaking, I was able to get MPEG1 working fine for
>me.  MPEG1, MPEG2, and MPEG4 support are what I am most interested
>in so my vote would be to do whatever needs to be done to maintain
>support for MPEG.  It would seem to me that no one format should be
>deemed important enough to eliminate support for others.  If ffmpeg is
>what is flawed, then I'd say focusing effort on getting it fixed would be
>the best use of resources.  With all of that said, I'd vote the best order of
>choices would be 
>
>- Try to use compiler directives for the 263/RTP part to remove the 
>   0.4.7 dependency at compile time
>- Create a separate branch just for H263_RTP
>- Fold everything into the main project causing the 0.4.7 dependency
>
>Thanks,
>Bill
>
>
>----- Original Message ----- 
>From: "David Stuart" <da...@si...>
>To: <jff...@li...>
>Sent: Wednesday, March 03, 2004 10:24 AM
>Subject: [Jffmpeg-devel] project direction?
>
>
>  
>
>>Hi All,
>>
>>So my latest update is nearing completion, but it looks like this update 
>>will once again be a big change. So now, I'd like to ask the adivce of 
>>the other developers. There are two big problems with this upcoming update:
>>
>>   1. For the moment it limits jffmpeg to 0.4.7
>>   2. MPEG support is removed
>>
>>Now, I don't see #2 as a big issue at the moment, since from the posts 
>>to this list, I gather that MPEG support doesn't currently work (in 
>>fact, I suspect that if you went back before any of my updates that MPEG 
>>support probably didn't work in the initial version due to some bugs 
>>that were present).
>>
>>But, #1 is a bit tougher. The issue as I outlined earlier is that we 
>>have a patch to the ffmpeg core that needs to be applied in order to 
>>achieve compliance with RFC2190. This is really just for H263 over RTP.
>>
>>If I'm not mistaken the original goal of the project was to worry more 
>>about opening different media containers (avi, etc) and playing the 
>>contents. Basically to play things from a file, or maybe stream them 
>>over rtsp or such so long as the RTP support is straight forward (I see 
>>H263/RTP as a special case in this regards). This would eliminate the 
>>0.4.7 dependency if we don't have H263/RTP.
>>
>>So, we have a few options:
>>- Fold everything into the main project causing the 0.4.7 dependency
>>- Create a separate branch just for H263_RTP
>>- Try to use compiler directives for the 263/RTP part to remove the 
>>0.4.7 dependency at compile time..
>>
>>Are there any favourites with the crowd?
>>
>>-- 
>>David Stuart, SIPquest
>>Email: dave (at) sipquest (dot) com
>>Phone: 254-8886 x234  Web: http://www.sipquest.com/
>>Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5
>>
>>
>>
>>
>>-------------------------------------------------------
>>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>>Build and deploy apps & Web services for Linux with
>>a free DVD software kit from IBM. Click Now!
>>http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
>>_______________________________________________
>>Jffmpeg-devel mailing list
>>Jff...@li...
>>https://lists.sourceforge.net/lists/listinfo/jffmpeg-devel
>>
>>    
>>
>
>
>-------------------------------------------------------
>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>Build and deploy apps & Web services for Linux with
>a free DVD software kit from IBM. Click Now!
>http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
>_______________________________________________
>Jffmpeg-devel mailing list
>Jff...@li...
>https://lists.sourceforge.net/lists/listinfo/jffmpeg-devel
>  
>

-- 
David Stuart, SIPquest
Email: dave (at) sipquest (dot) com
Phone: 254-8886 x234  Web: http://www.sipquest.com/
Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5

Re: [Jffmpeg-devel] project direction?

[Bill S. <bi...@gw...>]

Hi David,

With some minor tweaking, I was able to get MPEG1 working fine for
me.  MPEG1, MPEG2, and MPEG4 support are what I am most interested
in so my vote would be to do whatever needs to be done to maintain
support for MPEG.  It would seem to me that no one format should be
deemed important enough to eliminate support for others.  If ffmpeg is
what is flawed, then I'd say focusing effort on getting it fixed would be
the best use of resources.  With all of that said, I'd vote the best order of
choices would be 

- Try to use compiler directives for the 263/RTP part to remove the 
   0.4.7 dependency at compile time
- Create a separate branch just for H263_RTP
- Fold everything into the main project causing the 0.4.7 dependency

Thanks,
Bill


----- Original Message ----- 
From: "David Stuart" <da...@si...>
To: <jff...@li...>
Sent: Wednesday, March 03, 2004 10:24 AM
Subject: [Jffmpeg-devel] project direction?


> Hi All,
> 
> So my latest update is nearing completion, but it looks like this update 
> will once again be a big change. So now, I'd like to ask the adivce of 
> the other developers. There are two big problems with this upcoming update:
> 
>    1. For the moment it limits jffmpeg to 0.4.7
>    2. MPEG support is removed
> 
> Now, I don't see #2 as a big issue at the moment, since from the posts 
> to this list, I gather that MPEG support doesn't currently work (in 
> fact, I suspect that if you went back before any of my updates that MPEG 
> support probably didn't work in the initial version due to some bugs 
> that were present).
> 
> But, #1 is a bit tougher. The issue as I outlined earlier is that we 
> have a patch to the ffmpeg core that needs to be applied in order to 
> achieve compliance with RFC2190. This is really just for H263 over RTP.
> 
> If I'm not mistaken the original goal of the project was to worry more 
> about opening different media containers (avi, etc) and playing the 
> contents. Basically to play things from a file, or maybe stream them 
> over rtsp or such so long as the RTP support is straight forward (I see 
> H263/RTP as a special case in this regards). This would eliminate the 
> 0.4.7 dependency if we don't have H263/RTP.
> 
> So, we have a few options:
> - Fold everything into the main project causing the 0.4.7 dependency
> - Create a separate branch just for H263_RTP
> - Try to use compiler directives for the 263/RTP part to remove the 
> 0.4.7 dependency at compile time..
> 
> Are there any favourites with the crowd?
> 
> -- 
> David Stuart, SIPquest
> Email: dave (at) sipquest (dot) com
> Phone: 254-8886 x234  Web: http://www.sipquest.com/
> Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Jffmpeg-devel mailing list
> Jff...@li...
> https://lists.sourceforge.net/lists/listinfo/jffmpeg-devel
> 

[Jffmpeg-devel] project direction?

[David S. <da...@si...>]

Hi All,

So my latest update is nearing completion, but it looks like this update 
will once again be a big change. So now, I'd like to ask the adivce of 
the other developers. There are two big problems with this upcoming update:

   1. For the moment it limits jffmpeg to 0.4.7
   2. MPEG support is removed

Now, I don't see #2 as a big issue at the moment, since from the posts 
to this list, I gather that MPEG support doesn't currently work (in 
fact, I suspect that if you went back before any of my updates that MPEG 
support probably didn't work in the initial version due to some bugs 
that were present).

But, #1 is a bit tougher. The issue as I outlined earlier is that we 
have a patch to the ffmpeg core that needs to be applied in order to 
achieve compliance with RFC2190. This is really just for H263 over RTP.

If I'm not mistaken the original goal of the project was to worry more 
about opening different media containers (avi, etc) and playing the 
contents. Basically to play things from a file, or maybe stream them 
over rtsp or such so long as the RTP support is straight forward (I see 
H263/RTP as a special case in this regards). This would eliminate the 
0.4.7 dependency if we don't have H263/RTP.

So, we have a few options:
- Fold everything into the main project causing the 0.4.7 dependency
- Create a separate branch just for H263_RTP
- Try to use compiler directives for the 263/RTP part to remove the 
0.4.7 dependency at compile time..

Are there any favourites with the crowd?

-- 
David Stuart, SIPquest
Email: dave (at) sipquest (dot) com
Phone: 254-8886 x234  Web: http://www.sipquest.com/
Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5

[Fwd: Re: [Jffmpeg-devel] need some hints]

[David S. <da...@si...>]

  Copying the devel list...

-------- Original Message --------
Subject: Re: [Jffmpeg-devel] need some hints
Date: Mon, 01 Mar 2004 17:24:14 -0500
From: David Stuart <da...@si...>
Organization: SIPQuest
To: Alexandre Schulter <sch...@in...>
CC: jffmpeg-devel-request <jff...@li...>
References: <Pine.GSO.4.44.0403011901410.547-100000@juno>



Hmm, looks like MPEG2 still needs some work, then. I'm not overly 
suprised, it has not really been tested.

Pray tell, if you are still in an experimental mood, does it work with 
MPEG-1?



Alexandre Schulter wrote:

>Bad news, it does work. A AVI file encoded with H263 does work, but MPEG2
>does not.
>
>
>Alexandre Schulter
>
>On Thu, 26 Feb 2004, David Stuart wrote:
>
>  
>
>>OK, how about this.. using ffmpeg, create an h.263 encoded file (video
>>only) and try to play that using jffmpeg. If this works for you then we
>>know the problem is in the jffmpeg support for MPEG, and not with your
>>setup and/or configuration. If it doesn't work, well then we should look
>>at your setup.
>>
>>
>>Alexandre Schulter wrote:
>>
>>    
>>
>>>I'm on Linux. The error that happened with the file with only video was:
>>>
>>> Unable to handle format: MPEG, 720x480, FrameRate=29.9, Length=518400
>>>Failed to realize: com.sun.media.PlaybackEngine@fb56b1
>>>Error: Unable to realize com.sun.media.PlaybackEngine@fb56b1
>>>
>>>To create the file without audio, I used ffmpeg:
>>>
>>>ffmpeg -i test.mpg -vcodec copy -an test_noaudio.mpg
>>>
>>>
>>>
>>>      
>>>
>
>  
>

-- 
David Stuart, SIPquest
Email: dave (at) sipquest (dot) com
Phone: 254-8886 x234  Web: http://www.sipquest.com/
Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5





-- 
David Stuart, SIPquest
Email: dave (at) sipquest (dot) com
Phone: 254-8886 x234  Web: http://www.sipquest.com/
Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5

Re: [Jffmpeg-devel] need some hints

[Alexandre S. <sch...@in...>]

I'm on Linux. The error that happened with the file with only video was:

  Unable to handle format: MPEG, 720x480, FrameRate=29.9, Length=518400
Failed to realize: com.sun.media.PlaybackEngine@fb56b1
Error: Unable to realize com.sun.media.PlaybackEngine@fb56b1

To create the file without audio, I used ffmpeg:

ffmpeg -i test.mpg -vcodec copy -an test_noaudio.mpg


Alexandre Schulter

On Wed, 25 Feb 2004, David Stuart wrote:

> Sorry to hear that, I was hoping the MPEG stuff would work without too
> much tinkering. Are you on Windows, Linux, or .. ?
>
> You're still getting the error message about "mpegaudio", even with an
> mpeg file with no audio?
>
> How did you create the file? Can you record an MPEG video clip using a
> stock JMStudio (make sure microphone capture is turned off), and then
> play it back using the one with the codec?
>
> Alexandre Schulter wrote:
>
> >Yes, I tried to play some mpeg files without audio, but the same problem
> >happened.
> >
> >
>

Re: [Jffmpeg-devel] need some hints

[David S. <da...@si...>]

Sorry to hear that, I was hoping the MPEG stuff would work without too 
much tinkering. Are you on Windows, Linux, or .. ?

You're still getting the error message about "mpegaudio", even with an 
mpeg file with no audio?

How did you create the file? Can you record an MPEG video clip using a 
stock JMStudio (make sure microphone capture is turned off), and then 
play it back using the one with the codec?

Alexandre Schulter wrote:

>Yes, I tried to play some mpeg files without audio, but the same problem
>happened.
>  
>

Re: [Jffmpeg-devel] Re: [JMF] JMF and mpeg4?

[David S. <da...@si...>]

Stephen Davidson wrote:

> I have just done some testing, a bit of work in file layout, and 
> mostly cheering. 


heh heh! At the moment I would say you're doing all the PR work for the 
project.. ;)

>> My understanding is that jffmpeg does some work to initialize the 
>> avcodec
>> library, then captures YUV bitmap images from it as frames. Is this
>> correct? 
>

In most cases, yes. Bascially JMF will pass one "frame" of the input as 
a Buffer object which will be decoded into an output buffer as a single 
frame of the selected output type. This is the situation when you try to 
decode from a file and play it. The encoding process is just reversed in 
this case.

The exception to this is H263_RTP, where some packetization has to be 
done in the codec (it's a shame really, it kind of ruins the otherwise 
nice architectural picture). Personally, I blame RFC2190. ;)

I am not sure how other types of information are transmitted over RTP. I 
hear that MPEG for instance is combined by JMF into frames so that it is 
treated the same as the "file" case. I suspect that only H236_RTP and 
H236_1998_RTP are special cases.

So this is where it would likely be easy to extend. If it holds true 
that the input and output are always a single frame of the image, it 
will be easy to extend to more types since jffmpeg acts more as a 
wrapper for the real ffmpeg.

If however, more special cases are needed for RTP then it gets tricky. 
But then, if you are not worried about RTP it might work well for you.


You are certainly welcome to pull the code down and experiment with it; 
however be aware that there is a major update coming in the not too 
distant future (mainly dealing with finalizing support for H263_RTP) so 
you might want to hold off submissions until after this is finished. 
Personally I am anticipating something in the coming weeks.

Re: [Jffmpeg-devel] need some hints

[Alexandre S. <sch...@in...>]

Yes, I tried to play some mpeg files without audio, but the same problem
happened.


Alexandre Schulter

On Fri, 20 Feb 2004, David Stuart wrote:

> A few things that you should probably double check:
>
> Make sure that the library is in your LD_LIBRARY_PATH somewhere. If
> you're running JMStudio then you can put the library file in the "lib"
> folder inside of the JMF directory. Failing that you might have to go as
> far as putting it under WINDOWS\System32 if you're on the windows platform.
>
> Also make sure you have the jffmpeg.jar in your classpath.
>
> Next, you should probably double check to see that it was added OK in
> JMStudio. You might also want to remove the other codecs which support
> the same types as jffmpeg (just to make sure the new one is getting
> selected).
>
>
> Alexandre Schulter wrote:
>
> >java -classpath
> >/home/alexandre/jffmpeg/build/lib/jffmpeg.jar:/mnt/scsi4/java/JMF2.1.1/lib/jmf.jar
> >-Djava.library.path=/home/alexandre/jffmpeg/build/lib
> >net.sourceforge.jffmpeg.Test
> >
> OK, at least it's in the CLASSPATH, check...
>
> >	But it didn't run, cause no output format was set. So I added this
> >to Test.java:
> >
>
> The "Test.java" class is showing its age; I haven't touched it for
> awhile (there might be bugs)..
>
> >YUVFormat out = new YUVFormat(new Dimension(320,240),
> >Format.NOT_SPECIFIED, Format.byteArray, Format.NOT_SPECIFIED,
> >YUVFormat.YUV_420, 320, 320, 0, 77120, 76800);
> >my_jffmpeg.setOutputFormat(out);
> >
> >	Then finally I saw the "Hello world"...
> >
> >	To register the plugin, I used this code:
> >
> >		// Name of the new plugin
> >		 String JffmpegDecoderPlugin = new
> >String("net.sourceforge.jffmpeg.NativeDecoder");
> >
> >		 // Supported input Formats
> >		 Format[] supportedInputFormats = new Format[] {
> >				new VideoFormat(VideoFormat.MPEG),
> >				new VideoFormat(VideoFormat.H263),
> >				new VideoFormat(VideoFormat.H263_RTP)
> >		 };
> >
> >		 // Supported output Formats
> >		 Format[] supportedOutputFormats = new Format[] {
> >				new YUVFormat(YUVFormat.YUV_420)
> >		 };
> >
> >		 // Add the new plug-in to the plug-in registry
> >		 PlugInManager.addPlugIn(JffmpegDecoderPlugin,
> >supportedInputFormats, supportedOutputFormats, PlugInManager.CODEC);
> >
> >		 // Save the changes to the plug-in registry
> >		 try{
> >			PlugInManager.commit();
> >		 }catch (IOException ioe) { System.out.println("nooo!!"); }
> >
> >	jffmpeg.jar needs to be in the classpath for it to work. Then
> >net.sourceforge.jffmpeg.NativeDecoder appears in the jmfregistry tool, as
> >a codec plugin.
> >	So, the problem is I can't play MPEG2 or MPEG1 coded files. The
> >first one I tried threw this error:
> >
>
> The code looks OK to me,,
>
> >Unable to handle format: mpegaudio, 44100.0 Hz, 16-bit, Stereo,
> >LittleEndian, Signed, 48000.0 frame rate, FrameSize=11264 bits
> >Failed to prefetch: com.sun.media.PlaybackEngine@fb56b1
> >Error: Unable to prefetch com.sun.media.PlaybackEngine@fb56b1
> >
>
> mpeg audio? I'm not sure that jffmpeg is doing mpeg audio (at least,
> yet).. VideoFormat.MPEG doesn't sound like audio. I'd have to look at
> the various formats in JMF to see if there's something different for
> MPEG audio.
>
> Do you have a file without audio you could try? (of course, if you need
> the audio that might be a stumbling block)..
>
> Dave
>
> --
> David Stuart, SIPquest
> Email: dave (at) sipquest (dot) com
> Phone: 254-8886 x234  Web: http://www.sipquest.com/
> Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5
>
>
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Jffmpeg-devel mailing list
> Jff...@li...
> https://lists.sourceforge.net/lists/listinfo/jffmpeg-devel
>

[Jffmpeg-devel] Re: [JMF] JMF and mpeg4?

[Stephen D. <go...@fr...>]

Hi Steve.

Thanks, but the complements should really go to others on the list.

I have just done some testing, a bit of work in file layout, and mostly cheering.

Fancisco and Dave have been doing all the "Heavy Work", and an excellent job of it as well.

As for the documentation, good idea.  I need to get some time together to study this.  In the meantime, I am reposting this to the JFFMpeg list as 
they can answer your questions better than I can.

Regards,
Steve

Steve Willis wrote:
> Steve,
> 
> First, thanks for your work on jffmpeg. I have been trying to get jffmpeg
> to play DivX 3 (msmpeg4 to ffmpeg) files for a few weeks now (you
> responded to my initial question on this list). I have been studying the
> ffplay.c source code as well as the jffmpeg source.
> 
> My understanding is that jffmpeg does some work to initialize the avcodec
> library, then captures YUV bitmap images from it as frames. Is this
> correct?
> 
> If anyone would take some time to document the basics of how jffmpeg
> works, I am certainly willing to put in the time to bridge a larger set of
> codecs from ffmpeg. This just isn't my area of expertise, and I'm a little
> out of my depth. But I think some documentation about how the current
> jffmpeg implementation integrates with libavcodec to play MPEG-2 files
> would help me open up more ffmpeg supported formats.
> 
> Thanks again for your hard work!
> 
> Steve
> 

-- 
Java/J2EE Developer/Integrator
Co-Chair, Dallas/FortWorth J2EE Sig
214-724-7741

Re: [Jffmpeg-devel] Re: JMF wrapper for ffmpeg (SourceForge project)

[David S. <da...@si...>]

Hi Steve,

As for MPEG-2, I don't think I will check anything in until we at least 
maintain the current number of formats.

The 0.4.7 and 0.4.8 thing has potential for confusion, I admit. The 
problem is that we cannot achieve RFC2190 compliance with 0.4.8 (at 
least until the contractor's work I'm using is folded into the ffmpeg 
stream), and I guess you cannot use 0.4.7 for another reason..

The root of the problem is that we are not paying our contractor to port 
his patch to 0.4.8; only to make it work with jffmpeg. Unfortunately the 
patch is larger than I am comfortable with porting myself. Once his work 
is done I will speak to him about his patch..

The only way out that I can see is to have some kind of compilation 
directive to make H263_RTP optional (but if enabled, it would then 
require the patch and also 0.4.7, at least for now). I sense 
preprocessor ugliness ahead..


Stephen Davidson wrote:

> Hi David.
>
> Ummm, this is going to make things interesting.  I will admit that I 
> have not been able to get JMF to support MPEG-2/4 using JFFMpeg yet, 
> but I don't know that this is not because of an issue with known 
> defective hardware.  What has me concerned is;
> 1) I AM currently using 0.4.8, specifically for some non-JMF stuff;
> 2) I am currently working with MPEG-2 almost exclusively....
>
> On the other hand, due to the JMF issues I AM having, I might be 
> better off to just go straight to FFMPeg for the moment?
>
> Regards,
> Steve
>
> David Stuart wrote:
>
>> Actually the reason I haven't posted anything for awhile is because 
>> I'm trying to stabilize a new version with Guilhem. Guilhem has done 
>> some good work including fixing most of the encoding errors in H263 
>> and H263_RTP as well as added conversion to RGB (thereby eliminating 
>> the extra conversion step in JMF).
>>
>> So there's good things coming but his update will introduce a 
>> dependency on ffmpeg 0.4.7 (because he needed to patch ffmpeg to 
>> properly support H263_RTP). Also he's temporarily removed MPEG 
>> support, something I would hope to add back before checking in..
>>
>> So maybe now WOULD be a good time to make a dot release, because the 
>> next version will likely significantly change several things..
>>
>> MPEG-4 is on the table for future enhancements but we're not there 
>> yet. First we want to stabilize 263, and then 263+...
>>
>>
>
>
>

-- 
David Stuart, SIPquest
Email: dave (at) sipquest (dot) com
Phone: 254-8886 x234  Web: http://www.sipquest.com/
Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5

Re: [Jffmpeg-devel] Re: JMF wrapper for ffmpeg (SourceForge project)

[Stephen D. <go...@fr...>]

Hi David.

Ummm, this is going to make things interesting.  I will admit that I have not been able to get JMF to support MPEG-2/4 using JFFMpeg yet, but I 
don't know that this is not because of an issue with known defective hardware.  What has me concerned is;
1) I AM currently using 0.4.8, specifically for some non-JMF stuff;
2) I am currently working with MPEG-2 almost exclusively....

On the other hand, due to the JMF issues I AM having, I might be better off to just go straight to FFMPeg for the moment?

Regards,
Steve

David Stuart wrote:
> Actually the reason I haven't posted anything for awhile is because I'm 
> trying to stabilize a new version with Guilhem. Guilhem has done some 
> good work including fixing most of the encoding errors in H263 and 
> H263_RTP as well as added conversion to RGB (thereby eliminating the 
> extra conversion step in JMF).
> 
> So there's good things coming but his update will introduce a dependency 
> on ffmpeg 0.4.7 (because he needed to patch ffmpeg to properly support 
> H263_RTP). Also he's temporarily removed MPEG support, something I would 
> hope to add back before checking in..
> 
> So maybe now WOULD be a good time to make a dot release, because the 
> next version will likely significantly change several things..
> 
> MPEG-4 is on the table for future enhancements but we're not there yet. 
> First we want to stabilize 263, and then 263+...
> 
> 



-- 
Java/J2EE Developer/Integrator
Co-Chair, Dallas/FortWorth J2EE Sig
214-724-7741

[Jffmpeg-devel] Re: AW: JMF wrapper for ffmpeg (SourceForge project)

[Stephen D. <go...@fr...>]

Hi Michael.

I use Eclipse on Win2K, and have not had a problem at all.  As a result, I do not know the WinCVS settings.  If you want to try Eclipse, free 
download at http://eclipse.org.

I am using both Win2K & Linux, so can give you a hand.  What are you having trouble with?

Regards,
Steve

Michael Zufferey wrote:
> Hello!
> 
> It is a very good new that the project is not abandoned!
> 
> I have tried to checkout the file from the CVS repository using WinCVS
> without success! It cannot find the module name and/or the path! I have
> tried with /cvsroot/jffmpeg or /jffmpeg and other without success!
> 
> Do I have done something wrong?
> 
> So I have downloaded the file manually and recreate the folders
> structure on my harddisk! But I am not sure that this is a good
> solution!
> 
> I work with Windows XP and not Linux and I feel a bit lost with the
> installation instruction!
> 
> If it is not too much to ask you, could you please explain me briefly
> the structure of the packages (how jffmpeg is organized and which
> classes (C++ and Java) and where are them) and how can I compile the
> software under Windows (I have .net installed)?
> 
> Are there mailing list or other website about this project?
> 
> Many thank for your attention and help.
> 
> Regards,
> Michael 
> 

-- 
Java/J2EE Developer/Integrator
Co-Chair, Dallas/FortWorth J2EE Sig
214-724-7741

Re: [Jffmpeg-devel] Re: JMF wrapper for ffmpeg (SourceForge project)

[David S. <da...@si...>]

Actually the reason I haven't posted anything for awhile is because I'm=20
trying to stabilize a new version with Guilhem. Guilhem has done some=20
good work including fixing most of the encoding errors in H263 and=20
H263_RTP as well as added conversion to RGB (thereby eliminating the=20
extra conversion step in JMF).

So there's good things coming but his update will introduce a dependency=20
on ffmpeg 0.4.7 (because he needed to patch ffmpeg to properly support=20
H263_RTP). Also he's temporarily removed MPEG support, something I would=20
hope to add back before checking in..

So maybe now WOULD be a good time to make a dot release, because the=20
next version will likely significantly change several things..

MPEG-4 is on the table for future enhancements but we're not there yet.=20
First we want to stabilize 263, and then 263+...


Stephen Davidson wrote:

> Hi Mike.
>
> Looks can be deceiving, happily.
>
> It is not abandoned, but instead has TWO corporate backers (one in=20
> Spain, one in Canada), and currently one occasional contributor.  If=20
> you check the change logs, you would see.
>
> Suppose we should release a version, 'cause I think it is stable.  I=20
> have not seen any postings from Dave lately, and he usually sends an=20
> email when  he has checked something nifty and new in.
>
> Regards,
> Steve
>
> Michael Zufferey wrote:
>
>> Dear Mr. Stephen Davidson,
>>
>> =20
>>
>> I am a PhD student at the University of Klagenfurt, Austria! In my=20
>> project I will be involved in MPEG-4, MPEG-7, Java and JMF.=20
>> Consequently, I am very interested in your project =93JMF wrapper for=20
>> ffmpeg=94 hosted at https://sourceforge.net/projects/jffmpeg/ . Anyway=
,=20
>> I have seen that the project doesn=92t progress and is in an early=20
>> stage of development! Is it may be abandoned or stopped? Or later the=20
>> development will continue?
>
--=20
David Stuart, SIPquest
Email: dave (at) sipquest (dot) com
Phone: 254-8886 x234  Web: http://www.sipquest.com/
Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5

[Jffmpeg-devel] Re: JMF wrapper for ffmpeg (SourceForge project)

[Stephen D. <go...@fr...>]

Hi Mike.

Looks can be deceiving, happily.

It is not abandoned, but instead has TWO corporate backers (one in Spain,=
 one in Canada), and currently one occasional contributor.  If you check =

the change logs, you would see.

Suppose we should release a version, 'cause I think it is stable.  I have=
 not seen any postings from Dave lately, and he usually sends an email wh=
en=20
  he has checked something nifty and new in.

Regards,
Steve

Michael Zufferey wrote:
> Dear Mr. Stephen Davidson,
>=20
> =20
>=20
> I am a PhD student at the University of Klagenfurt, Austria! In my=20
> project I will be involved in MPEG-4, MPEG-7, Java and JMF.=20
> Consequently, I am very interested in your project =93JMF wrapper for=20
> ffmpeg=94 hosted at https://sourceforge.net/projects/jffmpeg/ . Anyway,=
 I=20
> have seen that the project doesn=92t progress and is in an early stage =
of=20
> development! Is it may be abandoned or stopped? Or later the developmen=
t=20
> will continue?
>=20
> =20
>=20
> Thank you very much for your attention.
>=20
> =20
>=20
> Best wishes,
>=20
> Michael Zufferey
>=20
> University of Klagenfurt
>=20
> Austria
>=20
> =20
>=20


--=20
Java/J2EE Developer/Integrator
Co-Chair, Dallas/FortWorth J2EE Sig
214-724-7741

Re: [Jffmpeg-devel] MPEG-2 m2p files, and MPEG1 issues

[David S. <da...@si...>]

Stephen Davidson wrote:

> What I am trying to do is use JMS Studio to play the M2P files at;
> http://www.j2eeguys.com/~steve/
> http://www.j2eeguys.com/~steve/1539.m2p
>
> These are MPEG-2 Video files.  Adding JFFMpeg as a codec does not seem 
> to allow JMStudio to handle Video MPEG2. 


I have not personally as of yet tried MPEG-2 Video files. I am not sure 
if they ever worked; although come to think of it "jason AT vennerable 
DOT com" might have mentioned to me that he had it working at one point 
(with his own modified version however).

Is there even a Video Type registered in JMF for this? If not, one might 
have to be coded..

[Jffmpeg-devel] MPEG-2 m2p files, and MPEG1 issues

[Stephen D. <go...@fr...>]

Greetings.

Ok, I have jffmpeg building and compiling again.

What I am trying to do is use JMS Studio to play the M2P files at;
http://www.j2eeguys.com/~steve/
http://www.j2eeguys.com/~steve/1539.m2p

These are MPEG-2 Video files.  Adding JFFMpeg as a codec does not seem to allow JMStudio to handle Video MPEG2.

So, what do I need to do to get more than just sound?  Replace JMStudio with my own applet?

Regards,
Steve

-- 
Java/J2EE Developer/Integrator
Co-Chair, Dallas/FortWorth J2EE Sig
214-724-7741

Re: [Jffmpeg-devel] need some hints

[David S. <da...@si...>]

A few things that you should probably double check:

Make sure that the library is in your LD_LIBRARY_PATH somewhere. If 
you're running JMStudio then you can put the library file in the "lib" 
folder inside of the JMF directory. Failing that you might have to go as 
far as putting it under WINDOWS\System32 if you're on the windows platform.

Also make sure you have the jffmpeg.jar in your classpath.

Next, you should probably double check to see that it was added OK in 
JMStudio. You might also want to remove the other codecs which support 
the same types as jffmpeg (just to make sure the new one is getting 
selected).


Alexandre Schulter wrote:

>java -classpath
>/home/alexandre/jffmpeg/build/lib/jffmpeg.jar:/mnt/scsi4/java/JMF2.1.1/lib/jmf.jar
>-Djava.library.path=/home/alexandre/jffmpeg/build/lib
>net.sourceforge.jffmpeg.Test
>
OK, at least it's in the CLASSPATH, check...

>	But it didn't run, cause no output format was set. So I added this
>to Test.java:
>

The "Test.java" class is showing its age; I haven't touched it for 
awhile (there might be bugs)..

>YUVFormat out = new YUVFormat(new Dimension(320,240),
>Format.NOT_SPECIFIED, Format.byteArray, Format.NOT_SPECIFIED,
>YUVFormat.YUV_420, 320, 320, 0, 77120, 76800);
>my_jffmpeg.setOutputFormat(out);
>
>	Then finally I saw the "Hello world"...
>
>	To register the plugin, I used this code:
>
>		// Name of the new plugin
>		 String JffmpegDecoderPlugin = new
>String("net.sourceforge.jffmpeg.NativeDecoder");
>
>		 // Supported input Formats
>		 Format[] supportedInputFormats = new Format[] {
>				new VideoFormat(VideoFormat.MPEG),
>				new VideoFormat(VideoFormat.H263),
>				new VideoFormat(VideoFormat.H263_RTP)
>		 };
>
>		 // Supported output Formats
>		 Format[] supportedOutputFormats = new Format[] {
>				new YUVFormat(YUVFormat.YUV_420)
>		 };
>
>		 // Add the new plug-in to the plug-in registry
>		 PlugInManager.addPlugIn(JffmpegDecoderPlugin,
>supportedInputFormats, supportedOutputFormats, PlugInManager.CODEC);
>
>		 // Save the changes to the plug-in registry
>		 try{
>			PlugInManager.commit();
>		 }catch (IOException ioe) { System.out.println("nooo!!"); }
>
>	jffmpeg.jar needs to be in the classpath for it to work. Then
>net.sourceforge.jffmpeg.NativeDecoder appears in the jmfregistry tool, as
>a codec plugin.
>	So, the problem is I can't play MPEG2 or MPEG1 coded files. The
>first one I tried threw this error:
>

The code looks OK to me,,

>Unable to handle format: mpegaudio, 44100.0 Hz, 16-bit, Stereo,
>LittleEndian, Signed, 48000.0 frame rate, FrameSize=11264 bits
>Failed to prefetch: com.sun.media.PlaybackEngine@fb56b1
>Error: Unable to prefetch com.sun.media.PlaybackEngine@fb56b1
>

mpeg audio? I'm not sure that jffmpeg is doing mpeg audio (at least, 
yet).. VideoFormat.MPEG doesn't sound like audio. I'd have to look at 
the various formats in JMF to see if there's something different for 
MPEG audio.

Do you have a file without audio you could try? (of course, if you need 
the audio that might be a stumbling block)..

Dave

-- 
David Stuart, SIPquest
Email: dave (at) sipquest (dot) com
Phone: 254-8886 x234  Web: http://www.sipquest.com/
Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5

[Jffmpeg-devel] need some hints

[Alexandre S. <sch...@in...>]

	Hi everybody,

	First of all, congratulations for this great ideia, cause it's
amazing if someday we can use all those ffmpeg codecs with Java.
	I'm hoping to be able to play MPEG2 encoded files with Java under
Linux, and maybe network streams in the future. So, I downloaded and sucessfully
compiled and registered the jffmpeg plugin with JMF, but it's seems not to
be working.
	I'm using this:

Slackware Linux 9.0
SUN JDK 1.4.1_01
JMF 2.1.1
ffmpeg 0.4.8

	I did the necessary changes in the config.mak file, and then
compiled it with 'make'. A lot of warnings appeared, but it did compile...
To run the Test.java program, I used this:

java -classpath
/home/alexandre/jffmpeg/build/lib/jffmpeg.jar:/mnt/scsi4/java/JMF2.1.1/lib/jmf.jar
-Djava.library.path=/home/alexandre/jffmpeg/build/lib
net.sourceforge.jffmpeg.Test

	But it didn't run, cause no output format was set. So I added this
to Test.java:

YUVFormat out = new YUVFormat(new Dimension(320,240),
Format.NOT_SPECIFIED, Format.byteArray, Format.NOT_SPECIFIED,
YUVFormat.YUV_420, 320, 320, 0, 77120, 76800);
my_jffmpeg.setOutputFormat(out);

	Then finally I saw the "Hello world"...

	To register the plugin, I used this code:

		// Name of the new plugin
		 String JffmpegDecoderPlugin = new
String("net.sourceforge.jffmpeg.NativeDecoder");

		 // Supported input Formats
		 Format[] supportedInputFormats = new Format[] {
				new VideoFormat(VideoFormat.MPEG),
				new VideoFormat(VideoFormat.H263),
				new VideoFormat(VideoFormat.H263_RTP)
		 };

		 // Supported output Formats
		 Format[] supportedOutputFormats = new Format[] {
				new YUVFormat(YUVFormat.YUV_420)
		 };

		 // Add the new plug-in to the plug-in registry
		 PlugInManager.addPlugIn(JffmpegDecoderPlugin,
supportedInputFormats, supportedOutputFormats, PlugInManager.CODEC);

		 // Save the changes to the plug-in registry
		 try{
			PlugInManager.commit();
		 }catch (IOException ioe) { System.out.println("nooo!!"); }

	jffmpeg.jar needs to be in the classpath for it to work. Then
net.sourceforge.jffmpeg.NativeDecoder appears in the jmfregistry tool, as
a codec plugin.
	So, the problem is I can't play MPEG2 or MPEG1 coded files. The
first one I tried threw this error:

Unable to handle format: mpegaudio, 44100.0 Hz, 16-bit, Stereo,
LittleEndian, Signed, 48000.0 frame rate, FrameSize=11264 bits
Failed to prefetch: com.sun.media.PlaybackEngine@fb56b1
Error: Unable to prefetch com.sun.media.PlaybackEngine@fb56b1

	So I tried the same file, but with an audio sample rate of 48khz.
Then no audio error came up, which is weird because
com.sun.media.codec.audio.mpa.JavaDecoder seems to support both 44.1 and
48khz. But then this error came up:


  Unable to handle format: MPEG, 720x480, FrameRate=29.9, Length=518400
Failed to realize: com.sun.media.PlaybackEngine@fb56b1
Error: Unable to realize com.sun.media.PlaybackEngine@fb56b1


	Both files are in MPEG Program Stream format. I'll try AVI format
later, but that problably is not going to help. So, can anyone give some
hints?

Thanks for your attention,

Bye!

Alexandre Schulter

[Jffmpeg-devel] MPEG-2 m2p files, and MPEG1 issues

[Stephen D. <go...@fr...>]

Greetings.

Ok, I have jffmpeg building and compiling again.

What I am trying to do is use JMS Studio to play the M2P files at;
http://www.j2eeguys.com/~steve/
http://www.j2eeguys.com/~steve/1539.m2p

These are MPEG-2 Video files.  So, what do I need to do to get more than just sound?

Regards,
Steve

-- 
Java/J2EE Developer/Integrator
Co-Chair, Dallas/FortWorth J2EE Sig
214-724-7741

Re: [Jffmpeg-devel] simple questions

[David S. <da...@si...>]

H263 support is not bad; at least reading and writing to/from files 
seems to be working OK. H263_RTP is still a bit shaky (we are working on 
that- long story short; decoding seems to be fine but problems with 
encoding). MPEG is still largely untested (there is no MPEG_RTP yet) but 
I don't see why it wouldn't work.

Probably after H263 we might work on H263+, then move to H264/MPEG-4... 
after that it's really first-come-first serve. Feel free to download the 
code and tinker with it, however.. if you get something working for (for 
instance MPEG_RTP) we might fold it in..

Cha...@Al... wrote:

>
> Hi All,
>
> sorry if these questions are answered someplace else, but I couldn't 
> find them yet...
>
> In my JMF application, I want to be able to play any format that 
> ffmpeg supports, and
> I want to be able to stream an MPEG movie, for example, as MPEG_RTP or 
> MPEG4_RTP..
>
> How functional are jffmpeg's H263 and MPEG features? and how much time 
> would I expect to
> take to add the features that I described above to jffmpeg... cuz if 
> it's reasonable i'd be happy to
> do it..
>
> Thanks in advance,
> Chad 


-- 
David Stuart, SIPquest
Email: dave (at) sipquest (dot) com
Phone: 254-8886 x234  Web: http://www.sipquest.com/
Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5

[Jffmpeg-devel] simple questions

[<Cha...@Al...>]

Hi All,

sorry if these questions are answered someplace else, but I couldn't find 
them yet... 

In my JMF application, I want to be able to play any format that ffmpeg 
supports, and 
I want to be able to stream an MPEG movie, for example, as MPEG_RTP or 
MPEG4_RTP.. 

How functional are jffmpeg's H263 and MPEG features? and how much time 
would I expect to 
take to add the features that I described above to jffmpeg... cuz if it's 
reasonable i'd be happy to 
do it.. 

Thanks in advance,
Chad

Re: [Jffmpeg-devel] looking for a project admin

[Stephen D. <go...@fr...>]

Hi David.

I think I just saw some stuff on the FFMpeg list about H263 encoding errors.
Wonder if that is what might be causing the issue you are seeing? Anyways,
they are working on it, so it should be fixed shortly.

Regards,
Steve

David Stuart wrote:
> Thanks, I might want some help with the admin part after next month, 
> when presumably I have "finished" this part of my project and won't be 
> tinkering as much in jffmpeg (but then again, who knows, I might be back 
> in)..
> 


-- 
Java/J2EE Developer/Integrator
Co-Chair, Dallas/FortWorth J2EE Sig
214-724-7741

Re: [Jffmpeg-devel] more updates

[David S. <da...@si...>]

Yeah, I know ... :P

Unfortunately I had to go with 0.4.7 because of that patch. But, I'm 
talking to the author of this patch to see if I can get a more recent 
version of it against the 0.4.8 release. Either that, or try to find a 
way to remove the dependency on it..

Are you saying that CVS HEAD of ffmpeg is more stable than release 
0.4.8? I was not aware of this

Stephen Davidson wrote:

> Hi David.
>
> Um, you do know that 0.4.7 is several months old? aAd that while the
> current version claims to be 0.4.8 (and will eventually be release
> under that, someday), that ffmpeg CVS HEAD is actually the current
> stable release, with MANY bug fixes, right?
>
> Anyways, I am doing a test/debug/release cycle right now, and the
> next project is starting in a week or two.  That one, one of the first
> things I will do is bring this up to date (if noone else has done so
> yet).
>
> Regards,
> Steve

-- 
David Stuart, SIPquest
Email: dave (at) sipquest (dot) com
Phone: 254-8886 x234  Web: http://www.sipquest.com/
Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5

Re: [Jffmpeg-devel] looking for a project admin

[David S. <da...@si...>]

Thanks, I might want some help with the admin part after next month, 
when presumably I have "finished" this part of my project and won't be 
tinkering as much in jffmpeg (but then again, who knows, I might be back 
in)..

By the way,

My last updates have at least fixed the H263_RTP sending and receiving 
such that it works between two jffmpeg codecs. There is still a problem 
with RFC2190 compliance and as such it doesn't work that great between 
other codecs. That, and there are still some errors coming from the 
decoder (but I suspect this is really an encoding problem). I have also 
added a framerate and bitrate control into the mix.

There are still some problems with the encoder (aforementioned rfc2190 
compliance, and it occasionally causes the VM to crash, ooops).. but at 
least you can see a reasonable picture.


Stephen Davidson wrote:

> Hi Francisco.
>
> Sorry to hear you are so busy.  Hopefully, this means you are earning 
> some
> Overtime or Bonuses.
>
> David, you have my support if you want it.
>

Re: [Jffmpeg-devel] looking for a project admin

[David S. <da...@si...>]

Thanks, I might want some help with the admin part after next month, 
when presumably I have "finished" this part of my project and won't be 
tinkering as much in jffmpeg (but then again, who knows, I might be back 
in)..

By the way,

My last updates have at least fixed the H263_RTP sending and receiving 
such that it works between two jffmpeg codecs. There is still a problem 
with RFC2190 compliance and as such it doesn't work that great between 
other codecs. That, and there are still some errors coming from the 
decoder (but I suspect this is really an encoding problem). I have also 
added a framerate and bitrate control into the mix.

There are still some problems with the encoder (aforementioned rfc2190 
compliance, and it occasionally causes the VM to crash, ooops).. but at 
least you can see a reasonable picture.


Stephen Davidson wrote:

> Hi Francisco.
>
> Sorry to hear you are so busy.  Hopefully, this means you are earning 
> some
> Overtime or Bonuses.
>
> David, you have my support if you want it.
>