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. |
|
|
Thread Tools | Search this Thread | Display Modes |
3rd December 2009, 10:25 | #221 | Link | ||
Registered User
Join Date: May 2008
Posts: 1,840
|
Quote:
Quote:
I'm having problems setting DiAVC as preferred decoder on XP x86. It's a Q6600 with ffdshow the only other avc decoder installed and haali. If I disable ffdshow and open an avc m2ts/ts/mkv file in graphstudio a video decoder can't be found. However if I make a graph with haali+diavc it works for avisynth but it refuses to connect to video renderer, I can also set it to prefer in MPC-HC and it works. I've tried setting as preferred decoder in diavcsettings and changing to highest merit with graphstudio. Is anyone else experiencing this with XP or Vista? Any idea on how to set it to preferred? With windows 7 its working fine. Last edited by turbojet; 3rd December 2009 at 10:55. |
||
3rd December 2009, 20:58 | #222 | Link | |
Registered User
Join Date: Nov 2005
Posts: 497
|
Quote:
|
|
3rd December 2009, 23:31 | #223 | Link | |
Registered User
Join Date: Dec 2003
Posts: 179
|
Quote:
At times I get black screen, at times the picture freeze and at times everything is normal (all of the above usually alternates when seeking). I'm on Windows 7 x64 with everything up to date. |
|
4th December 2009, 01:52 | #224 | Link |
Registered User
Join Date: Jan 2007
Posts: 729
|
Resolution switching with linked MKV segments (files).
I recently reported a problem with video corruption using coreavc and attached two samples in this post: http://forum.doom9.org/showpost.php?...postcount=5265
I decided I should check your decoder too, as it clearly shows some promise. The good news is, DiAVC doesn't show the described video corruption and links the mkv segments fine if video width changes... ... the bad news: If height changes, the player will crash. That means that it crashes with the two samples I provided in the linked post. Your decoder however works with other linked videos I have (but didn't upload) that have constant height but changing width. I don't know whether it's a design limitation or not, but in case it's just something simple to fix, I decided to report it. Also, best luck with the decoder PS: The videos decode fine individualy, the issues only happen when linking is performed - so for testing, haali splitter is required. |
4th December 2009, 20:35 | #225 | Link | |
Registered User
Join Date: Nov 2005
Posts: 497
|
Quote:
|
|
4th December 2009, 22:04 | #226 | Link | |
Registered User
Join Date: Aug 2004
Posts: 211
|
Here you are:
http://www.multiupload.com/6O2ESAXATD http://www.multiupload.com/NOBIIIVN3Z P.s.: Thanks for mentioning multiupload, it seems pretty good. *edit* I missed his edit in that thread: Quote:
Last edited by Disabled; 4th December 2009 at 22:47. |
|
9th December 2009, 07:46 | #227 | Link |
Registered User
Join Date: Nov 2009
Posts: 327
|
Any news on the beta version? Also, I'm pretty sure I'll be waiting a long time for CoreCodec (zzz) to implement weighted prediction support, so I'd like to use DiAVC for most of my decoding. One of the first problems I encountered was that seeking seems to only succeed half the time. The other half, the audio keeps going, but the video freezes. Repeating the seek attempt multiple times eventually succeeds.
Edit: Another problem. When opening a new video while a video is already playing in MPC-HC, DiAVC starts with a blank frame and a seek must be performed before it shows video. Edit2: I've already complained about it before, but there is still some noticeable initialisation delay. Edit3: It also seems to me that, although DiAVC achieves a higher framerate and lower CPU usage, playback is choppier than with CoreAVC. When under load, DiAVC seems to drop frames more often than other Core. Hopefully these problems can be fixed. Keep up the good work. (Note: I'm using EVR Custom renderer on Intel GMA 3100.) Last edited by Stephen R. Savage; 9th December 2009 at 08:43. |
9th December 2009, 10:46 | #228 | Link | ||
Registered User
Join Date: Nov 2005
Posts: 497
|
Quote:
Quote:
I engaged in fixing bugs recently and the beta version is delayed for many days, the beta version will be released about 12 days later. I am not familar with the directshow and fixing bugs in filter is a hard work for me. It took up more times than I expected. "Playback is choppier" is because that the coreavc can drop un-referenced frames adaptively while the DiAVC hasn't the feature when the bitstream is hard, I will add the feature in future. As the beta version is faster than alpha version, the problem is easier.
__________________
The Next Generation Internet Video Codec project.[/url]. Last edited by schweinsz; 9th December 2009 at 10:52. |
||
9th December 2009, 13:19 | #230 | Link |
Registered User
Join Date: Nov 2005
Posts: 497
|
To the best of my knowledge, the renderer chop is due to the late-arrived frames. The current disign of the DiAVC always copy decoded frames to renderers without considering the current time. I believe the problem of chop can be reduced by faster decoder (beta version), dropping non-reference frames and lower playback rate. Is there some other solutions of the problem?
__________________
The Next Generation Internet Video Codec project.[/url]. |
9th December 2009, 17:24 | #233 | Link |
Registered User
Join Date: Nov 2005
Posts: 497
|
The DiAVC achieve 22fps for a certain bitstream of 30mbps, PAFF and 24fps on my laptop while the coreavc achieve 19fps, but I found the DiAVC is choppier, there is no possibility that coreavc never drop frames.
__________________
The Next Generation Internet Video Codec project.[/url]. |
9th December 2009, 17:26 | #234 | Link |
Registered User
Join Date: Nov 2005
Posts: 497
|
I have fixed most among them, I will release a new alpha version tomorrow after I fix another bug.
__________________
The Next Generation Internet Video Codec project.[/url]. |
10th December 2009, 06:42 | #237 | Link |
Registered User
Join Date: Nov 2009
Posts: 327
|
Some questions about (very) future development of DiAVC:
1) Is support for 4:2:2 or 4:4:4 subsampling, RGB coding, and higher bit depths (10-bit, 14-bit) planned? 2) Will that one bug that causes "maximum variance [-2,2]" in "bitstream that hardly exist in the world" be fixed? 3) Can conversion to RGB be implemented in the DirectShow decoder? I ask this because only the decoder in DirectShow can know the VUI data and apply the correct color matrices (and color primaries, but that is less important). The same question goes for fullrange content. 4) Does DiAVC set the interlace flag on pictures with field coding? I have no interlaced content so I can not check this. |
10th December 2009, 10:12 | #238 | Link | |
Registered User
Join Date: Nov 2005
Posts: 497
|
Quote:
A hard bitstream is not a uniform-hard bitstream, it is only hard on some piece of it.
__________________
The Next Generation Internet Video Codec project.[/url]. |
|
10th December 2009, 10:18 | #239 | Link | |||
Registered User
Join Date: Nov 2005
Posts: 497
|
Quote:
Quote:
Quote:
The current version always set Deinterlace_Bob for bitstreams that use interlace tools.
__________________
The Next Generation Internet Video Codec project.[/url]. |
|||
Tags |
avc, diavc, fastest decoder, h.264, software |
|
|