MM 3 alpha 3 Bug reports/ Feedback / Questions

[rovingcowboy]

any one else notice the trouble with the dockable windows in the monkey skin? i just got the error again, i might have seen it before but not for a long time.?

anyway any of the dockable windows when taken to the right dock will jump behind the list view

they don't resize hortizontaly and make strange images of all
windows when resized verticaly.?

the list view is not moving from the spot it is in. which is
the left border of it is in the middle of the screen?

i presume that is from not being albe to resize the directory tree hortizontaly ? all things use to move in either direction.

this is happening with any and every mm 3 skin.

no report is filed because it does not crash?

something strange is going on with media monkey 3.
very strange. the above error report is now working properly again? not sure what happened but the computer has been restarted since this report was made. i just seen in the scripts forum cadmanmeg got their monkey rok. to work again by rebooting the computer?

so does mm 3 have a issue with the length of time the computer is on?

[M3wThr33]

I just noticed setting the disc# tag in MM doesn't seem to transfer over to iTunes. It doesn't seem to read it from the ID3 tag.

[MaFt]

just a small issue and suggestion!

in volume levelling if you hover over 'automatically analyze volume of unanalyzed tracks' it shows the tooltip for 'clipping prevention'

also, the icons on the bottom right of the screen (open folder, shuffle on, auto dj etc etc) may be better with a mouse-over / tooltip style tag on them. otherwise people like me have to click on them to find out what they are...

MaFt

[rovingcowboy]

not sure if i said anything about this before or if anyone else has. but it needs said so.

the mm 3 alpha's since alpha 1 has been having troulbe with
the previous and next buttons.

if you click them too many times while playing songs. it locks
and stops monkey. when it does this stop i hear the hard drive make the same noise i use to hear when the cdrom was empting the cache doing burning which use to happen because of too small of cache settings.

so it seems that media monkey is clearing its cache of the songs on the now playing list and crashing. this does not toss any alerts it just locks monkey.

does not matter how long you been playing songs.
you can sit there and play 10 seconds of song then click either of the buttons,
and keep doing that for about 10 to 30 songs and it will lock.

[Ludek]

I cannot reproduce it. Is anyone able to reproduce this?

[mhendu]

I have been using MusicIPMixer to tag my tracks with Musicbrainz and unwisely chose to archive the analyses into all my files. This isn't a problem with WMA and MP3 files but it screwed up my capability to play certain AAC tracks in MediaMonkey 2.5 with the appropriate plug-in. Now for whatever reason certain AAC tracks refuse to import into MediaMonkey 3 (alpha 3), even though they play fine in iTunes. Unfortunately I can't undo the file modification - hopefully the MediaMonkey team can figure out what the program does to the files and make sure that version 3 will be able to import and play these tracks. Some of them import and play fine, just not all. Thanks!

[MarineBrat]

I cannot reproduce it. Is anyone able to reproduce this?

If you're referring to the previous and next button issue, I can't reproduce it. I just hit them at least a hundred times with no prob. I tried it with album art set both to Selected and Now Playing, and with album art turned off.

I currently only have 36 songs in my now playing though. Perhaps rovingcowboy had many more? I just mention that because I think he said that his hard drive seemed to be crunching/caching when it happens.

I just tried it again with 350 songs in now playing. No change. It works fine for me.

[mattisse]

I just noticed setting the disc# tag in MM doesn't seem to transfer over to iTunes. It doesn't seem to read it from the ID3 tag.

I believe that the Disc# is not stored in the ID3 tags at all thus far. Why not? There is a frame declared in the ID3 standard for such a purpose --> TPOS - Part of a set

[rovingcowboy]

I cannot reproduce it. Is anyone able to reproduce this?

If you're referring to the previous and next button issue, I can't reproduce it. I just hit them at least a hundred times with no prob. I tried it with album art set both to Selected and Now Playing, and with album art turned off.

I currently only have 36 songs in my now playing though. Perhaps rovingcowboy had many more? I just mention that because I think he said that his hard drive seemed to be crunching/caching when it happens.

I just tried it again with 350 songs in now playing. No change. It works fine for me.

it happens all the time here even if i click them for about the same number of songs but only 2 seconds after the name shows up in the player, so i can read it and see if i want to hear it. i am using shuffle and continous when doing this.
it happens on any skin.
and i can do it at will.

mm 3 is on this winxp sp2 huge hd and 768 mbs of ram.
about 2000 mbs for the page file.
it's done this all the time i thought you others had also seen it?
if i let it go long enough it will toss an alert of the crash but that is only for the lock up not what caused it.

and every time it does this the cache clears. it is really remindful of the errors that caused us to get coasters when burnning cdroms.

i am wondering if this might be an error in mm 3 that makes mm 3 use the ram in the cdrom drive for the cache? that would be a smaller amount of ram which would account for the clearing of it.

it would also tie in with the cdrom burning errors others are getting because if mm 2 or 3 is using the cdrom ram for caching then there wont be any room for the songs in the playlists.

i have not had trouble burning with mm 2 i have not tried it with mm 3 yet.

but i know it is emptying the cache as i hear the waterfall sound in the tower each time it does it. and thats the same noise i heard when the cdrom use to dump the cache.



try the clicking of the buttons every time the song title loads in the player and see if you can get it in that short of time. i have a pent 4 so you might have a faster cpu.

i also have winamp on the computer..


hey dev's i just remembered an error on the old 486 win95
system. it was dealing with winamp since that was the only
player that will fit on that small system.

but when i started the computer up it could not find the swap file for some reason and, i noticed it keep location the cdrom drives ram and using it for the swap file.

i think it was windows more then winamp, but winamp would cause the trouble when i tried to play midi files or wav's on that old system,
it would crash i could not hear the cache dump, because it was only 8 mbs back then and was dumped fast.

but i am sure it is windows being triggered by the media player codes to lock in to the cdrom ram for caching.

why? because it is the first time since that win95 system that i have had a hd player lock in to the cdrom ram for caching.

it makes me think you might have used a bit of old code for something.? or monkey is asking for too much cache memory?

i should think 2000 mb's would be enough for monkey to use in the swap file
although the hd is getting filled up.

about 20 gb's left out of 80. that might be squezzing the programs in to the swap file and causing less room?
but 20 gb's of hd freespace should be enough too.

that is all i can remember about that old error and what i think is causing this same thing in monkey.

[MarineBrat]

i am wondering if this might be an error in mm 3 that makes mm 3 use the ram in the cdrom drive for the cache? that would be a smaller amount of ram which would account for the clearing of it.

Are you playing songs directly from the CDRom drive or from existing MP3's on your hard disk? I'm playing MP3 from the hard drive, and repeatedly clicking next as fast as I can at least 20-30 times, and then previous as fast as I can. Thus far it has smoothly jumped from one song to the next.

I'm using "WaveOut output 2.0.2a" and Aqua3 skin.

try the clicking of the buttons every time the song title loads in the player and see if you can get it in that short of time. i have a pent 4 so you might have a faster cpu.

This machine is probably a little faster. Dual P4 Xeon 2.4gHz, 1 gig ram.

[Guest]

I have not tried alpha version not sure how to beta test but I Saw someone post about back button.. I agree the back button in random does not function correctly. In random mode the back button functions exactly the same as the forward button which makes no sense. Should play the last song that was played not just any song. Not sure if this is already being fixed but wanted to put in my vote that this is a very very very important feature for those of us who love random song playing. I'm sure I'm not alone.

[Morten]

I have not tried alpha version not sure how to beta test but I Saw someone post about back button.. I agree the back button in random does not function correctly. In random mode the back button functions exactly the same as the forward button which makes no sense. Should play the last song that was played not just any song. Not sure if this is already being fixed but wanted to put in my vote that this is a very very very important feature for those of us who love random song playing. I'm sure I'm not alone.

This hasn't been fixed. I hope it will be too.

[rovingcowboy]

i am wondering if this might be an error in mm 3 that makes mm 3 use the ram in the cdrom drive for the cache? that would be a smaller amount of ram which would account for the clearing of it.

Are you playing songs directly from the CDRom drive or from existing MP3's on your hard disk? I'm playing MP3 from the hard drive, and repeatedly clicking next as fast as I can at least 20-30 times, and then previous as fast as I can. Thus far it has smoothly jumped from one song to the next.

I'm using "WaveOut output 2.0.2a" and Aqua3 skin.

try the clicking of the buttons every time the song title loads in the player and see if you can get it in that short of time. i have a pent 4 so you might have a faster cpu.

This machine is probably a little faster. Dual P4 Xeon 2.4gHz, 1 gig ram.

i'm using ogg files and have no cdrom in the drive at all that is what makes it strange why is the ram in the cdrom being used for caching?

or maybe it is the hd drive dumpping it but making the noise so loud it sounds like it is right in front like the cdrom drives are?

i am using the same wav output plug in you are.
my pent 4 is a 235 or so hrz cpu.

i am also wondering if this might be due the ogg files. since
on win 98 with mm 2.5.5 i found an error dealing with the ogg vorbis dll file. is that the same one used in this mm 3 alpha version? that error in 2.5.5 causes the whole of monkey to up and stop. i have to close monkey and restart. which is the same thing i am doing here when it locks, closing and restarting monkey then all is fine it seems the longer i play mm 3 the faster it will do the lock up.
could the ogg vorbis dll be the one that is signaling to use the cdrom ram for the swap file?