Hi folks;
Stay cool ;-)
No reason to be in a clash!
I think, RichHowe and the rest has described the primary problem very well.
I'm also working in the IT and software development;
My post was just a suggestion.
The different problems behind are well known to me.
So there are indeed two points of view:
- the developers view
- the users view
From the users view, it would be nice, to have the related NAME of the block from the block library.
It would make it a bit easier, to HANDLE the whole preset (i.e. I can also see, which other kinds of parameter-settings I've used).
That would be, also for me, nice.
Not more and not less than it is.
From the developers view, it's a bit more complicated.
To understand that, someone has to know something about software structures and especially the file structure of the Axe-presets.
And he has to consider, WHAT is stored WHERE.
So, to help carloszeke to understand, if hasn't yet (There is nothing wrong with! Perhaps you know and/or can do things, I or we cant't ;-) That's life and we have to live with),
the thing is, that we talk about the (preset)informations, stored in the Axe. That's important!
Axe-Edit does retrieve these informations when connected, and shows them in the editor.
In this (loaded) preset information, the USER-GIVEN NAME of the block, previously taken from the block library, is NOT saved,
When you load a block from the block library, you tell, at first the editor, later on by saving also the Axe, ONLY which parameter settings you want to adjust to the selected block.
ONLY the settings. Not the related, user-given, NAME!
So, if you load a preset from the Axe later on, Axe-Edit cannot know this name, undoubtedly.
Now, you could say, OK, but look at the cabs; all their names are shown in the editor; everytime I can see, which one I've chosen.
Right.
But ...
the names and the settings of the cabs are stored in the cab library in the Axe.
So, the parameter settings (of the cabs i.e.) AND THE NAMES are present the whole time;
IN THE AXE AND IN THE EDITOR, WHEN HE CONNECT ITSELF WITH THE AXE.
AND, there is space in the preset file, reserved for the CAB NAME, not only for the cab parameter settings.
That's the reason for the possibility to handle i.e. these names.
To make it possible, to handle block library names, you have to change the file structure of the preset file.
For now, the file has a fixed structure and length.
Also you would have to save the block library in the axe.
The list of names of the block library you can see, is either stored locally on your computer, or, when starting the software, will be fed into it.
But this list isn't in your Axe.
To store, for example, only the additional name (from block library) in the preset file, would make no sense, because there
will be no link to the file on the computer (and also to the related settings), when you load the preset into the Axe-Editor.
What is going on, when you change the settings of your library block on the Axe and load the preset into the editor?
The editor would show you the name "MXR Phase90" i.e, but not the correct settings ... and so on.
I will stop here, because it is a wide range of things to consider.
Finally it would be possible, to integrate the wish.
But prior, the developer would have to consider a lot of things, to implement it.
I hope, my remarks could additionally help a little bit to understand,
I have been right describing the Axe-details,
and everyone will appropriately take into consideration,
that I'm from germany;
so my native language isn't english ;-)
Best regards to all!
Axe is a killer <;-))))
But not of GOOD manners!
CU and bye
Mike
