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. |
9th February 2019, 15:52 | #6701 | Link |
Registered User
Join Date: Feb 2007
Location: Sweden
Posts: 483
|
MKVToolNix v31.0.0 is released.
https://mkvtoolnix.download/windows/releases/31.0.0/ |
11th February 2019, 12:21 | #6702 | Link |
Registered User
Join Date: May 2015
Posts: 8
|
AutoEncode bug with FDK-AAC [M4A]
Partially Bug related to this previous one https://forum.doom9.org/showthread.p...30#post1722030:
Using MeGUI 2908 with AutoEncode button. Setting: AudioInput: <filename>.aac AudioOutput <filename>.m4a Encoder: FDK-AAC Extension M4A Result: AudioOutput: <filename>.mp4 This time there is no error while encoding audio, neither with final muxing. It's just a typo error with audio Extension GUI choice not correctly saved when MeGUI generate cmdline job BTW with the [Queue] audio button, extension choice is correctly passed to cmdline. |
11th February 2019, 13:00 | #6703 | Link |
Registered User
Join Date: May 2015
Posts: 8
|
OneClick DGI Source Nvidia Crop&Resize not used
Using MeGUI 2908 with [OneClick]
[source]: MP4 1920x1080 AVC, AAC [project]: Code:
[Indexer]: DGDecNV with Audio Demux [Avisynth]: DGI Source Auto Crop&Resize Use Nvidia Crop&Resize if possible Max Width: 960 [Video]: x264 [RAWAVC] [Audio]: FDK-AAC [M4A] [Muxing]: MP4 Problem isn't present if I use [Avisynth script creator] then [AutoEncode] Cheer |
12th February 2019, 02:44 | #6704 | Link |
Unreasonable User
Join Date: Nov 2003
Posts: 216
|
There's definitely a problem with DGIndexNV 2053.0.165 (32-bit). Every blu-ray source has the bottom 8 pixels cropped off and the picture stretched to compensate.
I confirmed it with discs I had ripped before. By using the same avs script I had used months before, I can confirm that the crop no longer matches and the AR is indeed stretched. Last edited by Lyle_JP; 12th February 2019 at 06:10. |
15th February 2019, 19:55 | #6706 | Link |
Registered User
Join Date: Aug 2012
Posts: 43
|
This issue is not fixed however with 167 or 168.
EDIT: Tested further. Cropping/Resizing seems to work now again, when using AVS cropping. When using "NVIDIA Crop & Resize" the resulting video has approx 2px black at top and 6px black at bottom. Last edited by pommesmatte; 15th February 2019 at 21:40. |
16th February 2019, 12:00 | #6707 | Link | |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Quote:
|
|
3rd March 2019, 15:25 | #6711 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Zather,
a couple of Bluray encoding issues.... When using Blu-ray as the target playback device, MeGUI won't allow a 720x480 video to be encoded as progressive, even with --fake-interlaced enabled. I tried enabling it via the GUI and adding it to the custom command line. It seems that it should be compliant though. http://www.chaneru.com/Roku/HLS/X264...ake-interlaced Quote:
Cheers. Last edited by hello_hello; 4th March 2019 at 04:04. Reason: spelling |
|
4th March 2019, 08:27 | #6713 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
sneaker_ger,
I didn't realise --weightp 2 is illegal for Bluray. At least adding it to the command line isn't breaking compliance. Another possible issue (I'm not sure). For a 720x480 video at 23.976fps, both these guides say --fake-interlaced is required along with --pulldown 32. http://www.x264bluray.com/home/480p-ntsc https://forum.doom9.org/showthread.php?t=154533 MeGUI adds --pulldown 32 when Bluray is selected as the target playback device, but not --fake-interlaced. And a question.... My recollection was for Bluray encoding to be complaint, the encoder has to write a raw .264 stream and not write directly to MKV. I can't remember why, but is that correct, and if so, should it be something MeGUI enforces when Bluray is selected as the target device? Cheers. |
9th March 2019, 10:59 | #6715 | Link | |
Registered User
Join Date: Aug 2012
Posts: 43
|
Quote:
https://forum.doom9.org/showthread.p...10#post1864410 NVIDIA Crop&Resize is still not usable. EDIT: See next post for details, resizing bug seems fixed though. Last edited by pommesmatte; 9th March 2019 at 18:18. |
|
9th March 2019, 15:17 | #6716 | Link |
Registered User
Join Date: Aug 2012
Posts: 43
|
New/old cropping bug with MeGUI 2908 and DGIndex 169 with NVIDIA Crop
Details on the remaining bug with Nvidia Crop&Resize (DGindex version 169).
It seems that its a different bug again, no problem with resizing, but again a move in the cropped area. I used cropping of 134 pix top and bottom (slightly undercropped on purpose, so you can see the black bars.) Original stream shows approx 2px remaining black on top and bottom Cropped with Avisynth shows the same 2px on top and bottom. Cropped with Nvidia Crop the above black border doubles to approx 4px and the bottom one vanishes. EDIT: The strange thing is: This only happens on some files, other are fine. Last edited by pommesmatte; 9th March 2019 at 15:44. |
9th March 2019, 17:44 | #6718 | Link | ||
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
Quote:
__________________
BeHappy, AviSynth audio transcoder. |
||
9th March 2019, 18:11 | #6719 | Link |
Registered User
Join Date: May 2015
Posts: 8
|
When you say "The nVidia driver is currently broken", you talk about the last relaese of it.
I use an old version of the Nvidia driver without this issue. So the question is since which version the bug appear to know which old driver version is it safe to use ? Last edited by taz742; 9th March 2019 at 18:27. |
|
|