Frameserving from Premiere / Premiere Pro

[leonhard]

Hi, although I did the frameserving stuff a lot of time, now I am experiencing problems. The situation:

Frameserving on Win2k from PREMIERE 6 to PluginPac Frameserver works fine.

Trying to do the same the old fashion way via LinkToAvisynth with Avisynth 1.03beta selected gives me "Wrong Server Version" Error Code, when a corresponding avs file with IPCSource within is opened. This Error Code was explained before in the Virtual Dub FAQ region, but this is unfortunately removed. So what shall I do with this? Why acctually is IPCSource not available in current Avisynth version?

Under XP using PREMIERE PRO for the use of LinkToAvisynth I got the same.
Using PluginPacFrameserver I did not get the familiar PluginPacFrameServer Window but a rendering Proccess was indicated within premiere first and then a "PluginPac Frameserver not serving. Chech again?" notice was displayed. As a lot things are different in Premiere Pro, I might as well be I did something wrong.

So as usual, any comment is appreciated.
Olaf

[Wilbert]

Trying to do the same the old fashion way via LinkToAvisynth with Avisynth 1.03beta selected gives me "Wrong Server Version" Error Code, when a corresponding avs file with IPCSource within is opened.
You need to have a special version of the premiere frameserver (http://www.videotools.net). Dunno which one.

edit: v0.93 IIRC

Why acctually is IPCSource not available in current Avisynth version?
Long story. It probably would have if the sources were available.

Under XP using PREMIERE PRO for the use of LinkToAvisynth I got the same.
I don't know if IPCSource is supposed to work with Premiere Pro (using the special version of Premiere server at videotools).

Using PluginPacFrameserver I did not get the familiar PluginPacFrameServer Window but a rendering Proccess was indicated within premiere first and then a "PluginPac Frameserver not serving. Chech again?" notice was displayed. As a lot things are different in Premiere Pro, I might as well be I did something wrong.
This should work. I hope DDogg can help you further ...

[leonhard]

Thanks for your prompt answers Wilbert. Actually I did a lot of Web Research today, and step by step encouraged and trying to test all at least a bit promising combinations of different settings I finally managed to make Premiere at least frameserve via the PluginPac FrameServer. Somehow my main mistake was to got mixed with PluginPac FrameServer and PluginPac Frameserver VfWCodec. So after tackling this out, now there is at least a working solution and one can simply use a current avisynth Version. So far so good.

So, as far as IPCSource is concerned, sounds a bit like flying knives behind the scene? Also what Edwin writes about contacting Ben for it evokes somehow curiosity. As well as why taking away the information for old version, this so far I really don't understand.

Honestly said, so far, but this will probably be because of my limted insight, I neither understand why to make all the different version so incompatible?

Now the next step will be to figure a out a working solution for the import to Premiere. I mean perhaps it has to be like this, but using the IM-Avisynth.prm I unfortunately only get black video (thumbs) in the timeline. So I don't know, is this fine or not? Audio at least is as usual.

[Wilbert]

So, as far as IPCSource is concerned, sounds a bit like flying knives behind the scene? Also what Edwin writes about contacting Ben for it evokes somehow curiosity. As well as why taking away the information for old version, this so far I really don't understand.
Me neither.

Short history what happened after that: Edwin introduced IPCSource again and didn't release the source => he put IPCSource into a separate plugin (without source) when people requested the source of AviSynth itself => he put 30 trial period with some limitations on his recent versions of premiere video server.

Now the next step will be to figure a out a working solution for the import to Premiere. I mean perhaps it has to be like this, but using the IM-Avisynth.prm
You are talking about this version:
http://www.ox.compsoc.net/~flend/avisynth/index.html
correct?

[leonhard]

Actually yes, this Version i tried, and as described in the documentation, and at least with this, the sound (as I already said but simply repeated to distiguish) diplayed correctly.

As well I tried the first Version Avisynth0.25, which gives very strange results, not displaying sound correctly, neither filmlenght, some fixed value and on top a strange (non-)flmtype.

Both version commenly display black "footage".

Actually I like to work field based which premiere doesnot, at least not up to 6.5, and so as soon as you do some filtering, well, good chances you screw up your footage. Often I want to extract a progressive frame as a pic. So far the best way i know to deintelace is to separate the fields with avisynth and then to use Donalds smartbob deinterlace filter. So far this filter I use within Virtual Dub. The only reason for it is because I don't know how to configure/ tune the settings for this filter within an avs script. So what would be convenient for me would be a way to prepare erverything with Avisynth and then use greppy premiere as an export tool.

The only bad feelings I have at the moment is about the color conversion if i don't use 6.5 but pro.


Olaf

[Mug Funky]

AVIS, the cut down ffvfw codec will serve to premiere.

and i think there's a (free) alternative to the videotools/net premiere server that isn't quite as obnoxious in opening up browser windows (thank god for zonealarm)

*loading premiere*

oh, that's pluginPac. never mind then.

[leonhard]

hi mug funky. as ffvfw comes with avisyth I tried it as well. Unfortunately I didn't achieve a success. Somehow it produced a real big avi. So I got confused. Did you succeed with it? What were your settings?

Olaf