![]() ![]() #Mcebuddy quicksync how to#(, 01:25 AM)sub Wrote: (, 01:00 AM)spin35 Wrote: If anyone has any suggestions on how to automate the removal of pre and post padding, I'm all ears. If anyone has any suggestions on how to automate the removal of pre and post padding, I'm all ears. I know that MCEBuddy has got Start and End trim options in the conversion task, but you need to review the completed file before you can trim it. #Mcebuddy quicksync manual#txt file option to generate an edl file that I can use to trim off the pre and post padding, but I don't think this reduces the manual workload very much other than saving me having to scribble down the times while reviewing in VLC in order to type them into the Trim.Bat. I'm thinking that I might be able to use the Comskip. Currently this is mandraulic, using VLC with a a add-on to show the elapsed time on the screen to determine the Stime and Ftime to type into a batch file that has an ffmpeg line with -ss and -to parameters. The last part of my process before inserting into plex is to trim off the Pre and Post padding from the recordings so as to just have the program from start to finish in the Plex server. The syntax for the matching was derived from the MCEBuddy advanced doco that was explaining how to match show names. The fact that MCEBuddy reads the V5 xml files was an accidental discovery, and the fact that the Channel Name Match field reads the in the xml was all new to me. I've struggled to find coherent information to make things work the way I wanted it to. I realise that this post is more about MCEBuddy and Comskip than NextPVR, but I thought this might help the community of NextPVR users. txt file that allows you to manually adjust the ad-breaks in the show. The discovery that there is a -w debug screen option is great news as well as the option of running comskip with a previously generated. ![]() The Comskip Tuning Guide is a great help. I'm now in the process of tweaking the ini files to get better results for SBS and the other stations. The last task is the original that I was using with V4 but which now has the channel match set to * ~ABC* ~SBS* with comskip on and the comskip.ini for the commercial stations. I now have a conversion task for SBS with the channel match set to SBS* and the Remove ads is set to Comskip and the Comskip INI line points to an. This now lends itself to having conversion tasks with different comskip.ini profiles to account for the difference between some channels e.g SBS and the other commercial stations. įor the ABC task I set the Channel Name match to ABC* so that it will process any recording with a channel that begins with ABC, then set Remove ads to "no", so from now on any ABC recordings just get transcoded. The discovery that MCE buddy reads the XML file means that I can now have multiple conversion tasks in MCEBuddy which are tailored to different channels, without the need for PostProcessing.bat. I had been toying with the PostProcessing.BAT in NextPVR scripts area but I wasn't getting an elegant solution. ini file which sometimes resulted in bits of programs going missing - particularly from ABC and SBS recordings. The problem with at is that Comskip is done to all recordings with a common. #Mcebuddy quicksync mp4#With NextPVR V4 I had set up a conversion task in MCDBuddy that took all recordings from NextPVR, ran Comskip over it, then transcoded it to X264 MP4 for insertion into my Plex Media Server's file tree. The problem that I was trying to solve was to prevent recordings from the ABC being processed through Comskip. What I've only just discovered is that MCEBuddy reads that XML data. One thing that I noticed when I upgraded to V5 was the presence of an XML file with each recorded TS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |