Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Can a Compressor 3.5 droplet work with Virtual Cluster?

  • Can a Compressor 3.5 droplet work with Virtual Cluster?

    Posted by Phil Incorvia on February 8, 2010 at 8:01 pm

    Hello All,

    I’m doing a lot of work with the 5Dmk2 and transcoding with droplets is great. However, whenever I submit a droplet to use the virtual cluster I’ve set up, Batch Monitor shows it as ‘Waiting’.

    I’ve ‘waited’ for up to an hour with no results. Tried it with a batch of one video, three videos and my ideal of 16 videos. Same result. Also tried with a virtual cluster of 4 and 6 nodes. Nuthin’.

    Is anyone having success at using a droplet with their virtual cluster?

    Mac Pro 2×2.8 Quad Core, 16GB RAM, OS 10.6.2… what else?

    Thanks!
    Phil

    Scott Houston replied 12 years, 6 months ago 4 Members · 3 Replies
  • 3 Replies
  • Mikko Palo

    May 19, 2010 at 6:56 am

    Bump.

    I’ve the same problem. Can anyone help, please?

    Mikko

  • Paul Golden

    October 29, 2010 at 5:48 pm

    Having the same problem here as well. Dropped a 1gb file into a droplet assigned to my computer’s 8 core cluster and nada! Just waiting…Have stopped and started Qmaster services. No luck

    Apple…. help?

  • Scott Houston

    November 8, 2013 at 9:08 pm

    To bring this thread 3 years forward… 🙂

    Same thing is still happening using Compressor 4.0.7.

    It clearly seems to be a bug as I did an A-B test without restarting any machines (host or clients) in the cluster and tried to submit 8 files by dragging them to the droplet.

    Within a few seconds the batch appeared as expected in Share Monitor, but was stuck “waiting.”

    After a few minutes I manually created a batch in Compressor using the exact same 8 files, with same settings and same destination and submitted it directly from Compressor.

    After a few seconds that batch also appeared in Share Monitor and immediately started processing correctly.

    After it was finished successfully I then thought that maybe the “waiting” batch would then start up since things had gotten started in the queue.

    No such luck – it just continued to hang with the “waiting” status.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy