17

(59 replies, posted in Software & Plug-ins)

The whole thing is 100 % written from scratch with SDL. The UI troubles are not technical but more about finding out which key is available to everyone (e.g. is there a F12 key on the keyboard, should CTRL-C be actually CMD-C on Macs etc.). Oldschool trackers are maybe the most tactile software ever written and basically utilize the keyboard as well as it's possible - it's a bit of a challenge to make that work on touch screens unless you somehow find a very different way to track.

18

(59 replies, posted in Software & Plug-ins)

OK, I'll try to make a somewhat useful video with the very basics!

19

(59 replies, posted in Software & Plug-ins)

What I have learned is that making portable software is not about getting it running but trying to somehow satisfy all platforms and their weird UI conventions...

I guess I'll start with an undo feature, it's useful in any case!

koub1s: I don't think editing in Prototracker is much different from Protracker, except for the sequence editor. You basically work in the pattern editor and keep hitting right CTRL to test the pattern. smile

20

(59 replies, posted in Software & Plug-ins)

koub1s: I see what you mean: dotpict is surprisingly nice to use with the two-finger approach. I wonder if I could combine adding support for a gamepad (LSDj style) and a similar approach with touch screens with a context sensitive side panel as in your mockup, use the d-pad/left finger to select what you edit and then A/B/right finger to actually change the value. Thanks for the ideas!

21

(59 replies, posted in Software & Plug-ins)

mk: Some of those are already fixed but I have been lazy to update the web version. Will update tonight!

Shortcuts: good idea. You can use the mouse in the mean time to jump to an editor.

Missing keys: I take it that Fn+DEL (or whatever the combination is) is too cumbersome to use or does it simply do nothing? I agree that mac keyboards are crap for getting things done when you know what you are doing.

I am looking at this tiny portable keyboard I would like to get to use with my PocketCHIP but it also misses the cursor keys (it's TINY... and cute). So, I am thinking maybe there could be a compact mode where there's only one octave at Q-2-W-3.etc.-U and you can use IJKL as the cursor keys. And the right side could have the O key for insert and P for delete and so on since they are now unused.

Waveforms: There's a wave "browser" that has a grid of all the waveforms. I need to put that in somehow.

22

(59 replies, posted in Software & Plug-ins)

koub1s: Yeah it's a native Android app. It's terrible to use, though. (Is it even possible to have an usable tracker with no keyboard?)

bod: Does the audio skip on your CHIP? You can see the console for alsa error messages (pcm buffer underrun etc.)

23

(59 replies, posted in Software & Plug-ins)

bod wrote:

So, I just scored a PocketChip at ebay for little over 100€ (Couldn't wait).

Is there a possibility for me to compile the tracker or get the binaries for the system. Since it's just a Debian, it shouldn't be a problem to compile by myself.

I put the code on GitHub a few days ago. Just clone the source (or download the zip), install GCC, SDL2 etc. and "make chip8". smile

https://github.com/kometbomb/prototracker

garvalf wrote:

Can't you compile it?

I have a problem when packaging the .deb file, dpkg just hangs. I was going to simply create a new Linux virtual machine and start from scratch, it could be as simple as the virtual machine running out of memory or so.

Thanks for the binary! I was actually planning to make the Linux download work like the Windows build, that is so it has the libraries included (and so it has 32 and 64-bit binaries and it automatically runs the correct one... used that technique for my game and it seems to work perfectly).

@Yoyz2k: Thanks... I was inspired by George Michael's passing but of course a lot more has happened since! sad

@n00bstar: Yeah I really should... at least I managed to release that half-ready thing. smile (People have really complimented the tunes so good work!)

@Draggs: Does klystrack say something? It should write a log file in the directory you run it from, maybe that has some clues?

Linux builds should come later... for some reason my build system broke down and refuses to create the packages so I need to find a workaround.

https://github.com/kometbomb/klystrack/ … .7.0-final

Probably has its fair share of bugs and so on but: fuck 2016.

Well, I think the compiler would agree it's not a good thing to suppress warnings. Please report back how well it works on a Raspberry!

P.S. I don't use an IDE so I guess I'm pretty much a sitting duck. Absolutely no excuses. wink

I have done some terrible things in the code, mainly using void* type arguments for ints and so on, which is not that clever in hindsight (an int is 4 bytes and a pointer is something other than that in your case, on 32-bit systems it should be four and four bytes so it doesn't matter). klystrack works on a 64-bit Linux so it probably works here too. Before you ask, I don't remember why I made this decision and I do know it's terrible.

So, you could just use the switches the error message suggests, i.e. "-Werror=int-to-pointer-cast" and "-Wint-to-pointer-cast", which bypass the warnings and doesn't trigger the error message. You can add that on line 21 in Makefile, after the other switches.

I hope that helps!

Thanks for the compliments. I think the filter is much better in AT2, though...

Ilkke really hit the bullseye with Mr. Catometer! It falls under the open source license you can make your own stickers. smile

Thank you, hearing that made my day. smile

31

(59 replies, posted in Software & Plug-ins)

Proof:

I need to fix the layout to use the 480x272 resolution on the 'CHIP but otherwise it's quite usable (well, as usable as anything on that keyboard... I love that thing to pieces but the keyboard is quite horrible). I also want to make it usable with a gamepad at some point.

32

(59 replies, posted in Software & Plug-ins)

Thanks! Yeah, standalone builds will follow. I have it already running on my PocketCHIP.