AtomicParsley (Windows) crashes when writing some descriptions

Philip Gardner philip.gardner at asgardpublishing.co.uk
Tue Sep 20 06:25:37 EDT 2011


I am finding the same. It only happens on some downloads.
PhilG

On 20/09/2011 07:44, Kevin Reilly wrote:
> As per the subject, at least I think that's what's going on.
>
> The last two weeks' episodes of Click, and this week's Spooks (pid
> b0153b3h), were causing AtomicParsley to hang on this Windows 7 64bit
> installation, resulting in raw code 65280 being written to the log when
> the crashed AtomicParsley was closed. The resulting MP4 file was usable,
> but had no tags applied.
>
> I have managed to work around the problem (at least for Spooks; I've not
> had a chance to try it with anything else) by commenting out the push
> commands in the following block of the main perl script:
>
> # add descriptions to audio podcasts and video
>   if ( $tags->{is_video} || $tags->{is_podcast}) {
>     # push @cmd, ('--description', $tags->{description} );
>      if ( $opt->{tag_longdescription} ) {
>       # push @cmd, ( '--longDescription', $tags->{longDescription} );
>      } elsif ( $opt->{tag_longdesc} ) {
>       # push @cmd, ( '--longdesc', $tags->{longDescription} );
>      }
>    }
>
> Obviously the next step is to comment out each push command in turn to
> determine which one, or ones, are actually causing the problem. My gut
> instinct is that it's one of the long descriptions, rather than the
> regular description, that's causing grief although that is just a guess.
> The odd thing is that the long description is also added to the file in
> the 'lyrics' field and causes no issues, suggesting it's NOT just a
> problem whereby a particular string of characters is causing difficulties
> when read by AtomicParsley. Perhaps it's just a length problem? Buffer
> overflow?
>
> I'm going to be away from the PC for the next ten hours or so, and unable
> to do any more testing, but hopefully this may assist anyone else who's
> seeing similar behaviour, and perhaps lead to an explanation and/or a
> better work-around?
>
> get_iplayer was installed using the latest (4.4) Windows installer.
>



More information about the get_iplayer mailing list