On 30/01/2013 19:15, alan wrote:
Does this happen when you run atomicparsley on /any/ mp4 file? or just
this particular one? If it's all, then I'd try reinstalling
atomicparsley:
Jon - happens on any file, and continued after reinstalling atomicparsley.
I should have said at the outset that this was on a newly setup vps
running a minimal version of Ubuntu 10.04. In any case, I've now
installed a more complete version of Ubuntu 11.04 on the vps and got the
same problem. I think I'll have to give up on the vps.
The progress display only gets up to 2% or so for small files like
"Bells on Sunday" since it only takes a few buffer writes to complete
the temp file, so it's possible the tagging phase was completed. Were
the "-temp-" files roughly the same size as the original .m4a files and
were they playable? And did they contain metadata tags (try Right Click
-> Properties -> Audio in Nautilus or AtomicParsley <file> -t)? If the
answers are "yes" and "yes", that would narrow down the problem to point
where AtomicParsley attempts to replace the original file with the
tagged version. You could take the AtomicParsley command line from
get_iplayer's verbose log, add quotes around option values as necessary
and run it from the command line or a shell script to see if you get
different results without --overWrite in the command line. If so, that
would confirm the problem as being related to replacing the original
.m4a file. I don't know why that would hang just because you're on a
VPS. FWIW, someone reported a similar problem quite a while back:
https://bitbucket.org/wez/atomicparsley/issue/16/ap-freezes-on-creating-temp-file
If you can make a debug build of AtomicParsley, you might get further
than he did. Or you can just forget about the VPS and use that time for
more enjoyable things.
_______________________________________________
get_iplayer mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/get_iplayer
