Q: Proxy Resolution Problem
-
May 22, 2011 3:26 PMby Alejandro Grigera,The clip proxy file I'm trying to create is even smaller than the one FCS uses as default. Yes I want to create the file to export for the web but the system is taking to long to create both files so I'm trying to use the same one for both purposes. Don't know what you mean by a ProRes file since I'm using a H264 for proxy not a ProRes.
-
Jun 2, 2011 9:20 AMby Alejandro Grigera,I'm not confusing the proxies but It could be a nice idea to use the Edit Proxy to create the file I need to send to the web, I hope that setting let me choose a different resolution, I'll try that later.
This solution will help me save time by creating the file as soon as the clip reaches FCS but it will not reduce the amount of processing I need to create both files, If I could use the clip proxy I would only process the file once saving processing time. Even worst, I have some files I don't need to transcode or even create proxy since they are already in the final format and in those cases I'll loose even more processing time to generate the edit proxy I will never use.
Thanks
-
Jun 2, 2011 10:41 AMby Chris Summers,Hi,
How to you plan to deliver and use the clip proxies for web delivery? Save As in QuickTime?
Yes Edit Proxies will do it as well, but then ALL your edit proxies will be that res and you wont be able to use Edit Proxies (as they should be used) in your workflow later on.
It strikes me that perhaps your hardware is topping out under the load of what needs to be done. If you're needing to reconfigure the basic elements so drastically it will only get worse as time goes on.
What system and hardware spec are you running?
-
Jun 2, 2011 11:34 AMby Alejandro Grigera,What I need to do to delver the clip proxies is to create the clip proxy in the right codec (which i can do) but the problem is the resolution that FCS won't let me take it to 460x380. If your question is where do I get the file is as simple as finding it in the proxies.bundle and send it to an FTP server (which I can also do with a script)
I'm not using Edit Proxies and I don't think I'll be using them in the future so thats not a problem.
I'm sorry but I can only guess what you mean by "topping out" since English is my second lenguage. I understand It sounds like I don't have enough power to handle all the trancodings but I do, right now I have a dedicated MACPRO (8-core) to process all the transcoding from this FCS and another to handle things in another FCS. In the very near future I'm going to be able to make a 4 MACPRO (4x8-core) cluster using Qmaster to handle both FCS and a lot more things to come.
Yes, I know... I'm worry to much about details like saving 1 transcoding job out of 100. I get that all the time.
Anyway I get a lot o preasure from the web guys to speed up the process of uploading clips to the web as soon as our TV Station put them on the air, so I have to squeeze all I can from all points of the process.
Thanks for the help
-
Jun 2, 2011 12:20 PMby Chris Summers,Right:
If your question is where do I get the file is as simple as finding it in the proxies.bundle and send it to an FTP server (which I can also do with a script)
- you sir are a brave man to be going in there. well done, I salute you. nice solution. have you had any corruption issue with the bundle?
I'm not using Edit Proxies and I don't think I'll be using them in the future so thats not a problem.
- if you're absolutely sure. I've seen needs change over time, don't block yourself if you don't need to.
No Problem. Yes, I'm referring to the processsing power. Please remember disk speed and I/O speed is as important as CPU power when rendering.
Ok, so really the issue is you can set a custom frame size.
So, you made a custom compressor setting in Compressor.
Added and mapped this setting in FCSvr settings.
Set this to be the setting for clip proxies.
It transcodes, but defaults to some other frame size, is that correct?
If so, what happens when you bypass FCSvr and run the clips directly through Compressor with that setting?
-
Jun 2, 2011 12:35 PMby Alejandro Grigera,Never had a corruption problem so far (and I've done even worst things in there but I can't talk about it cause I think is illegal in some countries )
About disk speed I forgot to mention the XSAN which is the heart of all the system.
Yes everything is correct, it transcodes but for some reason the clip proxy is always 320x240 and if I try the setting manually in compressor you get the right frame size (460x380). Like I said in the first post this is being going on forever even in my first FCS ver 1.1.1 but is not the first time someone talk about it in the forums I was hoping someone came out with a wrong setting somewhere.
Best regards
-
Jun 2, 2011 1:02 PMby Chris Summers,If it works in Compressor but not FCSvr then FCSvr is using the wrong preset.
try to recreate a brand new custom setting in compressor.
re-map / link in FCSvr Admin panel.
reset the proxy codec selection.
let us know.
c.
(EDIT: I'm just setting up a test quickly, I have a feeling it's something simple i just need to see it in front of me.)
-
Jun 2, 2011 1:20 PMby Chris Summers,Apologies if you've done all this already:
Compressor:
Create or check your custom setting : "My Custom Compressor Setting 460x380" (for e.g.) ((note - this does not seem to be 4:3 what is this custom resolution?)
FCSvr:
Admin Panel > Transcode Settings > Create > Name: "My Custom FCSvr Setting 460x380" > Parameters > Compressor Setting > "My Custom Compressor Setting 460x380" > Save Setting. (here you are mapping 2 separate elements. a record in FCSvr to a compressor preset.)
Admin Panel > Transcode Settings > search for "My Custom FCSvr Setting 460x380" > Edit > Modify > Add All. Save changes.
Log out and back in to FCSvr (needed for the new setting to show in prefs.
Admin Panel > Prefernences > Anylyze > Clip Proxies > Admin Panel > "My Custom FCSvr Setting 460x380"
hope this helps.
c.
