Selecting elgato format prematurely moves files to show subdirectory, corrupting *.mp4

[GoogleCodeExporter]

What Version of iTiVo?
1.7.5
What Version of MacOS X?
10.5.6
What download format did you select?
Elgato Turbo *
What steps will reproduce the problem?
1. Select "Create subdirectories for shows"
2. Select Elgato Turbo.264 codec (Tried iphone)
3. Encode show

Please provide any additional information below.

During phase 2 (encoding) iTiVo seems to wait for the elgato software to
return from encoding. about 80% of the time, iTiVo does not wait for elgato
to finish encoding before moving the *.mp4 file to the show subdirectory,
thus creating a corrupt file. It is so close that it seems to wait almost
long enough (a minute or two left to encode) but decides it has waited
around long enough. (or iTivo gets jealous over the 60FPS encoding rate)

As an enhancement if the encoding could be done asynchronously that would
be ideal. The flow would be like this:

1) Download mpg file directly into subdirectory created for the show
2) Do additional processing (subtitles, etc)
3) Send encoding job to Elgato (don't wait for return)
4) Move on to downloading next mpg

Even if the next show downloads faster than the encoding is complete, the
show will be added to the elgato software queue for processing next. The
only downside is how to delete the *.mpg after processing.

Original issue reported on code.google.com by cliveb@gmail.com on 6 Mar 2009 at 8:21

[GoogleCodeExporter]

There is an issue with the fact that itivo may have to do additional processing 
after
the conversion is completed (like adding to itunes, adding metadata tags, or 
running
whatever commands are issued), as well as cleaning up a lot of the temporary 
junk
created to support all that stuff.

  I do agree it would be nice to be able to 'just hand it over to elgato and move on
to the next download', but it would require a pretty extensive change to the
codebase, which right now I'm not so excited to do..  :(

  However, the premature move to subdirectory was an issue related to a bug with the
elgato processing, which should *hopefully* be fixed in the current beta.  Still
working with someone to debug it all (I don't have the damn device) but I think 
we
have a good handle on the issues now so it shouldn't be doing that in the beta 
anymore.

Original comment by yoav.yer...@gmail.com on 14 Apr 2009 at 3:12

• Changed state: Accepted

[GoogleCodeExporter]

I believe this is now fixed..
  please re-open the bug if it is not...
  (can't test myself)

Original comment by yoav.yer...@gmail.com on 4 May 2009 at 3:41

• Changed state: Fixed

[GoogleCodeExporter]

Yup, fixed. Thanks. :)

Original comment by cliveb@gmail.com on 4 May 2009 at 7:26