CCCP Project Forums

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 2 [3] 4 5 ... 10
 21 
 on: September 10, 2014, 02:27:54 PM 
Started by JEEB - Last post by n99
Showing the Options menu of the new Beta while playing video was very slow, especially when a lot of RAM was used. This was not the case with the versions before that. You can especially see that with the blue bar at the top of each submenu.

 22 
 on: September 06, 2014, 07:43:49 PM 
Started by JEEB - Last post by cyberbeing
Yeah, the official builds still have the sanity check that we came up with, and then decided it was too easy to go over it with "relatively sane" content. I should really start pushing that patch to the upstream harder :P.

Quote
<kasper93> <@JEEB> kasper93, do note that we disable the sanity check. <<<< Yeah, and this is only thing keeping it from crashing.
<kasper93> atlTraceGeneral - Error in Rasterizer::ScanConvert: size (513382x63029) is too big
<kasper93> Indeed it is ;p I'm looking if this size is correct. It might be bogus.

I heard you before, but this doesn't make much sense. XySubFilter has never included any sort of sanity check, and it doesn't crash or use any significant amount of memory on that script. xy-VSFilter from CCCP doesn't have any issues either, while it uses the same version of your commit which crashes the ISR, right? I mean if you look at the lines around 01:52, it's just text with some simple tags. There is nothing there which should be massive enough to trigger MPC-HC's sanity check, so it must be a bug or something otherwise inefficient within the ISR code. I'd suspect it has something to do with how the MPC-HC ISR handles dirty rectangles with \move tags, but that is only speculation.

Code: [Select]
Dialogue: 4,0:01:46.41,0:01:51.16,OP1-Romaji,,0,0,0,,{\bord3\pos(1260,20)\fad(150,150)\an9\blur4\3c&HFFFFFF&\c&HFFFFFF&\t(2691,2691,\3c&HA184CB&\1c&HA184CB&)\t(3275,3275,\3c&H56413C&\1c&H56413C&)\t(3817,3817,\3c&H7E9EED&\1c&H7E9EED&)\t(4276,4276,\3c&H4E5B99&\1c&H4E5B99&)}hiku ni hikenai sorezore no jijou
Dialogue: 5,0:01:46.41,0:01:51.16,OP1-English,,0,0,0,,{\bord0\pos(1260,66)\fad(150,150)\an9\blur0.5\c&H2659FF&\t(564,981,\1c&H6130FF&)\t(2691,2691,\1c&HFFFFFF&)}We all have reasons why we can't back down
Dialogue: 5,0:01:46.41,0:01:51.16,OP1-Romaji,,0,0,0,,{\bord0\pos(1260,20)\fad(150,150)\an9\blur0.5\c&H2659FF&\t(564,981,\1c&H6130FF&)\t(2691,2691,\1c&HFFFFFF&)}hiku ni hikenai sorezore no jijou
Dialogue: 4,0:01:51.17,0:01:51.41,OP1-English2,,0,0,0,,{\bord3\an2\blur4\move(0,700,640,700,0,150)\fry60\fad(150,0)\3c&H627C91&\c&H627C91&\t(0,150,\fry0)}But I can't have it any other way (He's so simple)
Dialogue: 4,0:01:51.17,0:01:51.41,OP1-Romaji2,,0,0,0,,{\bord3\an8\blur4\move(0,20,640,20,0,150)\fry60\fad(150,0)\3c&H627C91&\c&H627C91&\t(0,150,\fry0)}hoka ni nani mo kangaerannai (massugu de)
Dialogue: 5,0:01:51.17,0:01:51.41,OP1-English2,,0,0,0,,{\bord0\an2\blur0.5\move(0,700,640,700,0,150)\fry60\t(0,150,\fry0)\fad(150,0)}But I can't have it any other way (He's so simple)
Dialogue: 5,0:01:51.17,0:01:51.41,OP1-Romaji2,,0,0,0,,{\bord0\an8\blur0.5\move(0,20,640,20,0,150)\fry60\t(0,150,\fry0)\fad(150,0)}hoka ni nani mo kangaerannai (massugu de)
Dialogue: 4,0:01:51.41,0:01:53.99,OP1-English2,,0,0,0,,{\bord3\an2\blur4\move(640,700,1280,700,2430,2830)\fry0\fad(0,150)\3c&H627C91&\c&H627C91&\t(2430,2830,\fry-60)}But I can't have it any other way (He's so simple)
Dialogue: 4,0:01:51.41,0:01:53.99,OP1-Romaji2,,0,0,0,,{\bord3\an8\blur4\move(640,20,1280,20,2430,2830)\fry0\fad(0,150)\3c&H627C91&\c&H627C91&\t(2430,2830,\fry-60)}hoka ni nani mo kangaerannai (massugu de)
Dialogue: 5,0:01:51.41,0:01:53.99,OP1-English2,,0,0,0,,{\bord0\an2\blur0.5\move(640,700,1280,700,2430,2830)\fry0\t(2430,2830,\fry-60)\fad(0,150)}But I can't have it any other way (He's so simple)
Dialogue: 5,0:01:51.41,0:01:53.99,OP1-Romaji2,,0,0,0,,{\bord0\an8\blur0.5\move(640,20,1280,20,2430,2830)\fry0\t(2430,2830,\fry-60)\fad(0,150)}hoka ni nani mo kangaerannai (massugu de)
Dialogue: 4,0:01:53.99,0:01:54.24,OP1-English2,,0,0,0,,{\bord3\an2\blur4\move(0,700,640,700,0,150)\fry60\fad(150,0)\3c&H627C91&\c&H627C91&\t(0,150,\fry0)}So I can't look away for even a second (But he's so dense)
Dialogue: 4,0:01:53.99,0:01:54.24,OP1-Romaji2,,0,0,0,,{\bord3\an8\blur4\move(0,20,640,20,0,150)\fry60\fad(150,0)\3c&H627C91&\c&H627C91&\t(0,150,\fry0)}isshun datte yosomi dekinai (nibui ne)
Dialogue: 5,0:01:53.99,0:01:54.24,OP1-English2,,0,0,0,,{\bord0\an2\blur0.5\move(0,700,640,700,0,150)\fry60\t(0,150,\fry0)\fad(150,0)}So I can't look away for even a second (But he's so dense)
Dialogue: 5,0:01:53.99,0:01:54.24,OP1-Romaji2,,0,0,0,,{\bord0\an8\blur0.5\move(0,20,640,20,0,150)\fry60\t(0,150,\fry0)\fad(150,0)}isshun datte yosomi dekinai (nibui ne)
Dialogue: 4,0:01:54.24,0:01:56.61,OP1-English2,,0,0,0,,{\bord3\an2\blur4\move(640,700,1280,700,2220,2620)\fry0\fad(0,150)\3c&H627C91&\c&H627C91&\t(2220,2620,\fry-60)}So I can't look away for even a second (But he's so dense)
Dialogue: 4,0:01:54.24,0:01:56.61,OP1-Romaji2,,0,0,0,,{\bord3\an8\blur4\move(640,20,1280,20,2220,2620)\fry0\fad(0,150)\3c&H627C91&\c&H627C91&\t(2220,2620,\fry-60)}isshun datte yosomi dekinai (nibui ne)
Dialogue: 5,0:01:54.24,0:01:56.61,OP1-English2,,0,0,0,,{\bord0\an2\blur0.5\move(640,700,1280,700,2220,2620)\fry0\t(2220,2620,\fry-60)\fad(0,150)}So I can't look away for even a second (But he's so dense)
Dialogue: 5,0:01:54.24,0:01:56.61,OP1-Romaji2,,0,0,0,,{\bord0\an8\blur0.5\move(640,20,1280,20,2220,2620)\fry0\t(2220,2620,\fry-60)\fad(0,150)}isshun datte yosomi dekinai (nibui ne)

As for the ISR, that is actually something we're testing in the latest beta after Underground78's latest changes early in the week (mo-tue) ;)

Ah, okay. The ISR is certainly making progress, but they currently aren't yet fully viable for fansubs in terms of performance and compatibility compared to xy-VSFilter/XySubFilter or even Libass. I pointed out a few things such things to them the other day. Underground78 for whatever reason always seems to go out of his way to never directly merge our code though, instead rewriting our code to something with near-identical and sometimes reduced functionality, which I don't really understand. They will get there eventually, but they are certainly taking the long and hard road, as they still haven't reached xy-VSFilter level of performance and functionality from way back in 2012. That said, I assume the purpose of enabling the ISR by default in that beta was to crowd-source collection of problem scripts for MPC-HC?

 23 
 on: September 06, 2014, 08:34:38 AM 
Started by JEEB - Last post by JEEB
Yeah, the official builds still have the sanity check that we came up with, and then decided it was too easy to go over it with "relatively sane" content. I should really start pushing that patch to the upstream harder :P.

Quote
<kasper93> <@JEEB> kasper93, do note that we disable the sanity check. <<<< Yeah, and this is only thing keeping it from crashing.
<kasper93> atlTraceGeneral - Error in Rasterizer::ScanConvert: size (513382x63029) is too big
<kasper93> Indeed it is ;p I'm looking if this size is correct. It might be bogus.

As for the ISR, that is actually something we're testing in the latest beta after Underground78's latest changes early in the week (mo-tue) ;) . I was supposed to write a release post for it, but this goddamn cold mixed with work kind of kept me away from it. (Also I can't believe I just slept for 15+ hours.)

 24 
 on: September 05, 2014, 06:22:50 PM 
Started by JEEB - Last post by cyberbeing
It's worth mentioning that I could only reproduce this crash Xtrike is reporting with the MPC-HC ISR enabled in that particular 2014-09-02-BETA CCCP build. I could not reproduce it at all with the official MPC-HC 1.7.6.217 nightly.

Another issue?
CCCP is enabling MPC-HC ISR by default in the 2014-09-02-BETA.

 25 
 on: September 05, 2014, 01:05:39 PM 
Started by JEEB - Last post by JEEB
Thanks for testing and the dump :) It seems like your usual out of memory error.

(click to show/hide)

(Also I was totally going to write an update post on this new beta, but work and catching a cold kind of kept me from that :P Will do that after I get some more tea and possibly feel a bit better)

Edit: I can replicate it on my Core 2 Duo laptop all the time, while my i7 desktop only replicates it every now and then. I wonder if caching of subpictures is related.

Edit2: Yes, caching was related. Turn off caching by setting View→Options→Subtitles→Sub pictures to buffer to zero, and it should just pause there for a while when allocating memory.

 26 
 on: September 04, 2014, 02:02:04 PM 
Started by JEEB - Last post by Xtrike
Crash keep happening in 2014-09-02-BETA while watching [FFF] Rokujouma no Shinryakusha - 08 [BD95A5E9] around 1:52min~

dmp file and dump text in the attachment.
Not sure if it helps or anything...

 27 
 on: September 04, 2014, 04:09:38 AM 
Started by ishardtofindaname - Last post by namaiki
You already ticked 'use built in subtitle renderer' as above and it still doesn't work?

 28 
 on: September 02, 2014, 09:53:36 PM 
Started by ishardtofindaname - Last post by ishardtofindaname
well the trick just need full screen mode [alt+enter]
if i chose non full screen mode the subtitle is cut off.
and how to use xysubfilter please tutorial?

or perhaps in next update can fix this?
sorry for late replay thank u namaiki

 29 
 on: September 02, 2014, 06:26:52 PM 
Started by zach26 - Last post by zach26
Ok, so I didn't try switching the monitors yet because it really does look like on .Mkv files that the picture looks just fine now. I set up madvr properly and a few test runs showed no discrepancies.

I can't thank you enough for the help. You guys are the best!


 30 
 on: August 31, 2014, 11:44:04 PM 
Started by zach26 - Last post by namaiki
Quote
Yes, I have an extended desktop. I always watch with MPC maxed out on my tv screen. It has always worked for me before.
Since you have multiple monitors enabled, make the screen that you want to play the videos on the 'primary monitor' or screen '1'. Problem should be solved after that.

Pages: 1 2 [3] 4 5 ... 10

Page created in 0.09 seconds with 16 queries.