[cadbusca]

I have now released Enhancement Pack IV for 1.1.1 which should be compiled using SVN598 or later and libogc SVN 4421 or later. Currently SVN599 displays an error but the compile completes successfully.

[cadbusca]

Yes, users are only allowed to publish patches. I am not attempting and do not wish to support a binary release, only to share my patch. If the official binary runs correctly on your system, then the Enhancement Pack patch should work correctly too. What do you mean you are not able to compile? If you have a pc then you can compile using the simple guide.

[cadbusca]

Yes, I just found that out so you need to continue to make/make install the latest libogc as documented earlier.

[cadbusca]

For those of you who are attempting to utilize this patch with 1.1, note that 1.1 utilizes the appswiimc directory for the various working files like settings.xml and onlinemedia.xml rather than the directory the wiimc.dol was loaded from. So for those of you who followed the requirement to keep the enhanced version separate from the released version, you can continue to keep an appswiimc-plus directory but will need to change the wiimc.h line #define APPFOLDER “wiimc” to #define APPFOLDER “wiimc-plus”

If you fail to do so all your enhanced settings will be reset to their default values if you run the released WIIMC.

Once 1.1 settles down, I will publish Enhancement Pack 4 containing a number of fixes to the current patch as well as a number of new enhanced features.

[cadbusca]

Two things:

I will be incorporating the above changes to provide an option to specify the playlist files in Enhancement Pack 4 for WIIMC 1.1 which will also fix a numbe of bugs in the previous patch and add some great new features, Thanks to hhansen for this playlist naming feature which I had not figured out how to do. It now seems so simple!

Devkitpro has now upgraded to libogc 1.8.4 as of Oct 3, so its probably a good idea to rerun devkitProUpdater-1.5.0.exe which will bring libogc up to the latest released level. EDIT: This is not enough. See following 2 posts.

[cadbusca]

I have compiled succeesfully up to SVN554 but after that I have run into problems. Please post your sucesses with compiling latest SVN’s and any steps you had to take to be successful so I can update the guide.

[cadbusca]

Rest assured that Santa and his elves are hard at work. Just be sure to hang your stocking by the chimney.
You could also check the source code link under the above “development” tab, to see how many presents they have ready so far. 😆

[cadbusca]

Effective with SVN549, you also need to recompile C:WIIMClibslibntfs as per the original instructions.
This will also update libogc in devkitpro with required variables.

cd /c/wiimc/libs/libntfs/

make

make install

[cadbusca]

Use VLC-Shares as posted at the top of these forums to convert those HD videos to MPEG2 on the fly using VLC.

[cadbusca]

OK, since no one has posted the libogc steps, I guess I’ll do it.

WIIMC now requires the use of the latest libogc SVN in place of the previous libogc 1.8.3. Here is how to get and install it in devkitpro.

1. Download the libogc tarball from http://devkitpro.svn.sourceforge.net/viewvc/devkitpro/trunk/libogc/, which shows the current SVN level at the top of the page, using the “download GNU tarball” link at the bottom of the page or directly using http://devkitpro.svn.sourceforge.net/viewvc/devkitpro/trunk/libogc/?view=tar

2. Extract the contained devkitpro-libogc.tar directory and copy the libogc directory contained therein to C: which will give you a C:libogc directory.

3. Now using Msys enter the following to compile libogc, and automatically update devkitpro:

cd /c/libogc

make

make install

4. Return and compile WIIMC with:

cd /c/wiimc

make

[cadbusca]

As of SVN529, the previous need to patch libogc introduced in SVN522 has been eliminated, and the new functions embedded in the WIIMC source code. Anyone who made this patch should remove it and recompile the libogc SVN and update devkitpro.

[cadbusca]

Thanks, the “ext” change was made in SVN513in response to a bug I had identified. I thought I had posted a correction to my post, because I too have found problems in using the patch with 531. There is also a problem in 531 with the return of MPlayer detected errors like >1280 videos that also causes my “spec” reporting option to fail. I’ve advised the developers of that so hopefully it will be fixed in a subsequent SVN.

[cadbusca]

That makes sense to me, and most SVN’s have compiled successfully with the previous environment. But it would be appreciated when requirements change if a short post could be made in “Development” so that the rest of us don’t chase our tails, and so you do not have your valuable time interrupted with all these what do I do now questions.

[cadbusca]

Apart from conflicts in input.cpp and menu.cpp which can all be resolved correctly by chosing “use this text box”, the R495 patch will merge correctly with SVN529, so there is no real need for an Enhancement Pack update at this time. The new features in Release IV will come when they are ready.

EDIT: This no longer appears to be the case. I have used this patch up to SVN508, but later SVN’s make more changes as noted in subsequent posts.

[cadbusca]

Seems to be the wrong place to look for #define debug, but if one were looking for #define DEBUG_MEM2_LEVEL it would be.

So assuming that is the target, it looks like this change would work. That’s a lot simpler than modifying libogc.

It would certainly be a better practice, and save a lot of wasted time, if the SVN’s were committed with such changes in place.

C:WIIMCsourceutilsmem2_manager.c

– //1: critical errors 2: detailed info
– #define DEBUG_MEM2_LEVEL 1 // to get info about used mem, it’s an approximation because of memory fragementation

+ // to get info about used mem, it’s an approximation because of memory fragmentation
+ //0: turn off debug 1: critical errors 2: detailed info
#define DEBUG_MEM2_LEVEL 0

[Author]

Posts