One missing piece.

All I need is: ArtistLastPlaygedAge and AlbumLastPlayedAge.
With that, I'm done and happy.

lumper5 wrote:Perhaps I missed the following while browsing this topic, but I did not see it covered. How to filter MegaDJ in MM 4.x so that only music type is selected. I've tried a query filer of MediaType=music but that only returns an empty list. I've tried variations on Type='Music" &tc, but nothing seems to work. I want to filter MegaDJ to exclude AudioBooks, Classical Music, Podcasts and other media types and only select Music. Suggestions?

I'm having the same issue. I thought for a second that maybe it was an enumeration and did MediaType=0 but then I still saw audio books in the list. Would be helpful to fix this.

I know this thread is old, but I just came across MDJ and wondered if it was possible to create a node that has duplicates in it (using ratings for the math)? My goal is to have a node that contains all of my tracks which are not BOMBS (so math filter for the number of tunes isn't constant), but I want tracks with a rating of 5 to exist in the node 5 times, those with a rating of 4 are there 4 times, etc. My end goal is for MMW to play the tracks with a higher rating more frequently then those with a lower rating (not necessarily to exclude lower-rated tracks from the node/playlist, just don't play them as often).

Is that doable with MDJ?


Thanks

Perhaps I missed the following while browsing this topic, but I did not see it covered. How to filter MegaDJ in MM 4.x so that only music type is selected. I've tried a query filer of MediaType=music but that only returns an empty list. I've tried variations on Type='Music" &tc, but nothing seems to work. I want to filter MegaDJ to exclude AudioBooks, Classical Music, Podcasts and other media types and only select Music. Suggestions?

A couple of new releases brings us to 2.59.

There were some time issues relating to local/global time, so that's been sorted. Also, I think the latest MM changed the main scripts path to the standard users path (rather than the "Program Files" path), so this release takes that into account.

Download in the usual way (or upgrade straight from MM).

http://www.skytopia.com/software/megadj/

Forgot to say before that 2.57 is out. This fixed the bug in 2.56 where a DLL is needed that the user may not have, thus causing MegaDJ not to load at all.

Download and install instructions for MegaDJ v2.57 from here as usual:
http://www.skytopia.com/software/megadj/

Happy new year all!

Based on a specifed MM Playlist, or a specific file directory,
Play X number of tracks by any AlbumArtist
lather, rinse, repeat

As you probably know, MegaDJ can handle the file path as a field, so something like this is possible:
SongPath~'blah' && AlbumArtist~'blah'

However, I'm guessing after the first batch is played through, you want the SongPath to automatically change? As Anthony said, 'fraid that's not possible currently. You would need to set the nodes up yourself. Maybe MagicNodes can offer what you want...

@Rollerphant:

What have you tried so far for the query? I'm thinking so far that this may be impossible, unless you first set up child nodes for each AlbumArtist, which could easily be a laborious process. Even if you can automate that part with something like MagicNodes, I don't know if MegaDJ would be able to interact with those nodes. But, my thinking is, if you can have MegaDJ nodes for each AlbumArtist, then you can create a master node that rotates X number of tracks from each of those AlbumArtist nodes.

Perhaps twinbee may have other ideas, however. I hope you're able to figure this out! If I think of anything else too, I'll let you know.

Trying to figure out how to do something that seems like it should be real simple.

Based on a specifed MM Playlist, or a specific file directory,
Play X number of tracks by any AlbumArtist
lather, rinse, repeat

I've tried to write the query, but keep getting stuck. Any help wuold be appreciated.

Thanks for the script!

MegaDJ v2.56 is now available.

For people who have more than 30000 tracks, MegaDJ now includes ALL the tracks in your collection when picking random tracks. Many thanks to Anthony for picking up this rather serious bug. The more you had before, the worse it was.

MegaDJ is now a smaller download, and the speed is up to twice as fast for many random playlists.

See MegaDJ homepage to download in the usual way:
http://www.skytopia.com/software/megadj/

I'll actually get 37-39 queued most of the time? Because those last few excluded were dupes?

Yep, that's right.

That check for dupes doesn't seem slow to me, and it works well.

True, but checking for song ID is different than checking for album. I seem to recall album being much harder/slower, but I can't say for sure.

I'd be curious to take a look at the C/C++ code..., and see if I can understand any of it.

Haha, talk about being plunged into the deep end Okay, what I might do before sending the code to you is port MegaDJ over to Visual Studio, as it will be much easier for you to set up. Also I've found the Microsoft compiler to run around twice as fast as the Dev-C++/mingw compiler, so I wanted to port it over to Visual Studio anyway at some point.

How does the current "No Dupes" function work? It seems like it removes the second or greater occurrences of a song with the same ID, right? Is this why, when I specify a node to queue, say 40 songs, I'll actually get 37-39 queued most of the time? Because those last few excluded were dupes? That check for dupes doesn't seem slow to me, and it works well.

Anyway, if "No Dupes" seems to work as simply as I think, then, would it be possible to add an option for checking for dupe albums? Albums have an ID value too, correct?

I'd be curious to take a look at the C/C++ code..., and see if I can understand any of it. Maybe some next project I do will be to learn the basics of C/C++, because currently, I know nothing of it

What's that quote, something like "the generation of random numbers is too important be left to chance" - haha

This one unfortunately is going to be a pig to test for. Unless you have good experience with random numbers, I have a feeling that maybe what you're seeing is what one would actually see with 'true' randomness anyway. It would be a coincidence if there weren't any coincidences and all that jazz, (and maybe you know of the birthday paradox: "if you get 20 people in a room there's a 50/50 chance that two of them will share the same birthday).

In any case, I'm semi-interested in adding a "no album-dupes" feature, though would worry this would impact on search speed.

You're also right that the main functionality is contained in the exe file. If you want to look further into this, I'd happily give this source code to you, though would ask you use it for your purposes and not spread it for now (not that you would, though actually, I have thought about opening up MegaDJ completely). Only if you're interested of course (you were brave enough to tackle the vbs file which is a bit messy to be honest, and I'm afraid the C/C++ source code for the exe is perhaps more convoluted ). C/C++ is trickier to program as well generally, and it'd be a bit awkward to setup (I used Dev-C++, maybe Visual Studio's compiler has better random number generation).

Cool, there's an update to MegaDJ I'll be happy to either install it and include my changes, or incorporate your changes to my current install. Either way, I'm in no rush to do anything, since I've been busy with other projects and such, so it might be a while before I get around to this.

I've been meaning to ask something... is there any way to control frequency of artists and/or albums? In my more specialized nodes (ones that query less than 1500 tracks), I'll fairly often see one or two (occasionally more) artists have four or more songs in my generated set of 20-30 tracks. Even worse, when that happens, the tracks tend to come from one album. It's like the algorithm is not completely random, haha. I mean, even in the relatively small subset of my library that these nodes query, there should be over 50 albums to choose from--so, getting these dupes is weird. I've looked previously in the code to see if I can find how the current implementation of "No Dupes" works so I could try to add "No Dupe Albums" or something like that, but all I could see and figure out in the code was how to enable or disable "No Dupes"...perhaps only the exe file does most of the work here?

The workaround for now is to refresh (F4) the two nodes which make up the rotation playlist. Make sure you have Easy_DJ and TOP_NE_PAS_EFFACER set up as random.