Enjoy the real configuration dialog (you'll need to change your settings from defaults again) [...]I did not had to update the settings, those were transferred from v0.4.0-pre.3+1 to v0.4.0-pre.3+2. It might be noteworthy that I update foobar2000 and user components manually only, except for the initial installation of foobar2000 which probably makes a difference regarding the preservation of the settings.
[...] enjoy the new pattern visualization [...]Awesome! After all these years we get to have a live pattern viewer. That's a neat surprise. Thank you very much!
Unfortunately I have to report a bug regarding the pattern visualization right away:
I'd like to suggest a couple items regarding the pattern visualization. I leave it to your expertise and motivation whether these are feasible, of course:
Try reducing or turning off volume ramping, but note that many XMs will sound bad without it, since the tracker implemented it and many composers assume it will be featured in the player.
I've also observed this GPU drain and have not really found any way to mitigate it if you still want smooth painting.
The choices available as a child window is very limited and the only way to reduce it is indeed to draw less often.
The GDI mode in foo_wave_seekbar has a much lower update rate than the other two frontends. foo_wave_minibar doesn't have any control at all, as it was made to not be complicated. The difference between GDI and minibar is strange, as they're pretty much the same kind of painting logic.
It wouldn't surprise me if this is something that newer Windows 10 builds introduced too, considering that I've never had any trouble in the past with either component.
As for resolving this, I've got no clue. Drawing rapidly as a child window in foobar2000 is a right mess and you have to either be wasteful or careful to not starve the message pump. It's one of the reasons why I never bothered to make any dockable visualisations as the perf just isn't there.
Last post by sanskrit44 -
edit: I just tested it out:is there any benefit to install wine-mono in first place when dotnet20sp2 gets installed right afterwards? afaik, mono is a replacement for dotnet and gets uninstalled by winetricks when you attempt to install dotnet anyways.
More a general OpenMPt question than anything, but I've noticed that modules that have short, chippy samples, such as dunderklumpen.xm by Loonie, have a bit of an attack added on to their samples, which can sound yucky with some modules, something that DUMB didn't do before. I'm curious why? Is it something the original tracker did? Additionally, the attack seems to be module dependent, chip 7.xm by Saxxonpike doesn't do it.
Last post by Chibisteven -
It's quite easy to do.
1. Right click on the range of songs you want to remove the tag from and click on properties.
2. Scroll down to the desired tag and right click on the name of the field and choose remove.
3. Click apply.
1. Right click on range of files you wish to remove this tag from and choose "Extended Tags..."
2. Find the desired tag and highlight it.
3. Click the red X to the left of the album art.
4. Click OK.
Values to play with if you want to troll your friends:
0 = Off (no warning) (same as the tag not existing)
1 = Explicit Warning
2 = Clean Version
I didn't see any command-line suggestions for this problem on Reddit. Do you have any?
To be clear, I can do it in a GUI like Mp3tag, but that is purposeless for my problem. I need an automated script, so only command-line is useful here.
You had a reply on reddit before you removed the post, did
I can't consistently remove these. Even after batch removing all tags.
Of course, I would like to preserve other tags, but I find the "ID3v1 comment" tag particularly stubborn.
How can I make it go away for good via the command-line?