Notices

David: did you check if you have proper "write" authorizations to the card, of if the memory is not corrupeted? because this is the first time I receive this issue, and can be related with not being possible to write to disk (that's how we save it)

Of course can also (more probable) be a bug of us, that you find a way to trigger, if that is the case we need to receive from you what you did, your device, versions etc.. to try to replicate. This will help us solve the problem faster!

Marcelo

Thanks, good to know.

I have write ability. I haven't been able to reproduce it as of yet. What's driving me nuts now is the endless time it takes to load. I could grow gray hair by the time it's done. I usually have to close and reopen it. it's ridiculous. Also it plays youtube videos out of sync. I don't have the problem with mytube, so it's Canola. Listen, I love the app, but with those problems, it's not ready for prime time.

David :

Let me explain you a couple of things in those issues:

- > Mplayer out of sync. It indeed happens, but as you can read in the forum its not happening to everyone. Mplayer out of canola is almost a different beast, so using this as comparion doesn't work quite well, but the embedded mode of mplayer has issues. We have been hoping that this would improve, as mplayer is the only one capable of doing the trick. Mytube doesn't suffer because? It opens mplayer. So don't just assume it's canola, because we "don't" do nothing with the file. We ask:
"Mplayer please play this file on this window"just that. So it's not canola, it's the combination of something + a version of mplayer played in embedded mode.


Anyhow, there's versions of mplayer that are better than others, and people seems to be having this problems (I will not say that is rare, no way) but it's also not 50% of people having it.

What have we done: We have been trying to find out what's the optimal version for it, but it seems that it's not too "logical" and people with really different setup of repositories and apps can have something that breaks the whole thing.

The refresh of DB is a bug, we will work on it, but after you said the other problems (taking time to load) I can tell you : it's actually crashing the scanner with some file on your disk. The best way to fix it it would take too much effort from your side, but it would help us kill the problem :

Try to reduce the files / folders scanned and find out what files makes the scanner crash. For sure is a bug on OUR scanner, not dealing with a unexpected problem / format on your file. This was happeniing since the beginning and our only hope to solve is to get the file that makes it break, looking at that we can figure out what is the bug in our code and reproduce it.

So, if you can help us making it ready for prime times for users (that with ALL the reasons) don't care about the problems being here or there, they just want a good software that degrades well in face of a problem (for example, not stopping the reload without telling you anything)

Our actions : Friday we close a sprint of Canola development. I have been collecting all bugs from ITT and passing to the developers since then, and I can assure that Scanner bugs are there, as high priority. But we need to improve our library of testing
currently it's 2 8 giga bytes cards, with several musics from users here of ITT, they sent me because it was giving problems, as well picture files and so on...

So if you could do something like this:

A) set the media scanner to watch just 1 folder and see if it goes ok... then one more.. until it stops. That folder has a problem..
then you can go and zip (I can pass you a ftp) to you upload the folder to us, we can do a search inside the folder and debug.

B) About the youtube : can you tell us if you still have "chinook" repositories on?
Of course for us it would be a solution to SEND to the user exactly what we believe plays better the youtube, videos etc, but if we do that I can assure you people would kill us, because even the installer and the way the packaging of applications works on the linux distro of Maemo allows people to have this freedom.

Resuming:

We are paying the price of not having money to develop OUR media playback, or license it from someone else. If Nokia's default media engine played flv you would not face this problems as it's embedded mode is fine, but the overall performance is lower than mplayer, thus people go to mplayer not only for more formats supports but also because mplayer is indeed superior.

That's why we keep canola in "beta" mode. We believe it's quite usable in a out-of-the-flasher experience, but there's too much things arounds that can make it quite bad around :

a) bugs , from our side off course
b) several applications that we depend on not being quite "ready" as well
c) the way applications were installed before diablo, and people mixing chinoook and diablo repositories... mixing libraries.

This is not an excuse, but an explanation of : this is not negligence of our side. It's a whole platform evolving and a lot of work in several fronts are needed. We do what we can, Not only in Canola, but on Python, Bluetooth (take a look in how we are solving A2DP problem) but we are a small piece of the puzzle :/

If you want to send me some files, private message or you can use
handful AT gmail

Thanks for the pacience and information, and we will try to do our best

PS: I think in face of the scanner problems, and some id3 persistent problems, I will open one more sprint of development to focus only on those issues to make sure they are gone. We were planning to release beta10 next week, but I prefer to delay it 2 more weeks then to maybe not oslve some of this serious problems


Marcelo