I know I’ve mentioned renaming before… but it keeps on recurring, so I’ve tried A LOT to repeat this with the new version and this is repeatable.
v9.37 Logic X 10.1.1, standalone and AU
- Load a patch on the synth or from the preset panel
- Select Init Preset from the editor (it appears as Init Preset on the synth but with the original name in the editor)
- Edit the patch
- rename on the editor in the hardware panel using alt+click
- press enter
- the name is changed on the synth and the editor but the sound reverts to the original sound loaded.
Also:
- Load a preset from the hardware preset panel or the synth
- Initialise it (by clicking Init Preset button in editor)
It appears as Init patch on the synth, but the original name is on the editor
- rename on the editor using alt+click
- press enter
the patch is renamed on the synth and editor but the sound is the original loaded one… not Init Patch
I tried to attach a video file, but it won’t upload, so I’ll email a link.
GilW
2
I could reproduce these issues and reported them. Thank you!
My editor seems to behave in a different way.
9.37 standalone Mac OS10.11.3
Init Patch works as expected.
Renaming a patch doesn’t have any effect:
- Load a patch on the synth or from the preset panel
- right-click on the preset name.
- type a new name, press enter or ok
the name is not changed on the synth or in the editor.
GilW
4
If this is correct than it’s a critical issue. Will check this here, thanks for reporting.
Does any other OSX user experience the same problem ?
JacobH
5
I can repeat the “Renaming a patch doesn’t have any effect” issue Sander37 mentioned.
OS X 10.10.5 Editor v0.9.37
LuLoop
6
Hi Gil,
Renaming in windows and OSX using Stand alone. Same problem???. or maybe different???
using v9.37/1.1.16
See video.
Regards Luloop
https://www.youtube.com/watch?v=6sk_E_ORivg
GilW
7
Yes Luloop, same issue. Thanks for the heads up !
LuLoop
8
Hi Gil,
In the 1.1.19 / 0.9.39 version, the issue, renaming presets, is still there.
Regards Luloop
GilW
9
Known, Thanks for the heads up.
GilW
10
Both should be fixed in 0.9.40.
Will you be able to verify ?
Thanks in advance !
LuLoop
11
Hi Gil,
In the 0.9.40 / 1.1.20 the problem is gone
Regards Luloop