MediaMonkey 3.1 Testing NOTREP

[TwiztidSinz]

I've been looking forward to this new version for a long while now
Thanks for all the hard work that has gone into this.

[kookykrazee]

I don't know if this is a bug or not but when I go to rename some files and start typing, the autocomplete is sorta grayed out but you can arrow down to the name you want. Not a big deal to arrow down once but it previously had autoselected the first name in the list.

Keep up the great work!

K

[aprzybylo]

Is there somewhere the list of new features / changes in 3.1

[Michel37]

http://www.ventismedia.com/mantis

----------------
Listening to: Ayreon - The Accusation
via FoxyTunes

[nynaevelan]

That site is NOT helpful in finding out what features/changes have been made in 3.1. All it does is list the problems and/or requests that have been received and acknowledged by Ventis.

Nyn

[Michel37]

It is helpful.

Red = New

[rovingcowboy]

That site is NOT helpful in finding out what features/changes have been made in 3.1. All it does is list the problems and/or requests that have been received and acknowledged by Ventis.

Nyn

true.

but rusty said he will post updates with the whats new list in when they start with the next updat for 3.1 alpha testing.



so the above site is good to see what is being worked and what is needing worked but as a list to follow it is lacking.

[nynaevelan]

but rusty said he will post updates with the whats new list in when they start with the next updat for 3.1 alpha testing.



so the above site is good to see what is being worked and what is needing worked but as a list to follow it is lacking.

Well I hope that is going to be soon because I am running blind here. I am willing to take the risks to beta test but it would be nice what it is I am supposed to be testing. Except for making sure all the current features work, I still need to know what new features should be tested. Don't get me wrong I am not ungrateful for the opportunity of the beta versions, but this is very frustrating. Especially since I have posted problems and have yet to receive any input from developers. What is the point of beta testing if the developers will not address the issues... I'm giving up my time, I want ackowledgement of that. Ok, rant over.

Nyn

[rovingcowboy]

you can rest asured that they do see your posts of errors,
its just that they might be too busy some times to post a reply.

which is why you see me sometimes trying to fill in a general reply for them.
i don't do anything with them other then email questions or send in items like icons.
i use to beta test, but since i found out the system i have is so tweaked that some
of the errors every one was posting they had for mm 3.0.3, i never seen. so i am
not beta testing anything anymore. and i don't have new hardware or new devices
either so that is another reason for me to stop testing.

but they still need to know if the new features are infact messing with any of the old features,
so they can adjust them.
so keep up your good testing if you can find any errors in the other new features
that will be nice too. but don't just try a new feature if you don't know what it should
do in the first place. make sure you know what it is to run like then check it out.
that is how i did the testing of the new items only if i understood them.
then when someone said they found an error i tried to recreate it on my system by
what they did, if i could then it was a multi system error. if not then it might be
only their system or their hardware,

also to read that site just look at the green stuff, that is what they think is fixed.
click the number on it and read what the bug was and then try to recreate it on your
system if you have it let them know if you don't have it let them know but post
what version of monkey you are using to test it.


and anyone else with new hardware and or new os's and new devices you might
want to take up the beta testing if you have time.

[chrisjj]

All it does is list the problems and/or requests that have been received and acknowledged by Ventis.

It doesn't even do that. It omits dozens of problem reports received from me.

[nynaevelan]

All it does is list the problems and/or requests that have been received and acknowledged by Ventis.

It doesn't even do that. It omits dozens of problem reports received from me.

The key part of that sentence is received and acknowledged by Ventis

Until that part is done, they will not show up on that list. I plan on trying to sift through the "Official Wishlist" to see how many if any of those requests are on the list. But it will take me some time to get to it.

Nyn

[rovingcowboy]

All it does is list the problems and/or requests that have been received and acknowledged by Ventis.

It doesn't even do that. It omits dozens of problem reports received from me.

it could be working like this.
if the problem has already be reported by some one before you then why post it twice? just mark the second report as a confirming report. which is what is very needed to be able to see how many testers have the same error. if lots of testers have it then its multiple system, if only one then its more likely only something on their system.

so the more reports they get the better the program will be. but why add the same report for one error from every body that reports it.??