How to frameserve from Premiere CS5?

sebrame

Inspiring

Not sure about specific color space specs, but can report that AFS works beautifully with Squeeze 7. I use it many times daily.

Steve B

Stile35_DJAuthor

Participating Frequently

It seems that this version of frameserver is reserved ONLY for people who already paid to developer for it...

Jeff Bellune

Legend

For now, until it's officially released, that is correct. Once released, it will available as an open-source application under the GNU General Public License.

-Jeff

Participating Frequently

An informal poll of those of you using the current beta release of the Advanced Frameserver:

1) Personally, I find the fracturing of the frameserver settings across three tabs in the Export Settings window noisome. To me, since this plug-in is all about speed (theoretically) and ease-of-use, I find it unnecessarily "clicky" to go from tab to tab to change or verify settings.

What I'd like to see is the Video and Audio tabs eliminated, and the options contained on those tabs moved to the Frameserver tab. This more closely replicates the way which these options were presented in the original DMFS. I'm not saying we need a pop-up like in the original DMFS; I'm just suggesting that since we're not really encoding video or audio as you would with a more standard export module, and rather are "serving frames," it would be more logical to simplify the tabs and options.

I've brought this up before with the gentleman corresponding with the programmer, but it seems to have been ignored. I'm not attempting to be autocratic here, but I'm trying to streamline this plug-in for the masses, and before we have a final version released, I'd like to open a bit of discussion on it.

2) Another issue I brought up is the reference of the frameserving time-out being labeled as "autoclose." I think that native English speakers would agree that this has a different connotation than something like "auto-stop." I politicked for this one before, since we had "autostop," "autoclose," and "auto-close" in various parts of the interface--unfortunately, in this version, it's all "autoclose." What say you, People of the Forum?

Beyond that I think the frameserver is functionally complete and stable. I suspect that this will be the last version we'll see of the AFS, once it is released; unless something breaks in a later Premiere update, there really won't be much need for revision of this plug-in. This would be a good time to make any cosmetic changes, though, so if anyone has any thoughts of what they'd like to see modified in the plug-in, let's open up the table for discussion now.

Jeff Bellune

Legend

1) -1

2) +1

For 1), I think the Video/Audio tabs need to stay, if only for UI consistency. I agree that it's "clicky" having so few options on each tab, but the current layout fully addresses consistency during export. Additionally, the point may be moot if the SDK doesn't allow elimination of the Video/Audio tabs, instead only allowing additional tabs. I don't know if that's the case, but I'm tossing out the idea as something to consider.

-Jeff

Participating Frequently

Additionally, the point may be moot if the SDK doesn't allow elimination of the Video/Audio tabs, instead only allowing additional tabs. I don't know if that's the case, but I'm tossing out the idea as something to consider.

I don't believe that's the case. Change the Format dropdown to one of the image formats, e.g. Windows Bitmap: you have Filters, Video, and FTP. Change the Format to one of the audio-only formats, e.g. Windows Waveform: you have Audio and FTP. So, while I can't say definitively that you can eliminate both the Audio and Video tabs, it's clear you don't need them both.

Regardless, I think your point is valid, even if I don't agree That's why I wanted to get some discussion on this; I'm not trying to be a whiny baby, expecting my way to be the only way. I still feel there are too many tabs there; the FTP tab is pointless and should be killed (if possible), and even if things aren't whittled down to one "Frameserver" tab, I think the options on the "Frameserver" tab should be moved to the Video tab, at the least. This maintains the Audio/Video tab convention, but still simplifies the options and usage of them. Discuss!

Regarding the "autoclose" issue, here's how I'd like to see it in the UI:

1) The checkbox for enabling the timeout should say something like "Stop serving when idle"

2) "Idle timeout" is fine, but should perhaps have the addition of the time scale, and eliminate the slider bar, so that it says "Idle Timeout : 000 seconds." I think the slider bar is unnecessary UI clutter; I just click and type in the hot-text anyway.

3) Up in the Output Summary, the "autoclose" text should say "Continue serving when idle" and "Stop serving when idle for XX seconds." The same should be displayed in the AME queue.

sebrame

Inspiring

Ah...sadness. I was holding off on trying the Framserver due to the latest version of Squeeze's inclusion of a CS5 plugin that allowed encoding to Squeeze directly from Premiere. However, THAT little gem is far from useable, so I decided to finally get around to installing the latest version of the Frameserver that I just received. I was so excited to get a playable AVI from frame serving, however, when I encode the frame served file with Squeeze, no matter what export frame size I choose, the output file is the same frame size as the frame served AVI. So if I serve a 1920x1080 timeline to Squeeze, and encode to a 706x480 WMV, the resulting WMV is 1920x1080.

Participating Frequently

That's got to be a problem with Squeeze, then. I've encoded dozens of files with the frameserver to various applications, almost always with resizing, and had no issues--I always get the output size I specify.

Check your settings in Squeeze, and also try an intermediate file; might be a bug of some sort in Squeeze.

sebrame

Inspiring

I just tried an intermediate, and it transcodes normally using the same settings in Squeeze. I've got a trial of Episode, so I'm going to try that.

J

johannuar

Participant

Hi all, any updates on this?

http://tmpgenc.pegasys-inc.com/en/product/tvmw5.html

Participating Frequently

Nope, still waiting. I'll rattle the cage of our overseas compatriot...

jabloomf1230

Participating Frequently

TMPGEnc XPress 4 is being replaced:

The link implies that the new version uses the nVidia H.264 CUDA encoder, which might be a major advantage. The add on MainConcept CUDA encoder for PPro CS5 is substantially more expensive.

Stile35_DJAuthor

Participating Frequently

Is frameserver released officially? How can we get it? Only by sending some money or it will be distributed on frameserver page for donwload?

taravasya

Known Participant

This is not final releas. When will the final version is ready, the source-codes will be transferred to Satish Kumar (creator of this plugin). How soon after that, he will publish a new Official release I do not know.
Also possible will be created new OpenSource project, because from the old DebugMode Frame Server, in this new version is almost nothing left ...
In any case, with time this plugin will be available to everyone. Just need time ..

And while, that those who have helped me pay for work of a programmer can use the plug-in, as they want it ...

GoodLuck!

arturpu

Participating Frequently

Thank you for inserting a link,

Pozdrawiam : Artur Pukaluk

Participating Frequently

UNEXCITING UPDATE:

The frameserver is about 90% functional right now. A bug with RGB24 frameserving that caused transitions to render weird alpha issues has been fixed, which was the last major bug that was discovered. The frameserver also has a new name: Advanced Frameserver. Keepin' it simple

The last major hurdle that is being worked on is not so much a bug-squashing stampede, but rather some major overhauling to the way the frameserver dishes up frames to external applications. Generally, encoding from a frameserved signpost AVI file is as fast as encoding from an intermediate file. However, there is a significant slowdown when serving from a sequence with render-intensive effects or when using MRQ during export; this is primarily evident when using poorly multi-threaded apps like Squeeze or VirtualDub. However, when encoding to something like CCE or when using the multi-threaded version of Avisynth between the frameserver and VirtualDub, the time differential diminished or disappeared.

So, what the developer is working on is a method to request multiple frames in parallel and cache them, so that encoding applications that maybe aren't as efficient will have a "pool" of served frames to pull from, instead of asking for them one by one. This increases the overhead a bit, since the frameserver will have to cache a certain number of frames, but should be offset by much shorter encoding times. In order to implement this, however, the frameserver needs to be more or less written from scratch, so that's why there haven't been any updates lately. The frameserver is essentially complete; it's just being hot-rodded now

I'll update as we get closer to a revamped version of the frameserver--stay tuned. My thanks to everyone for your interest and support of the project.

Jeff Bellune

Legend

It may be unexciting, but it's very informative and well-presented.

Thanks!

-Jeff

aj hill

Participant

I just received the frameserver from taravasya. Looking forward to trying it. Thanks!

arturpu

Participating Frequently

привет, я польский, я не говорю на русском, но тем быстрее он говорит на русском языке, чем на английском языке.
Спасибо за ваш быстрый ответ, если вы знаете что-нибудь еще, дайте мне знать в порядке?
может быть на русском языке:)
Мой адрес: arturpu@o2.pl