[FEATURE] SCC and CCD encoder#1154
Conversation
|
The bitmap OCR hasn't been implemented either |
|
Dealing with different line endings hasn't been implemented yet either ("\n" vs "\r\n") |
|
Modifying subtitles hasn't been implemented yet. As mentioned in #1139 (comment) it's probably better if it was done in a different way |
|
I will need more examples to be able to continue with the rest |
|
For some reason the |
|
Because?
…On Mon, Dec 23, 2019, 07:02 Nils ANDRÉ-CHANG ***@***.***> wrote:
For some reason the .srt output doesn't work anymore
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1154?email_source=notifications&email_token=ABNMTWOWEC4D4OEEJGNX25TQ2CSFFA5CNFSM4J6LRJDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHQ7MMI#issuecomment-568456753>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNMTWPZ433H4VVPRE7X7ALQ2CSFFANCNFSM4J6LRJDA>
.
|
As I said "some reason". 🤣 I have no clue. I thought for some time it had to do with using enums instead of ints but that's not the problem. Also webvtt isn't affected so.... |
|
Okay, fixed it I didn't notice the |
thealphadollar
left a comment
There was a problem hiding this comment.
Amazing work @NilsIrl
|
CCExtractor CI platform finished running the test files on linux. Below is a summary of the test results:
It seems that not all tests were passed completely. This is an indication that the output of some files is not as expected (but might be according to you). Your PR breaks these cases:
Check the result page for more info. |
cfsmp3
left a comment
There was a problem hiding this comment.
This could be reasonably be merged. But it's missing an entry on the change log and, I assume, help screen.
|
Here is a list of post merge operations to perform:
|
|
Still fails: Just get rid of that dprintf() :-) |
Yeah I realised MSVC actually has a dprintf but it's a totally different function |
In general (not just for us) - submitting untested stuff decreases your street cred :-) It's OK we find bugs when we test corner cases, but a PR that doesn't even compile is not good... We want CCExtractor to be portable (as is it builds for anything that has a C compiler), so in general, any function that is an extension of a specific compiler (even if it is GCC) is best not to use. |
|
I changed the architecture to make it less "hacky". That is, this new architecture, is more linear and doesn't try to make sense of what is seemingly random. Codes are now hardcoded. This will make it easier to add features (color) without having to make it more complex. |
|
I'll also add that this last commit gives the exact same output as the previous one. (except that it doesn't produce trailing space anymore) |
|
CCExtractor CI platform finished running the test files on windows. Below is a summary of the test results:
It seems that not all tests were passed completely. This is an indication that the output of some files is not as expected (but might be according to you). Your PR breaks these cases:
Check the result page for more info. |
|
@NilsIrl can you resolve conflicts? (and let us know the current status) |
|
Another thing that isn't implemented is preamble codes that set the font and the placement on the screen at the same time. For the moment, it uses 2 codes for that (1 for the placement and 1 for the font). This isn't really problematic because it is rare the column is one that can be set using these preamble codes. |
Fix #1120
My familiarity with the project is as follows (check one):
Colours haven't been implemented yet.
The disassembly format hasn't been implemented yet.