mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-02-13 13:35:37 +00:00
Anagrammed words #74
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aramacciotti on GitHub (Oct 12, 2015).
CC extracting from this MPEG2-TS source (https://onedrive.live.com/redir?resid=9AE76B6175D960D3!381261&authkey=!ANmlBJmNWnzFyos&ithint=video%2cts) I get some anagrams instead of the original source.
Which could be the cause?
Here what I get currently:
2
00:00:02,336 --> 00:00:04,545
It's too late for Dre.amamin
We're practillcathy ere.
that should be instead:
2
00:00:02,336 --> 00:00:04,545
It's too late for Dreamamin.
We're practically there.
@anshul1912 commented on GitHub (Oct 12, 2015):
Thanks for report, it look like bug in caption, that part should be ignored by decoder. I will have a look at the video soon
@canihavesomecoffee commented on GitHub (Oct 12, 2015):
We've had the same issues with other samples before (groups of letters swapped around), as far as I can remember.
@cfsmp3 commented on GitHub (Oct 12, 2015):
Yes, garbling that comes and goes is a constant... there's always some
sample that breaks things...
On Mon, Oct 12, 2015 at 6:02 PM, Willem notifications@github.com wrote:
@aramacciotti commented on GitHub (Oct 12, 2015):
Does it mean that it's clear for you how to fix?
@anshul1912 commented on GitHub (Oct 16, 2015):
No its not clear how to fix it, but I have confirmed with video that this bug
@aramacciotti commented on GitHub (Oct 19, 2015):
Do you think I can help in some way? I can debug the code, but I have not still identified where the closed caption source characters are got.
If you think so, you can address me to the specific code fragment and I'll try to debug it
@anshul1912 commented on GitHub (Oct 19, 2015):
Problem is not in closed caption decoder but its in avcfuntions or sequenceing.c file names are not exact in src but similar.
though I am working on it, but if you can find out solution that would be nice of you 😄
@anshul1912 commented on GitHub (Oct 21, 2015):
when slice_header function is called twice with same pts and single payload then data which was pivot while previous call is flushed and code which do sequencing does not work, since that data should not been written or decoded until data with lower sequence is decoded. hence it makes output as jumbled up
@aramacciotti if you want to try you can change in lib_ccx/avc_functions.c slice_header
Just now I am looking at reason in Specs that is this scenerio really allowed in video with same pts have multiple slice header.
I also have to confirm manually through hex editor that is that video really having multiple slice header with same pts or we have some problem in code which call this function twice.
Above solution is just a hack to understand and confirm problem, I would suggest to not take this solution as final solution until investigation is complete
@aramacciotti commented on GitHub (Oct 21, 2015):
I downloaded the 0.77 source version and in its avc_functions.c slice_header (I found it in the root folder of the VisualStudio project) the current code is different from the fragment you wrote here.
I find:
instead of:
and I'm not able to find has_ccdata_buffered and timing in ctx.
Have I to download a different version?
@anshul1912 commented on GitHub (Oct 21, 2015):
Please git clone the latest code
@aramacciotti commented on GitHub (Oct 21, 2015):
I don't see any significant improvement with that code change.
Just to be sure, this is my current fragment:
@anshul1912 commented on GitHub (Oct 21, 2015):
This was output with change in code
Do you have some different output then mine
@aramacciotti commented on GitHub (Oct 21, 2015):
Yes, I get this:
@anshul1912 commented on GitHub (Oct 21, 2015):
can you try with my clone https://github.com/anshul1912/ccextractor.git
It works perfectly at my machine(linux, openSuse, 64 bit)
@aramacciotti commented on GitHub (Oct 21, 2015):
It's working fine! I'll test also with other contents where the issue was not present to verify that no regressions were added.
Thanks!
@anshul1912 commented on GitHub (Oct 21, 2015):
There are some regression added you can have a look at https://github.com/CCExtractor/ccextractor/issues/240 to see what files previously working fine are not working after my changes, but it will be good if you test with your own file too