Megui sugestion resolutiion md162/27/2024 As you can see, the audio is detected correctly when the script is checked, but when the job is run, MeGUI says there's no such function as FFMS2. Here's the relevant section from the log file. Why it's auto-loading plugins when the script is added to the audio section but not when the audio job is actually run, I have no idea. Using LoadPlugin() in the script to load the plugins manually cures the problem and the audio jobs run. When I try to run the job, MeGUI complains about missing functions.Īfter a bit of experimenting I'm sure the problem must be that MeGUI isn't auto-loading plugins from the installed Avisynth plugins folder when running audio jobs. It's added to the job queue without complaint. When trying to encode audio via a script, the script loads into the audio section without error. The problem only occurs when using MeGUI's portable Avisynth+, not when using the installed Avisyth 2.6. Is this going to be an XP thing? Or maybe an Avisynth+ thing? ![]() Please enlighten me a bit more dear GURUS, i can safely say i have a lot to learn from guys like Zathor, Ligh, dark shikari and others I am still trsting this may be there are other variables involved as well. But this feels pretty bad and awkward when a sort of untidy still in initial stages of development app like handbrake beats it in similar that sort of environment I would say this has to be looked into ( i am no specialist so apologies beforehand if i sound like a big mouth )īut have been using megui in various environments and can say disk usage affects adversely, i didnt mind this thing before as i used to think may be its how the source is or may be someone else is sucking the resources. I am one of the users in an offshore RDP with intel xeon processor and 64gigs of ram, with like 6 or 7 usersĪll doing their video encoding, editing or god knows what else.Īs soon as disk read write increases megui encoding goes down like anything and becomes less than 1/4th of the original speed. You are correct and i can confirm in normal environment megui is definitely more efficientĪctually my issue has been a bit different ( as i mentioned a few posts before ) Personally i love megui but this speed cap has forced me to look for other applications I mean both are x264 or x265 based but ids there any specific drawback of using handbrake. Secondly is there any major difference in the way handbrake processes a video and megui does ? How can i hard code a custom subtitle file something like adding a small text which displays for a few frames So after so many years of using MEGUI, i am onto handbrake and viola no slow encoding issues with it, wonder why that is ?īeen trying to get all my profile settings to it but there are a few I am unable to figure out You are right seems like high amount of reading and writing on the disk even if they are RAID ( 1 or 2) isnt letting things peak, thats the only thing i could deduce considering enough ram is available. That may start by reading the source from the media. ![]() When x264 doesn't use the majority of available CPU time, it's usually a sign that it waits for the video to be delivered. I guess his question remains why he feels the CPU not utilized perfectly. ![]() So the AviSynth filtering may not be the bottleneck. Well, this script doesn't contain any CPU intense filters.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |