Am i right in thinking MEC uses ffmpeg for all encoding, so supports all the formats ffmpeg does?

I understand that the chunk-by-chunk encoding is good (and pretty revolutionary) and I think that's the main appeal over the software over using ffmpeg directly - does that sound right or have i missed anything?

I'm also looking forward to giving the control panel a go.

I'm currently thinking of setting up a failover pair to act as the 'master' servers and then a cluster of say, 10 old machines I have lying around all maintained by 'heartbeat' (popular linux clustering software).

I'm keen to hear any more thoughts - do you have any idea how many clients are supported by one master machine? Would it be in the tens, or hundreds?

What sort of solution is recommended when a master reaches a limit? A master of masters?

I may write some documentation on this with the replies

hey thanks,

your understanding in chunk-by-chunk encoding is right, in the future there will be enhancemends to build a failover and loadbalancing encoding solution. without any extra installation requirements for clustering.

i have made some tests with an mpeg2ts stream with 15Mb/s with one server and 4 clients running in the network,
the performance over the network(1Gb/s) was round about 4-6%, the CPU performance from the server was round about 8-12% on a intel core 2 duo 6300 1.86Ghz and 2GB Ram.

some correction from the previous post, i dont mean "performance" in the previous post i mean "usage"

The distributed nature, of nodes and files is definitely the best feature, as I say.

Although some companies might not like to do it I really like the idea of distributing jobs through an entire company.

Say you've got 1000 machines in your business and a lot of the time they're probably idle, people are doing word processing and things - nothing too heavy.

Imagine if you could use the spare processing capacity as an enormous encoding hive? No extra investment for massive gains (albeit with a variable maximum capacity)

So a focus on a quick-to-install windows client that could perhaps be deployed as an MSI across a Windows network that would only use spare CPU capacity (Rather than fighting for resources) would eb a really good next step once the core features are stabilised.

I've got some free time in a month and i'm really looking forward to getting this running!

that is a great thing i mean
next i'am working on is an autoupdate feature for the Media Encoding Cluster, this will be very helpfull in a distributed environment to keep the Software up to date