-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bittboy builds? #75
Comments
Hey thanks for showing some love to the Pig! =) |
Here you go. If you have any recommendations for mappings, config that makes it run nicer please attach as a reply here and I'll include them in the official build. I don't have a device to test it myself. =) |
Omg I'm so sorry I didn't read you already built it yourself, way to go! The lack of testers was due to not being aware of anyone that could find any issues for this specific platform and describe steps on how to reproduce, very happy to have you :) |
It's alright, thank you though :) I tested Save As on my tracks, it works fine, so far I couldn't break this build in any way, should be safe enough to include in the release. Will do my best to report any issues from now on. As for mappings/etc the defaults should be fine for now. I actually have a pretty nice setup on the V90 (it has a "function" button which I use as shoulder button along with select) but it's hacky and I haven't tested the non-hacky way on the latest firmware. Even after I figure that out it'd be better to put it on a wiki or make a separate build for it since the Bittboy build also should work for Q90 (which is horizontal) and, well, Bittboy :D Sorry not really a Discord guy, but I might swing by sometime later. Thanks again! |
Jolly good, thanks a lot for checking in and trying it out 🥰 I'll try to do some more work on the coding side in a few weeks when I feel up to it again, right now I'm enjoying making music with 🐷 |
For Powkiddy V90 I made a package without building. |
Hi guys, not a discord person either but I am using LGPT on the v90. Not sure which build I have that works but it sure is the last one. I found mine on an SD image from a youtube video and changed stuff here and there to make it work on my 1.3.3 cfw. In any case, I'll try this new one, thanks a lot! I agree it would be nice if the v90 had its official build. Happy to report anything if that helps. |
What an improvement from the older version. Congratulations on the good work, and thanks. I'll come back with more feedback after I spend some time using and abusing it. |
Hello! |
I think the defaults are fine for now. There's enough latency to make it unusable for DJing but I couldn't make it better through configuration on the Bittboy build, not sure why. I love using menu button for screen navigation, it's so much better than going for shoulder buttons all the time, however the setup I use doesn't really work out of the box with the V90 CFW due to menu button hotkey combinations not registering, if that gets fixed someday I'll do a PR separately or something else. Maybe @ploupipoulpi has some ideas (glad to see another v90 enjoyer :-) ) |
for now I only see the config switching a and b for the v90 that would be nice. For navigation I already have muscle memory from LSDJ with select+dpad and I even prefer using the shoulder button on the v90 to the point that I might remap R1 to select for LSDJ. I wouldn't personally use the menu button for that also because I don't like its clickyness on the v90. Although I'm interested in your hacky way purelygrey, for science. I just finished a shell/python script for color theme selection at startup but I need more themes with the new available colors and I realized that I forgot the row number selection so I'll add that as well. I'm adding a "music" tab in gmenu2x on my v90 with things like GMU, LGPT and direct links to LDSJ and other chiptune roms, if you have any logo or any visual besides the pixelated piggy let me know, if you're interested in that setup I can share what I'm using. I haven't finished the "one text file" manual but if I can finish it soon we could add that, as it can then be made available in gmenu on the LGPT link (Y for manual on a link if it exists), that would be nice in a v90 build for Miyoo CFW. Finally, it would be great if an official LGPT build was listed in the the Miyoo CFW ports. I put the LGPT directory in /mnt/apps with everything in it, but for sample management, one might prefer have the project and sample directories directly on the main. I don't know what the best "default" would be. In the package we could also add the link for Gmenu2x
Thanks again for all the work, I'm moving pretty slow on this but making progress. I hope I can contribute a little to the piggy community. |
Here goes, for science! @djdiskmachine you can disregard everything below Same here about lsdj, I'd actually prefer to have a single select button for everything, but that only works on vertical handhelds. And yeah you're right I completely forgot that I modded my V90 with a piece of foam to dampen the annoying menu button microswitch 😀 it's an easy fix, get some EVA or some sort of soft foam and put it inbetween the switch and the button, makes it a lot better even if you won't use it for LGPT I haven't updated to the official 2.0.0 release yet, I used the
#!/bin/bash
sleep 0.5
cd mnt
./lgpt.elf &
program_pid=$!
while kill -0 "$program_pid" >/dev/null 2>&1; do
sleep 1
done
poweroff However as I mentioned Menu button is used as a system hotkey modifier in MiyooCFW and there's no fallthrough for it, I mean even when system hotkeys are turned off through a config file they do not register at all in LGPT, they just do nothing. A dirty fix for that is to set device type to Q90 instead of V90, so the system hotkey is on R2, and menu button is free for application hotkeys. Didn't have any problems with that as well so far Part of <ROOTFOLDER value="/mnt/PROJECTS"/>
<SAMPLELIB value="/mnt/SAMPLES"/>
<KEY_UP value="key:0:up" />
<KEY_DOWN value="key:0:down" />
<KEY_LEFT value="key:0:left" />
<KEY_RIGHT value="key:0:right" />
<KEY_A value="key:0:left alt" />
<KEY_B value="key:0:left ctrl" />
<KEY_LSHOULDER value="key:0:escape" />
<KEY_RSHOULDER value="key:0:right alt" />
<KEY_START value="key:0:return" /> |
Hi guys, @purelygrey @djdiskmachine Anyone willing to test in on a v90 (I haven't tried it on the 1.3.3, only on 2.0 beta2) or another device? How it works: you create a folder named "themes" in which you put individual themes XML with the following : You can have many different themes in the folder, it's going to list them based on file name. Script will display a menu that allows to select a theme based on its name with up/down and to modify the "Altrownumber" with left/right. Default sets the value to what is in the theme xml. Selecting a theme and pressing A applies the theme to the config.xml Only caveat is that it is pretty important to respect the syntax exactly (space included) in the config.xml and individual themes xml. If you want to test this script please let me know and I'll prepare a zip with everything inside. Now making themes can be a pain with the new colors, so I'm updating the theme creator page ( http://poyo.co/lgpt/ don't know the owner, downloaded the code and messed with it locally). My current local version has all the new colors, but they're not set up to display in the example yet. It will allow the export of properly formatted individual themes for the theme selector script. I'll have a local working version soon, however @djdiskmachine can you confirm exactly what the colors do now between hicolor, cursorcolor, and songview ones? It would be easier for me to update the tool. Here's the code for the theme selection script for the v90, still need to clean a few things up but it's enough for testing purposes (note: half of the credit goes to chatGPT which was very helpful for making this work):
|
Updated code for the page (you need https://www.eyecon.ro/colorpicker/#download to make it work locally):
|
thanks! I see why it works. Might work with 2.0 even though I don't know what happens at first install, when it autodetects the model if you change it. |
Hey peeps I was distracted by a flood of CI messages so I missed a lot of what was going on, sorry about that. A theme maker is fantastic, great work! About colors.. 'Unfortunately' there's been some additions 😅 |
Hei @djdiskmachine
--- Edit --- My bad I spoke too fast :D just saw the changes. Ok I'll get back to it ! |
Ah cool, gotcha! |
I've added bittboy as a build target for automated builds. If someone could verify this is working properly I'd like to close this issue. :) |
It does, though I haven't tried the 1.4.1 yet. I'm running 1.4.0 on the newest firmware, it seems to work just fine so far |
Alright! There should be no specific changes related to bittboy between 1.4.0 and 1.4.1, I'll consider this solved. |
Hello again! |
Interesting, I'm going to try it out before the end of the week! |
I've seen some reports on double binds when assigning custom button mappings with mapping.xml, is this something you've encountered? |
Can't say I have, however I don't use mapping.xml, I just map buttons inside config, maybe it's not related |
Can you post your config.xml please |
Here's my current config.xml:
I'm on Miyoo CFW 2.0.0 beta 2. Q90 is just a sibling device to Powkiddy V90, CFW lets you select the device on install -- I only use it to free up the "Menu" button from system hotkeys, because there's no fallthrough for it (yet) |
Also I need a bit more info about RTMidi, what to do and what to expect, I'm not exactly sure if I'm doing the right thing, is it right that I should add the mentioned folders names and files in Makefile under BITTBOY everywhere and compile it this way? |
Almost, you're gonna need to do something like this I'm getting linking errors with this patch though. Can't investigate any further at this moment, check back in later Edit: I did some more digging. The toolchain is missing rtmidi shared object files. |
Edit: Won't work, I missed some things OK here goes |
Actually I made a mistake for that one, here we go again |
Alright, it doesn't work, but at least it tries to! Outputs this:
It also by default works as an MTP device, it does something like:
So I tried to kill umtprd before running Piggy, but it didn't change anything, but I have barely any idea about what I'm doing :-) |
Yeah that's a shame. I suspect it's missing MIDI kernel support, this would be an issue towards maintainers of miyoo cfw unless you want to roll your own. 😅 |
MIDI would be a serial mode rather than MTP so if there's anything like that maybe check it out |
Hi, I was wondering the same thing, USB_CONFIGFS_F_MIDI was my lead but I didn't get very far. I don't understand enough on all that part currently to get much of it yet. It seems to be MTP by default at startup.
If you have any specific lead, I can create a discussion in the cfw to get to the bottom of it, they're super nice and responsive. I'm on a clean version of a recent nightly build, if there's any version you'd like me to test on the v90 let me know, I'm also super interested in the usbmidi for this thing. |
I'd love to join in the discussion, where do I find the cfw peeps? |
I created a thread here: TriForceX/MiyooCFW#610 |
I've tried killing the umtprd which does MTP stuff, and also modprobing g_serial and g_midi before running the tracker and logged the output, both don't seem to fail, but it didn't change anything, sadly. Fingers crossed though, usb midi for v90 would be sick! I'm slowly working on a custom shell and buttons for it, with usb-midi it would be such a good and full featured dedicated Piggy handheld |
Hello! I use LGPT on Powkiddy V90 and I use the Bittboy build for it. I build the 1.3o_2 myself and I've been running my projects on it for a bit and everything seems to work just fine.
What's required to bring Bittboy builds back? I've read they were dropped because of lack of testers, what kind of testing is needed?
Also to everyone involved -- fantastic job!
The text was updated successfully, but these errors were encountered: