@CS: it doesn't manage kits _yet_, but I'd like it to eventually. I'll put it on the to-do list.

@J3wel, it sounds like you'd be more interested in LSMC than in pylsdj. I haven't packaged it up for distribution just yet, but when it's out, it'll be a regular app.

The LSDJ wiki is a great source of information on LSDJ's internal format (http://littlesounddj.wikia.com/wiki/.sav_structure) I've been working with Johan on filling in some of the gaps as I ran into them, so it should be pretty complete.

lsdj-sav-utils is now pylsdj, and is now documented and reasonably stable. See http://chipmusic.org/forums/post/223974/

https://github.com/alexras/pylsdj

pylsdj is a arguably the most comprehensive library for dealing with LSDJ save files out there. It includes saving projects out of .sav files, loading them into other save files, loading and saving instruments between projects and editing things like tables, chains, phrases and the structure of the sequence itself.

This effort began way too many years ago, and had a few false starts along the way. It's finally to the point where it's documented and I'm confident with advertising its availability.

If you're not a programmer and some of these features sound exciting to you, Little Sound MC (https://github.com/alexras/lsmc) is coming soon to a computer near you (really soon, I promise; I just have to get it building on Windows).

An important note (forgive me if this is obvious): it seems that you have to force the Everdrive GB to backup its SRAM by switching to another ROM in order to retrieve it from the SD card; otherwise the .srm file you pull from the card will be empty. Took me a while to realize this.

Managed to carve out some time to work on this over the long weekend, and made a reasonably big dent. New screenshots here: https://www.dropbox.com/sh/c0yj0y0opuse … YxLMuhga#/

The main features that are still missing are synth and table import/export; hopefully I'll find time to wrap that up in the next couple of weeks.

24

(3 replies, posted in LittleGPTracker)

I'm running on 10.8.5 at the moment.

25

(3 replies, posted in LittleGPTracker)

On OS X, I had some trouble getting Piggy 1.1 to run. Turns out it was a permissions problem. To fix it, run the following in a Terminal from within the lgpt_OSX directory:

chmod a+x LittleGPTracker.app/Contents/MacOS/LittleGPTracker

Hope this helps if anyone else encounters this problem.

@cyberic: The code is on GitHub: https://github.com/alexras/lsdj-sav-utils

I wrote a binary format I/O library, called bread, precisely because the parsing code in the original lsdj-sav-utils codebase was getting super hairy. It's also on GitHub: https://github.com/alexras/bread

I would definitely welcome pull requests, but I'd like to get an alpha release out the door first.

Progress is being made, however slowly:

It's not much to look at (I'm in the "get the UI elements functioning before making them pretty" phase), but a lot of the initial rough patches have been worked through. UI construction is really tedious.

More to come. Thanks for bearing with me.

Yup! Thanks for your continued interest in this.

When I came back to the codebase in March, it was an absolute mess. I ended up refactoring the parsing portion of the code, which has made the whole thing a lot easier to maintain.

The basic mechanics (loading, storing, parsing) are done. Test coverage is a lot less than I'd like, but there are a handful of functional tests and they're passing.

There are a couple remaining long poles:

The binary format parsing library I'm using is kind of slow, since it's pure Python and does a ton of object creation under the hood during writes. I'm debating between speeding that library up with a patch and just writing something that does what I need; I'll probably end up doing the latter, since I really just need simple bitwise file I/O. When it can store a .savfile in under 5 seconds without running it in pypy I'll be happy.

It doesn't have a GUI yet, which I know is something that a lot of people wanted. I'm debating just making it run a web server and writing the UI in HTML/JS to save time.

Once its speed is acceptable and a basic GUI is in place, I'll need people to kick the tires and I'll start writing more thorough tests.

In short, it's pretty far along. I'd like to get it to the point where I can declare victory by the end of the year; thankfully I'll have some holiday time off to spend working on it.

I know that lsdmanager saves and loads .lsdsng files, which best as I can tell are just dumps of the song's battery RAM data. Have similar file formats been devised for LSDJ instruments, tables, kits, etc.?

30

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

I think it might be possible to stick it inside the .app's Contents/Resources directory, but it might have problems paths if it assumes that they're relative to the DefleMask binary itself. Sticking it in there and changing the binary path in the script didn't seem to work; haven't looked further than that yet.

31

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

Here's an AppleScript application that runs DefleMask with the included SDL dylib without having to install the dylib itself. The application assumes that it is running in the same folder as the dylib.

https://dl.dropboxusercontent.com/u/739 … leMask.zip

So, drop this in DefleMask_Mac and double-click, and it should run DefleMask.

The problem is probably that program names are case-sensitive. `sudo` should be lowercase:

sudo port install pkgconfig

I'm glossing over some technical detail here, but here's a roughly what's going on (so that this is less magical):

port (MacPorts) is a program that installs other programs. To install programs, it needs what's known as "superuser" or "root" privileges. The command sudo (which, IIRC, is short for "superuser do") allows authorized users to run commands in superuser mode. So what you're doing when you run "sudo port install pkgconfig" is saying "I want to run the command 'port install pkgconfig'" as the superuser.