New Post: How to set ffmpeg probesize and analyzeduration

For one of my HD WTVs I get massively unsynced video so that in a 90min output file the sound stream is running fine and to the end while video is ending up at about 60%, so 40% have not been transcoded.

The profile I use transcodes to MJPG via ffmpeg (which until now has worked flawlessly).
Log shows almost 50% of duplicate frames reported during conversion and - looking up at the start of the log - I find a note on not enough frames for calculating the rate-

2014-04-18T19:05:46 MCEBuddy.AppWrapper.FFmpegMediaInfo --> Launching process C:\Program Files\MCEBuddy2x\ffmpeg\ffmpeg.exe
2014-04-18T19:05:46 MCEBuddy.AppWrapper.FFmpegMediaInfo --> Process arguments  -probesize 100M -analyzeduration 300M -i "\\MEDIACENTER\VideoConv\MCEB_In\_Test\Frankenweenie_EN.wtv"
...
2014-04-18T19:05:47 MCEBuddy.AppWrapper.FFmpegMediaInfo --> [wtv @ 000000000242d7e0] Stream #3: not enough frames to estimate rate; consider increasing probesize
2014-04-18T19:05:47 MCEBuddy.AppWrapper.FFmpegMediaInfo --> [wtv @ 000000000242d7e0] Stream #4: not enough frames to estimate rate; consider increasing probesize

I'd like to set probesize and analyzeduration to a higher value for a test but don't find any hint on where to put this in the MCEBuddy profiles -

I tried mcebuddy.conf in the FFMpegBackupRemux section

SlowRemux0=-ss 2 -probesize 300M -analyzeduration 700M -i <source> -vcodec mpeg2video -qscale 0 -r auto -acodec copy -map 0:a -map 0:v -f mpegts

and the profiles.conf in the respective section

ffmpeg-general=-threads 0 -probesize 300M -analyzeduration 700M

but in either case after Slow Remuxing starts the log tells me that ffmpeg still is called with probesize 100M and analyzeduration 300M...

That's as far as I get, any help on how to set these parameters via MCEBuddy?