| |
Splunkh!
Registered: Apr 2021
Posts: 31 |
Android Goattracker compatible tracker
FakeSID is a FOSS Android chiptune tracker (inspired by LFT's Blackbird). The coder is now considering rewritting the whole thing, basing it on Goattracker! One very nice aspect of this is that Goattracker's .sng-files easily can be converted to SidWizard .swm-files (With Hermit's sng2swm-tool).
According to this thread on Github, the dude mentions he would need a little bit of help with some of the 6510-assembly bits. Anybody here who perhaps would like to point him towards the right direction? In that case leave a comment and more details can be added. Have a look at this thread: https://github.com/2bt/fakesid/issues/1#issuecomment-822011536
Personally I love the idea of punching in a few melodies or beats on my phone whilst being on the bus, and then move the fragments over to the breadbox when at home :) Also the gui on the previous/earlier android installment (FakeSID) is really sweet. Screenshots/apk are available at Github link above or at Play where it has gotten some pretty great ratings: https://play.google.com/store/apps/details?id=com.twobit.fakesid |
|
... 20 posts hidden. Click here to view all posts....
|
| |
RS-232
Registered: Oct 2024
Posts: 2 |
I think as long as the files generated are still loadable in GT2 it should be fine.
Is the reason for not using the global tables due to screen real estate on the android, or some other reason? |
| |
spider-j
Registered: Oct 2004
Posts: 498 |
Quoting JetboyWhy not.making it compatible? What is the point of doing crippled solution?
It's not that far fetched. NinjaTracker uses the same method and if you prepare your tunes in GoatTracker and throw them on gt2nt pattern fx will converted in that way automagically.
I wouldn't be surprised if the GT2 routine did the same or something similar when exporting to PRG / SID, depending on what features were used. Cadaver has a lot of stuff heavily optimized to save RAM and rastertime. |
| |
2bt
Registered: Jun 2021
Posts: 17 |
I initially had global tables in the app but found working with it cumbersome. There isn't a lot of space on a phone screen as RS-232 pointed out. But I also wanted to make the app a bit more intuitive than the original tracker, which might help new users not familiar with it.
A global table has practical advantages. All addresses, including start addresses, can be stored as a single byte. Instruments can share table data with the goal of minimizing memory usage. This happens when two instruments have the same initial table position. The android app supports this. But data could in theory be shared more creatively. For example, instrument A may execute a few initial rows after jumping right into the local table of instrument B. With only local tables shown in the app, you won't be able to do this kind of data sharing. Having looked at a bunch of songs in the wild, I can tell you that this is not very common. Instead, what's common is that wait commands in wave tables are underutilized and space could be saved but isn't. So the app's limitations in this regard should not a big loss. |
| |
2bt
Registered: Jun 2021
Posts: 17 |
I managed to build a web version which you can try out in the browser (on a PC).
https://2bt.github.io/gtmobile/index.html
Not as responsive as the real android app and no way file import/export. But I think it's fine for the purpose of getting some initial feedback regarding UI. Please try it out and let me know what you think. And tell all your friends about it. Constructive feedback will help make the final app better. |
| |
Hein
Registered: Apr 2004
Posts: 954 |
I've tried it, looks great so far. I think it'd be good to make some space for the 'advanced' tables. By combining the project tab with the settings menu, you'd have space for a tables tab with all the expert mode / table stuff. The solution you have come up with by embedding instrument table data directly in the instruments seems useful. I guess that's where it belongs to prevent it from getting too detached. I do wonder about the instruments that are created on the fly to accommodate command tables, I think they're confusing. But I'd have to try it more to see if it'd work well when creating new tunes.
I've used FL Studio Mobile on a small Android phone and SidTracker64 on iPad, they're probably both good sources of inspiration. Especially a piano roll works surprisingly well on a small device. Maybe the data input in your GT Mobile is too tiny and a bit cumbersome, thinking about novice users. If you can find other ways to enter data values (preferably not having to remember all the commands and exact hexadecimal values), it'd be more appealing to new users that don't know GT so well. After all, the base for creating SIDs are the sequencer, patterns and the instruments. The table pointers really seem advanced features on a mobile device, which you'd rather not deal with too much when having fun on such a small screen.
Really nice to see the progress nevertheless, looking forward to the updates. |
| |
2bt
Registered: Jun 2021
Posts: 17 |
Thanks for the feedback, Hein. Yea, a Piano roll might be very useful. Fake SID had something similar. I will think about it for a bit, it could be an alternative way of adding notes.
Regarding pattern commands, I was first thinking about having an icon for each command type, but couldn't come up with something I liked. I was also worried that experienced composers would miss the hex digits. When you want to put in a command, select a cell where you want it, then click the pencil on the right which opens up a dialog.
Btw, you can mark regions of the order and pattern table by holding down on a cell for a bit and then drag. There will be different buttons on the right. You can then copy that region and paste it elsewhere. For pattern data, there are also buttons with the following functions: transpose, set overwrite instrument, delete notes, set/delete commands.
I want to also add a kind of instrument manager where you can load instrument presets. I might need some help to come up with a good set of presets though. |
| |
Hein
Registered: Apr 2004
Posts: 954 |
Quoting 2bt
Regarding pattern commands, I was first thinking about having an icon for each command type, but couldn't come up with something I liked. I was also worried that experienced composers would miss the hex digits. When you want to put in a command, select a cell where you want it, then click the pencil on the right which opens up a dialog.
Ah, right.. I tried it at work quickly, but now noticed it's usable for both novice and advanced users this way, cool. |
| |
acrouzet
Registered: May 2020
Posts: 97 |
I personally think that SidTracker64 has a quite elegant solution for converting tables to a visually intuitive interface, although sacrificing hex values. Also, ST64 is for iPad only and screen real estate is an issue for phone tracking.
This interface looks good so far for a phone tracker, though. Could also work quite well on desktop with a few tweaks. Reminds me of GTUltra. |
| |
2bt
Registered: Jun 2021
Posts: 17 |
I just added loading and saving instruments. Just tap the instrument tab twice. |
| |
2bt
Registered: Jun 2021
Posts: 17 |
Here is the debug APK:
https://drive.google.com/file/d/1B_LMvW3vUbYGw5DYRs7wx34yW9SLj_.. |
| Previous - 1 | 2 | 3 | 4 - Next |
