[FFmpeg-user] ffmpeg CL translation from Linux to Windows

[Claudiu Rad-Lohanel]

On 11/13/2015 8:37 PM, MrNice wrote:
>
> On 13/11/15 15:35, Claudiu Rad wrote:
>> On 11/8/2015 8:25 PM, MrNice wrote:
>>> Hi,
>>>
>>> I need to compare ffmpeg behaviour between Linux and Windows.
>>> I installed Virtualbox on my Fedora host and Win 8.1 as guest.
>>> Now I need to translate the Linux CL
>>> ./ffmpeg -debug 1 -xerror -f pulse -ar 44100 -ac 2 -channel_layout
>>> stereo -thread_queue_size 512 -i
>>> alsa_input.pci-0000_00_14.2.analog-stereo -f v4l2 -ts mono2abs -channel
>>> 1 -video_size 720x576 -pix_fmt yuyv422 -thread_queue_size 512 -i
>>> /dev/video0 -c:v libx264 -vf setfield=tff -preset slow -qp 0 -x264opts
>>> tff=1 -aspect 4:3 -pix_fmt yuv422p -c:a pcm_s16le -channel_layout stereo
>>> /Store3/Test/t_`date +%Y%m%d_%H%M`.mkv -aspect 4:3 -f sdl "Dazzle
>>> output".
>> so you are trying to compare the capture from a USB device but want to
>> run windows inside a VM?
>> i surely wouldn't recommend that, there are many many things that may go
>> wrong.
>> it's way better to install windows side-by-side with linux on a
>> different drive/partition, make all updates, install all drivers and let
>> him do his job without linux/VM layers.
>>
>> and please.. when investigating and posting things, resume to simplest
>> command line possible that reproduces the issue.
>>
> [...]
>
> Back to the point; Windows is only to check if the bug occurs as well. I
> don't want as much as possible to use Win. Last time I used it was
> NT/2000... and I don't have an available computer for it and don't want
> to damage my running config. Anyway, first is to know if it's working,
> so I need to test.

i don't know much about this and sorry for not following your entire 
topic and issue due to time constraints, but i still have some remarks 
that may help:

- your errors contain negative timestamps which is weird. did you try 
all timestamp related ffmpeg options like vsync, copyts, start_at_zero, 
etc. to check their effects?

- frankly if issue reproduces with basic command line, considering the 
fact you are an isolated case, i would judge that the issue is related 
to your equipment/software? that's why one of my suggestions were to try 
a completely different capture card. another option is indeed, try 
windows via directshow. as much as you don't like it, actually from my 
experience in some video/streaming areas its the best option available. 
make sure however you use latest windows OS and try first default 
drivers for your capture device and eventually then explicitly install 
latest one if applicable. i wouldn't be surprised if your issue is 
hardware+driver+OS. in my experience i've seen situations where for 
example: mac + os x + blackmagic card + latest os x drivers + streaming 
tool osx version => periodic crashes . mac + windows + blackmagic card + 
latest windows drivers + streaming tool windows versions => complete success

- if you try windows, please don't do it inside a VM. the data path from 
and to your capture device has much more failure points. to rule out 
windows, i strongly recommend you to try as i've said, clean, latest one 
(windows 10 now), completely updated

-- 
jazzman