Conversion to M4A performs poorly with output directory on slow network drive
#1
Hi,

Using 3.01 on Win7. I notice that my radio downloads result first in a .dash.m4a file which then gets converted very slowly (~1.5x) to .m4a.

Conversion in older versions was much quicker. Used to take 10 mins or so to process a 3 hour audio file. Now taking forever!

Am using following command:

get_iplayer --type=radio --get "<what>" --nopurge --tag-isodate --radiomode=good --output "<where>" --file-prefix="<firstbcast>_<name>_<episode>"

Can I speed up the conversion process?
#2
Conversion speed is a function of system resources. It has nothing to do with get_iplayer itself. An overloaded CPU can slow down ffmpeg during conversion, but a slow disk - particularly a slow network disk - can have a much bigger effect. Converting at 1.5x is of course terrible, but so is 10 mins. A file that size should normally convert in seconds. Whatever is slowing you down is unique to your machine, so unless somebody can replicate the same terrible performance, there isn't much help we can offer.
#3
Thanks. My output argument is a network drive which will win no speed races, and for some reason write performance has dropped even lower lately. I am now get_iplayer-ing to an ssd and copying to the network only after the download is complete.

Much better idea. Conversion now happening at ~800x.


Possibly Related Threads…
Thread Author Replies Views Last Post
  Made a typo in output directory value - where did my file go? pwl2706 1 2,273 11-10-2018, 02:09 AM
Last Post: kamelne
  Homes Under the Hammer PVR (in HD) saving to my network share. Is this possible? cmr_iplayer 1 2,302 19-09-2015, 11:23 AM
Last Post: dinky
  Need to change output directory tonybb66 14 20,262 09-11-2014, 01:54 PM
Last Post: ZuluKolo
  Cannot see mapped NAS drive since 2.90 update Saliesbuzz 1 2,133 06-11-2014, 09:38 PM
Last Post: dinky