Just to let you guys know i tested the latest frameserver with the new TMPGenc 5 and it works wonderfully well.
Hi guys. Have been following this thread since December 2010
Sounds pretty cool that someone continues the development work of the "old" Debugmode Frameserver" for CS5.
Is there any chance to get the current (beta) version somehow in order to experiment with it?
If so could you plsPM me or whatever it takes in order to direct me to where this baby can be found
Thanks a lot. The community rocks!
Can someone confirm that you can frameserve to a watch folder on a shared network drive and compress the video with Squeeze running on a Mac that has access to the shared network folder? I know it should be possible, but I'd like to hear that someone has done it.
Squeeze running on a Mac
Will not work. The frameserver is PC only, both for serving and for playback of the served AVI.
It's limited to the group of testers right now. We should have the real deal very soon; I've not encountered any real bugs in the latest version. We'll start a new thread here once the official is released with all the relevant information.
The frameserver is PC only
We can think about this....
It really is the required function? What do you think?
As I understand, for this only need to adapt the codec for Mac?...
For the record, I just encoded to a Squeeze Watch Folder with AFS locally on a PC with excellent results. I'll give a network location a try later, but I see no reason why it shouldn't work.
I, for one. would like to serve from the PC to the Mac. But, I am probably in the minority and the development should follow completion of the original project. I would chip in again if you decide to go down this path.
I'm no programmer, but I suspect this would involve a massive overhaul of the code for the frameserver, if not an entirely new codebase to implement it.
I'm not saying its impossible, or that it's a bad idea--it's a great idea--but I think this would involve a fair bit of capital to get someone to work on this. The reason we were able to get AFS so "cheap" is because it wasn't a radical departure from DMFS. Yes, there are new features and optimizations, but this didn't involve any sort of crossplatforming.
Again, this is a swell idea, but I'll pass the torch to you to lead the attack
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.
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.
but it seems to have been ignored.
No... You are absolutely wrong. This does not so.
Personally, I think that when all separated by tabs, and it split into logical parts (video, audio, and settings relating exclusively to the functionality of AFS), is much easier to navigate. For a quick overview of the settings, there is a section summary:
where you can quickly see the current export settings. If you do not like to switch by tabs, you can create a preset exports. And just use it in two clicks.
But I respect opinions of the peoples around me, and I am ready to accept the democratic decision. So with great interest, I will follow this topic about this issue.
Colin, you helped me a lot, and now I do not want, what would you think that I'm ignoring your wishes, and so even though which opinions will dominate, I do ask for you AFS with all options on one tab.
And of course I will not dispute with an English speaking person, like properly in English are called things. We will change autoclose on ....
Actually, on what to change it? I do not exactly understand your words in the previous post.
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.
overview of the settings, there is a section summary: where you can quickly see the current export settings.
Here's the thing: I usually have the Summary twirled up/hidden, because it takes up space for more important things like the actual settings in the tabs. But yes, your point is valid.
If you do not like to switch by tabs, you can create a preset exports. And just use it in two clicks.
Yes, I do that too. However, I've been doing a lot of testing with various settings in the Frameserver, so presets aren't always good options. I just want to tick a few things here and there, and then do another test. But you're correct: for regular use, Presets are the best approach.
what would you think that I'm ignoring your wishes, and so even though which opinions will dominate, I do ask for you AFS with all options on one tab.
No, there's no need to do that! And my point was just that I wished to have conversation about it, as we are doing now. I am willing to accept when I'm wrong... most of the time So don't worry about a specific version based on my own view of it; I will submit to the will of the majority.
Actually, on what to change it? I do not exactly understand your words in the previous post.
Well, I'd like to get some other opinions on it, but I've offered a couple of ideas in response to Jeff's reply above. Before we change anything, let's get some more ideas from other testers. I just want the text to be as clear and obvious as it can be based on the function of the frameserver.
Thanks for your reply--no hard feelings!
It's amazing how this gentleman from Ukraine communicates with all of you here on this form, I mean just imagine this scenario, speaking to someone in Tokyo and only rely on google to translate your writings and readings while developing and collecting funds for a program that might or might not end up working? This guy has talent, I'm glad to see this kind of international interactivity between the members in this helpfull Adobe community. Hope it doesnt end here.
P.S I also have the FrameServer so Im not quite of topic
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.
I vote for that.
I was just wondering if there is any news on the development of this plugin? It's been a bit quiet lately...
It seems that this version of frameserver is reserved ONLY for people who already paid to developer for it...
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.
I wonder what the state of play of Advanced Frame Server is? It all seems to have stalled a little...
I contributed a little to the project, and am using the last released version.
Is that the final version? If so when will it go to Satish for public release??
Will there be an update for CS5.5?
I wouldn't say it's stalled; there's just not that much to do. By the way, I'm about as in the loop as you at this point
This will probably not be released as Debugmode Frameserver; this is a completely rewritten plug-in now. DMFS est mort, vive le AFS.
AFS works just fine in CS5.5.
Hello mark! Sorry for such a long silence. I have some problems with this community:
I think final and open source release, will appear in June, maybe in July.
About CS5.5 AFS work in this version normally.
Colin what about performance of AFS with single thrided coders? It`s now better?
Just used the frameserve for the first time yesterday and it worked great! Thank you so much to everyone who was involved in creating it. You guys are lifesavers!
i just downloaded AFS from softpedia
it's a 620kb file...
is this the official release because it is actually available?
where can you find documentation about how to use AFS effectively?
i am a nyc English teacher for special needs students
and really want to get good at this before school starts in september...
thank you so much for any help
congrats on the project!!!
Well...it's the same version number as the last release that I received an email about, and the size of the install file matches the last file I downloaded, so it looks like it's the final.
As far as instructions, there haven't been any all along. You simply double-click the installation EXE, and when you encode a timeline in Premiere, you'll see a new option for Advanced Frameserver. Really the only thing you can or need to alter is the location of the exported AVI "pointer file". Then, locate that file and use it as you would any other AVI.
Remember that it only lives as long as it's being exported from PPro via the AFS. Shut either of those down and it goes away.
creative illusions Productions
this might be an ultradumb question
but would be cool if it worked i think:
is there anyway to frameserve from PPRO cs5.03 and/or AE
to OCTANE to take advantage of the efficient gpu rendering OCTANE does
or is OCTANE a completely different type of rendering program?
all i want it for is 2d canon mts avchd files into various 2d output formats...
like i said, this may be a screwedup question...
thanks in advance,
Octane renders (makes 2d photo-realistic pics) using 3d geometry ex polygon meshes (.obj format) imported from modelling apps like
Sketchup or Blender.
It has nothing to do with video editing or compositing as such although you might use the rendered images or animation sequences produced by Octane in a video.
you can render images in octane then bring them into AE
but the workflow doesn't go the other way...
When using AFS, what Color space to use in the Video tab? For example, why RGB24 and why not YUY2 or vice versa?
Planning to test it with ProCoder 3, Squeeze 7 and maybe TMPGEnc. Do different encoders require different color spaces?
Not sure about specific color space specs, but can report that AFS works beautifully with Squeeze 7. I use it many times daily.
The different color spaces allow you to match the output of the frameserver to the target application's color space. A perfect example is serving to HC Encoder. It only accepts YV12 and YUY2, so RGB24/32 wouldn't work at all. Plus, if the target app only works with one color space, for example if it imports any footage but converts everything to RGB24, then you would be introducing an unnecessary color space conversion by sending it YUY2 footage.
O.k i got it!
Plus, if the target app only works with one color space, for example if it imports any footage but converts everything to RGB24, then you would be introducing an unnecessary color space conversion by sending it YUY2 footage.
So now the 10k $ question is how to figure out what color space app X works with. I have not yet found any information about it regarding Sorensson or ProCoder. They don't really print those thing with large letters. (Or, i have not found the right place yet..)
Well, Squeeze just accepted a YUV 4:2:0 source file and output a YUV 4:2:0 MOV file. So it seems you can feed Squeeze whatever you want from Pr. The only caveat is that I don't know if Squeeze is internally converting the YUV video to RGB before encoding it as YUV again. I don't see any logic in doing it that way, but I'm not a software engineer.
at me with ProCoder works very well
trying to get this afs workflow up and running
does anyone know if handbrake accepts watchfolders?
i keep setting the 'source' to my watchfolder
and AME begins to generate the avi intermediate file
but then just shows a green check mark for completed
and handbrake never gets started...
(the reason for this is to be able do 2pas vbr high 4.1 bluray exports
to see if they load up into encore without needing to transcode...)
thanks for any help,
up and running with afs and squeeze 7
however, i am only getting 1.80 fps video transfer rate
some scenes are heavily effected some are just straight footage
all of which are avchd 1920x1080 22mbit interlaced
on win7 cs5.03, quadro4000, 24gbram,many hdd's, i7 930 at 2.8ghz
does the fps transfer rate seem too slow
(i read somewhere that squeeze is not that good at multi threading
and it kinda shows: cpu is nowhere near 100percent usage
like when exporting out of media encoder...)
any help is appreciated...
There is glitches in exported video using advanced frameserver.
I confirm this, I'm getting major headaches to get a proper frameserver for CC. The only workarounds are to export it as Lagarith or any other lossless codec and then compress it with third-party program.
For the record, I use AVCHD 1080i50 workflow and the output video has major glitches due to wrong frame ordering. I've tried all kind of settings in Premiere and AFS, nothing seems to help.
I have glitches only in audio, not in video.
I use AFS in CC to TMPG5 and it works just fine.
If you got issues you need to tweak the 3rd party software.
Turned out that the After Effects' multithreading option caused the glitches. I turned off Render multiple frames simultaneously in After Effects and the problem seems to be solved.
For the record, I use MeGUI with x264.
However, I'm getting weird cracking noises on the audio that don't appear in the project itself. The workaround is to export the audio as uncompressed PCM and then encode it to AC3, but what can I do to avoid the issue?