eDRUMin version 2.2 BETA available

[Rob]

I can confirm the host port update issue on macOS. Sorry about that. As for the note banks, has the device gone out of 'Advanced mode'?

[sevenoneone]

I hope this is an appropriate place for this request... Rob, in your video about edge sense with single zone pads, i see the x-stick scaler goes up to at least 9. In v2.1 and in the v2.2 beta the highest value is 5. Is more possible? It'd be awesome to get louder rim sounds on the pads I'm using (Yamaha TP70, also testing a rubber Alesis Nitro pad)

[monospace]

As for the note banks, has the device gone out of 'Advanced mode'?

Indeed it has. That could have been me though. All good now, thanks.

[Rob]

Changes in build 4

• Fixed issue updating devices connected to USB Host Port

[Rob]

Hi Rob, I am wondering if there is a way to tell which preset is loaded? Maybe i just haven't come across how to tell. It seems that everyone would want to know this?
If not, could the one loaded be highlighted in the preset page?
Or maybe listed above the main page?
If I am away from the edrumin for a few days or more I forget what preset I was last loaded. I have been just reloading a preset that I want to be sure. But then I am not sure if there were changes that I didn't save and just lost by reloading a preset?
This leads me to one other question: If I have preset loaded and I have worked on it and made changes and saved them, Will those changes be applied to the preset when I save them? Or is the preset not updated unless I overwrite it? thanks for your help, Mbira

I worked on this today. I'm not getting you everything you want, but at least what I have done should help. For each preset type eDRUMin will now remember:

• whether the user was viewing 'user' or 'factory presets'
• the last selected user preset
• the last selected factory preset
• the last loaded preset (gets faintly highlighted)

This way when you are moving around in the Preset Manager, jumping around between different preset types and between user / factory presets, it'll be much easier to remember where you were and what you did.

[mrmbira]

Thanks Rob! that should help. just for my understanding of loaded and selected: Does loaded mean loaded into just the control app or would it be highlighted only when loaded into the hardware device?
I see that perhaps I don't understand what happens when I open a preset in the control app - does this load the preset directly into the hardware device too? I guess it must?
And if I have it not set to auto save, then the changes I make will only be loaded to the device when I select save?
So when you say it will remember the last selected preset does that mean the last one loaded? What is the difference between loaded and selected? Sorry for all the questions, I just want to make sure I understand how to use the changes you have made. And thanks so much for your quick response to my request.

[mrmbira]

Thanks Rob! that should help. just for my understanding of loaded and selected: Does loaded mean loaded into just the control app or would it be highlighted only when loaded into the hardware device?
I see that perhaps I don't understand what happens when I open a preset in the control app - does this load the preset directly into the hardware device too? I guess it must?
And if I have it not set to auto save, then the changes I make will only be loaded to the device when I select save?
So when you say it will remember the last selected preset does that mean the last one loaded? What is the difference between loaded and selected? Sorry for all the questions, I just want to make sure I understand how to use the changes you have made. And thanks so much for your quick response to my request.

one last clarification: if I am making changes in the control app with Auto save off, The changes seem to change my pads in real time, but if they haven't been sent to the device yet how do they do that? Is the control app running the show while open? And am I right in thinking that if I close the app without saving the changes, my settings would revert back to what had formerly been loaded to the device?
And those unsaved changes would they be lost from the app, or are they still present when I open the app again? And if I want to be able to recall them I would have to overwrite the current preset or create a new one. I looked in the manual to and only see references to auto save. thanks for any clarity on these things, Mbira

[monospace]

Changes in build 4

• Fixed issue updating devices connected to USB Host Port

Fix confirmed, thanks.

[Rob]

Thanks Rob! that should help. just for my understanding of loaded and selected: Does loaded mean loaded into just the control app or would it be highlighted only when loaded into the hardware device?
I see that perhaps I don't understand what happens when I open a preset in the control app - does this load the preset directly into the hardware device too? I guess it must?
And if I have it not set to auto save, then the changes I make will only be loaded to the device when I select save?
So when you say it will remember the last selected preset does that mean the last one loaded? What is the difference between loaded and selected? Sorry for all the questions, I just want to make sure I understand how to use the changes you have made. And thanks so much for your quick response to my request.

The device itself doesn't have enough memory to save presets--it basically only has one preset that is loaded from it's EEPROM when the device is powered up.

So the presets are stored on your computer and sent to the device as needed when you 'double click' on a preset. The settings from the preset are loaded into working memory, however, the settings are only written to the EEPROM if you have auto-save on, or if you click 'save'. So if you don't save and you power cycle the device, the settings previously stored in the EEPROM will be reloaded.

In build 5, which I will post later today, the last preset you selected and the last preset you double-clicked (to send to the device) will be remembered. A big part of the reason I'm hesitant to highlight the last double-click preset is because it might lead users to think that the presets are stored on the device and that making changes to the device will update the presets, which is not the case. I may still remove highlighting on the last double-clicked preset.

image.png (74.73 KiB) Viewed 2271 times

[mrmbira]

The device itself doesn't have enough memory to save presets--it basically only has one preset that is loaded from it's EEPROM when the device is powered up.

So the presets are stored on your computer and sent to the device as needed when you 'double click' on a preset. The settings from the preset are loaded into working memory, however, the settings are only written to the EEPROM if you have auto-save on, or if you click 'save'. So if you don't save and you power cycle the device, the settings previously stored in the EEPROM will be reloaded.

In build 5, which I will post later today, the last preset you selected and the last preset you double-clicked (to send to the device) will be remembered. A big part of the reason I'm hesitant to highlight the last double-click preset is because it might lead users to think that the presets are stored on the device and that making changes to the device will update the presets, which is not the case. I may still remove highlighting on the last double-clicked preset.

image.png
[/quote]

Rob, thanks for the clear explanation of how the presets work. I really didn't understand how it worked and now i do. I think if you put a paragraph in the manual explaining what you explained above, that would be so helpful to others and there shouldn't be any confusion about presets being stored on the device. So I hope you will leave the highlighting on the loaded preset as that will be so helpful with the way that I am working with presets now. thanks again, Mbira