Closed tconnz closed 7 years ago
This is the normal expected behavior, moving the MOOV atom only occurs after tagging takes place (due to issues with playback that come up if you tag after moving) and deluge, like all the other download client scripts, does not tag
If you'd like to move the moov atom and just tag after the fact you are free to do so. Simply have FFMPEG move the moov atom instead of using QTFastStart by adding -movflags, faststart
to your postopts parameters in autoProcess.ini
Cheers for the speedy response! P.S. Do you have a method of accepting donations/beer money?
No need to do that but if you'd like I have a PayPal and can always use beer money! It's tehpsyc@gmail.com
Sent from my iPhone
On Aug 5, 2017, at 16:59, tconnz notifications@github.com wrote:
Cheers for the speedy response! P.S. Do you have a method of accepting donations/beer money?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.
Legend, cheers :)
Much appreciated! Thanks again
If you'd like to move the moov atom and just tag after the fact you are free to do so. Simply have FFMPEG move the moov atom instead of using QTFastStart by adding -movflags, faststart to your postopts parameters in autoProcess.ini
By doing it this way we shouldn't run into any playback issues, correct?
You might, the whole reason I don’t do this as the default is occasionally after tagging if you move the MOOV before tagging you’ll get seeking and playback issues, but it is very rare
From: JySzE Sent: Sunday, February 18, 2018 2:46 PM To: mdhiggins/sickbeard_mp4_automator Cc: Michael Higgins; State change Subject: Re: [mdhiggins/sickbeard_mp4_automator] delugePostProcess.py doesn'trelocate moov, manual.py & postSonarr.py does (#777)
If you'd like to move the moov atom and just tag after the fact you are free to do so. Simply have FFMPEG move the moov atom instead of using QTFastStart by adding -movflags, faststart to your postopts parameters in autoProcess.ini By doing it this way we shouldn't run into any playback issues, correct? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.
Hi,
Firstly, a huge thanks for mdhiggins for the excellent scripts, my Plex setup would have been lost without them!
Have been using manual.py & RSS + torrent feeds for years, finally switched over to Sonarr & Radarr and just today go things working again.
I do have one query:
Should deulgePostProcess.py still relocate the moov atom data just like manual.py or postSonarr.py?
I've noticed without changing anything in autoprocess.ini, the delugePostProcess converts the files to MP4 as normal but doesn't relocate the moov data. Once the script hands the file back to Sonarr, Sonarr renames and moves the file to a NAS , then fires the postSonarr.py script goes back and the moov data is relocated.
Initial conversion is done on an SSD, then the file is moved to a NAS , and then the moov ataom data is relocated. Hopeful I can get it to run in the first step so its on the SSD and not across the LAN to the NAS :)
Anyone have the same experience or complete opposite?
Here's the info.log excerpt: