View Full Version : 3.0 progress
bond
11th June 2004, 09:41
Originally posted by Bidoche
1. There are no limitation to avisynth being ported on linux.
In the 3.0 core there is only one 2 line Windows dependancy in a small .cpp, nothing an #ifdef couldn't handle.hm, so if avisynth 3.0 is not relying anymore on vfw, will it also be able to handle variable framerate content?
Sigmatador
18th June 2004, 00:47
avi is cfr, so an "avi synth" is ^^
mkaluza
14th October 2004, 08:22
Hi. I wanted to ask if I could join the avisynth team. Can you tell me who should I talk to and where to find them? (I've seen a name of IRC channel once but now I can't find it)
I miss avisynth very much since I moved to linux and therefore I'd like to help porting it.
thanks for any hints
Kurosu
14th October 2004, 09:00
Originally posted by bond
hm, so if avisynth 3.0 is not relying anymore on vfw, will it also be able to handle variable framerate content?
There have talks on how it could be handled. The best that could be done was to add a duration to a frame. The resulting script would probably be unseekable though (and building an index prior to exporting through some interface like DirectShow). And it would also require that, for instance, a DirectShow interface is added to AviSynth.
All in all, maybe later.
Kurosu
14th October 2004, 09:07
Originally posted by mkaluza
Hi. I wanted to ask if I could join the avisynth team. Can you tell me who should I talk to and where to find them? (I've seen a name of IRC channel once but now I can't find it)
I'm not speaking for the "avisynth team", but anyone is welcome to contribute. You can meet the developpers on channel #avisynth on IRC network irc.freenode.net (check their webpage if you'd like to find a server close to you). ]Hop[ (aka Bidoche) is the core developper. There are 2 people working on the linux side of things, focusing on build process, freetype support and ffmpeg output/input support.
Some info in the 3.0 branch:
- requires g++ 3.x (tested with 3.3 branch); 2.95.x is known to fail
- use boost and stl libraries (have to be compiled by hand)
- is a lot more C++ than 2.5 branch
There's also a mailing list accessible as a newsgroup through gmame, but nothing new has made it to that list.
Wilbert
14th October 2004, 21:09
@mkaluza,
Just search for 'bidoche' on this forum, and send him a pm. I'm sure you can join!
Bidoche
24th October 2004, 14:30
Of course you can.
At a time, I was almost beggin for help, it's not to refuse it now.
d'Oursse
19th May 2005, 22:07
some news
* news will be posted here (http://avisynth3.unite-video.com/) (thanks to Unite Vidéo (http://unite-video.com/phpbb/portal.php) for hosting it)
* Avisynth 3.0 site (http://www.avisynth.org/AviSynth30) on avisynth.org with a small FAQ
* Installation in french here (http://unite-video.com/phpbb/viewtopic.php?t=6876)
* gstreamer plugin in progress
morsa
23rd May 2005, 06:49
So this means that finally higher than 8 bit per color channel will be possible?
Bidoche
27th May 2005, 22:44
Originally posted by morsa
So this means that finally higher than 8 bit per color channel will be possible? Yes, currently I made 2 such colorspaces builtin, but with plugins able to add colorspaces, I will probably let it for them.
sl1pkn07
1st June 2005, 18:53
[sl1pkn07@Spinflo linux]$ ./configure --with-stl-path=/usr --with-boost-path=/usr --with-ffmpeg-path=/usr --with-freetype-config=/usr/bin/freetype-config
checking build system type... i686-redhat-linux-gnu
checking host system type... i686-redhat-linux-gnu
checking target system type... i686-redhat-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to use default CXXFLAGS... yes
checking for style of include used by make... GNU
checking for g++... g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... none
checking how to run the C++ preprocessor... g++ -E
checking whether g++ supports -fvisibility=hidden... checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for whether to use assembly code... yes
checking for architecture type... ia32
checking for build extensions... .so .a .o
checking for platform specific LDFLAGS/CFLAGS... ok
checking for nasm... yes
checking for nasm patch version... 38
checking for nasm object format... elf
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking assert.h usability... yes
checking assert.h presence... yes
checking for assert.h... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking for clock_gettime in -lrt... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen in -ldl... yes
checking for dlclose in -ldl... yes
checking for dlsym in -ldl... yes
checking stl_user_config.h usability... yes
checking stl_user_config.h presence... no
configure: WARNING: stl_user_config.h: accepted by the compiler, rejected by the preprocessor!
configure: WARNING: stl_user_config.h: proceeding with the compiler's result
checking for stl_user_config.h... yes
checking for main in -lstlport_gcc... yes
checking boost/config.hpp usability... yes
checking boost/config.hpp presence... yes
checking for boost/config.hpp... yes
checking for main in -lboost_thread-gcc-mt-s-1_32... yes
checking ffmpeg/avcodec.h usability... yes
checking ffmpeg/avcodec.h presence... yes
checking for ffmpeg/avcodec.h... yes
checking for main in -lavcodec... yes
[b]checking for main in -lavformat... no[b]
configure: error: FFMPEG library not in /usr/lib
[sl1pkn07@Spinflo linux]$ locate stl_user_config.h
/usr/include/stlport/stl_user_config.h
[sl1pkn07@Spinflo linux]$ rpm -q -l ffmpeg
/usr/bin/ffmpeg
/usr/bin/ffplay
/usr/bin/ffserver
/usr/lib/libavcodec-0.4.9-pre1.so
/usr/lib/libavcodec.so
/usr/lib/libavformat-0.4.9-pre1.so
/usr/lib/libavformat.so
/usr/lib/vhook
/usr/lib/vhook/drawtext.so
/usr/lib/vhook/fish.so
/usr/lib/vhook/imlib2.so
/usr/lib/vhook/null.so
/usr/lib/vhook/ppm.so
/usr/share/doc/ffmpeg-0.4.9
/usr/share/doc/ffmpeg-0.4.9/COPYING
/usr/share/doc/ffmpeg-0.4.9/CREDITS
/usr/share/doc/ffmpeg-0.4.9/Changelog
/usr/share/doc/ffmpeg-0.4.9/README
/usr/share/man/man1/ffmpeg.1.gz
/usr/share/man/man1/ffplay.1.gz
/usr/share/man/man1/ffserver.1.gz
[sl1pkn07@Spinflo linux]$
please help
d'Oursse
1st June 2005, 19:08
The warning of STLPort is not important. autoconf is a piece of crap
for ffmpeg, well, look in /usr/lib if you have the file libavformat.a
if not, then ffmpeg is not installed properly.
sl1pkn07
1st June 2005, 20:22
[sl1pkn07@Spinflo ~]$ rpm -q -l ffmpeg-devel
/usr/include/ffmpeg
/usr/include/ffmpeg/avcodec.h
/usr/include/ffmpeg/avformat.h
/usr/include/ffmpeg/avio.h
/usr/include/ffmpeg/common.h
/usr/include/ffmpeg/rational.h
/usr/include/ffmpeg/rtp.h
/usr/include/ffmpeg/rtsp.h
/usr/include/ffmpeg/rtspcodes.h
/usr/lib/libavcodec.a
/usr/lib/libavformat.a
/usr/share/doc/ffmpeg-devel-0.4.9
/usr/share/doc/ffmpeg-devel-0.4.9/TODO
/usr/share/doc/ffmpeg-devel-0.4.9/faq.html
/usr/share/doc/ffmpeg-devel-0.4.9/faq.texi
/usr/share/doc/ffmpeg-devel-0.4.9/ffmpeg-doc.html
/usr/share/doc/ffmpeg-devel-0.4.9/ffmpeg-doc.texi
/usr/share/doc/ffmpeg-devel-0.4.9/ffmpeg.1
/usr/share/doc/ffmpeg-devel-0.4.9/ffmpeg_powerpc_performance_evaluation_howto.txt
/usr/share/doc/ffmpeg-devel-0.4.9/ffplay-doc.html
/usr/share/doc/ffmpeg-devel-0.4.9/ffplay-doc.texi
/usr/share/doc/ffmpeg-devel-0.4.9/ffplay.1
/usr/share/doc/ffmpeg-devel-0.4.9/ffserver-doc.html
/usr/share/doc/ffmpeg-devel-0.4.9/ffserver-doc.texi
/usr/share/doc/ffmpeg-devel-0.4.9/ffserver.1
/usr/share/doc/ffmpeg-devel-0.4.9/ffserver.conf
/usr/share/doc/ffmpeg-devel-0.4.9/hooks.html
/usr/share/doc/ffmpeg-devel-0.4.9/hooks.texi
/usr/share/doc/ffmpeg-devel-0.4.9/optimization.txt
/usr/share/doc/ffmpeg-devel-0.4.9/texi2pod.pl
[sl1pkn07@Spinflo ~]$
--------
d'Oursse
1st June 2005, 21:43
what should I answer to this ?
sl1pkn07
2nd June 2005, 00:26
(sorry my bad english)
i need help to compile Avisynth3.0 in linux
that problem I have so that me of that error, if I have all the necessary one?
d'Oursse
2nd June 2005, 06:51
well, it should be good. Rerun configure
Mug Funky
2nd June 2005, 09:25
Yes, currently I made 2 such colorspaces builtin, but with plugins able to add colorspaces, I will probably let it for them.
i'll write you into my will if you at least add support for 10-bit 4:2:2. i can give you samples if you want... so far SDI/decklink stuff has been mac only, but it'd be good to be able to do IVTC->25fps conversions from NTSC film masters.
then all we'd need is a huge amount of gig on a linux/win box to handle a feature length uncompressed PAL moofie.
Bidoche
5th June 2005, 14:07
And if I only make it possible for plugins to do so, do I get into your will as well ?
sl1pkn07
5th June 2005, 14:37
I surrender, does not compile. to see if it works with the new versions
d'Oursse
5th June 2005, 15:03
I surrender, does not compile. to see if it works with the new versions
same error on libavformat ? (please, don't paste all the configure output)
sl1pkn07
5th June 2005, 15:13
yes. libaformat is installed, but it Configure does not recognize it
(sorry my bad English)
d'Oursse
5th June 2005, 18:09
update your autoconf and automake
verify that libavformat.a exists in /usr/lib (not with rpm but with ls)
it works for me. But i've installed ffmpeg from the source package.
you have installed ffmpeg from rpm, so i can't help you much.
patxitron
6th June 2005, 20:36
Hello
First sorry about my crapy English.
I'm trying to compile avisynth (one hour ago updated CVS) into my new gentoo 2005.0.
In my system, ffmpeg-0.4.9_p20050226-r5, gstreamer-0.8.10, freetype-2.1.9 and nasm-0.98.39-r1 are already installed.
I installed STLport-4.6.2-r2 and boost-1.32.0-r4 using portage (the native gentoo package manager).
My first trouble was when I tryed to run the configure script (the avisynth one) those are the resulting last lines:
checking for dlsym in -ldl... yes
checking stl_user_config.h usability... yes
checking stl_user_config.h presence... no
configure: WARNING: stl_user_config.h: accepted by the compiler, rejected by the preprocessor!
configure: WARNING: stl_user_config.h: proceeding with the compiler's result
checking for stl_user_config.h... yes
checking for main in -lstlport_gcc... yes
checking boost/config.hpp usability... yes
checking boost/config.hpp presence... yes
checking for boost/config.hpp... yes
checking for main in -lboost_thread-gcc-mt-s-1_32... no
configure: WARNING: Boost library not in /usr/lib
configure: error: "Boost is needed !"
A simple "ls /usr/lib/libboost*" and I saw that this library is named "libboost_thread-mt.so.1.32.0" in my gentoo. I made a symbolic link to "libboost_thread-gcc-mt-s-1_32.so" and then I re-ran configure without trouble.
Next I typed "make" and this is the result:
patxi@zeus linux $ make
D: bin
C: core/blitter/blitter.cpp
C: core/blitter/memcopy.cpp
C: core/block/block.cpp
C: core/block/recycler.cpp
C: core/bufferwindow/blender.cpp
C: core/bufferwindow/copier.cpp
C: core/bufferwindow/leftturner.cpp
../../src/core/bufferwindow/leftturner.cpp: In member function `avs::BufferWindow avs::bw::LeftTurner<1>::operator()(const avs::BufferWindow&) const':
../../src/core/bufferwindow/leftturner.cpp:34: error: `template' (as a disambiguator) is only allowed within templates
make: *** [core/bufferwindow/leftturner.o] Error 1
I know that I don't followed strictly the instructions but it seems to me that this is not the problem. Maybe it is the gcc version (3.4.3)?
It's so nice that avisynth finally will run on linux! Thanks to all!
d'Oursse
6th June 2005, 20:39
i bet that you use gcc 3.4.*
patxitron
6th June 2005, 20:55
Yes, I'm using gcc-3.4.3
d'Oursse
6th June 2005, 22:12
gcc 3.4.* have problems with its parser, in particular for some special template use. And you know what ? :D
So, use instead gcc 3.3.* or gcc 4.0. I used once gcc 4.0 some months and avs 3 compiled fine with it. But i don't know for recent versions.
edit: and about the problems of boost, i would like to say something: using the packages could lead to such problems, as the package maintainer install the software where *he* wants to, and not where it should be, with the names *he* wants.
Avs3 compiles fine with gcc 3.3, and all the library installed as it's mentioned in the documentation.
If you have problems with the compilation, then it's mostly the package fault. And in that case, I can't help much, as each case could be different
patxitron
6th June 2005, 22:28
Well, I made some googling and I patched some files in order to get compiled by gcc-3.4 (and updated boost's circular-buffer to latest CVS version), now compile fails at functions/audio.cpp:
C: functions/audio.cpp
In file included from ../../src/functions/../parser/adaptor/caller.h:29,
from ../../src/functions/../parser/adapt.h:29,
from ../../src/functions/audio.cpp:26:
../../src/functions/../parser/adaptor/extractor.h: In member function `avs::PColorSpace avs::parser::adaptor::extractor<const avs::PColorSpace&>::operator()(avs::parser::VMState&, int) const':
../../src/functions/../parser/adaptor/extractor.h:129: error: `FromString' is not a member of `avs::ColorSpace'
../../src/functions/../parser/adapt.h:50: confused by earlier errors, bailing out
make: *** [functions/audio.o] Error 1
I made a seach over the whole source tree and 'ColorSpace::FromString' is called in 'filters/source/video/icmframedecompressor.cpp', 'filters/source/ffmpegsource.cpp' and 'parser/adaptor/extractor.h' but not defined anywhere. It is mentioned in a coment in core/colorspace/concrete/map.h:
// map used by the ColorSpace::FromString method to get ColorSpaces from names
best regards
d'Oursse
6th June 2005, 23:17
Well, I made some googling and I patched some files in order to get compiled by gcc-3.4 (and updated boost's circular-buffer to latest CVS version),
i fear that it will not compile with gcc 3.3 nor with 4.0. We know what to do to make compile it with gcc 3.4, but it's not a standard way. What we use is the standard way.
Nevertheless, feel free to mp your patch to Bidoche. Or better, go on IRC (#avisynth on freenode). We are often there and it's better to discus patch there rather than here.
now compile fails at functions/audio.cpp:
C: functions/audio.cpp
In file included from ../../src/functions/../parser/adaptor/caller.h:29,
from ../../src/functions/../parser/adapt.h:29,
from ../../src/functions/audio.cpp:26:
../../src/functions/../parser/adaptor/extractor.h: In member function `avs::PColorSpace avs::parser::adaptor::extractor<const avs::PColorSpace&>::operator()(avs::parser::VMState&, int) const':
../../src/functions/../parser/adaptor/extractor.h:129: error: `FromString' is not a member of `avs::ColorSpace'
../../src/functions/../parser/adapt.h:50: confused by earlier errors, bailing out
make: *** [functions/audio.o] Error 1
I made a seach over the whole source tree and 'ColorSpace::FromString' is called in 'filters/source/video/icmframedecompressor.cpp', 'filters/source/ffmpegsource.cpp' and 'parser/adaptor/extractor.h' but not defined anywhere. It is mentioned in a coment in core/colorspace/concrete/map.h:
// map used by the ColorSpace::FromString method to get ColorSpaces from names
best regards
there have been some modifications in the code. I don't recall exactly. It has been a while since i've updated cvs, as i'm mainly focused on the gstreamer source.
Again, feel free to go on IRC. My nick is caro. Bidoche's one is ]Hop[.
Thank you for your help.
d'Oursse
7th June 2005, 00:28
Ho, and i forget to say: cvs is not currently compiling. We know that, but avs 3 is in development ;)
Please don't report problems of compilation here. Not yet.
patxitron
7th June 2005, 13:48
I never tryed IRC before and my English skill is too bad for this sort of medium. Moreover, I'm not a developer yet (I just begun my first course of computer science engineering) I'm just anxious to try avisynth under linux ;). I'm sorry if I asked some questions in inapropiate time and/or place.
Anyway, I hope that I can test an alpha or pre-alpha version soon ;)
Thank you very much
Wilbert
7th June 2005, 13:53
I never tryed IRC before and my English skill is too bad for this sort of medium.
So, now you have an excuse to try irc. It's not that hard :)
Bidoche
7th June 2005, 20:11
Do not worry about your english, IRC is full of guys with bad english.
Anyway, the fix you need is to change 'FromString' to 'FromName' in extractor.h
@d'Oursse
Weren't you supposed to commit that change ?
patxitron
7th June 2005, 20:56
Thanks to all. You are so nice people...
Now the compilation of audio.cpp triggers a gcc bug (or something that looks like a bug) time to upgrade or downgrade my gcc version. But before this I must analyze the implications for my recently builded (from stage 1) gentoo.
Best regards
d'Oursse
22nd July 2005, 09:14
I have finally a gstreamersource on my hd which is working not too badly. The problem is now gstreamer, which is not as good as I expected. It should work well with avi. But there are problems with ogm and mkv.
The code in cvs does not contains yet the code. It needs tweaking. But, heh, it works a bit :)
Also, one modification: avisynth 3.0 only supports gcc 4.0, no more anterior versions of this compiler. The reason is to use the visibility feature (shared lib less huge and faster load in memory)
d'Oursse
27th July 2005, 17:47
you can see here some shots of a very simple test program that will be included later in cvs to test avs3 on linux
http://unite-video.com/phpbb/viewtopic.php?p=72452#72452
d'Oursse
5th October 2005, 23:28
some news
the current cvs tree will be compilable on linux this weekend. There are just 3 small modifications to do, but i wait for some approval from Bidoche.
If the linux users want to test it, download this file :
http://www.iecn.u-nancy.fr/~torri/files/web_avs3/avisynth3_20051005.tar.bz2
there's the libraries needed for the test application.
Put all the lib* files in /usr/lib or /usr/local/lib or somewhere else (but add that path to LD_LIBRARY_PATH)
put avisynth_test somewhere (preferably in a path contained in PATH)
the test application can load a file, preferably an avi one. Then gstreamersource is used to load the file. Then it displays the frame #100. You can change the # of the frame with Action->Goto
You must have gstreamer and gst-plugins installed. And the best is also having gst-ffmpeg installed.
unfortunately, the parser has some problem, so we can't use avs script right now. I hope that this will be fixed soon
708145
7th October 2005, 16:44
some news
the current cvs tree will be compilable on linux this weekend. There are just 3 small modifications to do, but i wait for some approval from Bidoche.
If the linux users want to test it, download this file :
http://www.iecn.u-nancy.fr/~torri/files/web_avs3/avisynth3_20051005.tar.bz2
there's the libraries needed for the test application.
Put all the lib* files in /usr/lib or /usr/local/lib or somewhere else (but add that path to LD_LIBRARY_PATH)
put avisynth_test somewhere (preferably in a path contained in PATH)
the test application can load a file, preferably an avi one. Then gstreamersource is used to load the file. Then it displays the frame #100. You can change the # of the frame with Action->Goto
You must have gstreamer and gst-plugins installed. And the best is also having gst-ffmpeg installed.
unfortunately, the parser has some problem, so we can't use avs script right now. I hope that this will be fixed soon
Nice to see progress :D
Just found some time to test:
So I set the path to
bergmats@rai35:~/src/avisynth3_20051005$ echo $LD_LIBRARY_PATH
/home/bergmats/src/avisynth3_20051005/
but it still can't find the lib:
bergmats@rai35:~/src/avisynth3_20051005$ ./avisynth_test /tobias/tobias/Madagascar.avi
./avisynth_test: error while loading shared libraries: libavisynth.so.3: cannot open shared object file: No such file or directory
I also installed gstreamer0.8-ffmpeg and libgstreamer-plugins0.8-0. Anything missing there maybe?
bis besser,
Tobias
d'Oursse
7th October 2005, 17:40
well, i don't really know. "It works for me (tm)"
in src/avisynth3_20051005/, try :
export LD_LIBRARY_PATH="."
./avisynth_test
Also, it's useless to give the avi file on the path. You have to choose it with a file selector. Maybe I should also allow to pass the file in the CLI
thank you for testing it :)
sl1pkn07
8th October 2005, 04:05
[sl1pkn07@SpinFlo avisynth3_20051005]$ ./avisynth_test
accept /home/sl1pkn07/dvdrip/WolfsRain13.mkv
notify video
set videoinfo
set frame count
terminate called after throwing an instance of 'avs::exception::Generic'
what(): FrameCount must be positive
Abortado
[sl1pkn07@SpinFlo avisynth3_20051005]$
using:
FedoraCore4
Gstreamer-0.8.11 (and plugins)
tested, Avi, Ogm and MKV files
saludos
d'Oursse
8th October 2005, 07:39
i have tested on a mkv file and it does not abort. But there's a problem with mkv and seek. I have to talk to the gstreamer dev about that.
could you create a sample of this mkv (say, 10s), verify that avisynth_test abort, and put it somewhere ?
no problem with the avi and ogm files ?
thank you
sl1pkn07
8th October 2005, 21:31
[sl1pkn07@SpinFlo avisynth3_20051005]$ ./avisynth_test
accept /home/sl1pkn07/Desktop/arkanonVSag_jones.avi (fail)
terminate called after throwing an instance of 'avs::exception::Generic'
what(): no matching sample type
Abortado
[sl1pkn07@SpinFlo avisynth3_20051005]$ ./avisynth_test
accept /mnt/hdf1/demux/Ranma/Ep005.ogm (open ok)
notify video
set videoinfo
set frame count
we seek...
on associe le buffer 373248 422400
Timestamp : 5,589s
seek done
1
2
3
4
5
6
accept /mnt/hdb1/[AstRG]Animatrix Dual_completa/[AstRG]Animatrix.DVD-RIP.DUAL.ogm (fail)
terminate called after throwing an instance of 'avs::exception::NoVideo'
what(): Clip has no video
Abortado
[sl1pkn07@SpinFlo avisynth3_20051005]$ ./avisynth_test
accept /mnt/sata-a1/Heroina.[Spanish-DVDRip].[XviD-Mp3].by.SDG.avi (fail)
notify video
set videoinfo
terminate called after throwing an instance of 'avs::exception::Generic'
what(): no matching sample type
Abortado
[sl1pkn07@SpinFlo avisynth3_20051005]$ ./avisynth_test
accept /mnt/hda1/[AHN]Elfen Lied Dual/[AHN][VE]_Elfen_Lied_01v2.mkv (fail)
notify video
set videoinfo
set frame count
we seek...
on associe le buffer 418176 422400
Timestamp : 134,676s
seek done
(avisynth_test:12101): GStreamer-CRITICAL **: gst_data_ref: assertion `GST_DATA_REFCOUNT_VALUE (data) > 0' failed
Violación de segmento (Segment Fault)
[sl1pkn07@SpinFlo avisynth3_20051005]$ ./avisynth_test
accept /mnt/hda1/[A-N]StepSister_completa/[A-N] StepSister - 01_Spanish sub.avi (fail)
notify video
set videoinfo
terminate called after throwing an instance of 'avs::exception::Generic'
what(): no matching sample type
Abortado
[sl1pkn07@SpinFlo avisynth3_20051005]$ ./avisynth_test
accept /mnt/hdf1/demux/[VE~AT] Ranma Nibun no Ichi Ep_017.ogm (fail)
terminate called after throwing an instance of 'avs::exception::NoVideo'
what(): Clip has no video
Abortado
[sl1pkn07@SpinFlo avisynth3_20051005]$ ./avisynth_test
accept /mnt/hdf1/demux/Ranma/Ep006.ogm (fail)
terminate called after throwing an instance of 'avs::exception::NoVideo'
what(): Clip has no video
Abortado
[sl1pkn07@SpinFlo avisynth3_20051005]$
OGM,AVI,MKV and MP4 fail (probe 20 videos, works only one :S)
Kurosu
8th October 2005, 23:28
Tested on Debian unstable. Had to remove the gstreamer .so because they conflicted with system settings. Removed boost_thread because system's one was OK. Use of stlport 5 didn't match the system one so I kept your shared objects.
My findings:
no file loaded+info => crash => not idiot-proof
wmv/mkv bail out with the usual message about framecount having to be positive
AVI without audio seems to work (frame accurate seeking)
AVI with audio bails out with 'no matching sample type'
mp4 A/V hangs
mp4 audio 'no matching sample type'
vob opens OK
ac3 reports no video (duh)
ts dies with "/usr/lib/gstreamer-0.8/libgstffmpeg.so: undefined symbol: mpegts_crc32"
Probably a bad mixing of cvs/distrib so versions
All of the above, except mp4, play well in totem, including ts and mkv.
It's taking shape! And already, DVD files can be opened with your tool.
Good job, and good luck.
d'Oursse
9th October 2005, 00:21
ouch, there are a lot of non working files.
I would like to mention that gst-ffmpeg is needed, because divx/xvid files are not handled correctly with only their decoder that are in gst-plugins. Maybe other decoders have also problems without gst-ffmpeg
I would like to have an mkv file that fails with the app. All those I have (2 mkv) work, so it's difficult to know how debugging that problem.
I've not tested with audio streams only.
thank you for your reports
mg262
8th November 2005, 22:41
Bidoche and other developers:
If it is not too early to ask this question, could you give us some advice on what plug-in authors should do in order to make the rewriting for 3.0 as smooth as possible?
Bidoche
9th November 2005, 19:03
I guess it would be better if you understood the STL and template classes
mg262
9th November 2005, 19:37
Thank you for the reply.
I guess it would be better if you understood the STL and template classes
STL is one of the best reasons for using C++ :) Template classes: do you mean understand them in the abstract, or try to understand the template classes in the 3.0 code?
d'Oursse
10th November 2005, 18:21
mg262: i want to write some doc about writing plugins and to write a script that creates a "template" (not c++ template) to make plugins writing easier. But right now, I'm busy with the C interface
d'Oursse
11th November 2005, 17:11
here are some improvements:
1) the current parser is broken, but there is one case where it works (you have to put an expression only in the script). One has to wait for the new Bidoche's parser
2) I have made a C interface. It's not complete yet, but sufficient for the point 3)
3) I have added to x264 an avs3 input. It works :)
708145
12th November 2005, 01:53
here are some improvements:
1) the current parser is broken, but there is one case where it works (you have to put an expression only in the script). One has to wait for the new Bidoche's parser
2) I have made a C interface. It's not complete yet, but sufficient for the point 3)
3) I have added to x264 an avs3 input. It works :)
Many thanks so far :D
Just in time for my port of ELDER4X264 to linux :P
bis besser,
T0B1A5
Kopernikus
12th November 2005, 11:56
Is it necessary to add a avs3 Interface to all Encoders/Players/Tools one want to use with avs3 with non-Windows?
Is avs3 intended for use under Windows? Is an avi Export feature (like in avs2) for Windows possible? I think it is one of the biggest strengths of avs2 to work with many Tools out of the box.
Thank you for your efforts, I think I will like working with Avisynth under Linux :-)
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.