v3rm0n / m8c-android Goto Github PK

Hello

haptic feedback in1.0.30 not set or missing?
thank you for your work

best regards

Works fine with 2.x headless versions but after updating to the latest 3. x the M8 is no longer detected when starting the client.

What are the correct output/driver settings for Samsung phones? I have the S22+ and I can't hear any audio coming out of my speakers. The M8 UI works fine though...

Hello, I noticed a good amount of times touch controls "lose" completely or partially the input, making difficult to set some parameters or producing mistakes.

Example: when I try to set effects to notes, I press shift+up and then navigate the effects with the directional buttons. However, lots of time looks like the app loses my touch on the shift button, closing the effect table and bringing me back to the notes screen with the last effect selected.

On M8 webdisplay this was not happening, could be due to the larger area of each button? (M8 Webdisplay reproduce the size of original M8 buttons, scaling them to the display).

Device: Poco F2 with Android 13

Hi!
First off sorry I have a little programming background with python and html/CSS/java but I have never tried making android apps so I have no idea if that's complicated or not.

My question is if it possible to make an option to use a layout like the real deal? I mean something like they got on m8.run if you enable show controls. Its really hard to work with the controls right now since they are really small and very close together.

Thank you!

I cannot update the app (says "not installed" for recent releases). I'm trying this on a Retroid Pocket 3 with Android 11.

I guess the app assumes the gamepad is xbox controller or something similar, but d-input is a very common on android and it would be nice if we could use those controllers as well...

Hello, I'm trying to use this app, but no matter the phone I use, it crashes as soon as I press start.

I tried it on

• Poco F2 with Android 13
• Nexus 5X with Android 10
• Xperia XA2 with Android 9

for each one, I tried every possible combination of audio device and audio driver, but the result doesn't change: as soon as I press the "start" button, the app switch to a grey screen, then crashes.

My Teensy 4.1 have the latest headless M8 firmware flashed on it, and using it through Chromium and M8WebDisplay works well.

Something I can do to help troubleshoot?

Thanks a lot

Get into settings but no matter what configuration I choose it won't start upon pressing start. Am I doing something wrong?

Hello
the fx menu does not remain available in touch mode, as soon as you release the buttons on the screen, it makes the selection difficult but the haptic feedback is present and very satisfying but this little problem spoils the pleasure a little, of course, it must work better with a externe pad! could you perhaps add a button that would bring together the combo of the Edit button or be able to maintain / hold it so that the fx menu does not disappear when your fingers are released, that would be great! it's missing that ^^. Thanks in advance if you find a tip.

last firmware bug the display blink on my android 11 , but its ok with firmware 3.0.4.

can u help for this please : )

thanks

I see there's an option for audio buffer size in m8c. In m8c-android it looks like it's set to 4096. Would it be possible to add an option for adjusting the audio buffer size, so users can experiment with smaller buffers for lower latency?

do you think it's possible to add this haptic feedback function on the touch controls, it would be so practical and more lively; )

thank !

I'm having several issues getting this working on my Pixel 6 (on Android 13, fully up-to-date).

The app opens, I can connect to the Teensy and the display shows, but it only actually updates while I'm pressing a button. For example, if I press play, the waveform at the top shows, but then freezes. If I scroll around the interface, the waveform updates briefly as the cursor moves but then freezes again.

I've also not been able to get audio working at all, and I'm pretty sure I've tried all the available combinations of device and driver. I get no error messages, just no audio. When choosing the audio device, am I meant to be choosing the input device (the M8), or the output device? I get a list of 3 "Pixel 6" devices and one "USB-Audio - M8", although this last one only appears after I've connected to the M8 once, then closed and reopened the app.

As of version 1.0.17 the app finally worked without crashing on my OnePlus 8 pro.
There is only one audio out that i found working but the volume is really low and also i hear crackling.
Is there any logs i can provide for this?