@cayars said:
I don’t think this is a good idea at all. Your’re running it on your personal computer and you mentioned gaming which can be CPU intensive. You’re not going to want both running at the same time.
Just do like everyone else and only run the scripts when you’re not gaming or doing anything CPU intensive. This way you can just minimize the box that pops up.
BTW, there is a new version released with better performance.
Really, I understand where you’re coming from but most of the AAA games I play aren’t CPU-intensive anyway. And it’s not like I know when Sonarr picks up a certain release, sends it to SAB, and SAB post-processes it afterwards to send me a cue that I shouldn’t be gaming at that point in time. I would think that my overclocked CPU can handle converting few videos and running my not-so-CPU-intensive games at the same time.
I just want to have an option between disabling the console and re-enabling it when I like to.
Thanks for the update. Do you happen to have any plans posting the new release in the non-Plex Pass forums?
@Collisionc said: @kevindd992002 It’d be a lot easier to just use the full sickbeard_mp4_automator and use the sabnzbd integration, if you want to remove the command prompt from coming up.
I was trying to use that initially but wasn’t really sure on how to go about it. I was also under the impression that @cayars’ modification to the sickbear_mp4_automator script makes it better in terms of converting everything to mp4.
Cayar has made the process more user friendly, but you can do everything with the sickbeard_mp4_automator that you can with Cayar’s script.
Yes and no. Tagging is different. The original mucks up Plex if you have the personal agent since it leaves a lot of embedded junk in the files. I also modified/added new logic for audio that works much better with Plex. Also I reworked the internals so we get much better/higher quality encodes. I also handle the MOOV atom differently if I recall.
Basically tweaks to work better for long term storage.
@Collisionc said: @kevindd992002 It’d be a lot easier to just use the full sickbeard_mp4_automator and use the sabnzbd integration, if you want to remove the command prompt from coming up.
I was trying to use that initially but wasn’t really sure on how to go about it. I was also under the impression that @cayars’ modification to the sickbear_mp4_automator script makes it better in terms of converting everything to mp4.
Cayar has made the process more user friendly, but you can do everything with the sickbeard_mp4_automator that you can with Cayar’s script.
Yes and no. Tagging is different. The original mucks up Plex if you have the personal agent since it leaves a lot of embedded junk in the files. I also modified/added new logic for audio that works much better with Plex. Also I reworked the internals so we get much better/higher quality encodes. I also handle the MOOV atom differently if I recall.
Basically tweaks to work better for long term storage.
Is this true for the old and new version of your script?
Fully on the older one. Partial on the newer one. I say partial because it depends if you set it up to use software or hardware based conversion. Can only do so much with hardware.
@cayars said:
Fully on the older one. Partial on the newer one. I say partial because it depends if you set it up to use software or hardware based conversion. Can only do so much with hardware.
Ok. Dos that mean the older one is fully software-based?
Yes the older one will not use any hardware encoding even if present.
The new one can/will use hardware if present and the flag is set in the ini file.
I’ve tried all sorts of things to try and hide the Python window when the script runs but I can’t really get it to run silently. I cannot do your suggestion of running the scripts when I’m not gaming or just idle because everything is automated. The script runs after SAB/Sonarr downloads the tv show file so I don’t really know exactly when that is happening.
I’m simply browsing the Internet for a few days now and the window popping up is very irritating Can you please help me out here? I’m at a lost already after countless hours of research.
That’s the first thing that I did, change the extension of manual.py to pyw but it didn’t totally fix the issue. There’s still a cmd prompt window that shows up.
That’s the first thing that I did, change the extension of manual.py to pyw but it didn’t totally fix the issue. There’s still a cmd prompt window that shows up.
Ok. Would you mind me asking the reason why running scripts silently is not recommended when logs can be saved in a text file anyway? No pun intended, just curious
Also, I’m also sometimes experiencing the issue describe below:
The original source file is “The.59th.Annual.Grammy.Awards.720p.HDTV.DD5.1.HEVC.x265.mkv” but the resulting converted file becomes like this “The.59th.Annual.Grammy.Awards.720p.HDTV.DD5.1.HEVC.x265(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2)(2).mp4”. Why is this happening?
Hi
The (2) indicates, that it is redoing The.59th.Annual.Grammy.Awards.720p.HDTV.DD5.1.HEVC.x265.mp4
because it is still in the convert folder, if it is moved after the first run, then you will not see this.
So every time the script runs, it will recode the file and add an extra (2) to the file name.
So your file has been recoded a lot of times.
Thanks, that’s what I thought. I had to make the source folder and the destination folder of the script the same so that Sonarr can post-process the converted file properly. I think I know what’s causing the re-conversion process, it’s the extra scheduled task that I made that would server as a “failsafe” task. I’ll disable that and see if this problem goes away.
Can you please help me out here? I’m at a lost already after countless hours of research.
