AvxSynth: a Linux port of AviSynth

[Yellow_]

active1, do you have the ffms2avs plugin built in /home/.AVXSynth/plugins folder?

This may or may not help.

http://forum.doom9.org/showthread.php?p=1564447#post1564447

[videophool]

active1, do you have the ffms2avs plugin built in /home/.AVXSynth/plugins folder?


If it is not installed, then I would have expected to see an error, not to have the app die.

[videophool]

hi
im having a problem when i try to play the script
when i open AVXEdit and write a simple script, like this:

ffvideosource("/path/to/my/file.mkv")

then, AVXEdit disapear and don't open mplayer like when i type version()

:thanks:

We would like a repro. If you have a reasonable repro case, please open an issue here (http://code.google.com/p/avxsynth/issues/list)

[avxanne]

Ok first test something simple opened a flagged full range luma, h264AVC MOV off a DSLR, using FFVideoSource and histogram=classic, output is scaling luma 16 - 235 in the waveform, played back in MPlayer.


I tried reproducing the luma scaling problem with h264 video inside m2ts using a clip from my camera, and I don't see the scaling (I displayed the histogram as well as dumped out the yuv and saw values > 235). Could you post your clip so I can test it on my machine? Maybe it's a difference in library versions.

[Yellow_]

http://www.yellowspace.webspace.virginmedia.com/Gold.aMOV

I mentioned earlier in the thread that the luma scaling was specific to ffms2 2.16 and fixed by The Fluff quite a while ago, maybe recent commits by the AVXSynth devs have bumped version to 2.17 and resolved the problem. I haven't built it again since the initial release to test but it was scaling, used ffms2 long enough to know. :-)

[active1]

active1, do you have the ffms2avs plugin built in /home/.AVXSynth/plugins folder?

This may or may not help.

http://forum.doom9.org/showthread.php?p=1564447#post1564447

i have that folder in this directory
/home/lab/AVXSynth/plugins/ffms2avs
and it is contain : ffms2avs.kdev4 , libffms2avs.so , Makefile
and two other folders : Prerequisites & src

NOTE: i skipped three steps because i didn't know how to do them :rolleyes:

Create a .gdbinit in your home directory containing this text: (for 64-bit Ubuntu)
set env LD_PRELOAD /lib/x86_64-linux-gnu/libpthread.so.0 (for 32-bit Ubuntu)
set env LD_PRELOAD /lib/i386-linux-gnu/libpthread.so.0 This is a fix for the debugger hanging on dlopen)

We would like a repro. If you have a reasonable repro case, please open an issue here (http://code.google.com/p/avxsynth/issues/list)

sorry, i don't know what 'repro' means :stupid:

[videophool]

sorry, i don't know what 'repro' means :stupid:

If you have a set of steps to reproduce the error.

[avxsynth]

Hello to everyone on the forum from one of the committers (avxsynth@gmail.com)

Latest news:

The support for audio functions is checked in.

The following functions are supported:
- Tone
- FFAudioSource (***has been there already, can be used as audio source alongside with Tone function)
- DelayAudio
- AmplifydB
- Amplify
- AssumeSampleRate
- Normalize
- MixAudio
- ResampleAudio
- ConvertToMono
- EnsureVBRMP3Sync (*** not tested)
- MergeChannels
- MonoToStereo
- GetLeftChannel
- GetRightChannel
- GetChannel
- GetChannels
- KillVideo
- KillAudio
- ConvertAudioTo16bit
- ConvertAudioTo8bit
- ConvertAudioTo24bit
- ConvertAudioTo32bit
- ConvertAudioToFloat
- ConvertAudio

Remarks, comments, questions, suggestions...are more than welcome.

[avxsynth]

Script1: Using tone:
----------------------------------------------------------------
#ErrorHandlingExternal
clip0 = FFAudioSource(source="<path_to_your_media_file>")

f1 = 2*261.6
f2 = 2*329.6
f3 = 2*392.0
f4 = 2*f1

clip1 = Tone(frequency=f1, samplerate=44100)
clip2 = DelayAudio(Tone(frequency=f2, samplerate=44100), 1.0)
clip3 = MixAudio(clip1, clip2)
clip4 = DelayAudio(Tone(frequency=f3, samplerate=44100), 2.0)
clip5 = MixAudio(clip3, clip4)
clip6 = DelayAudio(Tone(frequency=f4, samplerate=44100), 3.0)
clip7 = MixAudio(clip5, clip6)

clip8 = MixAudio(clip0, clip7)
#
# use the line below to play sound at different sampling rates
#AssumeSampleRate(clip8, 64000)

----------------------------------------------------------------

Script2: Another set of functions tested:
----------------------------------------------------------------

#ErrorHandlingExternal
f1 = 2*261.6
f2 = 2*329.6
f3 = 2*392.0
f4 = 2*f1

clip1 = Tone(frequency=f1)
clip2 = DelayAudio(Tone(frequency=f2), 1.0)
clip3 = MergeChannels(clip1, clip2)
clip4 = DelayAudio(Tone(frequency=f3), 2.0)
clip5 = MergeChannels(clip3, clip4)
clip6 = DelayAudio(Tone(frequency=f4), 3.0)
clip7 = MergeChannels(clip5, clip6)

clip8 = ConvertToMono(clip7)

#
# the result of the two functions below should be
# unchanged audio volume
#
clip9 = AmplifydB(clip8, -30.0)
Amplify(clip9, 31.62)

-----------------------------------------------------------------

Script3: Illustrating proper downsampling (i.e. antialiasing)
----------------------------------------------------------------
#ErrorHandlingExternal

clip0 = Tone(frequency=440)
#clip0L = GetLeftChannel(clip0)
clip0L = GetChannels(clip0, 1)

clip1 = Tone(frequency=17000)
#clip1R = GetRightChannel(clip1)
clip1R = GetChannels(clip1, 2)

clip2 = MergeChannels(clip0L, clip1R)
clip3 = clip2 #ConvertAudioToFloat(clip2)
clip4 = ResampleAudio(clip3, 32000)
ConvertAudioTo16Bit(clip4)

[videophool]

hi
im having a problem when i try to play the script
when i open AVXEdit and write a simple script, like this:

ffvideosource("/path/to/my/file.mkv")

then, AVXEdit disapear and don't open mplayer like when i type version()

:thanks:

We have found a problem where AvxSynth is causing a segfault when there is a script error. We are working to identify and resolve the segfault. In the mean time, try this:


src=ffvideosource("/path/to/my/file.mkv")
ShowSMPTE(src)

[videophool]

We have found a problem where AvxSynth is causing a segfault when there is a script error.

Root cause has been identified, and fix is in progress.
http://code.google.com/p/avxsynth/issues/detail?id=6

[sl1pkn07]

i make pkgbuild for ArchLinux

http://aur.archlinux.org/packages.php?ID=57829

have patches for fix panths and other "fix"

greetings

[videophool]

i make pkgbuild for ArchLinux

http://aur.archlinux.org/packages.php?ID=57829

have patches for fix panths and other "fix"

greetings

Thanks for the contribution.

[qyot27]

If the user normally compiles mplayer themselves (and leaves the prefix alone, resulting in it installing the binary to /usr/local/bin), it results in a broken pipe due to AVXEdit and avxSynthFrameServer looking in /usr/bin rather than simply querying the $PATH. After I copied mplayer from /usr/local/bin to /usr/bin it worked fine.

[qyot27]

Also, I'm not sure of what the issue is, but it's not wanting to load FFMS2, resulting in the 'There is no function called FFVideoSource' error. The plugin is in ~/.AVXSynth/plugins. Things I'm unsure of here:

*Is all the building the prerequisites as shared necessary, or was that done simply out of Debian conventions? I tried building FFMS2 as static and as shared to link to ffms2avs, and neither one produced a working plugin. It takes too long to build FFmpeg on here, so I was only able to test with a static build of it. Not sure if that matters, as I'd think the only part that needs to be a shared object is the final plugin built by ffms2avs' Makefile, but that's only basing it on how the Windows plugins work.

*I also was using git master and SVN trunk versions rather than the point releases. Maybe that has something to do with it?




EDIT 2012-03-25: Yeah, I'm pretty sure it was because I didn't build FFmpeg as shared. I tested it again today with a shared FFmpeg, shared FFMS2, and then remade ffms2avs (+ the patch posted from the AUR) and it seemed to work fine opening a file and then resizing it.

Due to how messy this could potentially get with existing installs of those libraries (either from the distro repos or user-compiled), I'd strongly favor being able to use non-system copies of FFmpeg and FFMS2 to link against, as well as being able to use a static version of FFmpeg (if that truly is at the root of that issue I noted above). Of course if this was already planned, then just ignore me.

[videophool]

f course if this was already planned, then just ignore me.

The project could use an install expert to sort these things out. The current team is all SW developers, and our focus has been mainly on getting the framework ported and running.

[sl1pkn07]

hello. is possible add suport to compile with GCC 4.7.0?

greetings

[videophool]

hello. is possible add suport to compile with GCC 4.7.0?

greetings

Haven't tried yet. Are you seeing problems?

[sl1pkn07]

yes:

http://paste.kde.org/447110
http://paste.kde.org/447116

and not GCC 4.7.0 related:

http://paste.kde.org/447122

and:

make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule.

greetings

[videophool]

We will look at integrating the revised SoftWire. Our current version of AvxSynth has the built-in resize routines stubbed out and set to call into ffmpeg (they use SoftWire). This will be our first SoftWire test.

Our SoftWire investigation is not going well. We cannot even get the SoftWire test code to run on gcc 64.

[Mr VacBob]

Is SoftWire a JIT library? In that case you might be having problems with the ABI difference between Win64 and ELF/amd64. Basically some xmm registers need to be saved outside of calls into the Win64 system.

I took a quick look through the source and noticed some uses of things like 'unsigned', 'long', 'InterlockedIncrement' which probably indicate portability problems or 32/64bit bugs. 'unsigned' on loop counters can lead to overflow bugs and inhibits compiler optimization, while 'long' never has the size you want it to have, and use of atomic counters is bad unless you're very sure it makes the code thread-safe.

That said, if you inherited that code from AVISynth maybe it's best not to change it downstream.

As for all the non-JITted assembly I see commented out, it'd be best to port it to use x264's yasm library, which will also be good for AVISynth Win64.

Then you're only left with the portability problem of getting all the external plugins to work…

[videophool]

Is SoftWire a JIT library? In that case you might be having problems with the ABI difference between Win64 and ELF/amd64. Basically some xmm registers need to be saved outside of calls into the Win64 system.

I took a quick look through the source and noticed some uses of things like 'unsigned', 'long', 'InterlockedIncrement' which probably indicate portability problems or 32/64bit bugs. 'unsigned' on loop counters can lead to overflow bugs and inhibits compiler optimization, while 'long' never has the size you want it to have, and use of atomic counters is bad unless you're very sure it makes the code thread-safe.

That said, if you inherited that code from AVISynth maybe it's best not to change it downstream.

As for all the non-JITted assembly I see commented out, it'd be best to port it to use x264's yasm library, which will also be good for AVISynth Win64.

Then you're only left with the portability problem of getting all the external plugins to work…

Some posters on this thread had suggested that AviSynth 2.6 included SoftWire that had been successfully ported to gcc and Win64. Since AvxSynth still needs a good cross-platform optimization model, we decided to investigate to see if we could get SoftWire running with AvxSynth. The initial results are not encouraging.

[sh0dan]

Since softwire is abandoned by the original developer, and I think all 64 bit is mostly untested, you might want to look at asmjit, which is very similar, and enable you to do JIT code that is 32/64 and Windows/Linux compatible, you might want to use that instead -it looks very similar and nice.

http://code.google.com/p/asmjit/

[videophool]

Since softwire is abandoned by the original developer, and I think all 64 bit is mostly untested, you might want to look at asmjit, which is very similar, and enable you to do JIT code that is 32/64 and Windows/Linux compatible, you might want to use that instead -it looks very similar and nice.

http://code.google.com/p/asmjit/

Thanks. We will take a look.

[verydoomed]

I went to the website and compared to installing Regular windows avisynth this is SOOOO complicated that I am not even going to try.Even the first line of the instruction was a real put off "Install ubuntu-11.10" No thanks I much prefer my Mint 10.10 and am not willing to move to 11.10 I'll just have to stick with Avisynth under wine. I watched the youtube video also but I am not clear, will you be able to save your script and open it in some video editor on linux? or a simple equivalent to virtual dub?

[videophool]

I went to the website and compared to installing Regular windows avisynth this is SOOOO complicated that I am not even going to try.Even the first line of the instruction was a real put off "Install ubuntu-11.10" No thanks I much prefer my Mint 10.10 and am not willing to move to 11.10 ... I watched the youtube video also but I am not clear, will you be able to save your script and open it in some video editor on linux? or a simple equivalent to virtual dub?

We are a small team of sw devs without adequate resources to test on many platforms, or develop a good installer. You can probably install on other Linux platforms, and if someone provides the instructions, we will post them on the wiki.

Once AvxSynth is proven stable, we will work on an ffmpeg component so that any app that supports ffmpeg will be able to open .avs scripts. As for a Virtual-Dub like app, it would be great if an industrious developer decided to make such a contribution. In the mean time, we have a very simple editor, AvxEdit, and the frame server that we use ti pipe to X264.

I'll just have to stick with Avisynth under wine.
We find avisynth/wine to be very unstable, and it is subject to licensing problems with MSFT libraries. With a small committed community, avxsynth could quickly achieve the stability and support needed to replace the avs/wine hack.

[Yellow_]

Once AvxSynth is proven stable, we will work on an ffmpeg component so that any app that supports ffmpeg will be able to open .avs scripts. As for a Virtual-Dub like app, it would be great if an industrious developer decided to make such a contribution.

Sounds great.

There are a number of NLE type ffmpeg based applications available for Linux that'll offer more than Virtualdub functionality as is.

Blender has a video editor of sorts, but also a nodal based compositor and tracker/stabilizer, compositor soon to be OpenCL, code well on the way just not in trunk yet.

Kdenlive NLE with underlying MLT (Media Lovin Toolkit) is ffmpeg based. http://www.mltframework.org/twiki/bin/view/MLT/

[avxanne]

We have updated the the ffmpegsource plugin and renamed it to avxffms2. This updated code (check out recent code at www.avxsynth.org) should fix the issue some people were experiencing where the system could not find FFVideoSource(). Please delete the old libffms2avx.so from the ~/.AVXSynth/plugins/ directory so that avxsynth will pick up FFVideoSource from libavxffms2.so. This version was tested with the ffms 2.17 and libav 0.7.4

The source code of the plugin can also be found in the avxsynth_plugin branch of the ffmpegsource project svn tree.
http://code.google.com/p/ffmpegsource/source/browse/

[sl1pkn07]

please fix compile with gcc 4.7.0 (now in core in archlinux). or...

Note: I'M NOT PROGRAMMER. i asked a chat friend programmer

avxSynthFrameServer part:

g++ -Wl,-R/usr/lib/avxsynth/plugins -Wl,-R/usr/lib/avxsynth -Wl,-R/usr/lib/ -Wl -L../../../avxcommon -lavxcommon
-L../frameserverlib -lavxframeserver -lpthread -lm -ldl ./src/main.o -Wl -L../../../avxcommon -lavxcommon -L../frameserverlib -lavxframeserver -lpthread -lm -ldl -o avxSynthFrameServer
g++: error: unrecognized command line option '-Wl'
g++: error: unrecognized command line option '-Wl'
make[2]: *** [avxSynthFrameServer] Error 1

change this:

LIBS = -Wl $(AVXCOMMON_LIB) $(FRAMESERVER_LIB) $(SYSLIBRARIES)

to this:

LIBS = -Wl,$(AVXCOMMON_LIB) -Wl,$(FRAMESERVER_LIB) -Wl,$(SYSLIBRARIES)

i'm not sure if it is the correct, but compile without error


avsynth builtinfuntions part:


src/filters/focus.cpp: In function 'void avxsynth::AFH_YUY2_C(unsigned char*, int, int, int, int)':
src/filters/focus.cpp:522:6: error: redeclaration of 'unsigned char y'
src/filters/focus.cpp:507:11: error: 'int y' previously declared here
make: *** [src/filters/focus.o] Error 1

with this fix the issue?

uc y_ = ScaledPixelClip(p[x*2+0] * center_weight + (yy + p[x*2+2]) * outer_weight);
yy = p[x*2+0];
p[x*2+0] = y_;

with this compile. but make other warnings:

/common/include/source -c src/audio/audio.cpp -o src/audio/audio.o
src/audio/audio.cpp: In member function 'virtual void avxsynth::ResampleAudio::GetAudio(void*, avxsynth::__int64, avxsynth::__int64, avxsynth::IScriptEnvironment*)':
src/audio/audio.cpp:1403:37: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
src/audio/audio.cpp:1448:38: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]

and http://paste.kde.org/453290


ffms plugin part

http://paste.kde.org/453296

i dont know is related by avaxanne update or gcc 4.7

i test with ffmpeg distro package and libav 0.8.1 (same issue)

what is the diference between LibAV 0.7.4 and libav 0.8.1? (libav 0.7.4 don't compile with gcc 4.7)

greetings

[qyot27]

It seems that a different problem with FFMS2 has crept up. Now it complains about av_pix_fmt_descriptors being undeclared, resulting in a load failure and therefore FFVideoSource once again not being found. FFmpeg-git from early this morning, FFMS2-r670, AvxSynth r124.

Of course, I was also playing with trying to get it to load an FFMS2 that had the FFmpeg libs statically linked into it when this happened, but this doesn't seem like it'd be related to that.

[avxanne]

FFmpeg-git from early this morning, FFMS2-r670, AvxSynth r124.


As mentioned above, we tested with ffms 2.17 and libav 0.7.4 so there may be api incompatibilities. We will upgrade to more recent versions of these libraries in the near future.

[videophool]

We have moved the AvxSynth project to GitHub. We will take down the Google Code site shortly. www.avxsynth.org is already setup to redirect to GitHub.

[zacharias]

ok, now this seems veeeeeeerrrrrryyyyyyy promising. a lot really.
i will try this evening or even tomorrow morning to see if it works on debian stable/crunchbang. in wich version of ubuntu was it tested?
hopefully, specially resing filter/resample will work and specially the deinterlace itvc ones, if possible. thats my main issue. whenever i get interlaced source i have to use w1nd0w2.
i'll see and read the documentation.
one thing: does one need to compile mPlayer to make it work properly? afai can tell, it's not needed.
kudos

[zacharias]

on your how to page: https://github.com/avxsynth/avxsynth/wiki/System-Setup please consider changing the following on the point "AvxSynth Build"
from 1Get AvxSynth source code from github

git clone git@github.com:avxsynth/avxsynth.git
to
git clone http://github.com/avxsynth/avxsynth.git
i got an error whilst following ur tutorial, and this step solved it.
error:
Cloning into avxsynth...
The authenticity of host 'github.com (207.97.227.239)' can't be established.
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.
Permission denied (publickey).
fatal: The remote end hung up unexpectedly

using debian squeeze, btw ;)
kudos

[zacharias]

btw, failed to lauch the app. this is the content of my folder after instalation
http://17.imagebam.com/download/EQcMLDTZcyGQ1uVwZqOwjQ/18757/187569074/Screenshot%20-%2004292012%20-%2010%3A34%3A06%20PM.png
any thoughts?
kudos

[zacharias]

another update:
after installing FFMPEGSource, it destroyerd my previous ffmpeg compilation. i've done following this link:https://ffmpeg.org/trac/ffmpeg/wiki/UbuntuCompilationGuide
afaik, if one compile like the wiki of ffmpeg, your step is unnecessary, am i ritght?
please do provide some input on the previous threads as well, mate ;)
kudos

[videophool]

btw, failed to lauch the app. this is the content of my folder after instalation
any thoughts?
kudos

What is in $HOME$/.AVXSynth?

[avxanne]

on your how to page: https://github.com/avxsynth/avxsynth/wiki/System-Setup please consider changing the following on the point "AvxSynth Build"
from
to



Thank you for pointing that out. I've updated the wiki. The original instruction on the wiki worked if ssh was set-up.

[avxanne]

one thing: does one need to compile mPlayer to make it work properly? afai can tell, it's not needed.
kudos

You do not need mplayer if you just want to dump the frames to stdout. We currently have two applications:
1) AVXEdit - Launches mplayer when you click the "Mplayer" button and plays your AvxSynth script.

2) AvxSynthFrameServer -
Check-out https://github.com/avxsynth/avxsynth/wiki/AvxSynth-Frame-Server
With the default commandine parameter, it would launch mplayer so that the user can view the frames. If you specify it not to launch mplayer, the frames would be dumped to stdout. For example
./avxSynthFrameServer testavxsynthscript.avs false
You can pipe the output to an encoder, for example, to x264:
./avxSynthFrameServer testavxsynthscript.avs false | x264 --profile main --level 3.1 --bitrate 3600 --vbv-bufsize 7200 --vbv-maxrate 5400 --thread-input --fps 24 --keyint 48 --min-keyint 48 --no-scenecut --rc-lookahead 48 --deblock 0:0 --bframes 2 --b-adapt 2 --b-pyramid none --b-bias 0 --ref 3 --weightp 2 --qpmin 6 --qpmax 51 --qpstep 4 --ipratio 1.4 --pbratio 1.3 --vbv-init 0.9 --ratetol 1.0 --qcomp 0.5 --cplxblur 20 --qblur 0.5 --aq-mode 1 --aq-strength 1.0 --merange 16 --me umh --direct auto --subme 6 --partitions p8x8,b8x8,i4x4 --trellis 2 --psy-rd 1.00:0 --no-fast-pskip --aud --nal-hrd vbr --sar 1:1 --output elephantTrim_3600.264 --input-res 1280x720 -


Also, for our testing we did not compile mplayer and only did apt-get install mplayer.

[avxanne]

another update:
after installing FFMPEGSource, it destroyerd my previous ffmpeg compilation. i've done following this link:https://ffmpeg.org/trac/ffmpeg/wiki/UbuntuCompilationGuide
afaik, if one compile like the wiki of ffmpeg, your step is unnecessary, am i ritght?
please do provide some input on the previous threads as well, mate ;)
kudos

You could use whatever compilation of ffmpeg, but we've mostly tested with libav 0.7 and 0.8. Please do let us know if you see any issues between ffmpegsource and the more recent versions of ffmpeg.

[avxanne]

btw, failed to lauch the app. this is the content of my folder after instalation


That folder should have the AVXEdit executable after make.

What were the compile errors?

[zacharias]

That folder should have the AVXEdit executable after make.

What were the compile errors?

i got, none, afaik as i recall. im very exited to see this, dat to my knowlege, and the way i see it, (correct me if im wrong) kinda acts like a mix between avysinth+avsp for linux. wich is nice. i cant feed u back on the above questions mate. i've just instaled a brand new version of #!. so i wont be doing anything that might mess up mu ffmpeg + x264 compililing like i've said earlier... sorry on that. i just cant afford it having to reinstall *nix from scratch, because im noob (still)
but i will provide somefeeback on my experiments on how to make it work. i'l read some more documentation better and try to find ways to make this work.
since like i've said, i compile ffmpeg and x264 like the wiki i've mentioned, it wont be a bad idea for u uys take a look at that compilation since its used by thousands of *nix users, and somehow make AVXSynth work based on those. at least for debian/ubuntu and such distros based uppon dat.
kudos

[zacharias]

http://thumbnails66.imagebam.com/18918/5612f0189175172.jpg (http://www.imagebam.com/image/5612f0189175172)
here it is a sucssefull instalation. no bugs during install nothing! ;)
steps i took
1) compiled ffmpeg and x264 like this wiki: http://ffmpeg.org/trac/ffmpeg/wiki/UbuntuCompilationGuide
2) installed QT like so (dont know if its the best way to do it but it worked with me)
a)
$ sudo apt-get install libqxt-*
b)
sudo apt-get -y install libqt4-dev libqt4-designer libqt4-gui
3) installed the rest of the dependencies (exept for th "Build tools" cause it was already installed by he compilation of ffmpeg+x264 and mplayer cause i already had it installed) like the info by doing:
$ sudo apt-get install liblog4cpp5-dev liblog4cpp5 libcairo2-dev libpango1.0-dev libpango1.0-dev
4) skipped to the "AvxSynth Build" part and proceeded like the wiki
Success! :)
so far.

fyi: since it runs using QT, on just can simply double click "AVXEdit" and voilá.
FIY: im using testing #!waldorf based on debian wheezy.
kudos

[zacharias]

i coundt even preview a video. this error shows up:
http://thumbnails7.imagebam.com/18920/27b335189192610.jpg (http://www.imagebam.com/image/27b335189192610)
so i decided to compile and install FFMS-2.17
so after i run
./configure --enable-shared
i got the following error
configure: error: in `/home/zacharias/.local/share/Trash/files/ffms-2.17-src':
configure: error: cannot link with FFmpeg
See `config.log' for more details
any thoughts?
kudos

EDIT: plus i found this on the debian repo's
http://packages.debian.org/search?searchon=names&keywords=FFMS

[sl1pkn07]

See `config.log' for more details

[zacharias]

See `config.log' for more details

here is, mate
http://pastie.org/3881418

[sl1pkn07]

configure:15913: gcc -o conftest -O3 -I/usr/local/include -D__STDC_CONSTANT_MACROS -shared -fPIC -DPIC conftest.c -pthread -L/usr/local/lib -lavformat -lavcodec -ldl -lva -lXfixes -lXext -lX11 -ljack -lSDL -lx264 -lvpx -lvorbisenc -lvorbis -ltheoraenc -ltheoradec -logg -lopencore-amrwb -lopencore-amrnb -lmp3lame -lfaac -lz -lrt -lswscale -lavutil -lm >&5
/usr/bin/ld: /usr/local/lib/libx264.a(common.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libx264.a: could not read symbols: Bad value
collect2: ld returned 1 exit status

you fail build x264, or the ffmpeg package need other version of x264

[zacharias]

the fpic is the problem. already tryed to compile with --enable-pic
still nothing
kudos

[JEEB]

the fpic is the problem. already tryed to compile with --enable-pic
still nothing
kudos
It's because libraries you built ffmpeg with (that are linked into ffmpeg, and thus will be linked into the ffms you were building) are not built with fPIC.

Also, I already helped you build a working ffms with current ffmpeg for this on #ffmpeg, why continue for eff's sake? I've already told you what you have been doing wrong, and decided that it's just easier for one like you to just cut off all other libraries so that you don't need to rebuild them all just to get a working ffms (because ffms doesn't even use these libraries).

herp le derp

[zacharias]

@Jeeb
ive done the compilinv like uve suggested.still got the same error whilst trying to open video on avx.ffms voes well but error still there.that paste bin is the one ive showed u before i follow ur light.to wich im thankfull (: