I have found the problem! The update to EZStings 1.31 changed the position of the expression pedal. It is not something I use often. It seems that this affects saved files too. Which can’t be right! The pedal goes to 0% every time I press play! Is there a work around or how do I back this update out.
EZkeys version: 1.3.1 Operating system: Windows 10
When the track starts playing, the pedals go to their current states on the song track. That’s intended. If you record a pressed pedal to the track, it will stay pressed. Do you have MIDI on the track in EZkeys or only in your DAW? If only in your DAW, just turn off Follow Host.
Thank you for your quick reply. It seem to work perfectly in the DAW (Cubase, Calkwalk). It is in stand alone mode that the problem exists! When I activate play the expression pedal goes to 0% in a fraction of a second. Very, very annoying and I can’t find a way around it.
EZkeys version: 1.3.1 Operating system: Windows 10
The post has been modified 2 times, last modified 4 years ago by ElMojo.
The problem is only on EZKeys String Machine in my setup. As it has an expression pedal. I have since edited a track in Cubase and the problem is now happening in Cubase too. My EZKeys Grand and Upright pianos are working perfectly. The problem is very easy to recreate in stand-alone mode. Simply drag a MIDI file from the browser and press play. The expression pedal goes straight to 0%. This means you either get muffled or no sound until you manually adjust the pedal above 0%. This is not possible from Cubase. The only work around I can find is to start a few bars in using them to adjust the expression pedal after pressing record. This only works in stand-alone mode. It has left my String Machine unusable until it is fixed.
EZkeys version: 1.3.1 Operating system: Windows 10
Ah, in String Machine. Then I understand the issue. Yeah, that was not intended and will be fixed. Maybe a workaround for now can be to temporarily set the tempo to 1 and record a quick raise of the pedal to 100% into the beginning of the first block?
Thank you! Setting the tempo to 1 is something that I hadn’t figured out yet. Still very awkward. Is there some way I can go back to 1.3.0 until this is fixed.
EZkeys version: 1.3.1 Operating system: Windows 10
Yes having rendered the product (EZKeys Strings) unusable. How do we go back to 1.3.0 that doesn’t seem to have this show stopping error. Lets face it you should have tested everything before you committed to 1.3.1. Testing is something you should be doing before releases, not waiting for your Guinee Pigs to test it for you. So here we are are your very own Guinee Pigs kicking up a stink because you don’t test before release. You should as professionals know better.
EZkeys version: 1.3.1 Operating system: Windows 10
