Bug Report: WinFF Could not parse string

[Pinaki Gupta]

Sir,
I'm using WinFF 1.5.4 64bit on a Windows 7 64bit machine.
I needed to convert my video files into a particular x.264 formatted QuickTime
movie for archiving the footage for future use and distribution.

Here is my requirement:

MYQTHDx264.wff

<?xml version="1.0" encoding="utf-8"?>
<presets>
  <qmovvhqdinterlace>
    <label>QuickTime H.264 video with de-interlacing (very high quality)</label>
    <params>-crf 18 -vf "yadif=0:-1:1, hqdn3d=1.5:1.5:6:6, scale=trunc(iw/2)*2:trunc(ih/2)*2"  -vcodec libx264  -preset veryslow -vb 17408k -minrate 17408k -pix_fmt yuv420p -s hd1080 -acodec libvo_aacenc -ar 48000 -b:a 256k -coder 1 -flags +loop -cmp chroma -partitions +parti4x4+partp8x8+partb8x8 -me_method full -subq 6 -me_range 16 -g 12 -bf 2 -keyint_min 2 -sc_threshold 40 -refs 4 -profile:v high -level 4.0 -i_qfactor 0.71 -b_strategy 1 -threads 0 -r 25 </params>
    <extension>mov</extension>
    <category>QuickTime</category>
  </qmovvhqdinterlace>
</presets>


Suddenly I noticed WinFF could not parse the ffmpeg command string in some places..
Say I need to convert a source file "lemon_tree.mpeg" to "lemon_tree.mov",
Winff is giving the output as:

"C:\Program Files\WinFF\ffmpeg.exe" -y -i "R:\Adobe\lemon_tree.mpeg" -crf 18", hqdn3d=1.5:1.5:6:6, scale=trunc(iw/2)*2:trunc(ih/2)*2"  -vcodec libx264  -preset veryslow -vb 17408k -minrate 17408k -pix_fmt yuv420p -s hd1080 -acodec libvo_aacenc -ar 48000 -b:a 256k -coder 1 -flags +loop -cmp chroma -partitions +parti4x4+partp8x8+partb8x8 -me_method full -subq 6 -me_range 16 -g 12 -bf 2 -keyint_min 2 -sc_threshold 40 -refs 4 -profile:v high -level 4.0 -i_qfactor 0.71 -b_strategy 1 -threads 0 -r 25  "C:\Users\appuraja\Documents\lemon_tree.mov"

It is not parsing the 'yadif' filter at all. So I had to manually input this part of string into WinFF command-line.
PLEASE FIX this issue in the future release so I can convert my files without taking lot of time in modifying the WinFF command-line.

Thanks in Advance.

[BiggMatt]

yes i'll try to get to that

--
You received this message because you are subscribed to the Google Groups "WinFF" group.
To unsubscribe from this group and stop receiving emails from it, send an email to winff+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Paul Gevers]

Maybe a stupid question, but are the quotes around the -vf flags really
needed. It may still be wrong that it can't handle properly, but try
without quotes and see if it just works?

Paul

> <mailto:winff+un...@googlegroups.com>.

> For more options, visit https://groups.google.com/d/optout.
>
>

> --
> You received this message because you are subscribed to the Google
> Groups "WinFF" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to winff+un...@googlegroups.com

> <mailto:winff+un...@googlegroups.com>.

[Pinaki Gupta]

Sorry no hope,
Removing the quotes gives me:

"C:\Program Files\WinFF\ffmpeg.exe" -y -i "R:\Adobe\lemon_tree.mpeg" -crf 18 -filter:v , hqdn3d=1.5:1.5:6:6, scale=trunc(iw/2)*2:trunc(ih/2)*2  -vcodec libx264  -preset veryslow -vb 17408k -minrate 17408k -pix_fmt yuv420p -s hd1080 -acodec libvo_aacenc -ar 48000 -b:a 256k -coder 1 -flags +loop -cmp chroma -partitions +parti4x4+partp8x8+partb8x8 -me_method full -subq 6 -me_range 16 -g 12 -bf 2 -keyint_min 2 -sc_threshold 40 -refs 4 -profile:v high -level 4.0 -i_qfactor 0.71 -b_strategy 1 -threads 0 -r 25  "C:\Users\appuraja\Documents\lemon_tree.mov"

Still failed to get that 'yadif' filter.
More important, these quotes are necessary.

[Paul Gevers]

Other work around idea: put -filter:v in the preset instead of -vf. It
looks like our conversion of -vf to filter:v is failing on your preset.

Paul

[Pinaki Gupta]

Situation 1:

-crf 18 -filter:v yadif=0:-1:1, hqdn3d=1.5:1.5:6:6, scale=trunc(iw/2)*2:trunc(ih/2)*2  -vcodec libx264  -preset veryslow -vb 17408k -minrate 17408k -pix_fmt yuv420p -s hd1080 -acodec libvo_aacenc -ar 48000 -b:a 256k -coder 1 -flags +loop -cmp chroma -partitions +parti4x4+partp8x8+partb8x8 -me_method full -subq 6 -me_range 16 -g 12 -bf 2 -keyint_min 2 -sc_threshold 40 -refs 4 -profile:v high -level 4.0 -i_qfactor 0.71 -b_strategy 1 -threads 0 -r 25

Gives:


"C:\Program Files\WinFF\ffmpeg.exe" -y -i "R:\Adobe\lemon_tree.mpeg" -crf 18 -filter:v , hqdn3d=1.5:1.5:6:6, scale=trunc(iw/2)*2:trunc(ih/2)*2  -vcodec libx264  -preset veryslow -vb 17408k -minrate 17408k -pix_fmt yuv420p -s hd1080 -acodec libvo_aacenc -ar 48000 -b:a 256k -coder 1 -flags +loop -cmp chroma -partitions +parti4x4+partp8x8+partb8x8 -me_method full -subq 6 -me_range 16 -g 12 -bf 2 -keyint_min 2 -sc_threshold 40 -refs 4 -profile:v high -level 4.0 -i_qfactor 0.71 -b_strategy 1 -threads 0 -r 25  "C:\Users\appuraja\Documents\lemon_tree.mov"

Situation 2:

-crf 18 -filter:v "yadif=0:-1:1, hqdn3d=1.5:1.5:6:6, scale=trunc(iw/2)*2:trunc(ih/2)*2"  -vcodec libx264  -preset veryslow -vb 17408k -minrate 17408k -pix_fmt yuv420p -s hd1080 -acodec libvo_aacenc -ar 48000 -b:a 256k -coder 1 -flags +loop -cmp chroma -partitions +parti4x4+partp8x8+partb8x8 -me_method full -subq 6 -me_range 16 -g 12 -bf 2 -keyint_min 2 -sc_threshold 40 -refs 4 -profile:v high -level 4.0 -i_qfactor 0.71 -b_strategy 1 -threads 0 -r 25

is giving:

"C:\Program Files\WinFF\ffmpeg.exe" -y -i "R:\Adobe\lemon_tree.mpeg" -crf 18", hqdn3d=1.5:1.5:6:6, scale=trunc(iw/2)*2:trunc(ih/2)*2"  -vcodec libx264  -preset veryslow -vb 17408k -minrate 17408k -pix_fmt yuv420p -s hd1080 -acodec libvo_aacenc -ar 48000 -b:a 256k -coder 1 -flags +loop -cmp chroma -partitions +parti4x4+partp8x8+partb8x8 -me_method full -subq 6 -me_range 16 -g 12 -bf 2 -keyint_min 2 -sc_threshold 40 -refs 4 -profile:v high -level 4.0 -i_qfactor 0.71 -b_strategy 1 -threads 0 -r 25  "C:\Users\appuraja\Documents\lemon_tree.mov"

So I didn't find any way to temporarily solve this issue.

[Paul Gevers]

Hi Pinaki,

I checked the code, and indeed, I implemented yadif as the replacement
for "deinterlaced". If the "deinterlaced" box in the "video" tab is
CHECKED than yadif is not removed (but the arguments to it are). So this
is indeed a bug. I must have missed the fact that yadif could have
arguments when I implemented this (or at the time yadif didn't have
arguments). Unfortunately it means that you can't work around this issue
in Winff until a new release is made with a fix.

Please, to make sure this doesn't get lost, file a bug report in our
issue tracker: https://code.google.com/p/winff/issues/list

Paul

[Pinaki Gupta]

Thanks for the effort you have invested to check for the code and replied accordingly.
May I make a request..
I won't disturb the developers since I'm new to FFMPEG, WinFF and this group.
If you file a bug report to this link you mentioned and send them the link to our discussion here,
that would be a great help for me.
Thanks again.

[BiggMatt]

I've learned not to file anything with the ffmpeg developers

--

You received this message because you are subscribed to the Google Groups "WinFF" group.

To unsubscribe from this group and stop receiving emails from it, send an email to winff+un...@googlegroups.com.

[Paul Gevers]

On 05-01-15 08:55, BiggMatt wrote:
> I've learned not to file anything with the ffmpeg developers

Matt, the bug tracker is OUR bug tracker. Not the one for ffmpeg...

Paul

[BiggMatt]

uh, duh