meguIV: The Official Akiba-Online DVD Encoder (v1.0.1.1)

[anandneemish]

Happy Holidays all.

I have a BD framerate question. BD's native frame rate is 23.976 (I'll say 24 from now on). Most of the WMV BD rips that I have seen are at 30fps which appears to be much smoother for me.

I just did a test encode using MeguiVIT with double the framerate. However, even at 48fps, the results still look jerky.

Can someone point me to how to properly change the framerate using MeguiVIT.

Thanks.

P.S. I have another BD question. The ISO in question is 21.5GB. However, the m2ts file that contains the main content is only 13.3GB. There is another m2ts file that is 6GB but cannot be played in MPC or VLC. I wonder what can be in the 6GB m2ts file.

 

[Vitreous]

I have a BD framerate question. BD's native frame rate is 23.976 (I'll say 24 from now on). Most of the WMV BD rips that I have seen are at 30fps which appears to be much smoother for me.

Blu-ray supports a number of frame rates, not just 24fps. Probably the rips you have seen are from 30fps (or 29.97fps) BDs.

I just did a test encode using MeguiVIT with double the framerate. However, even at 48fps, the results still look jerky. Can someone point me to how to properly change the framerate using MeguiVIT.

Blu-ray also supports interlaced and progressive content. 24fps footage is always progressive. Your result looked jerky because MeguIVit defaults to interlaced input - feed it progressive input and it will create twice the number of frames, but every other one will be almost identical so it will just look like single rate.

Interlaced input can be made double frame rate with very high quality because it actually stores two different fields (images) per frame. Progressive input can be forced to double rate using motion interpolation but with less quality and visual artefacts. To do that in MeguIVit, select the "Custom Processing" tab, select "Progressive: Post Processing" at the top and check "Synthesize in-between frames".... but the motion interpolation in MeguIVit is a bit broken at the moment so result will be sub-standard. I have a better script that I will put in at some point (I am actually working on encoding tools again after a long break). However, even with a refined script, motion interpolation is not gonna get close in quality to the frame doubling you get from interlaced input.

P.S. I have another BD question. The ISO in question is 21.5GB. However, the m2ts file that contains the main content is only 13.3GB. There is another m2ts file that is 6GB but cannot be played in MPC or VLC. I wonder what can be in the 6GB m2ts file.

uzzled:

 

[anandneemish]

I have a better script that I will put in at some point (I am actually working on encoding tools again after a long break).

Yay!!! I'll wait for the better script.

As to the second question, I was curious as to the contents of a very large m2ts file that neither MPC nor VLC can render. I'll do some more reading on BD file structures. Then perhaps I can frame my question more intelligibly.

Thanks.

 

[Vitreous]

As to the second question, I was curious as to the contents of a very large m2ts file that neither MPC nor VLC can render. I'll do some more reading on BD file structures. Then perhaps I can frame my question more intelligibly.

Your question was perfectly intelligible, I was just indicating I have no idea what that big unusable file is. I've seen small .mts files that contain the BD menus that are not directly playable, but never such a large file like that.

 

[anandneemish]

No prob.

I just found this script on videohelp. Any thoughts on using this within the Avisynth profile? I tried it out on a really bad jerky video. Seems to have smoothed it out a little, but the source was really bad.

Just curious if you think this might be useful.

AssumeTFF()
ConvertToYUY2() <--- I kept the existing "ConvertToYV12()" command
SeparateFields()
SelectEvery(8, 0,1,0, 3,2, 5,4,5, 6,7)
Weave()

 

[Vitreous]

Any thoughts on using this within the Avisynth profile?

That script is performing a 3:2 pulldown process, it is a standard way of converting from 24fps to 30fps (or 23.976fps to 29.97fps), to convert from film to video. It's a kind-of artificial interlacing that produces 10 output fields for every 8 input. It's only necessary when you must have 30fps output, and in my opinion it looks bad - many people spend time trying to remove this pattern.

Many people would leave 24p film at 24p and relish the 'film-look'. If you don't and need a solution now, look into 'Interframe' over at d9, which is a frame-rate doubler suitable for film input. Another option is to add motion-blur to soften the jerkiness. MeguIVit is very good at that: select the "Custom Processing" tab, select "Progressive: Post Processing" at the top and check "Shutter Blur". Decrease "In" and increase "Out" for a stronger effect (hover over those two for some documentation).

 

[anandneemish]

That script is performing a 3:2 pulldown process, it is a standard way of converting from 24fps to 30fps (or 23.976fps to 29.97fps), to convert from film to video. It's a kind-of artificial interlacing that produces 10 output fields for every 8 input. It's only necessary when you must have 30fps output, and in my opinion it looks bad - many people spend time trying to remove this pattern.

Many people would leave 24p film at 24p and relish the 'film-look'. If you don't and need a solution now, look into 'Interframe' over at d9, which is a frame-rate doubler suitable for film input. Another option is to add motion-blur to soften the jerkiness. MeguIVit is very good at that: select the "Custom Processing" tab, select "Progressive: Post Processing" at the top and check "Shutter Blur". Decrease "In" and increase "Out" for a stronger effect (hover over those two for some documentation).

Thank you. I found that script while searching for 3:2 pulldown. I previously thought that 3:2 was the only way to get to 30fps.

Personally, I really dislike 24 fps. I can totally see the jerkiness on the big screen as well as on my monitor.

I think I'll try motion blur to see if that helps.

Thanks again.

 

[youmeus]

Hey Vit. I am having a bit of trouble finding the latest version of MeguiVit on Akiba-Online. I found this page: http://www.akiba-online.com/forum/showpost.php?p=872101&postcount=315 but this hasn't been updated since March. Can someone help me out with a link perhaps?
Thanks

 

[no__One]

Hello,

Are you looking for this ? \0/ (hope, it's help you)

 

[youmeus]

Hello,

Are you looking for this ? \0/ (hope, it's help you)

That's it! Thanks alot mate

 

[Vitreous]

meguIVit 1.0.0 beta-4

A quick service release of meguIVit. This is only a minor release, but I am back to working on these things after a long break.

Download meguIVit 1.0.0 beta-4

Installation:
- Download Rollyco's original meguIV from here (the links in the first post are currently down)
- Delete any already existing "Sandbox" folder in the same folder as meguIV
- Extract the meguIVit zip file, which creates a new "Sandbox" folder
- Run meguIV (which is now transformed into meguIVit)
- If you use Noise Processing settings (not enabled by default) then you need the contents of the attached ExtraDlls zip file too

Usage
See this quick pictorial guide for the first beta. The interface has changed in places, but it's still mostly the same.

____

Changes:
- Updated the sandbox with fixes that a few of us worked out earlier in the thread
- Latest avisynth plugins, which should provide some minor speed-up.
- Update to QuickTGMC 3.33 (some minor tweaks mostly regarding how it deals with source noise)
- Improved FPSx2 (Synthesize in-between frames) option, which allows you to force progressive 30fps into 60fps (or 24fps to 48fps etc.)
- Improved EdgeClean, which is now more delicate on fine detail. Good for older sources with strong over-sharpening.

___

meguIVit is based on a "One-Click" concept. When you drag a source into the first one-click window it automatically selects settings for high quality double rate deinterlacing. It chooses the fastest settings that are still considered [HQ] for your source. That means for most 60fps (or 50fps) deinterlacing jobs, you can just press "Go" and the result will be good. You can confirm whether your settings are HQ on the "Custom Processing" tab, there is a [HQ] box that goes green when your settings are good.

IMPORTANT: To rip a blu-ray, you extract the BDISO and drag one of the m2ts files from the BDMV\STREAM folder into meguIVit. However, you should also check "Switch Parity" on the "Advanced Config" tab. I haven't yet updated the program to do that automatically.

The myriad options are for repairing bad rips or improving poor sources, particular cropping or resizing requirements, ultra high quality or faster settings, adjusting threading for performance/stability and just general tweaking. Experiment or ask...

 

[shank]

I'm happy to see you are working on this again! I gave it a quick test run with a small 2 minute vob and this updated version worked out of the box (you may remember the troubleshooting we did with beta 3).

Though I'm assuming the new setup was used. The main window still says beta 3 and I only work with 480p @ 60fps, so I simply use the default settings and don't think I would notice the changes listed above. After the troubleshooting with beta 3, the remaining outstanding issue I had with it was needing to (manually) reduce the # of threads (every encode) because the auto selection was too much for my 6 core cpu. It will take more time to test that setting, so I'll post those tests when done.

Thank you for further improving meguIVit!

 

[Vitreous]

Yes, I didn't actually change the Megui executable, this was just a sandbox update. Mainly because another user asked where MeguIVit was, and I figured I may as well roll up the changes we worked out and update the plugins. Next version will be a more substantive update... (promise!)

 

[hehazone]

Hello there,

Usually I rip my ISO using Handbrake, but of course your tool are far better than whatever is on the market...

Does this support Video file (.mkv) too? Cus I get used to covert it using MakeMKV first to prevent the DVD protection error occur using your tool...

 

[Vitreous]

Yes, you can drop MKVs into it.

 

[tonyromeo]

Hi there, I have run a search on this thread but found no results.
I had a version of this proggy some time ago which I used to re encoded and deinterlace some .wmv video files, it did a beautiful job. Unfortunately I lost it and yesterday I dl'd this latest version but to my dismay when I choose the one click mode input it does not recognize .wmv.
Is there some setting I am missing here to remedy this or is the older version I had still available for dl?

I am not a techy. ;-)

Whoops....I just spotted your beta version above which seems to resolve my problem....thank you for your work.

 

[Princess-nuzzle-me]

I've just tried to rip the 18GB main movie m2ts file of IMBD-027 using MeguIVVit beta 4, but failed.

First attempt I left the file size at "Dont Care" and it came out as 180GB, so that got aborted after a while.

Second attempt was set at DVD size, but could only see 480p and 720p options (want the 1080p 60fps that others are able to achieve).

Can I suggest a separate thread for ripping blu-rays, ideally an idiots guide, because this thread has grown into a monster that I'm finding difficult to follow. The best rips I've seen are probably IMBD-002 and -004 (by Prof Vitreous?), so an idiots guide to how to repeat for others would be ideal, if that is possible?

 

[Vitreous]

Your first attempt was probably working. By default MeguIVit uses a two pass process as that increases the stability of such complex processing (and sometimes improves the speed too). The first pass generates a lossless temporary file that will be around 200Gb for a blu-ray. These are the temporary files mentioned in the first post (obviously larger for blu-ray over DVD). The second pass will convert it into a normal sized rip and then delete the temporary files.

- To do everything in one pass go the to "Encoder Config" tab and uncheck "Add pre-rendering job" but stability may be affected. You might improve stability for one-pass blu-rays by going to "Custom Processing" tab and changing "Main Threads" to 4 and "Sub Threads" to 1 (uncheck "Auto"). If you have 6Gb of RAM or more then you could set "Cache Memory" to 1000. But you might just be better leaving it in two pass mode.
- Important for blu-ray: you must check "Switch Parity" on the "Advanced Config" tab.
- I also suggest first time you go to the "Custom Processing" tab and type 2000 for "Trim End". That will do a quicker 2000 frame test rip so you can make sure things are working.

I don't know where you could "only see 480p and 720p options". Maybe you mean the "Video Profile"? Did you try scrolling up? However, you don't usually need to set this because the video profile gets set by default when you select a video source - as soon as you select a blu-ray m2ts file it will go to "1080p 60fps Default". You can set "1080p 60fps Quality+1" or "Fast Decode" as alternatives if you want...

My intent was to request a sticky for MeguIVit if/when I get it out of beta, I have a half-finished version with more features, but have not been able to find the time to finish it. However in practice the instructions are very simple: (1) Drag'n'drop file (2) Press Go (3) If it doesn't work, post here.

Yes I did those early 1080p 60fps IMBD rips. The quality there was in part down to a fairly high bitrate, in part because we hadn't seen anything like that before, but IMO mostly due to the fact Imouto were much more careful in filming those early HD vids.

 

[Princess-nuzzle-me]

OK thanks, am trying again after finding a USB drive with enough space - it refused to work with the source on my 650GB free space C drive. That was the cause of it shifting to 720 horizontal resolution, only went to proper size with an external drive.

 

[Vitreous]

Well, I hope it works. But I don't know what you're saying there. First of all 720 is not a horizontal resolution, it's a vertical resolution. More importantly, MeguIVit will never change the resolution it outputs because of the drive you use (whether full, external, SSD whatever, it won't change settings). So the problem you experienced was something else.