Waves Element 2 Preset Management Disgraceful

[wagtunes]

There ARE soundsets for Element, in the XPS format:
http://patcharena.com/downloads/comment ... bba6b6c3a2

Then they had to go through some special process with Waves like you have to do with UVI Falcon, because there is no way to make a sound bank on your own that shows up as a bank in Element 2.

It looks that a bank that was created with "Save To New File" in Element 2 as a new XPS file will no longer appear in the Presets list once the plugin and/or host is re-loaded. You have to use "Open Preset file" and load the XPS file with this again to have the bank and presets again in the list.

Only presets that are saved with "Save into Preset Menu As..." will always stay in the Preset list.
Those presets seem to be saved in the "Element2 Settings.xps" file at the location taht was mentioned earlier here.

So then how does one actually create a bank of presets similar to the factory ones? Or is that not possible? Waves says it isn't but that was a while ago.

You could created a new bank in XPS format with "Save to New File..." in the SAVE menu. For example you name it "Wagtunes Bank 1.xps".
You could then save new presets to this bank with "Save To Wagtunes Bank 1.xps as..." in the SAVE menu.
Presets will then appear in the preset list in alphabetical order without sub-folders, with "Wagtunes Bank 1:" as a title of the bank. Presets saved that way automatically seem to be saved to the corresponding XPS file.

As alraedy mentioned the custom bank seems to dispapear from teh list if the plugin is re-loaded and to get it again you have to reload the XPS file with "Open Preset File..." in the LOAD menu.

The currently used patch of an instance is saved with the host project, at least it works like that here.


As mentioned above saving patches in a host specific format seems to be possible too.


Currently that preset system is not really nice for using custom banks but still it is possble to save and load you own patches and/or banks.

Can you imagine all the support requests I'd get with this ridiculous system?

"Hey man, your bank disappeared. What happened to it?"

I'll pass.

If certain single patches should stay permanently in the presets list you could re-save them with "Put Into Preset Menu As...”. As alraedy mentioed those will then be stored in a specific default XPS file.

That's also mentioned in this description done by Waves about how to use free presets for their plúgins:
https://www.waves.com/1lib/pdf/presets/ ... resets.pdf

Yes, I could do that for my own personal system. But then somebody who gets a library from me gets a folder with patches. They don't get something like you get from Arturia when you can export your patches to a file. So they'd have to go through the same process that I went through in order to get my presets showing in their menu. Not ideal and certainly not a great selling point for the library.

[Ingonator]

This is a decription about deleting custom presets in Waves plugins (works with Waves synths and effects):

Deleting Presets

You may delete User Presets and presets within a Setup File. Factory Presets and Setup Library files cannot be deleted or overwritten.

1. Hold the Command key down.
2. Click-and-hold the Load button to see the pop-up menu.
3. While still holding the Command/Control key, select the preset or setup to delete.
4. A confirmation box will appear, allowing you to cancel or ‘OK’ the deletion.

I have used this with custom presets in Element 2 and some other Waves plugins and it indeed works.

[Ingonator]

I checked custom Element 2 XPS files with a text editor like WordPad and all parameters of a patch seem to be exposed in such text editor, including the patch name etc.

It is possible to copy the text for a patch from one XPS file to another and re-save the XPS file to create a new bank. The additional patches will then appear in the presets list. Either automatically if you saved to the default user XPS file called "Element2 Settings.xps" or after re-loading a custom xps file with "Open Preset File".

When opening the XPS file in a text editor a single patch starts with <Preset Name=" and ends with </Preset>.
The XPS file that contains a bank of patches starts with <PresetXMLTree version="2"> and ends with </PresetXMLTree>. Besides that only the text with the patches is included.

It should be possible to share Element 2 patches as text that then could be added to a XPS file.

The first factory preset of Element 2 as text (XPS file loaded in WordPad) looks like this after re-saving it as a user preset (with "Put Into Preset Menu As..." from the SAVE menu):

Code: Select all

<Preset Name="Abnormality (MW)" GenericType="ELMN">
        <PresetHeader>
            <PluginName>Element2</PluginName>
            <PluginSubComp>JFGS</PluginSubComp>
            <PluginVersion>9.92.0.45</PluginVersion>
            <ReadOnly>false</ReadOnly>
        </PresetHeader>
        <PresetData Setup="CURRENT">
            <Parameters Type="RealWorld">0 0 7 0 0 0 20.100000000000001421 2 0 0
0 0 0 0 23.199999999999999289 0 1 -3.1000000000000000888 1
100 0 100 1 1 3 2 4 6
0 8 0 3 0 1 14.099999999999999645 100 0
100 0 1 1 100 1 0 0 1
1 100 1 0 50 0 1 724.39999999999997726 0
1.1999999999999999556 0 29.5 0.5 1 20 0 0 0
0 20000 0 0 22 0 1 1 11
24 55 1 0 5 40 0 1 0
1 8 0 1 0 1 6 0 1
1 5 24 100 1 5 1 4 8
100 16 -24 1 0 1 0 0 12
1 -5 1 24 1 -24 1 12 1
-12 1 7 1 0 0 12 1 0
1 0 1 -5 1 0 1 11.699999999999999289 36.5
1 2 38 35.799999999999997158 0 0 0 0 -36
1.5 3.8999999999999999112 5 0.41000000000000003109 * * * * 10
0 1 1 1 1 8 0 0 0
0 * * 120 1 * * * 0
0 0 1 0 0 0 0 0 0
0 0 0 0 0 0 0 2 0
0 0 * * 0 0 2 1 1
2 1 1 1 0 1 0 1 *
0 2 2 </Parameters>
        </PresetData>
    </Preset>

After copying that txet to the default user XPS file the preset still sounds similar to the original one and also the parameters look identical in the GUI. Does not look like something got lost by just copying the text within WordPad.

[wagtunes]

I checked custom Element 2 XPS files with a text editor like WordPad and all parameters of a patch seem to be exposed in such text editor, including the patch name etc.

It is possible to copy the text for a patch from one XPS file to another and re-save the XPS file to create a new bank. The additional patches will then appear in the presets list. Either automatically if you saved to the default user XPS file called "Element2 Settings.xps" or after re-loading a custom xps file with "Open Preset File".

When opening the XPS file in a text editor a single patch starts with <Preset Name=" and ends with </Preset>.
The XPS file that contains a bank of patches starts with <PresetXMLTree version="2"> and ends with </PresetXMLTree>. Besides that only the text with the patches is included.

It should be possible to share Element 2 patches as text that then could be added to a XPS file.

The first factory preset of Element 2 as text (XPS file loaded in WordPad) looks like this:

Code: Select all

<Preset Name="Abnormality (MW)" GenericType="ELMN">
        <PresetHeader>
            <PluginName>Element2</PluginName>
            <PluginSubComp>JFGS</PluginSubComp>
            <PluginVersion>9.92.0.45</PluginVersion>
            <ReadOnly>false</ReadOnly>
        </PresetHeader>
        <PresetData Setup="CURRENT">
            <Parameters Type="RealWorld">0 0 7 0 0 0 20.100000000000001421 2 0 0
0 0 0 0 23.199999999999999289 0 1 -3.1000000000000000888 1
100 0 100 1 1 3 2 4 6
0 8 0 3 0 1 14.099999999999999645 100 0
100 0 1 1 100 1 0 0 1
1 100 1 0 50 0 1 724.39999999999997726 0
1.1999999999999999556 0 29.5 0.5 1 20 0 0 0
0 20000 0 0 22 0 1 1 11
24 55 1 0 5 40 0 1 0
1 8 0 1 0 1 6 0 1
1 5 24 100 1 5 1 4 8
100 16 -24 1 0 1 0 0 12
1 -5 1 24 1 -24 1 12 1
-12 1 7 1 0 0 12 1 0
1 0 1 -5 1 0 1 11.699999999999999289 36.5
1 2 38 35.799999999999997158 0 0 0 0 -36
1.5 3.8999999999999999112 5 0.41000000000000003109 * * * * 10
0 1 1 1 1 8 0 0 0
0 * * 120 1 * * * 0
0 0 1 0 0 0 0 0 0
0 0 0 0 0 0 0 2 0
0 0 * * 0 0 2 1 1
2 1 1 1 0 1 0 1 *
0 2 2 </Parameters>
        </PresetData>
    </Preset>

After copying that txet to the default user XPS file the preset still sounds similar to the original one and also the parameters look identical in the GUI. Does not look like something got lost by just copying the text within WordPad.

Just to be clear though, if creating a separating bank file, like Wagtunes Bank as an example, the user would have to reload that bank by loading a patch each time they open the plugin. Or does that bank permanently stay in the bank list?

[wagtunes]

Also, where did you find the XML files for the banks? I can't find anything on my system.

[Ingonator]

I checked custom Element 2 XPS files with a text editor like WordPad and all parameters of a patch seem to be exposed in such text editor, including the patch name etc.

It is possible to copy the text for a patch from one XPS file to another and re-save the XPS file to create a new bank. The additional patches will then appear in the presets list. Either automatically if you saved to the default user XPS file called "Element2 Settings.xps" or after re-loading a custom xps file with "Open Preset File".

When opening the XPS file in a text editor a single patch starts with <Preset Name=" and ends with </Preset>.
The XPS file that contains a bank of patches starts with <PresetXMLTree version="2"> and ends with </PresetXMLTree>. Besides that only the text with the patches is included.

It should be possible to share Element 2 patches as text that then could be added to a XPS file.

The first factory preset of Element 2 as text (XPS file loaded in WordPad) looks like this:

Code: Select all

<Preset Name="Abnormality (MW)" GenericType="ELMN">
        <PresetHeader>
            <PluginName>Element2</PluginName>
            <PluginSubComp>JFGS</PluginSubComp>
            <PluginVersion>9.92.0.45</PluginVersion>
            <ReadOnly>false</ReadOnly>
        </PresetHeader>
        <PresetData Setup="CURRENT">
            <Parameters Type="RealWorld">0 0 7 0 0 0 20.100000000000001421 2 0 0
0 0 0 0 23.199999999999999289 0 1 -3.1000000000000000888 1
100 0 100 1 1 3 2 4 6
0 8 0 3 0 1 14.099999999999999645 100 0
100 0 1 1 100 1 0 0 1
1 100 1 0 50 0 1 724.39999999999997726 0
1.1999999999999999556 0 29.5 0.5 1 20 0 0 0
0 20000 0 0 22 0 1 1 11
24 55 1 0 5 40 0 1 0
1 8 0 1 0 1 6 0 1
1 5 24 100 1 5 1 4 8
100 16 -24 1 0 1 0 0 12
1 -5 1 24 1 -24 1 12 1
-12 1 7 1 0 0 12 1 0
1 0 1 -5 1 0 1 11.699999999999999289 36.5
1 2 38 35.799999999999997158 0 0 0 0 -36
1.5 3.8999999999999999112 5 0.41000000000000003109 * * * * 10
0 1 1 1 1 8 0 0 0
0 * * 120 1 * * * 0
0 0 1 0 0 0 0 0 0
0 0 0 0 0 0 0 2 0
0 0 * * 0 0 2 1 1
2 1 1 1 0 1 0 1 *
0 2 2 </Parameters>
        </PresetData>
    </Preset>

After copying that txet to the default user XPS file the preset still sounds similar to the original one and also the parameters look identical in the GUI. Does not look like something got lost by just copying the text within WordPad.

Just to be clear though, if creating a separating bank file, like Wagtunes Bank as an example, the user would have to reload that bank by loading a patch each time they open the plugin. Or does that bank permanently stay in the bank list?

Only the default user preset bank where patches were saved with "Put Into Preset Menu As..." from the SAVE menu will load automatically.
Soundset created with "Create New File" have to be re-loaded agan when the plugin and/or host was closed.

A workaround is to save you favorite patches of a 3rd party bank with "Put Into Preset Menu As..." as i alraedy mentioned earlier.

With all user presets sub-folders like in the factory presets are not possible, no mattrer if the default user XPS file or a new one is used.

Anyway the method with copying texts of the patches which i just mentioned in my post above might work to create a new XPS bank file from multiple others. You might even save a new XPS file for each single patch and then later recombine to a new file with a bank of patches later.

[Ingonator]

Also, where did you find the XML files for the banks? I can't find anything on my system.

As i had also added to my previous post while you replied to it I re-saved a factory preset with "Put Into Preset Menu As..." from the SAVE menu.

Those patches are saved into the default user XPS file called "Element2 Settings.xps" found at C:\Users\Public\Waves Audio\Plug-In Settings" (in Windows 10).

This file does not exist until you have saved the first user preset with "Put Into Preset Menu As...".

[wagtunes]

Also, where did you find the XML files for the banks? I can't find anything on my system.

As i had also added to my previous post while you replied to it I re-saved a factory preset with "Put Into Preset Menu As..." from the SAVE menu.

Those patches are saved into the default user XPS file called "Element2 Settings.xps" found at C:\Users\Public\Waves Audio\Plug-In Settings" (in Windows 10).

This file does not exist until you have saved the first user preset with "Put Into Preset Menu As...".

Got it. Well, I need to figure out if this is all worth the effort taking into account possible customer support issues.

Thanks for the clarification on everything. No clue how you figured all this out. It does explain why there are almost no 3rd party libraries for this synth.

[Ingonator]

For those who did not notice yet for both Element 2 and Codex the factory presets are also available as NKS fies for NI Komplete Control and Maschine 2 software and corresponding controllers (while a controller is not necessary to use the software for browsing patches).

I got a Ni Komplete Kontrol S61 Mk1 since around two years (+ both the Komplete Kontrol and Maschine 2 software) and for Element 2 the NKS presets offer 70 parametrs being exposed to the hardware controller (9 pages with up to 8 parameters in each page).

If you know how to do it you could also save your own NKS presets for both Waves synths.

[wagtunes]

For those who did not notice yet for both Element 2 and Codex the factory presets are also available as NKS fies for NI Komplete Control and Maschine 2 software and corresponding controllers (while a controller is not necessary to use the software for browsing patches).

I got a Ni Komplete Kontrol S61 Mk1 since around two years (+ both the Komplete Kontrol and Maschine 2 software) and for Element 2 the NKS presets offer 70 parametrs being exposed to the hardware controller (9 pages with up to 8 parameters in each page).

If you know how to do it you could also save your own NKS presets for both Waves synths.

Interesting. I don't use any of that stuff but it is nice to know for the future just in case.

[Ingonator]

For those who did not notice yet for both Element 2 and Codex the factory presets are also available as NKS fies for NI Komplete Control and Maschine 2 software and corresponding controllers (while a controller is not necessary to use the software for browsing patches).

I got a Ni Komplete Kontrol S61 Mk1 since around two years (+ both the Komplete Kontrol and Maschine 2 software) and for Element 2 the NKS presets offer 70 parametrs being exposed to the hardware controller (9 pages with up to 8 parameters in each page).

If you know how to do it you could also save your own NKS presets for both Waves synths.

Interesting. I don't use any of that stuff but it is nice to know for the future just in case.

If you got NI Komplete 10 or 11 you should also have a license for the Komplete Kontrol software included (as standalone and plugins) where you could use NKS presets. "Komplete Kontrol" should appear in the Native Access software. The software will also work without a hardware controller from NI.

[wagtunes]

For those who did not notice yet for both Element 2 and Codex the factory presets are also available as NKS fies for NI Komplete Control and Maschine 2 software and corresponding controllers (while a controller is not necessary to use the software for browsing patches).

I got a Ni Komplete Kontrol S61 Mk1 since around two years (+ both the Komplete Kontrol and Maschine 2 software) and for Element 2 the NKS presets offer 70 parametrs being exposed to the hardware controller (9 pages with up to 8 parameters in each page).

If you know how to do it you could also save your own NKS presets for both Waves synths.

Interesting. I don't use any of that stuff but it is nice to know for the future just in case.

If you got NI Komplete 10 or 11 you should also have a license for the Komplete Kontrol software included (as standalone and plugins) where you could use NKS presets. "Komplete Kontrol" should appear in the Native Access software. The software will also work without a hardware controller from NI.

I'm sure I do. I just haven't found a need for it.

[MFXxx]

I can't believe this. There is no way to set up a user folder in Waves Element 2. This has been confirmed by Waves support. You create a patch, save it somewhere on your hard drive and then when you want to load it, you have to go to "Open Preset" and go to the location on your hard drive where you have them stored. That's it. That's your preset management system.

No wonder there are no 3rd party libraries for this synth. The folders you see when you go to load are built into the synth. They exist nowhere on your hard drive.

In this day and age, especially since Element 2 is relatively new, this is just disgraceful. What would be the point of me even creating a library for this thing? I mean who will tolerate a preset system like this for 3rd party libraries?

/rant

Funny enough I hacked around and sussed out how to solve this the other night, but it takes to editing the XPS files.
As is when adding a preset pack it will show up as a list above the menu system and you have to add each individually with a subsequent list below the factory presets. Not ideal.
Solution was convoluted but achievable.
Assuming Windows here as for Mac not a clue.
Backup or zip the preset xml you're editing just for safety's sake (your gambit either way).

Open C:\Users\Public\Waves Audio\Plug-In\Element2 Settings.xps file in notepad (or word as I did as better for editing then copy and pasted into notepad when saving the XPS file as the process is far simpler).

These are the user presets that appear below the factory presets.
********************************************************************************
NOTE IS BEST TO EDIT THESE OUTSIDE OF THE PROGRAM FILES DIRECTORY ENVIRONMENT AS ADMIN RIGHTS MAYBE REQUIRED AND JUST CONFUSE THINGS. COPY TO A PUBLIC LOCATION AND ONCE DONE COPY BACK TO THE ORIGINAL FOLDER AS THE ORIGINAL FILE NAME.

Now the convoluted and fun investment part:
1) Open the Element2settings.xps file and in a separate notepad the xps preset pack you want to edit and add to your preset list
ie mypresetpack.xps
by right hand mouse click "open with Notepad" or simply choose "edit".

2) In the notepad document the mypresetpack.xps delete the following header:
<PresetXMLTree version="2">
and delete the following at the end of the file:
</PresetXMLTree>
3) You should now have a batch of text starting with:
<Preset Name="PATCHNAME" GenericType="ELMN">
and ending with
</Preset>.
Study the layout and format as it will help with the next stage.
4) Now copy this text you have from the now edited mypresetpack.xpx into the Element2settings.xps it must be inserted after the
<PresetXMLTree version="2">.
Check the end of the pasted in portion and ensure there are no extra lines inserted.
(So the pasted text must be copied into the element2settings.xps between the following text:
<PresetXMLTree version="2">
<Preset Name="MY SECOND PRESET="ELMN"> (where MY SECOND PRESET IS THE PRESET NAME IN THE LIST).

Once you are famliar with the text format and tree structure with the text and preset naming you may want to move stuff around no worries.
********************************************************************************
Now the cumbersome part to avoid list and have presets catergorised into groups.

To apply a group to each preset, every preset must have the following inserted to group (put them in a menu) into the xml text between
<PresetHeader>
and
<PluginName>Element</PluginName>
with
<Group>My Group Name</Group>.
MY GROUP NAME will be the folder name in the vst's menu browser.

This must be done on each and every patch to be grouped. Of course you can have as many groups as you like. It's also worth noting the presets do not have to be in the order as the plugin will automatically group and collate the presets into the menu within the preset browser once done. Test it and you will see. If you look at the example below I have purposely placed a vox preset either side of the cymbal preset. They will still appear within 2 menus one name VOX and the other named OVERHEADS. It doesnt matter where these are placed as far the order goes, they wil lbe put in the appropriate sub folder in the menu controlled by the <GROUP NAME> text.

Example of my edit with one presets below from Renaissance Channel.

*************************************************************************************************************
<PresetXMLTree version="2">
<Preset Name="Voc_Female_1" GenericType="RNCH">
<PresetHeader>
<Group>Vox</Group>
<PluginName>RChannel</PluginName>
<ReadOnly>false</ReadOnly>
</PresetHeader>
<MessageToShell/>
<PresetData Setup="CURRENT">
<Parameters Type="RealWorld">1 3 0 131 0.9000000000000000222 1 0 1.6999999999999999556 310 1
1 0 6.5999999999999996447 3018 1.25 1 1 6.2000000000000001776 7443
0.9000000000000000222 1 * * * 0 0 1 0
0 2 733 1 0 * 0 0 0
733 1 0 * 1 3.6000000000000000888 240.96999999999999886 1 -11.599999999999999645
2.0400000000000000355 8 1000 63 0 56.229999999999996874 0 1.5 0
* * 0 0 -80 -80 130 250 *</Parameters>
</PresetData>
</Preset>
<Preset Name="Crash_2" GenericType="RNCH">
<PresetHeader>
<Group>Drums Overheads Crash</Group>
<PluginName>RChannel</PluginName>
<ReadOnly>false</ReadOnly>
</PresetHeader>
<MessageToShell/>
<PresetData Setup="CURRENT">
<Parameters Type="RealWorld">1 3 0 204 0.9000000000000000222 1 2 0 250 1
1 0 0 1325 1 1 0 2.6000000000000000888 11900
0.9000000000000000222 1 * * * 0 0 0 0
0 2 733 1 0 * 0 0 0
733 1 0 * 1 3.6000000000000000888 240.96999999999999886 0 -8.1999999999999975131
2.8799999999999998934 0 1000 63 0 56.229999999999996874 0 1.5 0
* * 1 0 -80 -80 130 250 *</Parameters>
</PresetData>
</Preset>
<Preset Name="Voc_Female_2" GenericType="RNCH">
<PresetHeader>
<Group>Vox</Group>
<PluginName>RChannel</PluginName>
<ReadOnly>false</ReadOnly>
</PresetHeader>
<MessageToShell/>
<PresetData Setup="CURRENT">
<Parameters Type="RealWorld">1 3 0 114 0.9000000000000000222 1 0 2.6000000000000000888 291 1
1 0 5.7000000000000001776 2709 1.1799999999999999378 1 2 6.4000000000000003553 5076
0.9000000000000000222 1 * * * 0 0 0 0
0 2 733 1 0 * 0 0 0
733 1 0 * 1 4.9299999999999997158 240.96999999999999886 0 -11.199999999999999289
2.9900000000000002132 7.5999999999999987566 1000 63 0 56.229999999999996874 0 1.5 0
* * 1 0 -80 -80 130 250 *</Parameters>
</PresetData>
*************************************************************************************************************
The above is a simple snap shot of some of my presets and not an entire xps file as it will need the following at the start and end of the text to work.

The presets are then repeated all the way to the end of the xps document until the end with:

</PresetXMLTree>

So the start of the instruction is:

<PresetXMLTree version="2">

(THEN ALL YOU PRESET DATA YOU EDITED)

To the end instruction which is :

</PresetXMLTree>

The individual preset loop points (start and finish) are : <Preset Name....> and <Preset>
I think everything else is self explanatory.

*************************************************************************************************************
I've managed to do this for example with preset packs from VSP which are already grouped and just removed the XMLTree portions of the text, copied into a branch and now appear automatically when loading.

Now keeping the presets in the default location make it easy for back up and storage if you ever need to move to another PC or reinstall.

The reason I say this is you can do the same with the Factory presets. These are stored in another file so the preset menu list is actually two different files in different locations on your hard drive...."TALK ABOUT CONVOLUTED".

The original factory banks can be edited just the same but appear differently as an XML file instead of a XPS file (again windows only here):
So for element2 you will find the file you need in:
C:\Program Files (x86)\Waves\Plug-Ins V9\Element2.bundle\Contents\Resources\Presets
named:
1000.xml.
Its the only file in there, fun huh!!!

This is the same location but for every plugin (check out your folder tree and you'll get the jist).
Again backup the file prior to editing (I usually just zip inidiviual files in directory and delete once test edited) and open the file (right mouse click open with Notepad).
Now do the same as you did with the xps file and presto.

The nice advantage in editing the factory presets is you can delete, group, add any of your own presets in it you wish. This may (or may not) help with your workflow and get rid of any junk. Of course its always nicer to have you own presets appearing in the menu next to the sponsored producer names or simpy be immature and rename you producers to the wombles for fun (again you get the jist).

In short. Takes time, but each preset pack takes around an hour to complete if you have to type in group names for sub menus, but worth it.

Hope this helps (i only did this a few nights ago so still fresh), however if anyone spots any errors PM me and ill check it out and edit this post to avoid confusion.

Peace and happy coding lol

Of course as a bottom line addum:

If there are any real geniuses out there, I am wondering if there is anyone who could simply develop a simple program to do all this automatically. JUST A KIND THOUGHT

M

[MFXxx]

Oh and just a thought if theres some one who really does know what they are doing, if theres a better work around for naming a batch of presets into a group please let me know. Thanks.

@Wagtunes Ive checked out that link for elements and thats a tiresome job as each is an indivual patch file and would need to be copied one by one into the settings xps file. IF anyone does this succefully feel free to post here. Thanks.

To get you started and help you with what nees to be done see below. These is the edit XML file for the factory presets for elements 2.

<Preset Name="000 Flowing Energy - TC" GenericType="ELMN">
<PresetHeader>
<Group>CHE</Group>
<PluginName>Element</PluginName>
<PluginVersion>9.2.4.16</PluginVersion>
<ReadOnly>false</ReadOnly>
</PresetHeader>
<MessageToShell/>
<PresetData Setup="CURRENT">
<Parameters Type="RealWorld">3 1 -4 0 0 1 0 2 0 -4
0 0 1 61.100000000000001 22.5 1 1 -35.399999999999999 1
51.700000000000003 0 75.099999999999994 0 1 0 4.2999999999999998 0 6
0 8 0 9 0 1 47.600000000000001 24.5 7.7999999999999998
77.299999999999997 54.600000000000001 7.4000000000000004 183.69999999999999 100 5.2000000000000002 45.100000000000001 5.7000000000000002 7.4000000000000004
801.70000000000005 100 9.6999999999999993 9.3000000000000007 3.8999999999999999 1 1.1000000000000001 113.8 100
34.700000000000003 31.199999999999999 -0.39999999999999991 9.1999999999999993 0 68.400000000000006 0 0 9.1999999999999993
8.6999999999999993 2923.3000000000002 1 0 8 28.899999999999999 1 1 1
2 0 1 1 2 9 0 1 1
3 23 0 1 1 4 2 0 1
1 5 13 53 1 3 1 9 8
100 16 0 1 0 1 0 1 0
1 0 1 0 1 0 1 0 1
0 1 0 1 0 1 0 1 0
1 0 1 0 1 0 1 52.5 34.799999999999997
1 2 20.899999999999999 41.5 0 16.199999999999999 0 8.3000000000000007 -15.300000000000001
1.5 3.8999999999999999 5 0.41000000000000003 * * * * 10
0 1 1 1 1 13 0 0 0
0 * * 120 1 * * * 0
0 0 0 0 0 0 0 0 0
0 1 0 0 0 0 0 2 0
0 0 * * </Parameters>
</PresetData>
</Preset>
<Preset Name="001 Flowing Energy - TC" GenericType="ELMN">
<PresetHeader>
<Group>CHE</Group>
<PluginName>Element</PluginName>
<PluginVersion>9.2.4.16</PluginVersion>
<ReadOnly>false</ReadOnly>
</PresetHeader>
<MessageToShell/>
<PresetData Setup="CURRENT">
<Parameters Type="RealWorld">3 1 -4 0 0 1 0 2 0 -4
0 0 1 61.100000000000001 22.5 1 1 6 1
51.700000000000003 0 75.099999999999994 0 1 0 0.80000000000000004 0 2.6000000000000001
0 8 0 9 0 1 57.5 31 23.5
84.400000000000006 54.600000000000001 3.3999999999999999 268 83.200000000000003 8.0999999999999996 56.5 -5.5999999999999996 6.7999999999999998
801.70000000000005 100 7.5999999999999996 0 31.399999999999999 1 1.1000000000000001 113.8 100
34.700000000000003 31.199999999999999 -0.39999999999999991 9.1999999999999993 1 75.900000000000006 -0.29999999999999993 3.1000000000000001 7.4000000000000004
5.2999999999999998 5288.8000000000002 1 0 8 48 1 1 1
22 68 1 1 2 9 0 1 1
3 23 0 1 1 4 2 0 1
1 5 13 53 1 5 1 9 8
70.299999999999997 16 2 1 0 1 0 1 0
1 1 1 0 1 0 1 0 1
2 1 0 1 0 1 0 1 1
1 0 1 0 1 0 1 40.100000000000001 34.799999999999997
1 2 20.899999999999999 41.5 0 0 0 0.10000000000000001 -21.100000000000001
1.5 3.8999999999999999 5 0.41000000000000003 * * * * 10
0 1 1 1 1 13 0 0 0
0 * * 120 1 * * * 0
1 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 2 0
0 0 * * </Parameters>
</PresetData>
</Preset>
</PresetXMLTree>

Added the original file with my edit as an attachment. Hope this is ok as comes with the plugin (if not just ping me and Ill remove it.

[fluffy_little_something]

That's absurdly clumsy and complex.
I suppose that happens when developers are too deep into their products and can't imagine anymore how an outsider might experience their products.

Reminds me of the nerdy instructions for fixing a broken Windows Update service