[Nick Davy]

Thanks for the update and workaround, although now I’ve found it only occurs inside DAW I can do the merge in the standalone and hopefully it will be okay once I open in DAW and I can save to another file as I won’t be able to read the updated file in the standalone until fix released.

[Nick Davy]

An another strange occurrence which has happened after merging issue.
I installed another ezkeys expansion and after install it asked for 2 updates to be applies see attachment but when applied (despite the fact that it was previously applied and at correct version) now all EZkeys expansions show an update is required the same one I had just installed which wasn’t the case before I started install.

Have added previous images from DAW as I might have not uploaded them.

[Nick Davy]

DAW
EZkeys plug-in version 1.2.4 (build 13303) [64-bit VST]
Core MIDI Library version 1.2.0

EZkeys plug-in version 1.2.4 (build 13303) [64-bit VST]
Standalone host version 1.2.4 (build 13303)
Core MIDI Library version 1.2.0

[Nick Davy]

Took me a little while to find the merge issue but it seems it only occurs inside a DAW (Studio One)
Have attached 2 screen clips one before and one after.

[Nick Davy]

Thanks for the update on the DAW saving issue will keep my eyes open for next release.

Will in meantime find the project that I had the issue on unfortuantely I wouldn’t have saved it once I encountered the issue so will need to check my scoring notes to see where I used that combination of keys.

Thanks again for quick response.12

[Nick Davy]

Yes I’m using latest version as I installed some SD3 updates yesterday.
Okay I’ve tried it again and it’s working now for some reason I will keep an eye on as I need to find original project.
Also for some reason when I save a project in Studio One I can’t read it in standalone mode but that’s another issue but attached. Have changed file extension from ezkp to txt as otherwise I get an attachment error.

[Author]

Replies