pix_video ieee1394 on linux WAS: Re: [GEM-dev] Gem says quicktime ok, then disagrees with itself

[B. Bogart]

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...

Anyhow Once I know how I'm support to switch to "1394" mode then at
least I'll be closer. I'll post the results of my work with the ffmpeg
sample code when I have an idea...

Oh and I got the code from:

http://www.inb.uni-luebeck.de/~boehme/using_libavcodec.html

Seeya,

B>

chris clepper wrote:
> 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 at iem.at
>>>> http://lists.puredata.info/listinfo/gem-dev
>>>>
>>>
>>
>>
>> _______________________________________________
>> GEM-dev mailing list
>> GEM-dev at iem.at
>> http://lists.puredata.info/listinfo/gem-dev
>>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20050630/42e6e457/attachment.pgp>