1 Jan
2016
1 Jan
'16
2:19 p.m.
Am 01.01.2016 um 02:42 schrieb Leslie Hartmier via DCPomatic:
Is there a consideration of being able to 'turn
on' the master server as an encode server from within DCPoM? I didn't catch on
until I looked at the log after my three computer test, to see that it had 22 lines, as
opposed to the single machine one that contains thousands. I simply ran the encode server
on the master as well as DCPoM itself, and that is not a problem (just put the encode
server in the Startup folder), but I was simply wondering.
Not sure if I understand what you're after, plus I have zero experience with the Linux
versions.
Normally, DCP-o-matic master GUI will also do encoding. As such, there is no need to start
the encode server on the same machine. May be useful if you also run the DOM-GUI on other
network machines as well and want to keep your main machine active as a encode server
conveniently.
For some people using machines with a very high number of logical cores (e.g. dual Xeon
machines), there used to be a considerable increase in encoding speed when having the DOM
GUI + a local encode server instance working at the same time. As Carl did some optimizing
around this recently, I expect this benefit now to have vanished or become small. Might
still be worth a try.
In current versions, you can deactivate DOM-GUI J2k encoding in advanced prefs, so that
only encode servers will receive encode jobs. That could be handy in very special
situations.
Ah, yes, CLI und GUI encode server versions have different ways to use prefs/encoding
parameters, so the CLI is a bit more flexible in that respect, as you can give it command
line parameters.
Finally, is there any way to find out what the overall
fps for the encoding was (not necessarily per encoding server, although that might be
neat) being stored in the log? I understand that I can simply calculate number of frames
divided by number of seconds that encoding took, but I like to keep the logs to determine
how it's all doing.
Yes, might be very simple for Carl to add this to the log writing when a DCP creation
process has ended.
- Carsten