Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Please do the steps listed below so I have some more information.

With no graphics or hardware changes I'm aware of, recently I started having this issue.
When I say slow response to skipping, I mean if I try move to a different part of the video, occasionally it response slowly.
Periodically the video freezes(not any other applications) while audio continues to play.
And just now I had MPC crash for the first time.
I've tried video sources from different hard drives. Restarted, updated graphics driver, reset CCCP settings, reinstalled, clean registry with Ccleaner and run a scan disk for bad sectors.
Any assistance would be appreciated

Thank you much for this.  It was like magic.  I'd love to know though, what exactly did this end up doing?  I'm so curious to know what the problem actually was. 

Fixed on IRC by installing the CCCP beta 2013-06-17.

More info: http://www.cccp-project.net/forums/index.php?topic=6604.msg43992#msg43992

Please do the steps listed below so I can have more information.

I was re-watching a concert of Miku, when I noticed that one of her songs (The Disappearance of Hatsune Miku) that contains fast and long subtitles does not show subtitles when the long lines start... Please help me!

oh sorry, i misread your response

it worked!

thanks

You might want to re-read my response, but let me still rewrite it for you

Open the settings app, click the System Settings button, and then check the AVI checkbox on the LAV side. Click OK.

And then LAV Splitter should get used under Play->Filters when that AVI file is opened. See if the result is different from what you get with the Windows default AVI Splitter.

AVI splitter is enabled in the filter, however, the problem still persists

So, where can I download this spec and the addition to it?

The original ASS specification is here.

madshi wrote a basic summary of the addition within SubRenderIntf. The plan was to document it more in-depth at a later date. I didn't expect anybody to find it so difficult to understand how that the "YCbCr Matrix" header was based entirely around explicit tagging. You make a good point that we should make these details more obvious and a bit more official. There were talks about adding details to the Aegisub Wiki as some point, or possibly creating an official amendment based that original ASS specification document, but it seems that never happened.

Where can I see the agreement of the people involved on this?
...
Again: where and when was that agreed on?

Somewhere in that massive heated debate on Google Code between xy-VSFilter dev, madVR dev, and Aegisub dev about how that YCbCr Matrix header should be defined. We ultimately settled on the interpretation that the ASS specification defined subtitle colors as YCbCr video -> RGB, rather than native RGB. This is what justified the requirement for explicit YCbCr Matrix tagging with ASS scripts, while only SRT were defined as RGB Native for use with "None".

The agreed upon tag added the possibility to create scripts in two ways and this was mainly because of the xy-vsfilter team objecting other header propositions that didn't have this problem, so I find it irritating that this very same team is now reluctant to actually implement the things they themselves pushed and is instead trying to redefine the spec's "None" to "resolution guessing is good enough" on their own. madshi was one of the main ppl. involved in discussing the new tag and one of his main requirements was always to have yuv and rgb rendering match, which is currently not the case currently because of this missing feature.

You are making many incorrect assumptions here, since what I've been telling is the current definition of "None" as defined by madshi, not myself. Rather than discuss this with me, why don't you ask madshi for clarification on our GoogleCode issue tracker about the correct usage and handling of "YCbCr Matrix = None". As far as I'm aware, I've only been repeating his exact definition of "None" all along as it fits into the finalized explicit matrix tagging scheme.

A bit outside of the discussion: currently xy-vsfilter does not even seem to be guessing by resolution when everything is set to "Auto" and "YCbCr Matrix: None" is supplied? (3.0.0.211 "stable") The release notes say it would be using resolution-guessing in that case but it seems to just assume "YCbCr Matrix: TV.601" instead. Can anyone else reproduce that?

How did we miss this... It looks like we introduced this bug one day before we released the first stable build supporting the YCbCr Matrix tags almost a year ago. Originally "YCbCr Matrix = None" was tied to dual-purpose Auto_Guess function as "Auto", which we split into separate "Auto" and "Guess" functions at the last minute to allow for a GUI override. It would seem at this point we forgot to change "YCbCr Matrix = None" so it would trigger "Guess" instead of "Auto".