# Applying the perform mode's effects permanently **URL:** \ **Category:** Feature Requests\ **Tags:** perform, play\ **Created:** [February 16, 2023, 12:09pm UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878 "2023-02-16T12:09:48Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![ambivalence](https://backstage.polyend.com/user_avatar/backstage.polyend.com/ambivalence/32/296_2.png) [@ambivalence](https://backstage.polyend.com/u/ambivalence)\ **Post date:** [February 16, 2023, 12:09pm UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/1 "2023-02-16T12:09:49Z")
### What is the problem? Sometimes you just mess with the Perform mode and find that sound that you want to have in your next progression’s step/pattern, but you can’t have it right away. Instead, you need to twist the knobs trying to find that relevant setting, even though the performance pads are the shortcuts to the same settings already. ### What do you want to achieve? The ability to permanently apply all the currently selected perform FXs to a pattern. For example, with _perform + save_ shortcut. After all, most of the performance FXs are like shortcuts/presets to the already available knobs tweaks. ### Are there any workarounds? Leaving the Perform mode and searching for all the tweaks manually. ### Any links to related discussions? The similar feature we all want that **should be seriously discussed more in new threads** : - [Recording automation in Perform mode](https://backstage.polyend.com/t/recording-automation-in-perform-mode/691) - [Exporting stems from Performance mode](https://backstage.polyend.com/t/preference-mode-status-to-stem/4138) ### Any references to other products? – ---
**Author:** ![scerifforosso](https://backstage.polyend.com/user_avatar/backstage.polyend.com/scerifforosso/32/123_2.png) [@scerifforosso](https://backstage.polyend.com/u/scerifforosso)\ **Post date:** [February 16, 2023, 12:51pm UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/2 "2023-02-16T12:51:36Z")
This sounds like a very interesting concept. If i got it right it would be like “saving” the current perform mode settings into a pattern… would you want this feature to override the existing pattern knob settings or automatically create a new pattern with the current perfromance settings? Personally i would not like it to overwrite the current ones i had before entering in performance mode, but i’d rather prefer the play to create a new “copy” of everything applying the performance values on top… what do you think? ---
**Author:** ![ambivalence](https://backstage.polyend.com/user_avatar/backstage.polyend.com/ambivalence/32/296_2.png) [@ambivalence](https://backstage.polyend.com/u/ambivalence)\ **Post date:** [February 16, 2023, 1:14pm UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/3 "2023-02-16T13:14:03Z")
do you mean creating a copied pattern right next to the current one? If I get it right, it will help **a lot** in a composing workflow, because you could always jump in the patterns view and then switch back and forth between a newly created and the unaffected one. No preparation work, no manual backups! And if so, I had it in mind too. All in all, I guess it could be an interesting feature maybe even worth a separate wish: the ability to save all the unsaved/modified state to the next pattern without overwriting. But it may easily be 2-in-1 here. I always prefer the global options for all the features, because who knows how folks would love to use these tricks in their workflow. I guess, it could even save the modified sequences in the variations, too. Personally, I think variations are way too powerful and underestimated. I’d prefer the option “create a new variation + make a new pattern”. Being in the new pattern you could make smooth progressions by [changing variations one by one](https://youtube.com/shorts/d1jo8SYKKkg). ---
**Author:** ![scerifforosso](https://backstage.polyend.com/user_avatar/backstage.polyend.com/scerifforosso/32/123_2.png) [@scerifforosso](https://backstage.polyend.com/u/scerifforosso)\ **Post date:** [February 16, 2023, 2:34pm UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/4 "2023-02-16T14:34:25Z")
Yes, variations could be a very nice option to save the new settings to as well… If this draft wish is promoted to a wish status, it has my vote for sure! 🙂 ---
**Author:** ![ambivalence](https://backstage.polyend.com/user_avatar/backstage.polyend.com/ambivalence/32/296_2.png) [@ambivalence](https://backstage.polyend.com/u/ambivalence)\ **Post date:** [February 19, 2023, 9:59am UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/5 "2023-02-19T09:59:41Z")
@scerifforosso I made other wishes that could allow user to save changes in new pattern/variation slots on the fly. It’s a strict wish system here, so you cannot wish two things at the same time, even if they’re strongly related. You may want to “heart” them or add something, so they won’t seem unneeded. [Save all the changes into another pattern and build up progressions without backup copies](https://backstage.polyend.com/t/save-all-the-changes-into-another-pattern-and-build-up-progressions-without-backup-copies/929) [Save all the changes as variations](https://backstage.polyend.com/t/save-all-the-changes-as-variations/930) @icaria36: how about this one? ---
**Author:** ![icaria36](https://backstage.polyend.com/user_avatar/backstage.polyend.com/icaria36/32/2337_2.png) [@icaria36](https://backstage.polyend.com/u/icaria36)\ **Post date:** [February 21, 2023, 9:22am UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/6 "2023-02-21T09:22:25Z")
See also this one: > [@Generate new patterns in Performance mode](https://backstage.polyend.com/t/generate-new-patterns-from-performance-page/950/2): > > Could this wish be a way to implement this other one: [Applying the perform mode's effects permanently](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878)? Would it make sense to merge both? ---
**Author:** ![icaria36](https://backstage.polyend.com/user_avatar/backstage.polyend.com/icaria36/32/2337_2.png) [@icaria36](https://backstage.polyend.com/u/icaria36)\ **Post date:** [February 23, 2023, 8:50pm UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/8 "2023-02-23T20:50:29Z")
Do you think [Generate new patterns in Performance mode](https://backstage.polyend.com/t/generate-new-patterns-in-performance-mode/950) covers the same wish that you have for the Play, just for the Tracker? If so, we could wait to see how that review goes and then, if successful, copy the same text for a Play version of the same wish. ---
**Author:** ![ambivalence](https://backstage.polyend.com/user_avatar/backstage.polyend.com/ambivalence/32/296_2.png) [@ambivalence](https://backstage.polyend.com/u/ambivalence)\ **Post date:** [February 25, 2023, 12:54pm UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/9 "2023-02-25T12:54:31Z")
Unfortunately, I don’t have Tracker to decide. These are separate wishes for different devices to just copypaste something, I guess. Also, why is this text any worse? The wish seems to be pretty straight-forward and had some support [here](https://backstage.polyend.com/t/recording-automation-in-perform-mode/691) (almost the same thing, but without declined idea of automations). That one was published more than 2 weeks ago. It’s up to you. In case it’s the same concept, maybe that thread should be named “Generate new patterns in Performance mode for Tracker and Play”? ---
**Author:** ![icaria36](https://backstage.polyend.com/user_avatar/backstage.polyend.com/icaria36/32/2337_2.png) [@icaria36](https://backstage.polyend.com/u/icaria36)\ **Post date:** [February 28, 2023, 7:43am UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/10 "2023-02-28T07:43:44Z")
Thank you! I’m moving this to the comments to keep the wish simple. > [@ambivalence](#): > > Worth noting, it’s not the same as the [perform-recording automation wish](https://backstage.polyend.com/t/recording-automation-in-perform-mode-on-the-play/691). That meant dynamically applied effects bound in time with sequences. > > It would be a huge bonus here to have these two related wishes: > > [Save all the changes into another pattern and build up progressions without backup copies](https://backstage.polyend.com/t/save-all-the-changes-into-another-pattern-and-build-up-progressions-without-backup-copies/929) > [Save all the changes as variations](https://backstage.polyend.com/t/save-all-the-changes-into-another-variations/930) > > …so along with the described functionality in this wish, user could: > > - simply overwrite the current pattern and apply all the perform changes on top > - save all the changes to the next/empty pattern > - save changes straight into the variations > - save changes both to the variations and the next pattern > - auto-switch: yes or no (if no, exiting the perform mode will work normally cancelling all the effects, while you could switch to that variation/pattern manually later) ---
**Author:** ![ambivalence](https://backstage.polyend.com/user_avatar/backstage.polyend.com/ambivalence/32/296_2.png) [@ambivalence](https://backstage.polyend.com/u/ambivalence)\ **Post date:** [February 28, 2023, 7:48am UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/12 "2023-02-28T07:48:54Z")
@icaria36 thank _you_ for editing and all the good stuff 🙂 ---
**Author:** ![miropoly](https://backstage.polyend.com/user_avatar/backstage.polyend.com/miropoly/32/45_2.png) [@miropoly](https://backstage.polyend.com/u/miropoly)\ **Post date:** [February 28, 2023, 11:18am UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/16 "2023-02-28T11:18:08Z")
@here thanks for contributing! Wish is open for voting 🙂 ---
**Author:** ![ambivalence](https://backstage.polyend.com/user_avatar/backstage.polyend.com/ambivalence/32/296_2.png) [@ambivalence](https://backstage.polyend.com/u/ambivalence)\ **Post date:** [October 21, 2023, 11:18am UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/17 "2023-10-21T11:18:51Z")
Even though having this wish implemented would definitely improve some workflow aspects, it makes me think once in a while how cool it would be to have an actual automation lane for the perform mode. Sure, it was declined and closed: > [@Recording automation in Perform mode](https://backstage.polyend.com/t/recording-automation-in-perform-mode/691): > > What is the problem? You can do crazy stuff with the Perform mode, but you cannot record it as an automation (and do more crazy stuff on top?). What do you want to achieve? Have some sort of automation lanes for those beautiful performance pads. Preferably, those lanes should be bound to the perform pads themselves, but not the settings these pads adjust, because they [may become editable](https://backstage.polyend.com/t/polyend-play-performance-mode-customizable-effect-values/347/10) later and it would be a bit more flexible option for player. Are there any workarounds? No. Any links … but, damn, it would add insane amount of value to the device. It’s ironic that PO-33 or actually any Pocket Operator have the ability to automate fx lanes and cost like 10x less. Is it really-really impossible to make the device «remember» what performance buttons should be automatically «pressed» at given time? ---
**Author:** ![merlin](https://backstage.polyend.com/user_avatar/backstage.polyend.com/merlin/32/2094_2.png) [@merlin](https://backstage.polyend.com/u/merlin)\ **Post date:** [November 28, 2023, 10:51am UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/18 "2023-11-28T10:51:51Z")
This woud be so great to have !!! I would love this on my OG Tracker 😃 ---
**Author:** ![env](https://backstage.polyend.com/letter_avatar_proxy/v4/letter/e/d9b06d/32.png) [@env](https://backstage.polyend.com/u/env)\ **Post date:** [January 17, 2024, 10:43am UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/19 "2024-01-17T10:43:10Z")
So this wish is not for Tracker Mini and OG? It should be O no, i prefer > [@Generate new patterns in Performance mode](https://backstage.polyend.com/t/generate-new-patterns-in-performance-mode/950): > > Ability to create new patterns on the Tracker in Performance mode, mixing different tracks of different patterns What is the problem? Tracker’s Performance mode is very powerful and allows for spontaneous creativity. However, the tracks’ mix, the effects used, and the times of the performance cannot be recorded. At most, you are left with the audio. What do you want to achieve? Generate new patterns by mixing different tracks in Performance mode on the Tracker. Are there any workarounds? W… 😇 ---
**Author:** ![andrew.capon](https://backstage.polyend.com/letter_avatar_proxy/v4/letter/a/eb9ed0/32.png) [@andrew.capon](https://backstage.polyend.com/u/andrew.capon)\ **Post date:** [January 25, 2024, 9:07am UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/20 "2024-01-25T09:07:27Z")
I just got a play and was searching for how to do this! So vote added. ---
**Author:** ![env](https://backstage.polyend.com/letter_avatar_proxy/v4/letter/e/d9b06d/32.png) [@env](https://backstage.polyend.com/u/env)\ **Post date:** [February 25, 2024, 11:53am UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/21 "2024-02-25T11:53:06Z")
💕got me a Play plus bumpedeebump! ---
**Author:** ![ambivalence](https://backstage.polyend.com/user_avatar/backstage.polyend.com/ambivalence/32/296_2.png) [@ambivalence](https://backstage.polyend.com/u/ambivalence)\ **Post date:** [March 4, 2024, 1:10pm UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/22 "2024-03-04T13:10:08Z")
happy to say, I sold my device mainly because this feature was ignored, as well as many other wishes that have many votes for that seem to do nothing after all. the most significant bummer is heavily related and was posted before I started this thread as a compromise: > [@Recording automation in Perform mode for Play+](https://backstage.polyend.com/t/recording-automation-in-perform-mode-for-play/6605): > > What is the problem? You can do crazy stuff with the Perform mode, but you cannot record it as an automation (and do more crazy stuff on top?). How does it differ from [Applying the perform mode’s effects permanently](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878): What do you want to achieve? Have some sort of automation lanes for those beautiful performance pads. Preferably, those lanes should be bound to the perform pads themselves, but not the settings these pads adjust, because they [may become editable](https://backstage.polyend.com/t/polyend-play-performance-mode-customizable-effect-values/347) later and it would be a bit more … > [@Recording automation in Perform mode for Play+](https://backstage.polyend.com/t/recording-automation-in-perform-mode-for-play/6605/7): > > Thanks for your contribution. Unfortunately, the wish doesn’t fit our current product design direction. > [@Recording automation in Perform mode](https://backstage.polyend.com/t/recording-automation-in-perform-mode/691): > > What is the problem? You can do crazy stuff with the Perform mode, but you cannot record it as an automation (and do more crazy stuff on top?). What do you want to achieve? Have some sort of automation lanes for those beautiful performance pads. Preferably, those lanes should be bound to the perform pads themselves, but not the settings these pads adjust, because they [may become editable](https://backstage.polyend.com/t/polyend-play-performance-mode-customizable-effect-values/347/10) later and it would be a bit more flexible option for player. Are there any workarounds? No. Any links … > [@Recording automation in Perform mode](https://backstage.polyend.com/t/recording-automation-in-perform-mode/691/18): > > thanks for the contribution, but unfortunately this one is not possible due to technical reasons. with these two things implemented (this thread + the one above) it would be an instant buy, even if the newer Play+ that seems to have a lot of bugs and still misses a lot of features, whatever. ---
**Author:** ![Sineway](https://backstage.polyend.com/user_avatar/backstage.polyend.com/sineway/32/3191_2.png) [@Sineway](https://backstage.polyend.com/u/Sineway)\ **Post date:** [June 3, 2024, 11:07pm UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/23 "2024-06-03T23:07:36Z")
This would essentially be Polyend Tracker take on Elektron’s Ctrl+All feature where you can apply changes to a pattern on the fly across all or several tracks. This sure gets my vote! ---
**Author:** ![Sineway](https://backstage.polyend.com/user_avatar/backstage.polyend.com/sineway/32/3191_2.png) [@Sineway](https://backstage.polyend.com/u/Sineway)\ **Post date:** [June 12, 2024, 8:48pm UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/24 "2024-06-12T20:48:05Z")
Oops, just realized that this is for the Play, not the Tracker. ---
**Author:** ![beautron](https://backstage.polyend.com/user_avatar/backstage.polyend.com/beautron/32/2515_2.png) [@beautron](https://backstage.polyend.com/u/beautron)\ **Post date:** [June 12, 2024, 9:39pm UTC](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878/25 "2024-06-12T21:39:05Z")
play+ rules. join us 👽 [Next page](https://backstage.polyend.com/t/applying-the-perform-modes-effects-permanently/878.md?page=2)