[ticatc3]

@Atlanx wrote:

Especially the 400 is important. If it is 404 pixel you will have problems.

No, it shouldn’t. I’ve got a Bluray rip in xvid 960×720, it plays perfectly.

Also I would not use MP3 for the audio and stick with what was originally in the source unless it requires encoding, in that case I would use AAC.

[ticatc3]

I followed this guide but the resulting .dol was less in file size than the official version; about 100 KB less.
Videos with stylized subtitles no longer play properly. I wonder if the devkitppc or libogc version have anything to do with it.

[ticatc3]

Well well, I could never figure out why those libs failed to compile but ended up doing what I wanted by some creative hex editing.

Basically I can’t compile WiiMC, right? But I can compile VBAGX (for example) and use that to reference what to hex edit so I basically cut down 2000 instances of the value 2A0(672) to one.

And so here it is: https://www.dropbox.com/s/1tjmr3yyz7d2tjh/WiiMC_704.dol
If anyone wants square pixels out of their videos or just want to fill out their screen they can use this.

If anyone wants to use their own viWidth value to fit their needs/TV they can go to hex address 0x1109F2 and manually change the value from 640 to 720, this is of course for people who use their Wii at 4:3 aspect ratio. 16:9 is already using high values so you can use screen zoom to fit your preferences.

[ticatc3]

@leon777 wrote:

u can do it with the wii hombrew complier…

Wrong, if that was all that was needed I would have done it a long time ago.
More like: libfribidi, libexif and libconv don’t compile no matter what you do. (Using XP at least) Not to mention the long time it takes to compile each that you start to get demotivated when you get a compile error.

There’s nothing I can change/add to improve performance, WiiMC is pretty much perfect to me, I was just starting to get annoyed that I can clearly see a black line on the right of the screen caused by using 672 and if we set this to 704 no one should ever notice any black line/s and get videos to display square pixels at the same time; two birds one rock.

704 is not ideal for DVDs but considering the difference is minimal no one will notice a thing, it’s for this reason that I also posted a similar request in the feature suggestion area, to be able to toggle between values or specify.

Just ask yourself do you want to see every pixel of the video or do you want to not be aware of what you’re missing? Go with the latter because each TV has different levels of overscan and you’re already losing who knows how much when you’re at 100% vertical zoom; which should be = to stretching videos to 480 lines, kind of like how the YouTube app stretches 360p(if 4:3) videos to 456 lines.

I can do what I want to some extent by setting my Wii to 16:9, WiiMC will use 720 instead which lets me partially mold the video into fitting the screen with the video zoom options but it’s not practical at all. So I discarded this option completely.

[Author]

Posts