You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something I do a lot for getting aggregate data when testing fixes on more common module formats is I run checks on the ModLand or Mod Archive collections with a program that takes a list of newline-separated filenames. Doing a similar test with xmp --load-only would be useful to determine if anything new is rejected by libxmp after implementing a patch. If there's a way to do this with xmp without invoking multiple xmp processes, I missed it. (The ModLand 2016 dump I test with has >20k Impulse Tracker modules, for example, so while argv is fine for less common formats, it just isn't adequate in this case.)
Would a feature like this be generally useful?
The text was updated successfully, but these errors were encountered:
I run "xmp ’shuf -n 100 modlist’"
You can probably save your playlist with "shuf -n 100 modlist > playlist" then run either "xmp ’cat playlist’" or "xmp ’head -n 1 playlist’ && sed -i 1d" for each line.
Scripting is awesome.
Something I do a lot for getting aggregate data when testing fixes on more common module formats is I run checks on the ModLand or Mod Archive collections with a program that takes a list of newline-separated filenames. Doing a similar test with
xmp --load-only
would be useful to determine if anything new is rejected by libxmp after implementing a patch. If there's a way to do this with xmp without invoking multiple xmp processes, I missed it. (The ModLand 2016 dump I test with has >20k Impulse Tracker modules, for example, so while argv is fine for less common formats, it just isn't adequate in this case.)Would a feature like this be generally useful?
The text was updated successfully, but these errors were encountered: