Відео

I’m thinking about making a guide on how to set everything up, but I’d like to look into some other ideas first, so it might take a while.

I'm impressed that you managed to get it started at all! Have you checked if your device can play any sound? If not, the main issue might be related to the drivers. For instance, there are various drivers for the different types of LCD screens for the R36s, and it can be quite complicated. I believe audio is handled through ALSA, because I used the internal settings from M8C to set it up.

@@roterodamus haha thanks, I've been playing with it for weeks to be honest - I've tried various things - last night I got it running with sound but it was very crackly, so I changed the config a bit and sound was gone completely never to return :D currently I have a modified version of arkos which runs on k36 models, with your i3 config and m8c version - I had to recompile libserialport and remove the default installation - current issue is that m8c always loads ontop of i3, I guess it's for some reason not loading like it did in your distro - within the current space and resizeable.

@@roterodamus do you have any steps, for how you installed/configured i3 and xorg? this could really help to ensure I get the same setup as you - I was trying to copy/paste parts of the file system and checking config files etc but maybe I've missed something silly.

@@jasonb_ Happy new year! i3 should start m8c via the i3 config, that's how I set it up at least. I don't remember the details clearly, but I believe i3 starts by a systemd service, similar to how emulationstation did it originally on Arkos. However, using i3 isn't actually essential. I mainly use i3 to hide the mouse cursor while running m8c. I might create a tutorial on how to set everything up, but I also want to explore some other ideas first, so it could take some time.

@@roterodamushappy new year buddy! I managed to get it all running! It was not easy - the two main problems was that M8C was always forced to run full screen and no sound. In the end it only worked while using pulse audio with a loop back device setup. I think I blew the speakers on the device, while trying to get also configured with loop back. For some reason, audio just would not work out of the box. I’m curious if you had to configure anything audio wise or it just worked by default. I am using a different Linux distro now, an older ARkOs build but inspired by your setup with i3. It’s taken weeks for me to get this far and now only some minor tweaks to have it perfect 😂 I’ll also make some repo so those who buy the r36s fakes/clones which have trouble running ARkOs will also be able to make decent music with it 😅

My r36s has a finicky headphone jack. The plug from my headphones is too short, which causes poor sound quality and keeps the speaker on. On the other hand, the plug from my in-ear monitors is too long, leading to a hissing noise and strange echoing. If your plug is too long, trying to pull it out of the device just a little bit might solve the problem. If it’s too short, an adapter like I have linked in the description might fix it.

@roterodamus Thanks for the suggestions! I've just tried with some cheap old headphones and there's far less hiss, so I think you're probably right.

I see how a dual boot setup could be useful, but I don't think I can handle the maintenance since it seems pretty complicated. The r36s has two SD card slots, so when I want to play games, I can just switch the cards. Mostly, though, I'm focused on making music! I'm not sure if the r36s the best option out there, but it's affordable and works well for M8 Headless.

Yes, someone created a version just like what you mentioned using a tool called aseqjoy. However, the joysticks have springs that push them back to their original position when you let go. I didn’t think it would be very useful to work that way.

I’m using this with a Maudio mini pro, bad keyboard but I can use the knobs to do the do effects etc, it’s fun. You need to connect the midi to m8c by using aconnect first and then hold the B button on an instrument parameter while turning the knob you want to use to map it.

Thanks! Means a lot.

From what I can tell from the m8c releases page, m8 firmware 3.1.0 is the most recently supported version which was added in m8c v1.5.1

I’m using v4 with it and it’s fine

From what I can tell from the m8c releases page, m8 firmware 3.1.0 is the most recently supported version which was added in m8c v1.5.1

​@kaijuskithedreamcaster thanks a lot for your answer i ll give it a try.

@@ugofosco8377were you ever able to get this working?

Did you ever get this working?

It starts but is unusable, i tried many firmwares with no luck.

+/- 1.5h

@@roterodamusdang it there’s always a deal breaker

@@roterodamusdang it there’s always a deal breaker

I have disabled the analog sticks in the latest update. It seems that the R33S may utilize a different controller configuration, and I am unsure if it is recognized in the kernel. Unfortunately, I do not have an R33S to verify this. If possible, you might want to try using an older version.

@@roterodamus If you want, I can try to program a version for r33s, but I would need your experience to do it. Are you active on the Dirtywave Discord? To find an alternative way to communicate other than UA-cam. Thank you for your response.

@@djStrombo Yes, I'm on Discord. You can find me using the same name, roterodamus.

@@roterodamus ok, I sent you a friend request

Did you ever get this figured out on the r33s?

Hey, I'm running into the same issue, could you tell me with a bit of detail how you chose the m+kb controls and did the mapping?

@@ignitiondj4025there is a gamepad icon before starting m8c top right steam. choose keyboard and mouse then bind keyboard keys A S Z X

also you can access in game with button top right of d pad > controller settings > controller settings

Ping :)

I don’t think that it would work, but I only have a r36s so I can’t test it. Maybe if you copy all the .dtb files and config file from the /boot partition that came with your device and copy them to the /boot partition of arkm8c overwriting any files if prompted.

R3 + dpad Up or Down

Maybe check the configs in the boot/m8c-settings. You’ll might be able to disable analog input in the m8c-config or disable antimicrox in the i3-config

@@roterodamus how do i access these files? when i mount the sd boot partition only shows me some files such as boot.ini some linux dtb files and a file without extension named uInitrd (im on windows)

@@hectorllanquin assuming you have the latest version, there should be a folder called arkm8c-settings in the boot partition

@@roterodamus updated to the latest version but i cant find documentation about these config files to check if there is an option to disable analog stick and changing the threshold didn't help either. Disabling antimicrox leaves me without controls at all. Any clues?

@@hectorllanquinSdl dead zone is kind of weird the max number is 32767 or 32768. But I think the only way to completely disable the analog sticks is to change the definition of the controller in gamecontrollerdb.txt. To find its location you need to ssh -Y into the r36s or connect a keyboard and run m8c from the terminal. It should tell you the location of gamecontrollerdb.txt and which controller. I haven’t tried any of this but it’s my best guess.

Put your device to sleep by pressing the power button, then wake it up. Wait for a couple seconds for m8c to respond. Latency should be fixed.

I’ll look into it!

Interested in this teensy case, have you shared it anywhere?

Also looking for info about that. For now I can't make anything to work for input audio (r36s and pc version)

Same problem 😔

If you are still dealing with this issue try this 1: cd yay 2: git checkout 96f90180a3cf72673b1769c23e2c74edb0293a9f 3: makepkg -si

run this command before $ makepkg -si: $ git checkout 96f90180a3cf72673b1769c23e2c74edb0293a9f it will set yay to a bit older version but will work

D-pad = Navigation B = Edit A = Options Y or L2 = Shift X or R2 = Play R3 + Up or Down = Brightness Up or Down FN + Select = Shutdown

Same here unfortunately - but the stndbye and wake cycle seemed to .. eh ... clear it =) ?