Have you applied the post-release crash fixes to the 22022 install (via prefs -> about | updates -> about tab -> button that appears in the build info section or should've been prompted if you've had the build trigger a crash) ?
I haven't. I didn't even know this existed until now.
It's a new thing to this preview build.
I don't see how in_snes should be involved at any point in all of this as it doesn't handle streams.
I was also confused what in_snes has to do with playing aac streams.
That's the thing in that it doesn't unless I've broken something else with the way input plug-ins are matched to the input plug-in to use but I'd then expect to be seeing that with my own testing. Unless it's something about the style of urls that you're trying to play which I'm missing from the ones I'm testing.
What skin are you using as a modern skin can entirely screw the assumptions up.
I use Big Bento (modern skin). I switched to classic default skin (so tiny on 2K screen) and problem2 went away but problem1 still persisted. Then I uninstalled in_mp3 and both problem1 and problem2 are gone. At least right now I cannot reproduce either while using Big Bento skin and default metadata read mode, tried restarting the app few times too.
Modern skins like the Bento based ones with their file info pane will try to get metadata & in_mp3 has concurrency issues with some of the requests vs things I've tried to put in place to avoid other metadata requests from the modern skin engine blocking things (something that will never be properly fixed without a replacement gen_ff / modern skin engine plug-in so that none of the metadata requests are done on the main ui thread which is just not a good thing to be ever doing).
From a user view point it just makes it look like wacup is always at fault when imho it's just that I'm doing things differently to what winamp did & trying to fudge that plug-in to work outside of winamp sadly shows up those problems which under a classic skin is generally not going to happen (excluding what 3rd party plug-ins might be trying to do).
Seems not using in_mp3 was key. Thanks! I'll keep posted if problem persists later on.
Does in_url also handle local mp3, aac and m4a files? Or is it some other input plugin? They seem to play just fine without in_mp3.
in_mp3 was only there for mp3, aac, related streams & tag editing on mp3 files (something that isn't provided when in_mp3 is disabled / removed). m4a/mp4 are handled via the in_mp4 plug-in & local .aac files are also sent to that plug-in instead of in_mp3 but that doesn't provide seeking support since that's not something .aac natively provides & I've yet to implement a brute force mode seeking to enable that.
in_url can do mp3 & aac streams along with recently trying to pass ogg+vorbis streams onto in_vorbis but I need to do more work so in_url becomes the general handler for streams so the other input plug-ins can then just focus on local file playback (which'll make determining what to do for other ogg / opus based streams simpler once it's been coded).
in_wave is used for local mp3 playback if there's not anything else claiming mp3 files which is a crude way to allow the x64 build to offer mp3 playback whilst allowing the x86 build to have a fallback mode if in_mp3 cannot be obtained during install.
edit: Seems not using in_mp3 crashes the player quite often especially when launching local files via the open file button but also sometimes when I launch stream url. Reinstalled in_mp3 but the problem2 (fails often to initially start internet radio stream) comes back. Switched to classic skin seemed to get rid of this problem but classic skins are not good on 2K screens. So I just uninstalled in_snes and the problem went away, and kept using Big Bento modern skin.
Classic skins offer 2x & 3x scaling modes but I get that doesn't look nice for some & when I'm using scaling on the modern skins I'm not the best person to suggest such options it seems. Is wacup's crash reporter being shown as I've not seen any crash reports that appear to relate to the open file dialog or having in_snes involved with things.
If you can try to replicate it, running wacup via the crash collector shortcut from the start menu or using the /procdump command-line mode or using the mode from prefs -> advanced -> error reporting would be useful to help try to determine what might be going on so it can try to be resolved. Then when it crashes, restart it normally & that will try to auto-submit it to the site - best to post here when that is done so I can try to match up the report to you or pm / email me a copy of what's generated as can be found via the link to open into the crash reports folder from prefs -> advanced -> error reporting.
About | updates -> about tab crash update fix button disappeared after the latest crash so I'm guessing the player automatically applied it? But it still kept crashing quite often.
If all of the currently available patched plug-ins / dlls are found to be present then it will no longer show the button. There is also an attempt to update things after a crash happens which depending on how things have been run might mean it gets applied without a prompt (e.g. if it's in a portable install) or it'll trigger a UAC / copying prompt (normally needed with a non-portable install in the "program files" folder).
