INTERACT FORUM

More => Old Versions => Media Center 11 (Development Ended) => Topic started by: IanG on January 20, 2006, 07:08:29 am

Title: How accurate is "Limit"?
Post by: IanG on January 20, 2006, 07:08:29 am
I'm trying to use "Limit" in Smartlists to select n minutes worth of mp3s.  Problem is that I often end up a long way short of what I want, e.g. I ask for 60 mins and get 45.  Any idea how I can fix this?  If it makes any difference, I've got mp3s ranging from a few seconds to over 30 min, so it should be possible to get very close to n every time.

Ian G.
Title: Re: How accurate is "Limit"?
Post by: Alex B on January 20, 2006, 07:29:26 am
I tried one of the predefined smartlists (Random -- one hour):

[media type]=[audio] ~t=60 ~sort=random

Most of the time it results 55-60 minutes. But sometimes the list has only a couple of short tracks or it is empty. This happens because MC just excludes the last track that goes over the limit. It doesn't make additional searches for shorter replacements. I have audio tracks that are over an hour.
Title: Re: How accurate is "Limit"?
Post by: IanG on January 20, 2006, 08:21:20 am
I tried one of the predefined smartlists (Random -- one hour):

[media type]=[audio] ~t=60 ~sort=random

Most of the time it results 55-60 minutes. But sometimes the list has only a couple of short tracks or it is empty. This happens because MC just excludes the last track that goes over the limit. It doesn't make additional searches for shorter replacements. I have audio tracks that are over an hour.

Thanks for that - I suspected as much!  I guess I'll have to add some extra selection criteria, though it would be nice if MC had a lower bound on the limit as well.

Ian G.
Title: Re: How accurate is "Limit"?
Post by: glynor on January 20, 2006, 02:06:11 pm
I tried one of the predefined smartlists (Random -- one hour):

[media type]=[audio] ~t=60 ~sort=random

Most of the time it results 55-60 minutes. But sometimes the list has only a couple of short tracks or it is empty. This happens because MC just excludes the last track that goes over the limit. It doesn't make additional searches for shorter replacements. I have audio tracks that are over an hour.

Ahhhh!!!  (Ding, light goes on.)  That's why it acts that way.  I could never figure out why occasionally, randomly those lists would be empty.  Now it all makes sense...