Here we go again! \ud83d\ude42 As I said before, this version of the patch is much better. Now you can specify some options like use or not the “cutlist” and you can choose to output the result to another file or not.<\/p>\n
I also changed the way the whole thing is done: before it was an entry in mythprotocol to start\/stop the transcode process. Now I’m dealing directly with the JobQueue, so you can remotely add any Job on the backend, not just the transcode task. It’s important to say that everything is prepared for SystemJobs, UserJobs, etc.. but<\/strong> here we have a HUGE<\/strong> security problem<\/em>: letting an user remotely add a SystemJob will open an way to a malicious user add a malicious job to be run on your computer..to this is why I didn’t code anything about this.<\/p>\n Tomorrow I’ll start doing things inside GMyth<\/a>:<\/p>\n I will also think about a good solution about getting the progress of the task inside the database. Maybe another patch ( [1] ) to use xml+http (avoiding the use of SQL queries).<\/p>\n\n