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
1c1b5a40
Commit
1c1b5a40
authored
Jun 09, 2006
by
Diego Biurrun
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
CVS --> Subversion
Originally committed as revision 5458 to
svn://svn.ffmpeg.org/ffmpeg/trunk
parent
dc4ed3b1
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
14 additions
and
22 deletions
+14
-22
faq.texi
doc/faq.texi
+4
-4
ffmpeg-doc.texi
doc/ffmpeg-doc.texi
+6
-14
ffmpeg_powerpc_performance_evaluation_howto.txt
doc/ffmpeg_powerpc_performance_evaluation_howto.txt
+2
-2
optimization.txt
doc/optimization.txt
+2
-2
No files found.
doc/faq.texi
View file @
1c1b5a40
...
...
@@ -103,9 +103,9 @@ and pass 'combfilter=2'.
@section I have a problem with an old version of ffmpeg; where should I report it?
Nowhere. Upgrade to the latest release or if there is no recent release upgrade
to
CVS
. You could also try to report it. Maybe you will get lucky and
to
Subversion HEAD
. You could also try to report it. Maybe you will get lucky and
become the first person in history to get an answer different from "upgrade
to
CVS
".
to
Subversion HEAD
".
@section -f jpeg doesn't work.
...
...
@@ -253,7 +253,7 @@ the silver bullet that solves this problem, feel free to shoot it at us.
@section I have a file in memory / a API different from *open/*read/ libc how do i use it with libavformat ?
You have to implement a URLProtocol, see libavformat/file.c in FFmpeg
CVS
and libmpdemux/demux
_
lavf.c in MPlayer
CVS
.
You have to implement a URLProtocol, see libavformat/file.c in FFmpeg
and libmpdemux/demux
_
lavf.c in MPlayer
sources
.
@bye
doc/ffmpeg-doc.texi
View file @
1c1b5a40
...
...
@@ -1170,7 +1170,7 @@ Indent size is 4.
The presentation is the one specified by 'indent -i4 -kr -nut'.
The TAB character is forbidden outside of Makefiles as is any
form of trailing whitespace. Commits containing either will be
rejected by the
CVS
repository.
rejected by the
Subversion
repository.
Main priority in FFmpeg is simplicity and small code size (=less
bugs).
...
...
@@ -1213,8 +1213,8 @@ int myfunc(int my_parameter)
fprintf and printf are forbidden in libavformat and libavcodec,
please use av
_
log() instead.
@node
CVS
Policy
@section
CVS
Policy
@node
Development
Policy
@section
Development
Policy
@enumerate
@item
...
...
@@ -1265,7 +1265,7 @@ please use av_log() instead.
particular bug. Comments such as "fixed!" or "Changed it." are unacceptable.
@item
If you apply a patch by someone else, include the name and email address in
the
CVS
log message. Since the ffmpeg-cvslog mailing list is publicly
the log message. Since the ffmpeg-cvslog mailing list is publicly
archived you should add some SPAM protection to the email address. Send an
answer to ffmpeg-devel (or wherever you got the patch from) saying that
you applied the patch.
...
...
@@ -1273,7 +1273,7 @@ please use av_log() instead.
Do NOT commit to code actively maintained by others without permission. Send
a patch to ffmpeg-devel instead.
@item
Subscribe to the ffmpeg-cvslog mailing list. The diffs of all
CVS
commits
Subscribe to the ffmpeg-cvslog mailing list. The diffs of all commits
are sent there and reviewed by all the other developers. Bugs and possible
improvements or general questions regarding commits are discussed there. We
expect you to react if problems with your code are uncovered.
...
...
@@ -1281,14 +1281,6 @@ please use av_log() instead.
Update the documentation if you change behavior or add features. If you are
unsure how best to do this, send a patch to ffmpeg-devel, the documentation
maintainer(s) will review and commit your stuff.
@item
Revert a commit ONLY in case of a big blunder like committing something not
intended to be committed or committing a wrong file, the wrong version of a
patch, CVS policy violation or broken code and you are going to recommit the
right thing immediately.
Never revert changes made a long time ago or buggy code. Fix it in the
normal way instead.
@item
Never write to unallocated memory, never write over the end of arrays,
always check values read from some untrusted source before using them
...
...
@@ -1347,7 +1339,7 @@ explanation why, but sometimes we are quite busy so it can take a week or two.
@section Regression tests
Before submitting a patch (or committing to
CVS
), you should at least
Before submitting a patch (or committing to
the repository
), you should at least
test that you did not break anything.
The regression tests build a synthetic video stream and a synthetic
...
...
doc/ffmpeg_powerpc_performance_evaluation_howto.txt
View file @
1c1b5a40
...
...
@@ -43,10 +43,10 @@ This needs to be done by hand. First, you need to configure FFmpeg as
usual, but add the "--powerpc-perf-enable" option. For instance:
#####
./configure --prefix=/usr/local/ffmpeg-
cvs
--cc=gcc-3.3 --tune=7450 --powerpc-perf-enable
./configure --prefix=/usr/local/ffmpeg-
svn
--cc=gcc-3.3 --tune=7450 --powerpc-perf-enable
#####
This will configure FFmpeg to install inside /usr/local/ffmpeg-
cvs
,
This will configure FFmpeg to install inside /usr/local/ffmpeg-
svn
,
compiling with gcc-3.3 (you should try to use this one or a newer
gcc), and tuning for the PowerPC 7450 (i.e. the newer G4; as a rule of
thumb, those at 550Mhz and more). It will also enable the PMC.
...
...
doc/optimization.txt
View file @
1c1b5a40
...
...
@@ -13,8 +13,8 @@ Understanding these overoptimized functions:
As many functions tend to be a bit difficult to understand because
of optimizations, it can be hard to optimize them further, or write
architecture-specific versions. It is recommened to look at older
CVS versions of the interesting files (just use ViewCVS
at
http://
www1.mplayerhq.hu/cgi-bin/cvsweb.cgi/ffmpeg/?cvsroot=FFMpeg
).
revisions of the interesting files (for a web frontend try ViewVC
at
http://
svn.mplayerhq.hu/ffmpeg/trunk/
).
Alternatively, look into the other architecture-specific versions in
the i386/, ppc/, alpha/ subdirectories. Even if you don't exactly
comprehend the instructions, it could help understanding the functions
...
...
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