[FFmpeg-trac] #5966(avdevice:new): ffmpeg/ffplay specify (H)DV camera's using iec61883 -dvguid option broken or wrong syntax?
FFmpeg
trac at avcodec.org
Sun Nov 20 21:28:00 EET 2016
#5966: ffmpeg/ffplay specify (H)DV camera's using iec61883 -dvguid option broken
or wrong syntax?
--------------------------------------+------------------------------------
Reporter: walterav1984 | Owner:
Type: defect | Status: new
Priority: normal | Component: avdevice
Version: git-master | Resolution:
Keywords: iec61883 | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
--------------------------------------+------------------------------------
Comment (by walterav1984):
Is this the head version of ffmpeg, thats the one I cloned this afternoon.
{{{
git clone git://source.ffmpeg.org/ffmpeg
}}}
I cannot show the failing output of "ffmpeg" since its doesn't even fails
on the -dvguid argument (bogus or not) I specify, ffmpeg will just record
succesfull from the 1st connected camera on the specified firewire
adapter(refered as port 1), although I'm specifying a other or wrong
camera using the -dvguid code:
{{{
./ffmpeg -f iec61883 -i 1 -dvtype dv -dvguid 0x0wronguidcode -target pal-
dv -aspect 16:9 ~/Desktop/somecamera.dv
ffmpeg version N-82572-gac206bb Copyright (c) 2000-2016 the FFmpeg
developers
built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 20160609
configuration: --enable-libiec61883 --extra-ldflags=-ldl --enable-ffplay
libavutil 55. 40.100 / 55. 40.100
libavcodec 57. 66.105 / 57. 66.105
libavformat 57. 58.100 / 57. 58.100
libavdevice 57. 2.100 / 57. 2.100
libavfilter 6. 67.100 / 6. 67.100
libswscale 4. 3.101 / 4. 3.101
libswresample 2. 4.100 / 2. 4.100
[iec61883 @ 0x3927560] Selecting IEEE1394 port: 1
libiec61883 error: Failed to get channels available.
Input #0, iec61883, from '1':
Duration: N/A, start: 0.000000, bitrate: 30848 kb/s
Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 64:45 DAR 16:9],
25000 kb/s, 25 fps, 25 tbr, 25 tbn, 25 tbc
Stream #0:1: Audio: pcm_s16le, 32000 Hz, stereo, s16, 1024 kb/s
Stream #0:2: Audio: pcm_s16le, 32000 Hz, stereo, s16, 1024 kb/s
Output #0, dv, to '/home/ubuntuadmin/Desktop/somecamera.dv':
Metadata:
encoder : Lavf57.58.100
Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 64:45 DAR 16:9],
q=2-31, 200 kb/s, 25 fps, 25 tbn, 25 tbc
Metadata:
encoder : Lavc57.66.105 dvvideo
Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s
Metadata:
encoder : Lavc57.66.105 pcm_s16le
Stream mapping:
Stream #0:0 -> #0:0 (dvvideo (native) -> dvvideo (native))
Stream #0:1 -> #0:1 (pcm_s16le (native) -> pcm_s16le (native))
Press [q] to stop, [?] for help
[dv @ 0x39455a0] Can't process DV frame #137. Insufficient audio data or
severe sync problem.x
frame= 139 fps= 25 q=-0.0 Lsize= 19266kB time=00:00:05.56
bitrate=28385.6kbits/s speed=1.01x
video:19547kB audio:1035kB subtitle:0kB other streams:0kB global
headers:0kB muxing overhead: unknown
}}}
On the otherhand "ffplay" will show an error if the -dvguid is really
wrong:
{{{
./ffplay -f iec61883 -i 1 -dvtype dv -dvguid 2
ffplay version N-82572-gac206bb Copyright (c) 2003-2016 the FFmpeg
developers
built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 20160609
configuration: --enable-libiec61883 --extra-ldflags=-ldl --enable-ffplay
libavutil 55. 40.100 / 55. 40.100
libavcodec 57. 66.105 / 57. 66.105
libavformat 57. 58.100 / 57. 58.100
libavdevice 57. 2.100 / 57. 2.100
libavfilter 6. 67.100 / 6. 67.100
libswscale 4. 3.101 / 4. 3.101
libswresample 2. 4.100 / 2. 4.100
[iec61883 @ 0x7f1100000920] Selecting IEEE1394 port: 1
rom1394_1 warning: read failed: 0x0000fffff000040csq= 0B f=0/0
rom1394_1 warning: read failed: 0x0000fffff0000410
[iec61883 @ 0x7f1100000920] No AV/C devices found.
1: Input/output error
}}}
Does this console output will clarify for a valid ticket as in "software
bug" since the -dvguid option seems not be correctly parsed. Or as a valid
ticket as in a request for a better documentation example howto use the
-dvguid option using multiple camera's?
--
Ticket URL: <https://trac.ffmpeg.org/ticket/5966#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list