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. |
25th September 2012, 15:31 | #14161 | Link |
Registered User
Join Date: Mar 2011
Posts: 216
|
It took me a while to figure out that it was created on the desktop instead of the video folder or MadVR install folder(a message that say's where the log is created when you activate debug mode would be nice) but here it is: http://www.mediafire.com/file/6pe56fufjr6i2c6/madVR_log_SamKook_2012-09-25.rar
|
25th September 2012, 16:05 | #14162 | Link |
Broadband Junkie
Join Date: Oct 2005
Posts: 1,859
|
Crash when activating FFDShow's resize filter during playback with horizontal size set to 4096.
Crash & Debug logs |
25th September 2012, 16:37 | #14164 | Link |
Registered User
Join Date: Jan 2004
Posts: 567
|
I just checked clock deviation with my newly built HTPC which is based on a Core i3-3225 with HD 4000 graphics. HDMI Audio is supplied by the OnBoard RealTek ALC898 (MSI Z77A-GD65). I tried 576i25 (deinterlaced to 50fps @ 50Hz) and 1080p (@23Hz) source material.
Here is what madVR displayed after about 1 hour of playback... 576i25: display 50.00090Hz [diff: +0.0009] clock deviation 0.00180% A frame drop is supposed to occur every few days, number heavily fluctuates 1080p: display 23.97227 [diff: -0,00373] clock deviation 0.00090% 1 frame drop every 4.18 minutes At 50Hz, the actual refresh rate is much closer to the target. Still the calculated clock deviation is higher compared to the 23Hz mode. The clock deviation should be much smaller for the more accurate 50Hz mode, shouldn't it? Don't you derive the VSync clock from the D3D raster status? Drop rate seems to more closely reflect the refresh rate accuracy.
__________________
Bye |
25th September 2012, 16:56 | #14165 | Link | ||
Broadband Junkie
Join Date: Oct 2005
Posts: 1,859
|
Quote:
Quote:
Not necessarily, since that's not what clock deviation represents. Last edited by cyberbeing; 25th September 2012 at 16:59. |
||
25th September 2012, 17:11 | #14166 | Link | |
Registered User
Join Date: Jan 2004
Posts: 567
|
Quote:
__________________
Bye |
|
25th September 2012, 17:16 | #14167 | Link |
Broadband Junkie
Join Date: Oct 2005
Posts: 1,859
|
That's absolutely false. You could theoretically have a massive clock deviation with a dropped frame interval in days.
In simple terms, you could probably think of clock deviation as a representation of how much faster or slower your actual playback rate is compared to your video framerate. |
25th September 2012, 17:21 | #14168 | Link | |
Registered User
Join Date: Jan 2004
Posts: 567
|
Quote:
__________________
Bye Last edited by CiNcH; 25th September 2012 at 17:23. |
|
25th September 2012, 17:35 | #14169 | Link | |
Broadband Junkie
Join Date: Oct 2005
Posts: 1,859
|
Quote:
|
|
25th September 2012, 18:21 | #14170 | Link |
Registered User
Join Date: Sep 2010
Posts: 321
|
I just watched The Avenger's Blu-ray with v0.83.4 and not a single drop frame or glitch while using FSE (while using Lav filters + reclock), great job madshi!
__________________
MPC-HC/MPC-BE, Lav Filters, MadVR CPU: AMD Ryzen 5 1600, Video: AMD Radeon RX Vega 56 -> TCL S405 55", Audio: Audio-Technica M50S |
25th September 2012, 18:52 | #14171 | Link |
Registered User
Join Date: Apr 2008
Posts: 1,106
|
Debug log attached from 0.83.4 after seeing the Direct3D error. With mpc-hc closed, I opened a file directly in FSE, and then double clicked mpc-hc's window to get to overlay mode and saw the Direct3D error appear, mpc-hc also paused itself after the error.
http://www.sendspace.com/file/ojmmei I also have an issue, I'm not sure if its expected. Resizing the windowed overlay mode shows strange looking effects inside the window, like a stair step scaling effect, with a dark red background. Last edited by mark0077; 25th September 2012 at 19:02. |
25th September 2012, 20:45 | #14172 | Link | ||
Registered User
Join Date: Jun 2006
Posts: 452
|
Quote:
I think madshi could try to speed up the destruction from the D3D-surface that is left from FSE on the moment you switch to overlay. Because FSE "holds" the D3D until it's destructed, Overlay can't create a new one. Another option could be not to destroy the D3D from FSE, but.., if this is somehow feasible, re-use it instead for Overlay . The minimum time gain would be the time needed for destruction + creation from a new D3D-surface. Quote:
For me, If I use the keyboard (ctrl +1, ...) to resize to a predefined size, the process is smooth. But if I use the mouse to resize, I see indeed strange things, because I'm in fact resizing to a changing target-size in every step, until I finally have the size that I wanted. Last edited by Pat357; 26th September 2012 at 00:20. Reason: typo's |
||
25th September 2012, 22:04 | #14173 | Link |
Registered User
Join Date: Aug 2012
Posts: 73
|
I run the last version of Madvr + AMD 6850.
When I use FSE, I have dropped frame but if I stay in FS, everything is very smooth...??? Before it was completely the opposite??? Have I made something bad with MPCHC??? I have tried many times but I cannot fix this issue :5 |
25th September 2012, 23:46 | #14174 | Link |
Registered User
Join Date: Feb 2004
Posts: 399
|
Hi madshi, could you possibly make the new "slower/delay stopping playback" optional ?
Here it's significantly slower (than 0.82.5) and brings absolutely nothing (madVR has _never_ crashed on stopping playback/exiting player). On XP SP3/ ZoomPlayer..
__________________
XP SP3 / Geforce 8500 / Zoom Player |
26th September 2012, 09:34 | #14179 | Link | ||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
> dwTaskbarThumbnails 331 +7 TdwTaskbarThumbnails.DoUpdate Could that code line result in an EOleException exception somehow? |
||||||||||
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|