[jamied486]

Thats a shame. I’ve just installed the pack you sent out a few days ago. Works nicely thus far. Thanks for your efforts?

Why does WiiMC+ have to run from wiimc-plus folder? If it could run from “wiimc” as an option, then would it work from the channel loader? I’ve of course renamed the wiimc-plus to wiimc with no good results, so I’m guessing that the binary is looking specifically for wiimc-plus.

Beyond compiling it myself to test this, are there any other options?

Thanks

[jamied486]

Very sorry to say that 1.2.4 is still crashing intermittently when trying to play an AVI.

From what I can tell, this problem has not changed since 1.2.0. I’ve seen no improvment.

Thanks Tantric for all your efforts. I guess it’s just a matter of time.

ezwiimc

[jamied486]

OK, I know I’m tempting fate here, but before I do, I’ll just start by thanking Tantric and everyone else for a great product. As a developer with software of my own out there that isn’t perfect, I know how frustrating it can be when something works fine under your own tests, and then people using it have problems.

After my last post on this topic where I basically indicated that I was having the same problems as everyone else, I reverted my installation back to 1.1.8 which works a treat.

Having come back here today to see if anything has changed I’m amazed that there are still heaps of people here having the problem and yet no solution…

The straw clutching, blaming fragmented drives, bad SD cards, etc all seem like a lot of guesswork to me. From what I can see, it doesn’t matter where the video comes from, or it’s format, the software is flaky. Something MUST have changed in the 1.1.8 to 1.2.0 update that has caused this problem.

Tantric, are you running the exact same binary, or a local build from the same code? Is it possible that the public binary has some minor corruption in it? Can you rebuild 1.20 and check to see if it matches?

The way this problem happens only on first play of a video smacks of an initialisation issue to me. Are we dealing with some uninitialised data within the application that on one run is OK, but on 4 out of 5 causes a crash?

Were the changes in code between 1.1.8 and 1.2.0 dramatic? It is worth doing a diff of the two sets of code, or would that be unrealistic?

I know I’m probably asking questions that have been asked before, or making suggestions that have been checked already. I’m not trying to teach anyone how to suck eggs, and I don’t mean to sound like a know-all. I’m just trying to sound out a few thoughts in case one of them hits the mark, especially for people like Tantric or jhb50 who have done so much.

Again, thanks for a great product. My family uses it almost daily, and apart from the nag to update, it works almost flawlessly under v1.1.8.

[jamied486]

I, like many of these other people have been having the same problem. I ended up reverting to 1.1.8 in an attempt to get round the problem because it was just too flaky for words.

I’m quite sure that 1.1.8 worked fine, almost never crashing; that’s why I chose that version to revert to.

Now I find that even 1.1.8 is unstable and like others here, from one attempt to the next I can’t be sure that it’s going to play a file or not. I would note however that if it plays a file OK, I can usually stop or finish that file, and then play others without any problems.

The crash ONLY happens for me on the first file played after starting wiimc. I always start from the channel forwarder. I haven’t tried the HBC route yet; I’ll give that a go.

It would be great to get this fixed, as we can’t disable the update nag, and like some people here, dismissing the nag seems to cause problems too.

[jamied486]

I too had problems, but only because step 8:

– 8. Extract the boot.elf file from the Hackmii Installer zip to a new folder on your SD Card. ex: SD:HBC

said to put the boot.elf in a folder off the root of the SD card.

Moving that folder to /apps allowed me to run it from within HBC. I already had HBC running 1.8 with IOS38. It’s now running IOS58 as required, and all is well for me (I don’t use USB, so I’m not sure about that).

Thanks for the instructions, it made the whole thing much easier.

ezwiimc

[jamied486]

Thanks for that Tantric.

You’re amazingly responsive here. It’s great to see the app so well supported.

[jamied486]

I agree with yuuichi.

If wiimc weren’t able to play the files then they wouldn’t play at all would they, or does a lack of support for a file format simply mean that it will play it, just not reliably.

I have files that appear to play fine for a while and then, perhaps because I am using an SMB connection to my overworked asus wl700ge, either the connection it too slow, or something similar and wiimc get’s into contortions trying to buffer the next chunk.

I’ve found that on the rare occasion that I can hit “home” to get back to a menu when this happens, simply resuming the video juts resumes the same problem, as if wiimc has it cached, or hasn’t emptied the buffer somehow.

If, in this scenario, I drop back to the wii system menu, and then go back into wiimc and resume, then all is fine, for a while until the whole shebang starts again.

The file I most recently had problems with was a cleanly re-encoded divx AVI file at a resolution of 606×360. As I said above, it played, but then stopped working after a short while (just over 10 minutes).

ezwiimc

[jamied486]

Thanks Tantric. I looked everywhere but at the tree in front of me.

ezwiimc

[jamied486]

I thought it might be best waiting for another release before upgrading from 1.0.4. I’m glad I did. From the activity here I could tell it wouldn’t be long.

I may be blind, but I was looking for some form of release notes. I couldn’t find any.

For me, 1.0.4 works well apart from the unstable playback of divx across a wifi SMB connection. I’m hoping that 1.0.6 will fix this (or at the very least, improve it).

Given the quantity of messages here about what was broken in 1.0.5, it’s a little hard to be sure of what was actually fixed, or improved. Can someone point me in the right direction please?

Thx.

[jamied486]

Just to note that I too am noticing freezes and lockups whilst playing an AVI over an SMB share. From my observations, I am inclined to confirm the suspicion that it is related to the wifi connection.

Admittedly, my SMB share is on an ASUS wl700ge, and there may issues with it’s performance or ability to feed wiimc the data quickly enough (though I’m not so sure about that part).

When it does happen it is similar to watching digital TV when the signal drops out and it clicks and splutters and the video freezes. Most times wiimc crashes with a dump on the screen and says “restarting in 8 seconds”. The restart does not always work. We have to hard boot the wii sometimes.

One thing that would be good is if wiimc would update the resume marker periodically as the file is playing so that if a crash occurs, the resume point is closer to where it crashed.

Overall, it works very very well. Wiimc has made the purchase of the Wii truly worthwhile from my point of view even with it’s couple of problems.

Thanks

ezwiimc

[jamied486]

Yes, I’ve read up on the others now and it would seem to be true. Having also tried a couple of the others now, wiimc wins hands down for ease of use and stability.

We’ve have it crash once thus far, but it was easily recovered, and without having to do a hard reset on the wii itself.

I’m finding that probably 60% of the homebrew apps we’ve tried are unstable to the point of needing to delete them. A number just crash and the only way out is to do a hard-reset (hold power down). wiimc thankfully is not one of the 60%.

Keep up the good work.

[jamied486]

OK, thanks for that. A shame, but something I can live with for now. Do you know if any of the other media players on the wii support it? Perhaps I can install another for that ability.

Thanks again

ezwiimc

[Author]

Posts