Hey Johannes,

The text should probably changed to something that makes more sense perhaps:

FFMPEG loader FAILED... Maybe quicktime? quicktime4linux loader FAILED... Maybe mpeg? MPEG3 loader FAILED... I give up... error: GEM: pix_film: Unable to open file: /raid0/media/dv_capture1.mov

As for quicktime DV files I'm anoyed. I know I've played QT DV files in Gem on linux before, on a suse9 machine maybe a year ago... I just compiled Gem using whatever libs were installed, and boom it would load quicktime DV files.

So how do I get my machine to load quicktime DV files?

mplayer plays them fine.

Totem plays them fine (and reports the codec as "DV (ffmpeg)" )

vlc does not play it, tries to load as a MPEG PS (whatever that is)

ffplay does not play it (unknown format) I tried ffplay -img [bleh] but none of the results of ffmpeg -formats is a valid "format" (including dv, dvvideo etc..)

Anyone have this working?? I even recompiled Gem with libavcodeccvs from the mplayer repository still no dice... It it was not so easy that first time.... *sigh*

Any tips appreciated.

B>

IOhannes m zmoelnig wrote:

B. Bogart wrote:

...

Hey all,

All great, then when I create a pix_movie I get:

pix_film:: libffmpeg support pix_film:: quicktime support pix_film:: libmpeg3 support

Still looking good. When I try and load my DV quicktime:

FFMPEG: unsupported! quicktime4linux: unsupported! MPEG3: unsupported! error: GEM: pix_film: Unable to open file: /raid0/media/dv_capture1.mov

oh, this is just a misunderstanding. the "unsupported!"-printout just indicates, that the given API was unable to open your file (so quicktime4linux probably does not recognize the DV-codec of dv_capture1.mov)

mfg.sd.ar IOhannes

Possible, but I think the mplayer people would provide a very up-to-date version:

||/ Name Version Description +++-==============-==============-============================================ ii ffmpeg 20050427-0sarg audio/video encoder, streaming server & audi

Certainly a recent date...

Is anyone decoding DV videos (QT) in Gem or ffmpeg on linux?

:|

B>

dpkg reports

Thoralf Schulze wrote:

Hi,

ffdshow (the windows/directshow incarnation of ffmpeg) supports dv video just fine. This probably doesn't help in your case, maybe the ffmpeh version you link against is too old or something.

with kind regards, thoralf.

---

Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com

---

GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev

Hey again,

Well after a LOT more digging I found some things out. First off I realised that mplayer was decoding my DV MOV with ffmpeg. Good news, so I messed with ffplay some more and finally got it to load my MOV the same as totem & mplayer (using ffmpeg).

So the issue seems to be that ffmpeg does not know what kind of file it is, but knows how to decode it.

ffplay dv.mov

gives:

unkown format

ffplay -f dv dv.mov

Works!!!

So we need to force ffmpeg to try a certain codec in this case... Is this possible from inside Gem? Clearly ffmpeg is much better at decoding than recognizing formats, could there be a manual mode to specify the codec manually to pix_film ? Or is there some other library (code from mplayer?) that actually IS good at recognizing formats? mplayer actually tries to load the DV file with qdv.dll but since it is not on my system it gives up and tries ffmpeg, and clearly tells it what format to expect.

So I feel much closer to loading this file in Gem, what do I need to do to get it to actually work? (now that it is clear that ffmpeg will play it).

Thanks.

B>

IOhannes m zmoelnig wrote:

B. Bogart wrote:

i think i have already said this before, but i have to admit (again) that i haven't been able to open _any_ video with FFMPEG (i/o error). probably making this work would help....

mfg.asdr. IOhannes

---

GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev

Hey Guenter,

This is an interesting suggestion. I can't try it now since I'm away from that machine.

Does it imply that ffmpeg uses the filename to check filetype? Or only as a last resort when the magic number test fails?

So if the codec is "DV" then this quicktime is not at all involved? No QT headers or anything? This may explain why qtinfo says the file is not a quicktime... I'm confused why this "codec" would not require a "container" format though... oy!

Anyhow I'll try it tomorrow.

Oh and BTW I can use ffplay to decode three DV videos at the same time, using about 80% CPU on my new Athlon64 3200. no dropped frames visible.. pretty handy.

B.

� wrote:

Hi,

Have you tried to rename it to dv.dv (other extension !) Maybe it is not a quicktime file after all.

Guenter

On Wed, 29 Jun 2005, B. Bogart wrote:

...

Hey again,

Well after a LOT more digging I found some things out. First off I realised that mplayer was decoding my DV MOV with ffmpeg. Good news, so I messed with ffplay some more and finally got it to load my MOV the same as totem & mplayer (using ffmpeg).

So the issue seems to be that ffmpeg does not know what kind of file it is, but knows how to decode it.

ffplay dv.mov

gives:

unkown format

ffplay -f dv dv.mov

Works!!!

So we need to force ffmpeg to try a certain codec in this case... Is this possible from inside Gem? Clearly ffmpeg is much better at decoding than recognizing formats, could there be a manual mode to specify the codec manually to pix_film ? Or is there some other library (code from mplayer?) that actually IS good at recognizing formats? mplayer actually tries to load the DV file with qdv.dll but since it is not on my system it gives up and tries ffmpeg, and clearly tells it what format to expect.

So I feel much closer to loading this file in Gem, what do I need to do to get it to actually work? (now that it is clear that ffmpeg will play it).

Thanks.

B>

IOhannes m zmoelnig wrote:

...

B. Bogart wrote:

i think i have already said this before, but i have to admit (again) that i haven't been able to open _any_ video with FFMPEG (i/o error). probably making this work would help....

mfg.asdr. IOhannes

---

GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev

---

GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev

Hey all,

Ok I renamed my dv file to dv_capture.dv and now ffplay loads it fine without complaining and without the -f dv option.

Even with .dv in the name still Gem will not load it. I can't see any reason for this since ffmpeg loads the file fine on its own...

Johannes, I wonder if I could help you at all with your struggles with ffmpeg? I'm just using apt with the stuff from debian-marillat.

Anyhow I'd really like to get this resolved, since ffmpeg is clearly able to read the file. (I think I'll be using DV a lot in the future)

Any ideas why ffmpeg would load the file but Gem not? Same messages as before ffmpeg "unsupported" unable to load file...

I'll try dv.mov and dv.dv tomorrow. (as well as removing -Werror from the PDP makefiles, blech!)

B.

IOhannes m zmoelnig wrote:

B. Bogart wrote:

...

Hey Guenter,

This is an interesting suggestion. I can't try it now since I'm away from that machine.

a good test would be "file dv.mov"

mfg.asdr IOhannes

---

GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev

A DV stream is not a Quicktime file, it's the raw data with no container at all. It is possible to have one of the DV formats (DV25, DVCPRO, DVCPRO-HD) in a Quicktime container, but that is a different file type altogether.

Quicktime API can handle .dv file streams on OSX and Windows.

cgc

On Jun 30, 2005, at 5:11 AM, günter geiger wrote:

Hi,

well, in general I do not have the slightest idea about dv. I just remembered that I once had to rename a dv file in order for it to be recognized by ffplay. Now, what leaves to be done is to check what ffplay actually does with this file, maybe it really deduces the codec from the extension. Maybe mplayer has a better way to detect what the file actually is. If it is really quicktime or not.

Guenter

On Wed, 29 Jun 2005, B. Bogart wrote:

...

Hey all,

Ok I renamed my dv file to dv_capture.dv and now ffplay loads it fine without complaining and without the -f dv option.

Even with .dv in the name still Gem will not load it. I can't see any reason for this since ffmpeg loads the file fine on its own...

Johannes, I wonder if I could help you at all with your struggles with ffmpeg? I'm just using apt with the stuff from debian-marillat.

Anyhow I'd really like to get this resolved, since ffmpeg is clearly able to read the file. (I think I'll be using DV a lot in the future)

Any ideas why ffmpeg would load the file but Gem not? Same messages as before ffmpeg "unsupported" unable to load file...

I'll try dv.mov and dv.dv tomorrow. (as well as removing -Werror from the PDP makefiles, blech!)

B.

IOhannes m zmoelnig wrote:

...

B. Bogart wrote:

...

Hey Guenter,

This is an interesting suggestion. I can't try it now since I'm away from that machine.

a good test would be "file dv.mov"

mfg.asdr IOhannes

---

GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev

---

GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev

B. Bogart wrote:

Hi,

Thanks for the clarification Chris, I had a feeling you would know the answer.

I got some ffmpeg sample code from the net and I'll take a look to see if that loads the file fine and go from there.

I thought I would mess around with my iBot camera today, I had to manually create the /dev/video1394/0 device, but now coriander sees the camera and will display the output. So the question is how do I tell pix_video to look at it? pix_video reports both 1394 and v4l support. I messed with "driver 0|1" and "device 0|1" but could not get anything out of it. I find these messages really confusing, often devices and drivers are considered the same thing.. blech. "device /dev/video1394/0" would actually be easier...

actually i am wondering now, why i didn't do it like that... i have no idea what happens if i open an ieee1394-device with the v4l-api. would it crash ? so that is why i chose to differentiate between the 2 "driver"-APIs with a message, and to separate between hardware devices (camera1, camera2) with another message.

apart from that: [pix_video] (in ieee1394 mode) tries to open /dev/ieee1394/dv/host#/{PAL,NTSC}/in, where "#" can be defined via the "device"-option. this device is created (with devfs) by the module "dv1394". i do know that devfs has been deprecated for some time, and i don't know how udev behaves in this way. the fallback (if there is no /dev/ieee1394/dv/host#/{PAL,NTSC}/in) is /dev/dv1394 (which might be created by udev (or by hand :-())

mfg.asd.r IOhannes

B. Bogart wrote:

Hey all,

Any ideas why ffmpeg would load the file but Gem not? Same messages as before ffmpeg "unsupported" unable to load file...

could you try to pass the filename URI-encoded to [pix_film] ? like file://bi/ba/bo/video.dv instead of /bi/ba/bo/video.dv

mfg.asdr. IOhannes

Hi,

the file:// URI makes no difference, gem still does not load the file.

The sample code I downloaded does not link again my version of libsvcodec. (probably a very old example).

I google for a more recent example, any suggestions anyone?

Back to messing with 1394

B>

IOhannes m zmoelnig wrote:

IOhannes m zmoelnig wrote:

...

B. Bogart wrote:

...

Hey all,

Any ideas why ffmpeg would load the file but Gem not? Same messages as before ffmpeg "unsupported" unable to load file...

could you try to pass the filename URI-encoded to [pix_film] ? like file://bi/ba/bo/video.dv instead of /bi/ba/bo/video.dv

or even better: file:///bi/video.dv instead of /bi/video.dv ;-)

mfg.a.dr IOhannes

...

mfg.asdr. IOhannes

---

GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev

---

GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev

Hey Johannes, thanks for looking at this, I guess you fixed your ffmpeg?

So I still can't get it to work...

When I start PD I get:

couldn't open alsa sequencer GEM: Graphics Environment for Multimedia GEM: ver: 0.90 GEM: compiled: Jul 7 2005 GEM: maintained by IOhannes m zmoelnig GEM: Authors : Mark Danks (original version on irix/windows) GEM: Chris Clepper (macOS-X) GEM: Daniel Heckenberg (windows) GEM: James Tittle (macOS-X) GEM: IOhannes m zmoelnig (linux/windows) PDP: pure data packet pix_film:: libffmpeg support pix_film:: quicktime support pix_film:: libmpeg3 support pix_film:: libmpeg support GEM: Start rendering

Then when I load the dv file with decoder "0" (ffmpeg?):

* open /raid0/media/dv_capture1.dv 0 gives:

GEM: pix_film: Loaded file: /raid0/media/dv_capture1.dv with -1 frames (720x480) error while decoding

The "error decoding..." happens when I try and send a frame #

* open /raid0/media/dv_capture1.dv 1 gives:

GEM: pix_film: Loaded file: /raid0/media/dv_capture1.dv with -1 frames (720x480) error while decoding

* open /raid0/media/dv_capture1.dv 2 gives:

GEM: pix_film: Loaded file: /raid0/media/dv_capture1.dv with -1 frames (720x480) error while decoding

* open /raid0/media/dv_capture1.dv 3 gives:

quicktime failedGEM: pix_film: Loaded file: /raid0/media/dv_capture1.dv with -1 frames (720x480) error while decoding

* open /raid0/media/dv_capture1.dv 4 gives:

MPEG3 failedGEM: pix_film: Loaded file: /raid0/media/dv_capture1.dv with -1 frames (720x480) error while decoding

* open /raid0/media/dv_capture1.dv 5 gives:

GEM: pix_film: Loaded file: /raid0/media/dv_capture1.dv with -1 frames (720x480) error while decoding

Looks like the console buffer does not get flushed when one of the codec's fail and we end up getting the error message only during the next attempt to load the file. Note I see that quicktime and mpeg3 failed, but no messages about ffmpeg nor mpeg. in the gem-window we just get ugly garbled pixel data in the texture.

Thanks for trying, I feel we are close!!!

b>

IOhannes m zmoelnig wrote:

B. Bogart wrote:

...

Hi,

the file:// URI makes no difference, gem still does not load the file.

The sample code I downloaded does not link again my version of libsvcodec. (probably a very old example).

I google for a more recent example, any suggestions anyone?

ok, i finally made it work. the line for registering all codecs to ffmpeg was missing.

so the recent CVS-version should work with ffmpeg. unfortunately it does not yet report back the number of frames (neither at load-time nor when it reaches the end); so it is hard to loop if you don't know the exact number of frames. additionally you have to initialize the current frame (either via "auto" or an explicit frame) to see something: just loading will give you a success message and a white canvas :-(

anyhow, it works fine but i had problems with mpegs (e.g. alea.mpg). therefore you can specify an additional argument on opening that defines the preferred library (e.g. if you have ffmpeg+quicktime+mpeg3 support (in this order as displayed on startup), [open alea.mpg 2( will first try to open the file with libmpeg3, and if that fails will go through all 3 supported libraries)

mfg.a.drs IOhannes

---

GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev

chris clepper wrote:

On Jun 24, 2005, at 9:57 AM, B. Bogart wrote:

...

Hey all,

I got Gem-CVS compiled on OSX now but upon trying to load a DV quicktime movie was suprised that Gem is contridicting itself. :(

GEM on OSX should use the real Quicktime and not libquicktime. Try again using -framework Quicktime -framework Carbon and so on.

either Ben is _not_ using OS-X right now (even though he states so), or the configure-script is completely fucked up.

reading the lines about marillat-apt-sources makes me think of debian rather than of darwin.

mfg.asd.r IOhannes