# Scaler 2.5 overwriting full sessions

**URL:** <https://forum.scalermusic.com/t/scaler-2-5-overwriting-full-sessions/8616>\
**Category:** Bug Reports\
**Created:** [November 19, 2021, 10:07pm UTC](https://forum.scalermusic.com/t/scaler-2-5-overwriting-full-sessions/8616 "2021-11-19T22:07:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![xtremsounds](https://avatars.discourse-cdn.com/v4/letter/x/ed655f/32.png) [@xtremsounds](https://forum.scalermusic.com/u/xtremsounds)\
**Post date:** [November 19, 2021, 10:07pm UTC](https://forum.scalermusic.com/t/scaler-2-5-overwriting-full-sessions/8616/1 "2021-11-19T22:07:30Z")

</div>

HI I tried saving a new preset and selecting entire session after clearing out the recorded notes in section a. When replacing the existing preset and then loading it again, the chords in section a still show up instead of loading section c into section a.

Also a slight improvement could be made when dragging a chord over a pattern. the delay to switch to the pattern is a bit long slowing down workflow a little.

---

<div class="post-metadata">

**Author:** ![TMacD](https://yyz2.discourse-cdn.com/flex012/user_avatar/forum.scalermusic.com/tmacd/32/6358_2.png) [@TMacD](https://forum.scalermusic.com/u/TMacD)\
**Post date:** [December 13, 2021, 9:04pm UTC](https://forum.scalermusic.com/t/scaler-2-5-overwriting-full-sessions/8616/2 "2021-12-13T21:04:56Z")

</div>

I’m also seeing some frustrating behaviors in the SAVE chord/session department.

Just yesterday I went to resave a Session via the SAVE button and the REPLACE option only to have it retain the old settings and burn down a bunch of work. This has happened a multiple times.

I also just posted a bug report related to Scaler crashing when accessing and using certain SAVED Session files and editing a mapping. Those files were posted.

I suspect the save/recall workflow is on their radar at the moment,at least I hope it is.

---

<div class="post-metadata">

**Author:** ![Ed1](https://yyz2.discourse-cdn.com/flex012/user_avatar/forum.scalermusic.com/ed1/32/263_2.png) [@Ed1](https://forum.scalermusic.com/u/Ed1)\
**Post date:** [December 15, 2021, 3:33am UTC](https://forum.scalermusic.com/t/scaler-2-5-overwriting-full-sessions/8616/3 "2021-12-15T03:33:20Z")

</div>

> [@TMacD](#):
>
> I’m also seeing some frustrating behaviors in the SAVE chord/session department

> [@TMacD](#):
>
> I suspect the save/recall workflow is on their radar at the moment

Yes it is, we are trying to fix all this in the 2.5.1 patch.

Thanks for reporting

---

<div class="post-metadata">

**Author:** ![1stInversion](https://avatars.discourse-cdn.com/v4/letter/1/ac91a4/32.png) [@1stInversion](https://forum.scalermusic.com/u/1stInversion)\
**Post date:** [June 7, 2022, 10:32pm UTC](https://forum.scalermusic.com/t/scaler-2-5-overwriting-full-sessions/8616/4 "2022-06-07T22:32:54Z")

</div>

Ouch! Thanks for reporting about it. I’ve not used that function much if at all but I tend to remember reports on things and it helps me avoid brick walls. Fortunately, it’s known and let’s hope it can be corrected without too much agony.