What is really saved in a project files?

I’m actually trying to save a blank project. Meaning starting from scratch blank Polypulse preset (with no FX, no engine selected, no output FX, no send FX, and some preference settings), then save it as an INIT project file so the next time i start a new project i can do it from that Polypulse state. And actually it looks it’s not possible. When i reboot the firmware or power up the Polypulse and then i load my INIT project i still have Output FX, Engine, track FX loaded by default and not at all the configuration i expect from loading my INIT project.

So what a Project file is really saving regarding the actual Polypulse state when you create it ?

In fact, why is it that when i power up or restart Polypulse firmware i always have the same default configuration. In my case subtractive engine on track 1 and no selected engine for the other tracks + the delay as a send FX + Limiter for Output FX.

Why can’t i change that specific state ?

The output FX not saving/loading is a bug. I’ll fix it for next update.

Projects are stored as a folder with individual *.inst and *.seq files for each track. To prevent project folders from being filled with *.inst and *.seq files for tracks that are essentially empty/unused it determines which tracks to save when saving a project.

A track is saved if one of these conditions is met:

  • it has a sound engine selected
  • it has 2 or more audio effects
  • it has 1 FX that is not stereo

These defaults are chosen because they are a good starting point for most users:

  • the subtractive engine so you can start sequencing without first having to select a sound engine.
  • delay on track 5 so you can easily add a delay.
  • limiter on the output to prevent clipping

I’ve put adding a way to set a template/init project on my TODO list for next update!

2 Likes

Ok, thank you for your reply Ward.
It is very needed, because the more you practice the Polypulse the more you need to customize the way you work with.
A kind of “user-config”/“user template” file for users to decide in what state should the polypulse be from scratch is very important.
Plus it helps to manage CPU ressources.

1 Like

Since 0.1.29: jan 2025 update you can create a template project that is automatically loaded when the PolyPulse starts. Simply create a project called template in the /projects/ folder.

1 Like