1

Resolved

Broken output file using using AllowH264CopyRemuxing=true

description

Hi Ramit. Please disregard my previous issue, it seems the skipping of my output files is caused by the copy remuxing rather than slow remuxing.

When I use AllowH264CopyRemuxing=true with TS=Unprocessed as my profile I often get files that are broken as an output. They shudder, flicker and motion seems to trigger this.

Please check in my folder on your ftp server: Dodgexander
  • log of sample conversion.log (log of the sample conversion)
  • log of complete file conversion.log (log of the whole file conversion)
  • skippingoutput -sample.wtv (source sample)
There is a sample there you should be able to repeat the problem with.

Once you have converted the sample, the skipping starts when there is motion around 4m:40s into the clip.

My profile:
[TS Unprocessed]
Description=Use this to copy the WTV/DVRMS files to TS format and to remove commercials from your TS videos. It does not remove black bars, resize the video, deinterlace or select audio language. Use this if you have HD recordings which don't need processing.
order=copy,ffmpeg
copy-ext=.ts
copy-audiodelay=skip
ffmpeg-general=-threads 0
ffmpeg-video=-vcodec copy -f mpegts -map 0:a -map 0:v
ffmpeg-audio=-acodec copy
ffmpeg-audioac3=-acodec copy
ffmpeg-ext=.ts
ffmpeg-audiodelay=skip
FixedResolution=true
SkipCropping=true
AllowH264CopyRemuxing=true
The sample will be uploaded in roughly 2h from this being posted.

Thanks again for all your help.

file attachments

comments

rboy1 wrote Mar 27, 2013 at 5:16 AM

Try the latest BETA 03272013 with the option:

ForceStreamsRemuxing=true in the profile settings (along with the AllowH264CopyRemuxing=true)

rboy1 wrote Mar 27, 2013 at 5:18 AM

Sorry I mean ForceWTVStreamsRemuxing=true

Dodgexander wrote Mar 27, 2013 at 1:52 PM

I'm afraid it doesn't make a difference. I think this may be an ffmpeg fault. See ticket: 2398 on the ffmpeg tracker.

Dodgexander wrote Mar 27, 2013 at 1:56 PM

The ForceWTVStreamsRemuxing=true doesn't help with ticket 2220 either.

But oddly the fix for that is to add -ss 1 to the command of ffmpeg. Then the files that receive
av_interleaved_write_frame
Copy remux fine.

Trying to get them to see it as a fault but they won't respond to the ticket you made.

rboy1 wrote Mar 27, 2013 at 4:25 PM

ForceWTVStreamsRemuxing won't fix ffmpeg, it's an alternative to ffmpeg, the question is does that work for you? attach the conversion log

Dodgexander wrote Mar 27, 2013 at 5:07 PM

No it doesn't help.

ForceWTVStreamsRemuxing1.log shows what happens when fed the same sample related to this issue.

ForceWTVStreamsRemuxing2.log shows what happens when you feed a file that with ffmpeg copy, reverts to slow remuxing due to
av_interleaved_write_frame
So the new method doesn't help me in either case.

Dodgexander wrote Mar 27, 2013 at 5:08 PM

Added StreamsRemuxing2.log

rboy1 wrote Mar 27, 2013 at 7:01 PM

Looks like the file is locked by another process or in use:

Error : System.Runtime.InteropServices.COMException (0x80040204): At least one of the pins involved in the operation is already connected.

Dodgexander wrote Mar 27, 2013 at 7:47 PM

Okay, so I restarted my pc fresh and tried again. Both logs still contain: Error : System.Runtime.InteropServices.COMException (0x80040204): At least one of the pins involved in the operation is already connected.

Is it because ffmpeg is also connected? Because this was on a fresh boot with nothing running in the background.

Dodgexander wrote Apr 22, 2013 at 1:00 PM

So where are we with this? Given all the problems I have been having, is it worth just giving up? Thanks Ramit.

rboy1 wrote Apr 22, 2013 at 2:23 PM

I thought you said adding -ss 1 fixes the issue?

Dodgexander wrote Apr 22, 2013 at 5:22 PM

It does with the sample i provided, but not with the sample you provided. Apparently its to do with timestraps.

See latest comment on ffmpeg tracker

rboy1 wrote Jun 23, 2013 at 1:46 PM

Try the latest BETA version, also try using a handbrake based profile

rboy1 wrote Sep 21, 2013 at 11:32 PM

assuming this works now

rboy1 wrote Oct 1, 2013 at 2:19 AM

Check the latest BETA build 2.3.14 20130930 or later. This issue has been fixed.