booobb_old
bbooobb_old wrote:
How do I get wineskin osu to recognize my tablet? I am running it on a macbook m1 pro, and the tablet works fine on my desktop but not in osu.
What tablet are you using, and have you installed drivers for them? It's probably a case of the drivers being incompatible with Wine (or not properly configured to use Wine) but without further info there's little I can suggest.
Please also make sure you have set up the tablet options correctly in-game.
Naozumi
Naozumi wrote:
How can I stream the audio to discord? Since discord now supported for audio stream on macOS and I was able to stream the game audio which installed on crossover so I guess it's also doable on osu wine?
Ok, I've tested it out and to my surprise it doesn't work, even though I thought I recalled it working before...
Taking a look through how Wine deals with audio brings nothing surprising, and certainly nothing that I would presume Discord wouldn't be able to capture. Like all other macOS apps, Wine uses the CoreAudio driver and outputs to whatever output you set perfectly fine. The Rogue Amoeba ACE (audio capture engine – what Discord uses to capture sound) is closed source and proprietary but as far as I'm concerned there really shouldn't be anything preventing audio routing. Even as you mentioned, using Crossover works (and Crossover uses Wine).
My best guess is that it has something to do with how Wineskin creates wrappers. I will still need to investigate what exactly the reason for this is. In the meantime, considering that the Discord implementation of ACE is quite limited - you may need to use a workaround. Personally, I use BlackHole (https://github.com/ExistentialAudio/BlackHole) for any complicated audio routing setups.
UnluckyQueen, Lol3270
If our solutions were able to fix your issue, please let us know so we can note it as a confirmed fix. If not, please let us know what you tried and what's still not working.
———
Side note from me
On a side note, life has become busy for myself (particularly with high school exams, and this being my final year) and considering the very small number of people who actively support the osu! macOS userbase, it may take longer for us to respond to our messages.
The best way for us to respond quickly is by providing a detailed explanation of your issue with all relevant issues, looking through previous replies, letting us know what you've already done, and going through troubleshooting steps which are present on the top thread. Hopefully we will introduce an issue template that should speed this process up. For more complicated issues, such as those difficult to reproduce or not commonly experienced, it may take considerably longer for us to respond to these, so the information provided is extremely valuable.
Thanks to Technocoder for his original and ongoing work on osu! for macOS, and to everyone who continues to support the project. I hope that I'm able to still help out, now and in the future
The best way for us to respond quickly is by providing a detailed explanation of your issue with all relevant issues, looking through previous replies, letting us know what you've already done, and going through troubleshooting steps which are present on the top thread. Hopefully we will introduce an issue template that should speed this process up. For more complicated issues, such as those difficult to reproduce or not commonly experienced, it may take considerably longer for us to respond to these, so the information provided is extremely valuable.
Thanks to Technocoder for his original and ongoing work on osu! for macOS, and to everyone who continues to support the project. I hope that I'm able to still help out, now and in the future