View Profile
View Forum Posts
Private Message
Hello guys,
I've decided to start from beginning because many things has been scattered in my mind. So, i need to know how to make all parameters and sittings from A to Z
+ Reply to Thread
Results 1 to 20 of 20
-
-
Let me make sure I understand your question.Originally Posted by yaston
Hello guys,
I've decided to start from beginning because many things has been scattered in my mind. So, i need to know how to make all parameters and sittings from A to Z
You want someone to talk you through all the possible settings for a GUI that uses aften, avidemux, avisynth, besplit, dgindex, eac3to, ffmpeg, flac, lame, lsmash, mkvmerge, mp4box, ogg, pgcdemux, qaac, tsmuxer, vobsub, x264, x264 10 bit, x265 and xvid -- among others?
Not going to happen.
Best to start experimenting. Many of those apps have help files.Last edited by smrpix; 8th Jan 2015 at 14:31.
-
But how can i choose the right version? How can i use them all?
-
Start with Handbrake and learn that first.
Learning parameter options requires learning the meaning behind them & importance of those choices, first.
Have to learn to walk before you can run.
Scott -
100% agree.Originally Posted by Cornucopia
-
Well I started with Megui but I already had a background via virtualdub x264vfw and before that a general compression background. I never tried Handbrake.
All I can suggest to OP is describe what you wanna do at the moment and we'll help you thru it. You'll learn a lot when you accomplish your first task, you'll learn more with your second, third and so on. With about your 10th project, you'll be able to do most of it without needing any help.
But don't try to cram everything in at once, it won't work. Getting a background on the topic is one thing but nothing beats learning via application.
I didn't give a shit about 90% of the things smrpix listed in post #2 at first, but as my tasks grew more complex and demanding I had to learn more, even that dreaded avisynth that I couldn't produce a single script with without running into an error.
Learn by doing. -
I don't, not if learning Handbrake is to be a step towards learning to use MeGUI. It doesn't even use AviSynth and a lot of the terms it uses are different from what they're commonly called.Originally Posted by smrpix
I'd suggest beginning with a program that uses AviSynth but is easier to learn, ones such as RipBot, StaxRip, or XviD4PSP. After that, if the program he learned doesn't do all he wants, then switch over to MeGUI. And also learn AviSynth if the goal is to use MeGUI.
And as Mephisto suggested, experiment and test. That beats having everything spoon fed to you. And on the MeGUI page are a number of guides for its use. Has yaston bothered to read them?Last edited by manono; 9th Jan 2015 at 03:26.
-
I guess Handbrake and simialar apps are easier to learn, and yeah you'll have to interpolate various terms between different apps. But judging from previous posts by the O.P., he's looking to do a lot of fancy color and image restoration work, more than just converting or encoding. I'm guessing he'd need either a full-featured NLE or Avisynth/VirtualDub for that, plus an encoder.
- My sister Ann's brother -
No no, i only need to start with MeGUI !!!
-
You are asking an ENORMOUS question.
Did you look at these?:
https://www.videohelp.com/tools/MeGUI#guides -
I'd start with Avisynth, make sure what it is, how it works, get some avi file (get some very short uncompressed avi video if you do not have any avi) and make Avisynth script. Load it into VirtualDub or MPC-HC, check if it works. Megui can create those scripts for you, but you should know how it works. Understand Megui needs avisynth script to encode video. It either creates it itself or you can give it to Megui directly.Originally Posted by yaston
-
Originally Posted by yaston
Well, have you? If so, do you have any specific questions? If not, why should anyone want to help you when you won't take even the first steps to learn AviSynth and the program?Originally Posted by manono
-
yaston, just ask your question. How will you learn to use megui without trying to use it?
-
Ok guys, would you see here? These are the sittings i made... are they useful?
-
For what result?Originally Posted by yaston
I'm a bit impressed. You're fairly new to all this but you've already found settings that improve the quality over the default settings the x264 developers spent so much time perfecting.
Here's how you'd test your settings yourself.
Encode a video using your settings.
Reset the x264 encoder (load the defaults).
Choose Level 4.1, the Very Slow Speed Preset and Tune Film. Use exactly the same bitrate as before and the same script for encoding.
Encode it again.
What was the speed difference?
Which one looks better? -
Well, i did as you told me exactly... look at the screens there's no difference.
Screen 1: with the settings i made
Screen 2: with the defaults settings
But, i faced a problem !! MeGUI bacame so slow doing compression i don't know why ?!! and this problem happend before i did anything to the settings, i did format to the system and no way !! what should i do?!
Here's a screen shows, a sample "TS" of 23 MB to "MKV" 15 MB took 40 minute !!
These are the defaults settings as you said:
Last edited by yaston; 22nd Jan 2015 at 03:31.
-
I'm using a CRT monitor at the moment and it does hide a bit of fine detail, but at the moment those 2 pics look pretty similar to me. And, if they were encoded while specifying such a low bitrate, they look better than I would have expected.
I'd guess the slow speed would be due to QTGMC. Were you using it for the encodes above? It's slow. Depending on it's settings, it can be very slow. And when you're running 2 pass encoding, it's going to be slow twice. Both 1st and second pass will be slow.
When you're having a problem such as this, switch to MeGUI's Log tab and right click on some text inside. Then select Save/Log. That'll save everything to a log file on your drive somewhere. It'll include the version numbers of the important software required by MeGUI, the command line sent to the encoder, the AVISynth script used for encoding, any error message..... pretty much everything. It's really just a text file. You can copy and paste the contents of attach it to your post here. It'll provide far more information than screen shots.
When you close and re-open MeGUI, the info in the log tab resets.
If you open Windows Task Manager while MeGUI is encoding, what's CPU usage like? I imagine it'll be fairly low. If so, I'd guess it's QTGMC. Did I mention that it's slow?
All you can do is try to get your CPU working harder. My method is to encode more than one script at a time. Two will usually do it, but sometimes it takes three encodes at a time. If you run too many together, it'll probably have negative effect.
To get MeGUI to automatically run 2 jobs at a time, click on the Workers menu at the top and select "Create new worker". It'll offer to let you rename it but it doesn't matter. Worker 2 will do. Now when you click Start at the bottom of the queue, you should see 2 hobs running. Well not always.... MeGUI will only run one audio encoding job at a time but mostly it'll run 2 together. Check the job queue and when there's two scripts being encoded, have a look at CPU usage. Hopefully it's increased a fair bit.
Of course doing it that way won't increase the speed of each encode. If a script was running at 2fps (for example) a second script with the same filtering should run at about 2fps too. But together it's a total of 4fps.
If you're only encoding a single video then you can't encode more than one at a time, but you can make a script that encodes the first half of the video and a script that encodes the second half, then you can encode them both at the same time. After they're finished, you can join the encoded video.
Anyway, go through the info for encoded two videos at the same time and give that a try. Use Task manager to see how hard your CPU is working and we'll go from there.
If it's QTGMC slowing things down you'll probably find if you remove it from the script (and also any other filtering you've added to a script that might be slow) encoding speed will increase quite a bit. That's normal and it shows the "bottleneck" is QTGMC.
When things don't work as expected or very slowly etc, start again with a basic script. No filtering, just re-encoding. If the speed' returns to normal or the problem goes away, add something to the script and try again. If that's okay, add something else to the script to test again. Often finding the cause of problems is a process of elimination. Start with the basics, add things back one at a time while testing for problems in-between, and when the problem returns you'll probably no what's causing it,. -
Oh my Godness "QTGMC(preset="fast")" did all of this problem... !! When i removed it the encode became fast ^^
Look at the screen, i put it here when the encode was slow.
Where do i have to put to become fast? -
When you say computer is slow, the other information that should be mentioned is CPU reading from task manager, ..., with QTGMC you might stuck around 50%, so not only QTGMC is slow, but it makes CPU 50%, which is double slow at the end, QTGMC's avisynth filters just do that.
You can look at the Avisynth MT solutions, look on this website and search MT on the page, you might just spend some time to tune it up,
or encode run couple of instances at the same time, not sure if that is possible with Megui. -
The speed has got nothing to do with where QTGMC is in the script. It's just slow. Read my previous post again.
None of the other filters in the script are as slow as QTGMC, but when they're all together in a script things can slow down quite a bit. Get rid of the unnecessary stuff.
TFM() is for field matching, You don't need it.
FFT3dGPU / FFT3DFilter is the default noise filter used by QTGMC. It generally doesn't make sense to have QTGMC in a script with FFT3dGPU. Use QTGMC's noise filtering instead.
Removegrain() is a light weight noise filter QTGMC uses it. You don't need to add it too.
awarpsharp()
Sharpen()
I'm not crazy about sharppening so I can't comment much there.
Anyway, it'll all personal choice but I don't like over filtered video and you've got a lot of filtering. Use whatever looks good to you, but don't just add filters to a script because you can.
Quote
