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
e3c4740f
Commit
e3c4740f
authored
Mar 21, 2008
by
Baptiste Coudurier
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
indentation
Originally committed as revision 12528 to
svn://svn.ffmpeg.org/ffmpeg/trunk
parent
9f6152df
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
mov.c
libavformat/mov.c
+4
-4
No files found.
libavformat/mov.c
View file @
e3c4740f
...
...
@@ -132,10 +132,10 @@ typedef struct MOVContext {
/* those functions parse an atom */
/* return code:
1: found what I wanted, exit
0: continue to parse next atom
1: found what I wanted, exit
0: continue to parse next atom
-1: error occured, exit
*/
*/
/* links atom IDs to parse functions */
typedef
struct
MOVParseTableEntry
{
uint32_t
type
;
...
...
@@ -1565,7 +1565,7 @@ static int mov_read_header(AVFormatContext *s, AVFormatParameters *ap)
err
=
mov_read_default
(
mov
,
pb
,
atom
);
if
(
err
<
0
||
(
!
mov
->
found_moov
&&
!
mov
->
found_mdat
))
{
av_log
(
s
,
AV_LOG_ERROR
,
"mov: header not found !!! (err:%d, moov:%d, mdat:%d) pos:%"
PRId64
"
\n
"
,
err
,
mov
->
found_moov
,
mov
->
found_mdat
,
url_ftell
(
pb
));
err
,
mov
->
found_moov
,
mov
->
found_mdat
,
url_ftell
(
pb
));
return
-
1
;
}
dprintf
(
mov
->
fc
,
"on_parse_exit_offset=%d
\n
"
,
(
int
)
url_ftell
(
pb
));
...
...
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