On 19.06.2025 12:43, Terje J. Hanssen wrote:
Den 18.06.2025 22:17, skrev Andrew
Randrianasulu:
I tried
CinGG-20250430-x86_64.AppImage to record
HDV cam Live video connected via
IEEE-1394 (Sony iLink, Firewire) using
the iec61883 driver.
"For
the IEC
61883 driver,
the compression must be DV."
I
think HDV (mpeg2) was never implemented
there?
I noticed "must be DV", but was not sure how literal
"DV" was meant(?)
According to the ffmpeg man page for iec61883:
The iec61883 capture device supports capturing
from a video device connected via IEEE1394
(FireWire), using libiec61883 and the new
Linux FireWire stack (juju). This is the default
DV/HDV input method in Linux Kernel 2.6.37
and later, since the old FireWire stack was
removed.
Specify the FireWire port to be used as input
file, or "auto" to choose the first port
connected.
https://www.mankier.com/1/ffmpeg-devices#Input_Devices-iec61883
Kernel 2.6.37 was released in Jan 2011.
And according to Phoronix:Linux Has A New Firewire
IEEE-1394 Maintainer - Intends To Maintain Support
To 2029
https://www.phoronix.com/news/Linux-Firewire-New-Maintainer
I
am not sure if I can do anything even if
changes very simple - I have no such
hardware.....
Yeah, I understand that will be difficult.
My legacy SuperMicro workstation had a Firewire port
on its front panel, which now is working with a
Texas Instruments XIO2200A IEEE-1394a-2000
Controller (pci) mounted on the MSI mobo.
libIEC 61883 has not been enabled on my system
ffmpeg-7, but recently I got this bug accepted by
OBS, and iec61883 is just enabled in Factory.
So when it is available for Slowroll, I will try
recording with ffmpeg.
According to the manual:
The file format must be Quicktime for
Linux and video recording must be enabled
for it. Click on the wrench to set the video
compression.
For the IEC 61883 driver,
the compression must be DV.
https://cinelerra-gg.org/download/CinelerraGG_Manual/Live_Video.html
So I tried first
Shift-P
FFMPEG and qt, mp4 audio and dv_pal.qt video
I also tried
FFMPEG mpeg, Audio mpeg_mp2, Video mpeg and
mpeg_hdv
But got these error messages in both cases
using default port 0 or alternative port 1
AVC1394Control::initialize(): couldn't set
port: Invalid argument
int FFMPEG::init_encoder(const char*):
bad file format: /home/terje/test.mpeg
rom1394_0 warning: read failed:
0x0000fffff0000414
AVC1394Control::initialize(): node 0
int FFMPEG::init_encoder(const char*):
bad file format: /home/terje/test.mpeg
A control test of the connection with the
legacy 'dvgrab' recorded a m2t file ok.
Add here that dvgrab 3.5 was released 07.09.2009
This version automatically detects when your device is
DV or HDV so you do not have to remember to supply "-f
hdv."
https://github.com/ddennedy/dvgrab/blob/master/NEWS
* Automatically detect DV vs. HDV when not using
-noavc, -input, or -stdin.
* Now waits indefinitely for DV or HDV instead of
giving up after 10 seconds.
* Bugfixes
Repeat here my short dvgrab test on Leap 15.6, which
also has a possible related "libiec61883 error: Failed
to get channels available."
Yet, robust and worked as follows:
dvgrab -size 0 -autosplit
Found AV/C device with GUID 0x0800460104db475b
libiec61883 error: Failed to get channels
available.
Waiting for HDV...
Capture Started
^C"dvgrab-001.m2t": 344.78 MiB 2764 frames timecode
45:85:85.45 date 2025.06.19 22:37:52
Capture Stopped