# Program change info in 'definition files'

**URL:** <https://squarp.community/t/program-change-info-in-definition-files/7176>\
**Category:** Hapax\
**Created:** [March 16, 2022, 1:06pm UTC](https://squarp.community/t/program-change-info-in-definition-files/7176 "2022-03-16T13:06:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![stuhoss](https://squarp.community/letter_avatar_proxy/v4/letter/s/54ee81/32.png) [@stuhoss](https://squarp.community/u/stuhoss)\
**Post date:** [March 16, 2022, 1:06pm UTC](https://squarp.community/t/program-change-info-in-definition-files/7176/1 "2022-03-16T13:06:47Z")

</div>

I’m thinking of making a feature request related to the upcoming MIDI ‘definition files’ (or alternative) for HAPAX.  
Obviously it makes sense to see what Squarp have in store before making suggestions but I thought I’d see what people here think about this idea.

I’d love to be able to select from names of patches as well as CCs. So I can essentially select patches from the HAPAX for patterns in the same way as I can select instruments from pyramid.

For example, I have been really enjoying using my Roland JV-1010 on a bunch of the channels of HAPAX. I’ve been referring to [this handy sheet](https://docs.google.com/spreadsheets/d/1F2HihOomA8cItVsjR-6l4r20PYHsWU9bU6SEac03thA/edit#gid=977641119) for reference when selecting patches for particular tracks/patterns. (I didnt create it, a user on the gearspace forum posted it).

It would be very handy to have all that info stored alongside the names for MIDI CCs, just to cut down on needing to refer to manual/computer.

I wonder if anyone has any views on that approach I should consider before submitting the feature request? Seems a bit more complex than naming CCs as it would require naming specific combinations of PC, MSB and LSB numbers.

---

<div class="post-metadata">

**Author:** ![Maarten](https://squarp.community/letter_avatar_proxy/v4/letter/m/ecccb3/32.png) [@Maarten](https://squarp.community/u/Maarten)\
**Post date:** [March 16, 2022, 3:52pm UTC](https://squarp.community/t/program-change-info-in-definition-files/7176/2 "2022-03-16T15:52:13Z")

</div>

Good idea!

While there, it might be nice to add an option to send the program change just before the pattern launches, so devices that need more time to correctly load a patch will be ready before the first note starts 🙂

---

<div class="post-metadata">

**Author:** ![matthew](https://squarp.community/user_avatar/squarp.community/matthew/32/1792_2.png) [@matthew](https://squarp.community/u/matthew)\
**Post date:** [March 16, 2022, 4:17pm UTC](https://squarp.community/t/program-change-info-in-definition-files/7176/3 "2022-03-16T16:17:54Z")

</div>

A way to manually +/- the time in beats for the clip PC changes would be really great!

---

<div class="post-metadata">

**Author:** ![matthew](https://squarp.community/user_avatar/squarp.community/matthew/32/1792_2.png) [@matthew](https://squarp.community/u/matthew)\
**Post date:** [March 22, 2022, 12:24am UTC](https://squarp.community/t/program-change-info-in-definition-files/7176/4 "2022-03-22T00:24:22Z")

</div>

Ohhh Cirklon has the idea of presending program change:

 ![image](https://squarp.community/uploads/default/original/2X/1/1886a0d549c999599d493274caef376d33ce503e.png)

---

<div class="post-metadata">

**Author:** ![thetechnobear](https://squarp.community/user_avatar/squarp.community/thetechnobear/32/230_2.png) [@thetechnobear](https://squarp.community/u/thetechnobear)\
**Post date:** [March 22, 2022, 10:51am UTC](https://squarp.community/t/program-change-info-in-definition-files/7176/5 "2022-03-22T10:51:21Z")

</div>

Ive already raised this with Squarp, and they have said they raised a ticket, and will think about solutions.