Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Matt]

Doorbell conversation moved here:
https://yabb.jriver.com/interact/index.php/topic,130868.0.html

[lepa]

Using Save() / SaveAdd() seems to break ListMix

example:

Code: [Select]

Save(0, v_2021[filekey])/
Save(0, v_2020[filekey])
DATES:
ListMix(FormatDate([L1],yyyy),,44265;44520)

COUNT YEAR 2021:
Load(v_2021[filekey])

COUNT YEAR 2020:
Load(v_2020[filekey])

2020 doesn't exist in list but v_2020[filekey] is still increased on every cycle (both variables are)
ListMix(IfCase(FormatDate([L1],yyyy),2,2021,SaveAdd(v_2021[filekey], 1),2020, SaveAdd(v_2020[filekey],1)),,44265;44520)

COUNT 2021:
Load(v_2021[filekey])

COUNT 2020:
Load(v_2020[filekey])

on similar list mix WAS 2020 is not printed when Save function is not used
ListMix(IfCase(FormatDate([L1],yyyy),2,2021,WAS 2021,2020, WAS 2020),,44265;44520)

[zybex]

Yeah, ListMix is finicky.
Perhaps you can get the counts you want using ListFilter to get just the items between 2 values:

listcount(listfilter([myList],0,min, max))

Code: [Select]

2020 = listcount(listfilter(44265;44520,0,43831,44197))
2021 = listcount(listfilter(44265;44520,0,44197,44562))
Regarding the ListMix issue you point out - it has to do with the order in which listmix/listmix2 processes the expression. The normal way to process any EL expression is to resolve it from the inside out; that is, process the inner sub-expressions and functions first, and work your way out with the results as you get them. So ListMix() is resolving the inner functions (saveAdd) before actually running the ListMix() function. The IfCase and FormatDate execution is delayed since they depend on [L1], which is only assigned after the ListMix unwrapping.

The difference between ListMix and ListMix2 is the order on which the execution steps are done - functions-first vs unwrapping-first. But there are other implementation details which I don't know about but can see the effects - neither implementation is "pure", they both seem to try to optimize execution with some side effects on some cases, like the one you found. I think Matt has been adding some function exceptions to ListMix(), in that those functions get to be executed after unwrapping instead of before. In that case, adding SaveAdd() to that list would solve your problem... however I don't think this is the right approach.

[lepa]

Yeah, ListMix is finicky.
Perhaps you can get the counts you want using ListFilter to get just the items between 2 values:

listcount(listfilter([myList],0,min, max))

Code: [Select]

2020 = listcount(listfilter(44265;44520,0,43831,44197))
2021 = listcount(listfilter(44265;44520,0,44197,44562))
Regarding the ListMix issue you point out - it has to do with the order in which listmix/listmix2 processes the expression. The normal way to process any EL expression is to resolve it from the inside out; that is, process the inner sub-expressions and functions first, and work your way out with the results as you get them. So ListMix() is resolving the inner functions (saveAdd) before actually running the ListMix() function. The IfCase and FormatDate execution is delayed since they depend on [L1], which is only assigned after the ListMix unwrapping.

The difference between ListMix and ListMix2 is the order on which the execution steps are done - functions-first vs unwrapping-first. But there are other implementation details which I don't know about but can see the effects - neither implementation is "pure", they both seem to try to optimize execution with some side effects on some cases, like the one you found. I think Matt has been adding some function exceptions to ListMix(), in that those functions get to be executed after unwrapping instead of before. In that case, adding SaveAdd() to that list would solve your problem... however I don't think this is the right approach.

Yup. For your suggestion: I was trying to achieve that parsing list is done only once instead of going through list multiple times. Don't know how fast it would be to take ListCount() after every year handling and ListLimit() already handled items out...

[zybex]

It makes me wonder if things like this wouldn't be best done on a timer; ie, everyday at 4am a script would run, compiling all stats and storing the counts and tops in some field that would then be used in Views. Is it that important to have an up-to-the-minute number of plays for each track since forever? And things like the playcount for past years won't ever change anyway. Updating once a day seems fine for this use case.

[lepa]

That would be great. If only someone had time to create such thing... Perhaps this kind of stuff could be done with MCUtils scriptor which could then be started with timer. Dunno if it only works for selected files or is possibly select files from scriptor.

[lepa]

I think ListReplace(list, index, newItem) to replace one item based on index could be useful. At least i didn't notice that existing list functions support this. One could use ListCount() and ListLimit() I guess to replace item but one clean function would be nice.

[zybex]

That would be great. If only someone had time to create such thing... Perhaps this kind of stuff could be done with MCUtils scriptor which could then be started with timer. Dunno if it only works for selected files or is possibly select files from scriptor.

You have an IM