MeGUI - x264/XviD/lavc/Snow encoder with MP4/MKV/AVI output & audio [Archive] - Page 20

amango

20th December 2005, 13:30

Feature request:

I encode usually recorded stuff from DVB. For this material it is useful if I could set ranges (start-ending) which frames to encode to cut out advertisement.

Without the cutting-feature I am limited to VirtualDub, so I have to use the VfW-version of x264.... MeGui can only be used for DVD-ripps in his current form (as other apps like Auto Gordion Knot).

buzzqw

20th December 2005, 14:59

trim with cuttermaran/Mpeg2Schnitt
make a d2v project
import d2v to megui

BHH

greggerm

21st December 2005, 00:31

aww, crud.. thanks for those d2v files.. they remind me of what I should've fixed a long time ago. I'm pretty sure that if you take this line:
Field_Operation=1 (0:None 1:ForcedFILM 2:RawFrames)
and convert it into
Field_Operation=1
...
Umm.. which release of MeGUI it is you're using? Turns out that's been long fixed.

Doom9 - just curious - did I stumble upon a bug that was reintroduced into the program, or should I be using another build other than the one I am (Sharktooth's 0.2.3.1023D, as found in the development thread yesterday)

Thanks!
-Greg

Doom9

21st December 2005, 00:49

@amango: once we rewrite audio to no longer use BeSweet, that will be possible, but prior to that there's just no way.. going AviSynth we can accurately cut audio and video and that's what's needed to cut out commercials.

@greggerm: I'm honestly perplexed why this happens, I only have the 0.2.3.1023 source code here right now but that one seems to have the proper code. As x264.nl is currently down I can't check if the very latest source has this problem as well. But the funny thing is that I experienced the same problem (I'm not sure about the d2v containing the wrong contents.. I never checked) with the build on my HD (an older one).. and that one seems to have the proper code as well so I need to investigate this a bit more, but with the codec comparison I have my hands full.

P.S.If i have any further suggestions should i address them here or in the megui development discussion?Here please

A)Can you add the feature off time-start jobs?In order for the queud files to be encoded in a speicified time.Can you give me a reason not to start them immediately?

Doom9

21st December 2005, 01:03

well.. I found the dgindex bug alright, the problem is it was fixed when I was making the indexer more flexible and copied code around.. I was still using the code in the old location and fixed that, so once I started using the code at the new location, that one didn't include the fix. Somebody needs to change line

208 in DGIndexer.cs to

sw.WriteLine("Field_Operation=1");. And if the method public static void applyForceFilm(string fileName)is still in VideoUtil.cs, it can be safely removed (I hope.. I can't download the latest sources to compare with what I have and see if it compiles).

stax76

21st December 2005, 01:19

@amango

The available MPEG-2 cutters "don't seem to cut it" so until it's supported by MeGUI or StaxRip maybe you can generate your script using AVSEdit. I already wanted to start working on it as you and some others requested it but was scared of because the required changes will have rippling effects all over the application.

greggerm

21st December 2005, 03:37

well.. I found the dgindex bug alright, the problem is it was fixed when I was making the indexer more flexible and copied code around.. I was still using the code in the old location and fixed that, so once I started using the code at the new location, that one didn't include the fix. Somebody needs to change line...

I take it I'd need development tools in order to compile with that change on my own. :)

I'll sit tight and watch for the next build and hope it's cleaned up in there.

THANKS for your effort in weeding that out!
-Greg

Sharktooth

21st December 2005, 03:52

greggerm

21st December 2005, 04:35

EDIT: done. check the development thread. Sources and Bins are available.

Schweet - fetched - tested - works!

MeGUI operational question -
What's the parallel setting between MeGUI and Nero Recode for the Nero-branded "Psychovisual Enhancements" (the things that compress dark scenes more, theoretically savings space by sacrificing dark details). I'd like to tweak the settings a touch in MeGUI/x264 - I've been using Nero as a crutch, so I have to learn the REAL settings now.

Sharktooth

21st December 2005, 04:37

x264 has no "real" psy enanchments yet.

sh0dan

22nd December 2005, 09:24

Would it be possible for any of you put up a mirror somewhere. I haven't been able to download the binaries for more than a day. Very frustrating! :angry:

Sharktooth

22nd December 2005, 14:39

Would it be possible for any of you put up a mirror somewhere. I haven't been able to download the binaries for more than a day. Very frustrating! :angry:
a mirror is already provided. check this post: http://forum.doom9.org/showthread.php?p=754913#post754913

Paul Atreides

22nd December 2005, 20:56

nsis 2.12 could be use by Sharktooth to make x264 package

charleski

23rd December 2005, 05:25

@amango

The available MPEG-2 cutters "don't seem to cut it"
The vast majority of my encodes are DVB MPEG-2s cut and demuxed with ProjectX or PVAstrumento/cuttermaran. I have no problems with them in meGUI whatsoever.
Introducing editing functions into meGUi would hugely add to the complexity (as you need to maintain sync with the audio) and is completely unessecary as there are other tools that do the job.

stax76

23rd December 2005, 11:42

Maybe those apps have improved but compared to the application I use to cut I found those apps much of a pain last time I've tried.

nixo

27th December 2005, 10:31

Is it possible in MeGui to do a fixed quant XviD encode using a quantizer that isn't a whole number?

It seems to work fine from command line but I'm not having a lot of success in MeGui.

sh0dan

27th December 2005, 10:46

a mirror is already provided. check this post: http://forum.doom9.org/showthread.php?p=754913#post754913
I cannot see the Full Package anywhere - and it's still down.

Doom9

27th December 2005, 12:59

Is it possible in MeGui to do a fixed quant XviD encode using a quantizer that isn't a whole number?No (well, yes but doing that is only for programmers). And I'm pretty sure as far as XviD or other ASP codecs are concerned, you only have integer quantizers.

@sh0dan: I've added a link to the temporary mirror.

stax76

27th December 2005, 13:11

No (well, yes but doing that is only for programmers). And I'm pretty sure as far as XviD or other ASP codecs are concerned, you only have integer quantizers.

Don't know about mencoder but VFW codecs don't need integer, for DivX there is quite a bit difference beween 3 and 4, I tend to use XviD at 2.5, iirc it compares to DivX at 3.

Doom9

27th December 2005, 13:15

and what would 2.5 result in? 50% 2 and 50% 3? Don't tell me there's 2.5 quantizer I'm unaware off (and for that matter the XviD status window)

stax76

27th December 2005, 13:35

I just recently started to play with advanced codec settings so I'm pretty much clueless. I made however a quick XviD test, there appear to be a file size/quality difference:

q4 = 2.89 MB
q3.5 = 3.75 MB
q3 = 4.13 MB
q2.5 = 6.28 MB
q2 = 6.76 MB

akupenguin

27th December 2005, 13:39

Yes, XviD dithers the quants, 50% q2 and 50% q3.
lavc allows a qscale=2.5, and really does it (rounds to the nearest integer quant, but tweaks RD and trellis to get a quality point halfway between qscale=2 and qscale=3).

stax: Notice how your q2.5 is nowhere near halfway between q2 and q3. That's because the q3 half of the frames are lower quality, but most of the details missed there just have to be encoded in the next q2 frame. So overall you don't save many bits, and just lose a little compression efficiency.

nixo

27th December 2005, 13:56

AutoGK uses this approach when you choose 'Target Quality' mode. 75% quality equals quant 2.67, 67% equals quant 2.99 and so forth... It's really nice to do 1-pass encodes when your hardware isn't exactly state-of-the-art and file size isn't an issue.
I've been doing 2.67 quant encodes through VDubMod for a while and I just thought I'd ask since MeGUI looks really good to me... :-)

Doom9

27th December 2005, 14:12

well, it's no problem changing those up/down boxes. I don't see the sense of 1 pass encoding *at all* but it's no problem to make the change.

nixo

27th December 2005, 14:14

That'd be great. Thanks!

stax76

27th December 2005, 14:52

Sharktooth

27th December 2005, 15:04

nsis 2.12 could be use by Sharktooth to make x264 package
got it.

I cannot see the Full Package anywhere - and it's still down.
coz thats no longer the latest version. get this: http://www.webalice.it/f.corriga/megui/megui_0.2.3.1024.7z
and the sources are here: http://www.webalice.it/f.corriga/megui/MeGUI-src.ChngdFls_0.2.3.1024.rar

smok3

27th December 2005, 15:09

I use always single pass quality mode. Regarding multipass vs quality mode I started a thread recently. While there were great answers and help I'm still much interested in other peoples opinion on the topic, it can be found here:

http://forum.doom9.org/showthread.php?t=104548
what command line exactly are you using for x264 quality mode?
how do you calculate the proper q amount (based on input resolution?)?

stax76

27th December 2005, 15:51

what command line exactly are you using for x264 quality mode?
how do you calculate the proper q amount (based on input resolution?)?

Nixo had requested it for XviD, I'm not using AVC. There is a reason why I should educate myself regarding x264 and want to do so pretty soon.

smok3

28th December 2005, 00:11

right, actually my 2nd question 'how do you calculate the proper q amount' does not make any sense (just figured that out few minutes after posting...)

Inventive Software

9th January 2006, 21:05

*Bump*

berrinam

9th January 2006, 22:55

Morte66

11th January 2006, 10:54

Does this thread really need to be revived? For all those not yet aware, MeGUI now has a home on Sourceforge: http://sourceforge.net/projects/megui

Bugs should be posted on the MeGUI Bug-Report Thread (http://forum.doom9.org/showthread.php?t=105160) and feature requests should be posted on the MeGUI Feature Request Thread (http://forum.doom9.org/showthread.php?t=105162). As a result, there doesn't seem much need for this thread, does there?

Some sort of "User" thread would be handy for people who use MeGUI without being part of the development team. Maybe a sticky. It should cover where to download it, how to install it, what else you need; and it would point to the bug/dev/request/x264 threads. That should keep things going until MeGUI settles down and gets a Guide and download link on the Doom9 static site.

It took me the best part of a day to find MeGUI and get it working for DVD backup, and I still ended up unknowingly using an old build. :)

TNHitokiRi

14th January 2006, 20:27

i wish i had enough patience to read through the 50 pages, im pretty sure that this problem has been addressed. in the first few pages, Rash had a problem with loading a AVS file.

http://img408.imageshack.us/my.php?image=untitled16px.png

thats the exact error i get. The AVS works fine in virtualdub(and mod), and in all video players. I use ffdshow (libavcodec) to get it to work in virtualdub.

I think the problem could be related to the fact that im on Windows x64 edition. Thanks

lexor

14th January 2006, 21:19

I don't want to start a new thread for this little question, so I'll add to this one.

Where is the menu bar? namely where is bitrate calculator? I can't find it in config dialog either. Where did it move?

this is what I see: http://img429.imageshack.us/img429/2584/meguimain8sv.jpg (latest Shartooth's build)

Mutant_Fruit

14th January 2006, 21:20

use MeGUI full.

lexor

14th January 2006, 21:23

Woah? But it was no problem before. Do I really need full megui for bitrate calc now?

/edit: oops, just noticed ST's explanation in bug report thread :) nvm

berrinam

14th January 2006, 23:26

Guys, why are you reporting bugs here? There is a dedicated Bug-Reporting thread for exactly that. Why come back here? The bug report thread even has a list of all known bugs on the first page, to avoid you having to wade through all the pages.

If you want to get help with your bugs, please report them in the right place.

lexor

15th January 2006, 04:05

If you want to get help with your bugs, please report them in the right place.
sorry, I didn't realise what I was having is a bug, I read in the other thread about options redesign, I thought calc moved somewhere and I couldn't find it.

ggab

15th January 2006, 09:25

(r394A) Updated MeGUI (ver 0.2.3.1030) and AVC2AVI GUI with .NET 2.0 binaries.
(r394) Updated Installer. Added MeGUI Context Sensitive help (patch by mutant_fruit).
what is the last version that can run with .net v1.1 (i don't have the new 2.0 one yet)?

r394?

if yes, is there any URL link to download it?

thanks :)

Doom9

15th January 2006, 11:52

r394?don't confuse x264 with MeGUI.. you can use an old MeGUI version with a new x264 build and vice versa.. obviously if x264 is newer than MeGUI then you may not have all x264 options available.. MeGUI needs to be updated to support new x264 options.

Just download the 2.0 runtime.. you can have both runtimes in parallel and there are no negative sideffects whatsoever (I have both at work, with two development environments, and I wouldn't recommend it if I weren't absolutely sure that it would have any negative effects.. I couldn't risk that with my machine at work).
We don't keep old builds around.. it's up to you to do that, or check out the source code by a specific data and do your own builds.. you are unlikely to find a dev willing to spend time to worry about oudated builds, and the 2.0 move has various advantages for us, nontheless the one that those who do not have the full blown Visual Studio IDE (which is not cheap), can still participate using the free of charge Visual Studio Express.

max-holz

15th January 2006, 16:52

I want understand one thing, why 0.2.3.2024 modifies Sharktooth profiles and reset all the application path?
I think that since this project had became public with cvs there has been a big confusion.

Doom9

15th January 2006, 17:03

why 0.2.3.2024 modifies Sharktooth profilesHuh? There have been no changes in Profile, VideoProfile or VideoCodecSettings and those are the objects that have something to do with profiles. But MeGUI always have and always will write all profiles to your HD when you exit.. so these files are updated each time you exit megui. But as I said, it has always been like that ever since MeGUI got profiles.

and reset all the application path?It doesn't. But the refactoring changes the format of the settings file so it has to be recreated.. since your settings file can no longer be opened (This is no different than you having to redo dgindex projects every now and then), it means you lose your configuration. It takes you about 1 minute to redo that so I don't see the problem.
Somewhere in between my two latest releases (prior to the 2024) jobs became incompatible with old ones.. I heard nobody complaining..

max-holz

15th January 2006, 17:11

It doesn't. But the refactoring changes the format of the settings file so it has to be recreated.. since your settings file can no longer be opened (This is no different than you having to redo dgindex projects every now and then), it means you lose your configuration. It takes you about 1 minute to redo that so I don't see the problem.
Somewhere in between my two latest releases (prior to the 2024) jobs became incompatible with old ones.. I heard nobody complaining..

Why that? Why I must recreate all the general settings every time I reopen the application, what's the meaning of that? In every application I set my general settings and then they are saved till I decided to change them.

Doom9

15th January 2006, 17:18

Why I must recreate all the general settings every time I reopen the applicationYou don't.. but refactoring means making changes to existing code.. for instance the settings object.. so old ones cannot be opened. This has happened once in I don't know how many builds.. it's been months upon months with no change. I think it's rather rude to whine when you get a free software, constant improvements and all that free of charge. In other projects, like DGIndex for instance, compatibility is broken a lot more frequently. There are just two ways to make necessary changes: 1) bending over backwards to keep the whiners happy, or 2) make your improvements properly without regard for compatibility, and that every now and then breaks something. As another example, it is not uncommong for VfW codecs to require a "load defaults" when you install a new build.

The Link

15th January 2006, 17:22

Why that? Why I must recreate all the general settings every time I reopen the application, what's the meaning of that? In every application I set my general settings and then they are saved till I decided to change them.
??? I just had to go thru the settings for one time after the upgrade. The settings were saved and are available every time I restart MeGUI.

max-holz

15th January 2006, 17:22

Ok Doom9

ggab

16th January 2006, 00:21

thks doom9 for the tips :)

Hyper Shinchan

16th January 2006, 23:39

I haven't really understood if .net 2.0 works on XP SP1 (why are you using it? Well, I can't update it, that's all, for various reasons).
It seems to work, but it shows badly the frame speed. It says something like 1000 fps, when it's 10.00 fps. But it seems to be the only problem, I hope (but maybe I'll start using command-line, also if I need to make huge batch).

Doom9

16th January 2006, 23:52

It says something like 1000 fps, when it's 10.00 fps.using an old release? That was fixed in 2024.

I haven't really understood if .net 2.0 works on XP SP1Yes it does.. it works even on old and crappy systems. And using XP without SP2 is like having sex with a prostitute and not using a condom.. very risky. And there's no reason why you couldn't install the 2.0 runtime.. it works side by side with the 1.1 runtime.. unlike java where you have to tell an app which runtime to use, it's all done automatically in .NET.. any .NET program will look for the version it was compiled again.. it will run in newer versions as well, but it'll pick the closest match.. all your .NET 1.1 programs will keep on using the old runtime, so they will work exactly as before.

And I do hate repeating myself.. I've been pointing out all the .NET 2.0 facts before. I have a dual installation at work.. and there's no way I can risk breaking anything there.. a lot depends on me being able to maintain code made for the old runtime.