Skip to content

Commit

Permalink
Checkin noad-0.6.0
Browse files Browse the repository at this point in the history
  • Loading branch information
madmartin committed Aug 7, 2017
0 parents commit 68e0659
Show file tree
Hide file tree
Showing 62 changed files with 25,586 additions and 0 deletions.
2 changes: 2 additions & 0 deletions AUTHORS
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
noad is made by 'theNoad' (real-name not given)
you con reach the author via email: [email protected]
340 changes: 340 additions & 0 deletions COPYING

Large diffs are not rendered by default.

80 changes: 80 additions & 0 deletions ChangeLog
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
Version 0.6.0
- add audio-silence-detection
- add check for ac3-scan
- fixed a bug in online-scan (wrong marks if there is a short part with ac3-sound
at the start of the recording)

Version 0.5.3
- change the way to find the mpeg2-headers in configure
look for pkg-config
else try /usr/include
else try /usr/local/include
- fixed a bug in restart scan after searching for a new logo in online mode
- changed umask for create mark-files

Version 0.5.2
- little speedup in blackline-detection
- change configure to avoid automatic compiling of toolies
- add overlap-detection in online-mode

Version 0.5.1
- fixed a bug in scanRecord (online-mode only)
- add logging-function for backtrace in case of errors

Version 0.5.0
- some code-cleanups
- add Parameter --markfile to set a different markfile-name
- do logo redetection if no logo found after 12 minutes (Sea of Love, Kabel 1, 6.6.04)
- fixed a bug in cSVDRPC::ReadCompleteReply()
- fixed a bug in checkBlackFrameOnMark (Nuhr vom Feinsten, ProSieben, 28.06.04)
- improvement of ac3-detection
- introducing online-mode
- fixed a bug in scanRecord (04.11.04)

Version 0.4.2:
- default nice-level changed to 19
- fixed a bug in checkBlackFrameOnMark
- fixed a bug in checkMarkPair
- ignore last line in detectBlackLines (bottom)
- fixed a bug in ac3 detection
- added some helper-scripts from Andreas Lenz (noad_scripts.zip, see README inside zip-file)


Version 0.4.1:
- Fehlerbereinigung configure.ac
- start als Hintergrundprozess verbessert
- pid-file zur Vermeidung von Doppelaufrufen eingef�hrt
- Schrittweite f�r ac3-scan verringert
- setzen von fehlerhaften Marken in checkBlacklineOnmark bereinigt
- einige Script-Verbesserungen nach einem patch von Thomas G�nther
- Zusammenfassung der Versionen 0.3.2b und 0.4.0
- add switch "nelonen" based on a patch from Esa Loukkola
- add english readme

Version 0.4.0:
- overlap-detection
- ac3 detection
- scripte allnewnoad/noadifnew pr�fen jetzt auf vorhandene marks.vdr
- stat2html �berarbeitet
- OSD-Message
- priority �nderbar

Version 0.3.4:
- Verwendung von Automake/Autoconf ==> configure
- Erkennung von vertikal verschobenen Logos
- Priority-Level einstellbar per Parameter
- Statistik-Format erweitert

Version 0.3.3:
- Kommentare zu den Marken in der marks.vdr
- Erkennung von Wiederholungen vor/nach der Werbung
- OSD-Nachrichten f�r Start und Ende von noad
- Logo-Speicherung defaultm�ssig abgeschaltet
- Versions-Nummer abrufbar

Version 0.3.1:
- �nderungen f�r libmpeg 0.3.2 pre-Release
- Bereinigung div. Compiler-Warnings
- Ausgabe div. Statistikwerte
- script zum bearbeiteten aller noch nicht bearbeiteten Aufnahmen (allnewnoad)
- script zum l�schen aller gespeicherten logos (clearlogos)
167 changes: 167 additions & 0 deletions INSTALL
Original file line number Diff line number Diff line change
@@ -0,0 +1,167 @@
Basic Installation
==================

These are generic installation instructions.

The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

The file `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.

Running `configure' takes a while. While running, it prints some
messages telling which features it is checking for.

2. Type `make' to compile the package.

3. Type `make install' to install the programs and any data files and
documentation.

4. You can remove the program binaries and object files from the
source code directory by typing `make clean'.

Compilers and Options
=====================

Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures
====================================

You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
CPU-COMPANY-SYSTEM

See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.

If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults
================

If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Operation Controls
==================

`configure' recognizes the following options to control how it
operates.

`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.

`--help'
Print a summary of the options to `configure', and exit.

`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made.

`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.

`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.

`configure' also accepts some other, not widely useful, options.

25 changes: 25 additions & 0 deletions Makefile.am
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
#SUBDIRS = libvo

noinst_LIBRARIES=libnoad.a
libnoad_a_SOURCES=tools.cpp vdr_cl.cpp svdrpc.cpp tools.h vdr_cl.h svdrpc.h mpeg2wrap.cpp mpeg2wrap.h

bin_PROGRAMS=noad
noad_SOURCES=cchecklogo.cpp ccontrol.cpp cgetlogo.cpp ctoolbox.cpp noad.cpp tnoad.cpp noaddata.cpp\
audiotools.cpp main.cpp \
audiotools.h cchecklogo.h ccontrol.h cgetlogo.h ctoolbox.h noad.h tnoad.h noaddata.h videodir.h

noad_LDADD=libnoad.a

noinst_PROGRAMS=@PICSRC@ @TOOLSRC@
EXTRA_PROGRAMS=markpics showindex

markpics_SOURCES=markpics.cpp
markpics_LDADD=libnoad.a
markpics_LDFLAGS=-lMagick++

showindex_SOURCES=showindex.cpp
showindex_LDADD=libnoad.a

bin_SCRIPTS=allnewnoad allnoad allnoadnice allnoaduncut clearlogos noadifnew stat2html statupd noadcall.sh

EXTRA_DIST=$(bin_SCRIPTS) README.en mystat.HTML noad_scripts.zip
Loading

0 comments on commit 68e0659

Please sign in to comment.