Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
15251073
Commit
15251073
authored
Sep 10, 2013
by
Michael Niedermayer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
ffmpeg: improve built in docs for passing commands
Signed-off-by:
Michael Niedermayer
<
michaelni@gmx.at
>
parent
f8f4e48b
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
2 deletions
+3
-2
ffmpeg.c
ffmpeg.c
+3
-2
No files found.
ffmpeg.c
View file @
15251073
...
...
@@ -2681,7 +2681,7 @@ static int check_keyboard_interaction(int64_t cur_time)
char
buf
[
4096
],
target
[
64
],
command
[
256
],
arg
[
256
]
=
{
0
};
double
time
;
int
k
,
n
=
0
;
fprintf
(
stderr
,
"
\n
Enter command: <target>
<time>
<command>[ <argument>]
\n
"
);
fprintf
(
stderr
,
"
\n
Enter command: <target>
|all <time>|-1
<command>[ <argument>]
\n
"
);
i
=
0
;
while
((
k
=
read_key
())
!=
'\n'
&&
k
!=
'\r'
&&
i
<
sizeof
(
buf
)
-
1
)
if
(
k
>
0
)
...
...
@@ -2734,7 +2734,8 @@ static int check_keyboard_interaction(int64_t cur_time)
"? show this help
\n
"
"+ increase verbosity
\n
"
"- decrease verbosity
\n
"
"c Send command to filtergraph
\n
"
"c Send command to first matching filter supporting it
\n
"
"C Send/Que command to all matching filters
\n
"
"D cycle through available debug modes
\n
"
"h dump packets/hex press to cycle through the 3 states
\n
"
"q quit
\n
"
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment