Print

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

[Lenmaer]

Hello.
I would like to know if it was possible for you to keep http://www.cccp-project.net/wiki/index.php?title=CCCP_Beta_Testing_Guide updated?
Because, right know we don't know what the changes are in each new beta.

Thanks a lot.

[JEEB]

Will try, but it has been rather hectic, and random stuff has emerged and gone out of those builds' -tryouts. As Lord has developed patches for hi10p, I have made builds and put them into betas (more like alphas), with the pace we kept doing some of these and with my amount of free time towards all of this, I just had to cut somewhere :3

In other words, each of the July betas contains a -tryouts build patched for hi10p in one or another way, with the possibility of extra debug output depending on the patch (some betas were removed from the beta folder as they had problems -- although the 'crashing when trying to clean up' bug was not ours, but -tryouts'). If all goes well, this hectic phase might end in a few days, and then we can get to making last checks + the next release.

Oh, and the 2011-07-21_02 beta contains a fix for a H.264 time stamp overflow that was making things play back at 25fps instead of whatever frame rate they really had.

[Lenmaer]

OK, thanks for your answer.

Keep up the good work. 

[cyberbeing]

New 2011-07-22_01 mystery build has been up for a bit. With all these builds, it seems like it would make sense to sync your local tree with GitHub every time you make a new build. At least that way, code changes from build to build could be seen, without a written changelog.

[JEEB]

New 2011-07-22_01 mystery build has been up for a bit. With all these builds, it seems like it would make sense to sync your local tree with GitHub every time you make a new build. At least that way, code changes from build to build could be seen, without a written changelog.

I'm usually pushing my changes up onto git every time a build seems more stable or as stable as the last one (and/or when I have the time). Just pushed in today's repository status (2011-07-22_01), Lord has done a tremendous job with making -tryouts not crash at least with some of the "unknown" (to -tryouts) colorspaces, such as currently 9bit H.264 -- as well as with fixing filters from taking in data they can't deal with.

Lurking around #cccp and #darkhold on Rizon is extremely recommended for people who really want to know what's going on in real time.

[Lord]

Most of those are just test builds, because there was some actual component development involved this time. Putting them right in the beta dir probably wasn't the best idea at least.
Either way, the current changes I recall (which should be about final for the release now):

1. Duration fix for matroska files that have no DefaultDuration set for the video track, and some insanely high time scale values in the stream (the files were apparently produced by x264's matroska output). This caused a divison for the frame duration on the tryout side to end up with 0, that seems to just get "corrected" later to the default for 25 fps.
Added a workaround that sets the duration to 1 in this case, though I have no idea why it is not just ignoring the zero value altogether when it should be using the times it gets from the splitter anyway (it does get ignored fine when it is above 0).

2. Adjust CCCP Settings and VSFilter for the new pre-buffering changes. Default is still no buffer, and the checkbox sets it to 10 when enabled.
The usual fun of checkboxes stand there, namely that all current values that aren't 10 are treated as 0 and written as such when you apply.

3. Our beloved 10-bit stuff, limitations of which are mostly described at the end of this post. One related thing to note is that it also involves altering the color space matching priorities for 420P ("YV12"), to prefer YUV formats before RGB.

[Lenmaer]

Thanks for keeping us informed.
But I've a question, do you plan to incorporate the LAVSplitter and LAVAudio also in the final version?
Or is it postponed to a future release or simply abandoned?

[The Seeker]

But I've a question, do you plan to incorporate the LAVSplitter and LAVAudio also in the final version?

I too wondered about this.

[Lord]

The splitter is planned for next release, unsure about audio yet.

[cyberbeing]

I assume Haali would continue to be used for MKV, since LAVSplitter doesn't support Ordered Chapters?

[JEEB]

I assume Haali would continue to be used for MKV, since LAVSplitter doesn't support Ordered Chapters?

Correct. The plan is to enable mp4|mov, mpeg-ts|ps in LAV Splitter, and flv (and maybe ogm|ogg) during the testing phase at least. Matroska will be kept under Haali's supervision until ordered chapters-based segment linking gets supported in LAV Splitter (and when any possible other problems get sorted out).

As for LAV Audio, I have to admit that I want to test it out After seeing a random -tryouts bork with DTS-ES when using libavcodec's decoder, while LAV Audio was playing it fine, I'm getting more and more ascertain that we'll want to ditch the -tryouts boat at one point of time or another.

We will then move to LAV Audio if the cases it borks with will be less than -tryouts' -- or if they both have the same borks. LAV Video will most certainly follow after it gets some more love on the development side of things.

Edit: renamed the 28th beta as an RC. If no big problems arise, we're making a hi10p-compatible release during the weekend.

[Lord]

Correct. The plan is to enable mp4|mov, mpeg-ts|ps in LAV Splitter, and flv (and maybe ogm|ogg) during the testing phase at least.

You surely didn't mean that at least.

[Lenmaer]

Hi again.

I know I already asked this last year in the suggestion thread, but would it be possible for you to add different languages for MPC-HC? Even as separate/additional installer.
I'm asking this again, because they're more and more people using CCCP but who also aren't good at english reading/talking.

Another question (curiosity), why isn't chiyo-chan the default background anymore in MPC-HC? It was the default one for a long time in CCCP.
Maybe you could also make a contest for a new cute logo?

Also, why don't you add new MPC-HC toolbars? Like the ones you can find here: http://sourceforge.net/apps/trac/mpc-hc/wiki/Toolbar_images
The mpc_toolbar_round_black_32 [32x32] is really nice.

[Lord]

I know I already asked this last year in the suggestion thread, but would it be possible for you to add different languages for MPC-HC? Even as separate/additional installer.
I'm asking this again, because they're more and more people using CCCP but who also aren't good at english reading/talking.

Localization was considered back then but noone bothered to actually do much in the end. Translating installer and the settings app, rewriting them to actually support such at all, and then adding the UI stuff for changing languages are considerable work to do. Not to mention the support mess that a localized UI will cause in general.
Just making an addon for mpc-hc is likely relatively easy though, but not sure how useful that would be.

Another question (curiosity), why isn't chiyo-chan the default background anymore in MPC-HC? It was the default one for a long time in CCCP.

Only in one release (that means for about 6 months) years ago, and she wasn't liked that much.

Also, why don't you add new MPC-HC toolbars? Like the ones you can find here: http://sourceforge.net/apps/trac/mpc-hc/wiki/Toolbar_images
The mpc_toolbar_round_black_32 [32x32] is really nice.

They're basically user preference stuff, in other words about all 2 users who want to change it will benefit from them, for the rest it is just bloat. And apparently you have to copy/rename files to change it anyway, so not that much point in having more than one included in CCCP.

[JEEB]

Recent changes:

• main branch
  
  • general installer script updates
  • AC3 in -tryouts set to libavcodec (looking at that one bug that was found with DTS-ES that seemingly made us use libdts at the moment, will move to libavcodec if there's even the slightest hint that it can work better than the lolold libdts library)
  • Wavpack enabled in -tryouts with libavcodec decoder
  • removed CoreWavpack as an updated wavpack.c in libavcodec can do more than it ever did (read: we copied the current wavpack.c off current libav and put into -tryouts)
  • "Remove the DXVA checkbox that has broken more playback than given happiness."
• lav filters branch
  
  • LAVSplitter generally added, doesn't do squat about settings yet
  • Haali removed from everything but Matroska and OGM (not like you'll find many OGM files nowadays, but if you have and have a say about which splitter works better with them -- do tell)
  • Lord doing check-up on the LAVSplitter sources, possibly needed changes noted