Hi Greg,

On 06/11/2012 14:22, Greg Logan wrote:
On 12-11-06 08:21 AM, James S Perrin wrote:
Hi,
     Does anyone have Galicaster (1.2.1) working with MH1.4/Trunk? We are
able to schedule recordings and they are captured on the CA (VGA test
with white noise) but when the (default) workflow has finished there is
nothing to see or hear. The Operations show that capture has has been
skipped, but ingest and rest of the operations all succeeded - though
they report no tracks found in the log.

     Same CA works with 1.3 so it could be our inexperience setting up MH
that is the problem.

While I'm not familiar with the way Galicaster does its ingest, we did
change the XML namespaces on the mediapackages in 1.4.  Your symptoms
exactly match what happens when an older mediapackage is ingested into a
1.4 core, so I suspect that's what's going on.  We've discussed this a
couple of times in the dev meetings, but we haven't come up with a
proposal to handle this case yet.  It's simple to fix (I do it with a
one line sed script in my study system), just a matter of someone
writing up the namespace mangling that's needed!

It probably went over my head at the time, still so much too learn. Gives us a starting point even of we just fudge Galicaster for now. Is there an issue for this I can't find one?

Thanks,
James


--
------------------------------------------------------------------------
  James S. Perrin

  Media Technologies Team
  Devonshire House, University Precinct
  The University of Manchester
  Oxford Road, Manchester, M13 9PL

  t: +44 (0) 161 275 6945
  e: [email protected]
  w: www.manchester.ac.uk/researchcomputing
------------------------------------------------------------------------
 "The test of intellect is the refusal to belabour the obvious"
 - Alfred Bester
------------------------------------------------------------------------
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to