Cavern
Cavern copied to clipboard
VoidXH
MAUI migration
Oh, whoops, my bad. I always get the converter mixed up with the player app. So rephrasing as a side note, have you considered an android build for the player? I know there's Dolby Atmos for mobile devices but only a few of devices/ROMs support/include it 😔
That's just an audio player with no video functionality, not a substitute for system-integrated Atmos virtualization.
Oh, I though the player would eventually get a video player. but yeah, you're right. It wouldn't really be a substitute but it would be nice to have a basic decoder and virtualizer/spatializer with personalized HRTF. Hell, I would even settle for basic pHRTF virtual surround like HeSuVi, but on Android, but rn we're just stuck with Dolby Atmos or Sony 360 Reality Audio which apparently has a pHRTF generator but I'm yet to get accurate results with those compared to a few I've found going through existing ones. Viper4Android and JamesDSP allow using convolvers but only for stereo sources. Anyhow, perhaps Android could still use the Headphone Virtualizer render target to load the audio externally through a video player. But I wouldn't bother if it would require too much effort to do something that we can do (probably much faster) on PC anyway lol
Assuming this gets finished, would it be possible to have a Cavern Flatpak made available?
Yes, it's possible, but I really have to work out a release pipeline for that.
One problem: .NET 7 has severely reduced performance from .NET 6. .NET 8 should only be used if it results in at least equal performance. We'll see, the release date is tomorrow.
Please dont move to MAUI... its shit... i very much like the old functional design instead of a more aesthetically pleasing but complete ASS in performance
Please dont move to MAUI... its shit... i very much like the old functional design instead of a more aesthetically pleasing but complete ASS in performance
Aside from "its shit" do you have any specific issues with MAUI?
@Continous it's rebranded Xamarin with all the bugs...
Im not so sure about performance impact, so I don't talk about it (I'm sure you will find something interesting). But people usually choose MAUI to write one codebase for all platforms (which is totally fine, especially when you have 2 members on your team). Well if cross platform is your concern, use https://github.com/AvaloniaUI/Avalonia
WPF is so much mature and battle tested than MAUI I will choose it everyday of the week
I just don't get why you should choose MAUI
https://github.com/dotnet/maui/discussions/10839
If it has any notable performance impact or bugs, I won't follow through with this migration, but it's worth a try to make Cavernize multiplatform.
Yeah, it's also worth considering that every UI framework has it's shortcomings. I get not liking Maui, but being a bit more specific would really help sidestep any issues.
If it has any notable performance impact or bugs, I won't follow through with this migration, but it's worth a try to make Cavernize multiplatform.
Oh hi Bence, first of all thank you. you are doing the lord's work here, I wish I could donate but I'm a student myself, so I'm not in position to do so.
Secondly, AvaloniaUI is much much more mature than MAUI... It's worth taking a look https://github.com/AvaloniaUI/Avalonia
Too much effort, this time is better allocated for projects such as Filter Studio.