Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
11th October 2018, 20:48 | #6442 | Link | |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Quote:
Are you able to reproduce that? If yes please use this version here for that and paste the log: http://megui.org/megui_debug.7z |
|
11th October 2018, 21:03 | #6443 | Link | |
Registered User
Join Date: Oct 2015
Posts: 97
|
Quote:
|
|
12th October 2018, 00:04 | #6444 | Link | |
Registered User
Join Date: Mar 2017
Posts: 51
|
Looks like the same TabControl error I faced.
Zathor, does the below log help? Quote:
|
|
12th October 2018, 18:30 | #6445 | Link | |
Registered User
Join Date: Feb 2011
Posts: 331
|
Quote:
|
|
13th October 2018, 11:34 | #6446 | Link | |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Quote:
You can also delete all rules that way you are back to the old way. Thanks, partially. Ideally the debug version would be used but as you cannot reproduce it, it is hard to do so. |
|
13th October 2018, 17:09 | #6448 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Quote:
For a text input file when you change the input/output fps and they match, the chapter timings don't change, but the corresponding keyframes in the QP file do, so it's assuming frames are being added/removed, much like ChangeFPS(). For either input type, when the input and output fps don't match, the equivalent of AssumeFPS() is applied. ie the chapter timings change but the corresponding keyframes don't. Without a preview open, I think the way text input files are currently handled is more logical. The preview throws a spanner in the works though because the preview video has a fixed number of frames, so I think when a preview is opened either the input or output fps should be locked to the video frame rate, then when you change the other, the equivalent of AssumeFPS() is applied. I'd imagined something like.... I have an NTSC video I sped up from 23.976fps to 25fps. I open the script and the output fps becomes locked at 25fps. I then open the chapters from the DVD and select 23.976fps as the input frame rate. The chapter timings are stretched from 23.976fps to 25fps to match the video. Or maybe you have a more clever idea..... |
|
13th October 2018, 19:28 | #6449 | Link |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Could you please check this version? I changed the chapter creator a bit.
http://megui.org/megui_test.7z EDIT1: new version online. fpsout cannot be changed anymore if a player is open. EDIT2: new version online. fpsin cannot be changed anymore if the input file has fps information. Last edited by Zathor; 14th October 2018 at 21:28. |
15th October 2018, 19:08 | #6450 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,782
|
Dear Zathor.
In the last months I read several posts (also in VideoHelp forums) that VSFilter, the one and only subtitle filter shipped with MeGUI, does not support some advanced (e.g. Aegisub supported) effects of ASS (e.g. gradual fading in/out). Would you consider offering some range of subtitle plugins in the future, if more meet your requirements (e.g. of used color spaces)? |
15th October 2018, 20:57 | #6452 | Link |
Registered User
Join Date: Dec 2002
Posts: 5,565
|
I'm surprised to read that as xy-vsfilter is the default renderer Aegisub uses. (libass is optional)
MeGUI is shipping pinterf's version, right? I don't think it has any less features than the one in Aegisub. If there's a problem they should upload a sample. Maybe there is some unknown regression. (Or maybe just user error.) |
16th October 2018, 03:16 | #6454 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
It does a bit.
For some reason MPC-HC has no trouble opening scripts with pinterf's vsfilter, or when pinterf's version is in the auto-loading folder, and the subtitles display as expected, but not so much for MeGUI or AvsPmod. I couldn't even begin to speculate why. Zathor, sorry I must have missed your earlier post, but to play with the new and improved Chapter Creator, should I download the test version of MeGUI you linked to in your post, or the current version on the development server? Thanks. |
16th October 2018, 13:06 | #6456 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Zathor,
The Input/Output chapter timings displaying together in the GUI is nice addition, although as someone who's never satisfied, I now crave an additional column displaying the corresponding qp file keyframes too. Quote:
Regardless of the input type, when the input/output fps are the same, the chapter input/output timings should always remain unchanged, IMHO. There's no reason for the input fps not to default to the fps of the input file, and the output fps could default to the frame rate of a preview when it's opened. The input/output fps should effectively be a numerator and denominator though. If the wrong frame rates are specified, I'd classify it as user error. A preview script has a fixed number of frames and a specific frame rate and duration. The only sane assumption is neither will change, so you'd be opening chapters from the source to adjust the timings to match the script output duration, and selecting the original frame rate as input fps and the script frame rate as the output fps should take care of that. The keyframe numbers would be based on the input fps. If the total frame count has changed compared to the source, when applying IVTC to an NTSC DVD for example, the preview frame rate would still be the output frame rate, but the input fps must be 23.976 even if the input IFO insists on 29.970fps. If the input/output fps are both 23.976, the chapter timings won't change. The keyframe numbers would be calculated based on a 23.976 frame rate. Lastly, the total frame count and duration for the script output could both be different to the source. Applying IVTC to an NTSC DVD and speeding it up to 25fps, for example. The input fps needs to be 23.976 no matter what the IFO says, and the output would be 25fps. The chapter timings would be adjusted according to the change in duration, and once again the corresponding keyframes numbers are calculated according to the 23.976 input fps. So now I've thought about it again, I probably over-thought it a little before. Two rules should cover the common sense scenarios, with or without a preview. Rule 1: If the input/output fps are the same, the chapter timings don't change, even if they don't match the source/output frame rate. The keyframe numbers are based on the input fps. Rule 2: If the input/output fps are different, they become the numerator and denominator for chapter timings and stretch them accordingly, but they don't "stretch" the keyframe numbers. They're still based solely on the input fps. Unless I've under-thought it this time, I think that covers it. Cheers. Last edited by hello_hello; 17th October 2018 at 17:17. |
|
19th October 2018, 20:27 | #6459 | Link |
Registered User
Join Date: Dec 2011
Posts: 148
|
Cannot unselect/select "Starts new jobs in queue immediatly" no more ...
If I use One Click Encoder, then click on Queue, MeGUI immediately starts with Extracting Tracks. Last edited by Glarioo; 20th October 2018 at 05:20. |
Thread Tools | Search this Thread |
Display Modes | |
|
|