[BUG] Error: Parameter -o1/o2 not understood. #421

Closed
opened 2026-01-29 16:43:35 +00:00 by claunia · 14 comments
Owner

Originally created by @unicode45 on GitHub (Apr 17, 2018).

Please prefix your issue with one of the following: [BUG], [PROPOSAL], [QUESTION].

CCExtractor version (using the --version parameter preferably) : 0,85b

In raising this issue, I confirm the following (please check boxes, eg [X] - and delete unchecked ones):

  • I have read and understood the contributors guide.
  • I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present.
  • I have checked that the issue I'm posting isn't already reported.
  • I have checked that the issue I'm porting isn't already solved and no duplicates exist in closed issues and in opened issues
  • I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.
  • I have used the latest available version of CCExtractor to verify this issue exists.

My familiarity with the project is as follows (check one, eg [X] - and delete unchecked ones):

  • I have never used CCExtractor.
  • I have used CCExtractor just a couple of times.
  • I absolutely love CCExtractor, but have not contributed previously.
  • I am an active contributor to CCExtractor.

Necessary information

  • Is this a regression (did it work before)? [x] NO | [ ] YES - please specify the last known working version
  • What platform did you use? [x] Windows - [x] Linux - [ ] Mac
  • What were the used arguments? -o1 filename1.ext -o2 filename2.ext

Additional information
Parameter -oN seems not working for a long time(I test on 0.7x to 0.85b but all failed).

Originally created by @unicode45 on GitHub (Apr 17, 2018). Please prefix your issue with one of the following: [BUG], [PROPOSAL], [QUESTION]. CCExtractor version (using the --version parameter preferably) : 0,85b **In raising this issue, I confirm the following (please check boxes, eg [X] - and delete unchecked ones):** - [x] I have read and understood the [contributors guide](https://github.com/CCExtractor/ccextractor/blob/master/.github/CONTRIBUTING.md). - [x] I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present. - [x] I have checked that the issue I'm posting isn't already reported. - [x] I have checked that the issue I'm porting isn't already solved and no duplicates exist in [closed issues](https://github.com/CCExtractor/ccextractor/issues?q=is%3Aissue+is%3Aclosed) and in [opened issues](https://github.com/CCExtractor/ccextractor/issues) - [x] I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion. - [x] I have used the latest available version of CCExtractor to verify this issue exists. **My familiarity with the project is as follows (check one, eg [X] - and delete unchecked ones):** - [ ] I have never used CCExtractor. - [ ] I have used CCExtractor just a couple of times. - [x] I absolutely love CCExtractor, but have not contributed previously. - [ ] I am an active contributor to CCExtractor. **Necessary information** - Is this a regression (did it work before)? [x] NO | [ ] YES - *please specify the last known working version* - What platform did you use? [x] Windows - [x] Linux - [ ] Mac - What were the used arguments? `-o1 filename1.ext -o2 filename2.ext` **Additional information** Parameter -oN seems not working for a long time(I test on 0.7x to 0.85b but all failed).
Author
Owner

@thealphadollar commented on GitHub (May 6, 2018):

@unicode45, can you please detail the issue a bit more? I'm unable to see what video file was used and what exactly were the passed commands.

That'll help us solve the issue faster :)

@thealphadollar commented on GitHub (May 6, 2018): @unicode45, can you please detail the issue a bit more? I'm unable to see what video file was used and what *exactly* were the passed commands. That'll help us solve the issue faster :)
Author
Owner

@thealphadollar commented on GitHub (May 6, 2018):

@unicode45 Getting a little deeper into the issue, we never had an option like that. I've removed the instance of it in the help, I apologize for the misleading :D

@thealphadollar commented on GitHub (May 6, 2018): @unicode45 Getting a little deeper into the issue, we never had an option like that. I've removed the instance of it in the help, I apologize for the misleading :D
Author
Owner

@unicode45 commented on GitHub (May 9, 2018):

Thanks for the explanation. : )

@unicode45 commented on GitHub (May 9, 2018): Thanks for the explanation. : )
Author
Owner

@cfsmp3 commented on GitHub (May 9, 2018):

Well, o1 and o2 were valid options. Don't remember what we replaced them
with though.

On Sun, May 6, 2018, 07:51 Shivam Kumar Jha notifications@github.com
wrote:

@unicode45 https://github.com/unicode45 Getting a little deeper into
the issue, we never had an option like that. I've removed the instance of
it in the help, I apologize for the misleading :D


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CCExtractor/ccextractor/issues/973#issuecomment-386884998,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFrJ2UHjpXRx79r3idhjED1vBmKABIE1ks5tvw3ZgaJpZM4TXkpI
.

@cfsmp3 commented on GitHub (May 9, 2018): Well, o1 and o2 were valid options. Don't remember what we replaced them with though. On Sun, May 6, 2018, 07:51 Shivam Kumar Jha <notifications@github.com> wrote: > @unicode45 <https://github.com/unicode45> Getting a little deeper into > the issue, we never had an option like that. I've removed the instance of > it in the help, I apologize for the misleading :D > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/CCExtractor/ccextractor/issues/973#issuecomment-386884998>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AFrJ2UHjpXRx79r3idhjED1vBmKABIE1ks5tvw3ZgaJpZM4TXkpI> > . >
Author
Owner

@thealphadollar commented on GitHub (May 11, 2018):

@unicode45 Can you please provide the file you were operating on?

@thealphadollar commented on GitHub (May 11, 2018): @unicode45 Can you please provide the file you were operating on?
Author
Owner

@unicode45 commented on GitHub (May 12, 2018):

Here's a sample Korean ts file that I used.
https://drive.google.com/file/d/0B8AjqtxcLQDxeW5qT0RGSzQzZm8/view

I tried -o1 and -o2 option becuase *.p1.svc01.srt always containts the right Korean subtitle contents while .srt is empty.

@unicode45 commented on GitHub (May 12, 2018): Here's a sample Korean ts file that I used. https://drive.google.com/file/d/0B8AjqtxcLQDxeW5qT0RGSzQzZm8/view I tried -o1 and -o2 option becuase *.p1.svc01.srt always containts the right Korean subtitle contents while .srt is empty.
Author
Owner

@thealphadollar commented on GitHub (May 12, 2018):

@unicode45 Are you sure this is the right file? I'm doubtful since ffprobe shows no subtitle stream and even vlc is not able to detect/play any CC.

screenshot from 2018-05-12 21-12-19

@thealphadollar commented on GitHub (May 12, 2018): @unicode45 Are you sure this is the right file? I'm doubtful since ffprobe shows no subtitle stream and even vlc is not able to detect/play any CC. ![screenshot from 2018-05-12 21-12-19](https://user-images.githubusercontent.com/32812320/39959036-6023c9f8-5629-11e8-8482-64691c191b31.png)
Author
Owner
@unicode45 commented on GitHub (May 12, 2018): Sorry. this might be a better sample. https://doc-00-2s-docs.googleusercontent.com/docs/securesc/dhkuk4q9mgunis2fm53qs8dpimqu3un0/49e70t76sald3e3on3027l7sotjdn2va/1526140800000/12314372573940017857/04182627330199378501/1dQGwjRP49mBU1FkrNrJEdIgkTrrQomNG?e=download I've checked with MediaInfo and EIA-708 stream found.
Author
Owner

@thealphadollar commented on GitHub (May 12, 2018):

@unicode45 Ahh, maybe a problem at my side but the link is not working.

@thealphadollar commented on GitHub (May 12, 2018): @unicode45 Ahh, maybe a problem at my side but the link is not working.
Author
Owner

@unicode45 commented on GitHub (May 12, 2018):

How about this one?
https://drive.google.com/file/d/1OTLS_8SaKco_ZHXATz3p6Z-2H_WB-8dc/view?usp=drivesdk

@unicode45 commented on GitHub (May 12, 2018): How about this one? https://drive.google.com/file/d/1OTLS_8SaKco_ZHXATz3p6Z-2H_WB-8dc/view?usp=drivesdk
Author
Owner

@thealphadollar commented on GitHub (May 12, 2018):

Hey @unicode45, please have a look at the issue that was created two years back regarding the same.

For eg.
To extract data from channel 2 of the stream, you can give a command like,

ccextractor [input_file] -2 -o [output_filename]

The -o [output_filename] can be omitted if you want to stick to default naming.

@thealphadollar commented on GitHub (May 12, 2018): Hey @unicode45, please have a look at the [issue](https://github.com/CCExtractor/ccextractor/issues/374#issuecomment-222220372) that was created two years back regarding the same. For eg. To extract data from channel 2 of the stream, you can give a command like, ```bash ccextractor [input_file] -2 -o [output_filename] ``` The `-o [output_filename]` can be omitted if you want to stick to default naming.
Author
Owner

@unicode45 commented on GitHub (May 13, 2018):

Thanks for the information.
As you mentioned, it was duplicated report.

@unicode45 commented on GitHub (May 13, 2018): Thanks for the information. As you mentioned, it was duplicated report.
Author
Owner

@FossPrime commented on GitHub (Jun 5, 2019):

These docs are really misleading... -2 seems to be broken badly with multi track MP4's.

https://www.ccextractor.org/doku.php?id=public:general:command_line_usage

 -o outputfilename: Use -o parameters to define output filename if you don't
                       like the default ones (same as infile plus _1 or _2 when
                       needed and file extension, e.g. .srt).
                           -o or -o1 -> Name of the first (maybe only) output
                                        file.
                           -o2       -> Name of the second output file, when
                                        it applies.
@FossPrime commented on GitHub (Jun 5, 2019): These docs are really misleading... `-2` seems to be broken badly with multi track MP4's. https://www.ccextractor.org/doku.php?id=public:general:command_line_usage ``` -o outputfilename: Use -o parameters to define output filename if you don't like the default ones (same as infile plus _1 or _2 when needed and file extension, e.g. .srt). -o or -o1 -> Name of the first (maybe only) output file. -o2 -> Name of the second output file, when it applies. ```
Author
Owner

@cfsmp3 commented on GitHub (Jun 5, 2019):

Yes. -o1 and -o2 were probably one of the first supported parameters and
they came from the 608-only days, where you could have 2 languages only.

If multilanguage doesn't work in .mp4 it's not really an issue with -o2
(which it's likely to just be implemented in 608).

On Tue, Jun 4, 2019 at 4:44 PM Ray Foss notifications@github.com wrote:

These docs are really misleading... -2 seems to be broken badly with
multi track MP4's.

-o outputfilename: Use -o parameters to define output filename if you don't
like the default ones (same as infile plus _1 or _2 when
needed and file extension, e.g. .srt).
-o or -o1 -> Name of the first (maybe only) output
file.
-o2 -> Name of the second output file, when
it applies.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/CCExtractor/ccextractor/issues/973?email_source=notifications&email_token=ABNMTWML2IK7MJFRVYZ6KATPY346JA5CNFSM4E26JJEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW6FZIQ#issuecomment-498883746,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNMTWKZSXS7BQIEYRAPYVLPY346JANCNFSM4E26JJEA
.

@cfsmp3 commented on GitHub (Jun 5, 2019): Yes. -o1 and -o2 were probably one of the first supported parameters and they came from the 608-only days, where you could have 2 languages only. If multilanguage doesn't work in .mp4 it's not really an issue with -o2 (which it's likely to just be implemented in 608). On Tue, Jun 4, 2019 at 4:44 PM Ray Foss <notifications@github.com> wrote: > These docs are really misleading... -2 seems to be broken badly with > multi track MP4's. > > -o outputfilename: Use -o parameters to define output filename if you don't > like the default ones (same as infile plus _1 or _2 when > needed and file extension, e.g. .srt). > -o or -o1 -> Name of the first (maybe only) output > file. > -o2 -> Name of the second output file, when > it applies. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/CCExtractor/ccextractor/issues/973?email_source=notifications&email_token=ABNMTWML2IK7MJFRVYZ6KATPY346JA5CNFSM4E26JJEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW6FZIQ#issuecomment-498883746>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABNMTWKZSXS7BQIEYRAPYVLPY346JANCNFSM4E26JJEA> > . >
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ccextractor#421