Collab

[konsumer]

I am working on a web-only editor for allpat files (and more later) here

My primary initial motivation is being able to map electribe stock instruments in patterns to hacktribe, so demos will work, but I think it could be a generally useful tool for editing patterns and other things.

It currently works without needing a server (I read the files directly in the browser, so it could work offline, too.) I'd love to have another set of eyes on it, since the bit-twiddling parts is not totally clear to me.

I haven't setup downloading yet (since I am unclear how the global-config section of e2sallpat file works) but maybe we could join forces? I would be happy to take on the "GUI" part, as a web-app, so you can focus on the python cli part.

The main code for managing the e2sallpat is here

[bangcorrupt]

Great idea. I can't offer much help with javascript or web programming, but there is some documentation for the global settings file format on korgforums.

If you want to check it, you can start with a factory reset then export all patterns. Then change one parameter and export all patterns again. Hexdump each file and diff the result to see which bytes changed. The global settings are at the start of the file wrapped in 'GLST' / 'GLED'.

Eventually I plan to add definitions for all formats using python construct library, similar to the FX presets, although it may be a while before I can work on this again. @untergeekDE wrote a script to edit sample indexes in pattern files, it may be helpful.

[konsumer]

I can't offer much help with javascript or web programming

Nah, I got that part covered. It already allows zip & e2sallpat file upload, and parses the name and pattern-params and stuff, as well as outputting a zip file, and accepting a zipfile and doing it all in reverse. I think I have all the "infrastructure code" in place, as well as the basic GUI. You can see current version here. The main missing part is not being totally sure about the file-formats.

but there is some documentation for the global settings file format on korgforums.

I will take a look! This looks very useful.

I am currently pulling the global header from the e2sallpat as bytes, and adding it to each individual pat before outputting them as single files (in the zip.) I guess I am not sure how to save that global part in the zip file (like what file name did you use, originally?) and also how to deal with multiple pat files that come from different sources (like imagine you upload 5 pats from different other e2sallpat files, how do I do the global header that they will share?

If you want to check it, you can start with a factory reset then export all patterns. Then change one parameter and export all patterns again. Hexdump each file and diff the result to see which bytes changed. The global settings are at the start of the file wrapped in 'GLST' / 'GLED'.

This is a great suggestion. I don't have regular access to the device (it's my partner's kid's, and they love it) but I will try this at some point, and save a few dumps for analysis.

Eventually I plan to add definitions for all formats using python construct library, similar to the FX presets, although it may be a while before I can work on this again. @untergeekDE wrote a script to edit sample indexes in pattern files, it may be helpful.

That is helpful! I will try it out. I think I still want to finish my GUI for it, as there are some other things I want to add (better sample/pattern management, especially bulk edits.)

[bangcorrupt]

how do I do the global header that they will share?

The pattern files don't have a global settings section, if you add one they won't import as separate files. Differing global settings shouldn't effect anything in the pattern, it's only the stuff in the global settings menu.

how to save that global part

I saved the global settings as a binary file called something like global-settings.e2global. The file name doesn't really matter as there isn't an onboard option for import/export of global settings alone, only as part of the allpat file. We can import/export global settings using system exclusive messages.

[konsumer]

I haven't had much time to work on this, but I am excited about these ideas, have been thinking about stuff, and will try to put some work into it, this weekend.

I recently made this js lib that makes working with C structs fairly simple in JS, so for pattern-bytes, I think I just need to translate the structs to that (they are similar now, but this will simplify) and write some code to mess with it in the frontend, since all the fields are fixed-length (I think) it should be pretty straightforward.

I saved the global settings as a binary file called something like global-settings.e2global.

Perfect. I will do that too, and add a little editor widget for messing with those settings.

there isn't an onboard option for import/export of global settings alone

I think I could add this. Seems like there are 3 parts:

• global settings
• patterns
• instruments/samples

I have the most basic patterns stuff setup now, but I think I could maybe combine the first 2 areas a bit. My current UI could maybe just have some buttons overloaded a bit more:

[Upload]  [Download]  [Global Params]

Where "Upload" (or file DnD) accepts:

• e2sallpat (patterns & global settings)
• zip (same thing, but in a zip file)
• e2spat for single additions to pattern-collection

I can currently detect zip/e2sallpat with "magic bytes" and I will look into differentiating with a single e2spat vs e2sallpat.

"Download" could popup dialog for:

• e2sallpat (patterns & global settings)
• zip (patterns & global settings)

"Global Params" would be:

• Editor for current global settings (from zip or e2sallpat)
• "File Upload" - so you can give it a separate e2global file
• "File Download" - so you can save a separate e2global file
• "Machine Upload" - use sysex to send the current global settings
• "Machine Download" - use sysex to receive the current global settings

We can import/export global settings using system exclusive messages.

Ooh! I like this idea. I have not worked much with web midi, but I think it could be used to send/receive sysex, too, and this would be a great couple of buttons in the "Global Params" dialog. It's also possible with native/electron but browser-APIs for this stuff are becoming fairly ubiquitous, and it would be cool if users do not have to download/install anything.

Another idea was to add something like this for pattern-editing. similar to this (from Electribe2 Pattern Editor):

For instruments and samples, I think it also has some really good ideas, but I need to think about how to map it to web UI, a bit.

[konsumer]

I have been super-swamped with work & other projects, but I haven't forgotten! Hopefully I will have some time to work on it, soon.

[tripsylon]

Great work !!! I was trying it out but am not able to export an all pattern file, a zip file goes fine. I was using safari on a Macbook pro.
An advice how to do this?
Thank You :).

[konsumer]

Yeh, it definitely needs some work, but I have been a bit bogged-down with day-work. I will try to make some time for it, soon.