# See patches nested inside performances

**URL:** <https://forum.udo-audio.com/t/see-patches-nested-inside-performances/3358>\
**Category:** UDO Audio Gear\
**Tags:** issue\
**Created:** [7 May 2025 18:03 UTC](https://forum.udo-audio.com/t/see-patches-nested-inside-performances/3358 "2025-05-07T18:03:21Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Feelingthin](https://avatars.discourse-cdn.com/v4/letter/f/b9bd4f/32.png) [@Feelingthin](https://forum.udo-audio.com/u/Feelingthin)\
**Post date:** [7 May 2025 18:03 UTC](https://forum.udo-audio.com/t/see-patches-nested-inside-performances/3358/1 "2025-05-07T18:03:21Z")

</div>

Is there a way to see what patches are referenced by a performance? I’d like to know what is being referenced so I can take note of them for other performances or copy them over and edit them.

---

<div class="post-metadata">

**Author:** ![udo-audio](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.udo-audio.com/udo-audio/32/8_2.png) [@udo-audio](https://forum.udo-audio.com/u/udo-audio)\
**Post date:** [7 May 2025 18:37 UTC](https://forum.udo-audio.com/t/see-patches-nested-inside-performances/3358/2 "2025-05-07T18:37:00Z")

</div>

@Feelingthin the memory within a performance is technically completely separate. That is it does not reference a stored patch per - se. You can save a patch form a performance into the patch memory area and then reuse it in another performance.

The idea is that you can keep patches, and edit them at will, without modifying perhaps several performances that use it.

---

<div class="post-metadata">

**Author:** ![Feelingthin](https://avatars.discourse-cdn.com/v4/letter/f/b9bd4f/32.png) [@Feelingthin](https://forum.udo-audio.com/u/Feelingthin)\
**Post date:** [7 May 2025 19:52 UTC](https://forum.udo-audio.com/t/see-patches-nested-inside-performances/3358/3 "2025-05-07T19:52:00Z")

</div>

Maybe I’ll take some patches within the factory performances and store them in patch memory so I can reference them for my own performances. That’s all. I’m still unlearning the Prophet 10 way of doing it. Your way is much better. Carry on, thanks!

---

<div class="post-metadata">

**Author:** ![goodweather](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.udo-audio.com/goodweather/32/91_2.png) [@goodweather](https://forum.udo-audio.com/u/goodweather)\
**Post date:** [11 May 2025 15:59 UTC](https://forum.udo-audio.com/t/see-patches-nested-inside-performances/3358/4 "2025-05-11T15:59:16Z")

</div>

You will see them with my editor but they will be useful only if they get other names than the default GEMINI PATCH 😆

 ![Super8G panel E](https://europe1.discourse-cdn.com/flex017/uploads/udo_audio/original/1X/ba2f050e6ad0d705619177156a7355fb3c0ad3a4.jpeg)

---

<div class="post-metadata">

**Author:** ![Feelingthin](https://avatars.discourse-cdn.com/v4/letter/f/b9bd4f/32.png) [@Feelingthin](https://forum.udo-audio.com/u/Feelingthin)\
**Post date:** [18 May 2025 22:23 UTC](https://forum.udo-audio.com/t/see-patches-nested-inside-performances/3358/5 "2025-05-18T22:23:08Z")

</div>

Is this editor released yet? I like editing without a screen, but would be handy for archiving and keeping track of my presets.

---

<div class="post-metadata">

**Author:** ![goodweather](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.udo-audio.com/goodweather/32/91_2.png) [@goodweather](https://forum.udo-audio.com/u/goodweather)\
**Post date:** [24 May 2025 16:56 UTC](https://forum.udo-audio.com/t/see-patches-nested-inside-performances/3358/6 "2025-05-24T16:56:28Z")

</div>

No, not yet. For the moment it is on Pause but I’ll restart working on it this summer (or earlier if possible). Thx for asking!