# Squarp Pyramid to Instrument Converter

**URL:** <https://forum.electra.one/t/squarp-pyramid-to-instrument-converter/597>\
**Category:** Developers\
**Created:** [April 26, 2021, 4:32pm UTC](https://forum.electra.one/t/squarp-pyramid-to-instrument-converter/597 "2021-04-26T16:32:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thetechnobear](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/thetechnobear/32/134_2.png) [@thetechnobear](https://forum.electra.one/u/thetechnobear)\
**Post date:** [April 26, 2021, 4:32pm UTC](https://forum.electra.one/t/squarp-pyramid-to-instrument-converter/597/1 "2021-04-26T16:32:20Z")

</div>

this is small python script bit like my preset to instrument converter…( see [here](https://forum.electra.one/t/preset-to-instrument-python-script/221) )

> **[ElectraOne/tools/pyramid2inst at master · TheTechnobear/ElectraOne](https://github.com/TheTechnobear/ElectraOne/tree/master/tools/pyramid2inst)**
>
> patches and tools for electra.one . Contribute to TheTechnobear/ElectraOne development by creating an account on GitHub.

this allows Squarp Pyramid ‘instrument definition’ files to converted into instrument definitions for the Electra One

It should be noted the Pyramid has very short names for parameters due to small screen, and they are all upper case

however, I still find this very useful - since it gives me the basic cc mapping, so I don’t have to look up cc mapping - and can rename these to ‘nicer’ names in the instrument definitions files.  
I might also start categorising them, or adding overlays.

anyway I hope you find it useful

Mark

* * *

## Pyramid Definition Files

you can get a ton of pyramid defintion files here :

> **[Pyramid definition file](https://squarp.community/c/def/11)**
>
> Squarp Instruments users community

## How to use

a) go to forum, find instrument …  
b) copy definition from post  
c) paste into a text file (e.g. rample.txt)  
d) run python script against this text fie

```auto
python2 rample.txt

```

this creates a new file with eif file (electra one insrument definitioin)

e) perhaps edit this eif file - you might want to change manufacturer, or parameters names

f) import into the Electra One Editor

## Things to note/assumed info

- this only supports CCs currently , not note definitions
- format  
first three lines should be:

```auto
NAME:
OUT:
CHANNEL:

```

- I use name - and ignore out/channel
- afetr this i expect a list off CC and names in format  
`CC number:CC name`

## Limitations

The pyramid definition file is very limited

- it only contains a name, so i use this for manufacture, product etc
- names are very short, so expect a lot of abbreviations 🙂

---

<div class="post-metadata">

**Author:** ![Dontlament](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/dontlament/32/448_2.png) [@Dontlament](https://forum.electra.one/u/Dontlament)\
**Post date:** [June 15, 2021, 10:30am UTC](https://forum.electra.one/t/squarp-pyramid-to-instrument-converter/597/2 "2021-06-15T10:30:56Z")

</div>

Thanks very much mate! This should come in very handy.

Question: Should the script actually be called like this? I got it working doing this:

`python2 pyramid2inst.py myfile.txt`

Don’t often work with Python so could just be something I’m doing, but got it working, so I’m happy – thanks!

---

<div class="post-metadata">

**Author:** ![Kenoun](https://avatars.discourse-cdn.com/v4/letter/k/73ab20/32.png) [@Kenoun](https://forum.electra.one/u/Kenoun)\
**Post date:** [March 22, 2024, 3:15pm UTC](https://forum.electra.one/t/squarp-pyramid-to-instrument-converter/597/3 "2024-03-22T15:15:21Z")

</div>

Hi,

Just sent you a private message. Would really appreciate it if you could check it out. Thanks for doing this!!!