View Issue Details

IDProjectCategoryView StatusLast Update
0003602ardourbugspublic2020-04-19 20:14
Reporterdanboid Assigned Tocth103  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Target Version3.0-beta1 
Summary0003602: presets not saved or restored for Crystal VST
DescriptionSave and restore of presets seems to basically work for most VSTs I've tried so far under 8257/squeeze 32 but not with the Crystal softsynth:

http://www.greenoak.com/crystal/

It would be a real shame if this can't be made to work because otherwise crystal works great under A3 and its one of the very best and most respected free plugins available hence I think it'd be one of the first many will want to try.
TagsNo tags attached.

Activities

cth103

2010-12-15 02:59

administrator   ~0009635

Should be fixed in SVN.

danboid

2010-12-15 15:55

reporter   ~0009636

Sorry, problem persists under 8284

cth103

2010-12-15 16:39

administrator   ~0009638

Something odd is going on then, I think. Can you give me a step-by-step list of what you are doing (from adding Crystal to a track onwards) and what you expect to happen?

danboid

2010-12-15 19:30

reporter   ~0009639

rm -rf ~/.config/ardour3
execute ardevst and create new session
add a MIDI track with region and a note or two
add Crystal to track processor box/ mixer strip
open plugin gui
choose a preset from the drop-down to the left of the Add button
(optionally play to check plugin/preset is OK)
save session
quit A3
execute ardesvst
load previously created session
session loads fine except for the chosen preset for Crystal plugin - it loads in its default state just as before choosing any preset.

I expected my chosen presets settings to be restored as seems to work fine for most other VSTis I've tried.

8284 under squeeze

danboid

2010-12-26 13:48

reporter   ~0009707

Last edited: 2010-12-26 13:49

Whilst this bug does still apply to 8340, its not really an issue as Crystal does support PC so to get A3 to remember your presets you just have to specify them via PC instead of via the VST plugin GUI.

Note that when I was using wine 1.2.x, crystal would crash and take A3 with it when I tried sending it a PC but alls well in this respect under wine 1.3.2- PC change works just fine. What is strange though is that with the older wine the presets were listed by their name instead of preset number in the A3 VST GUI. This has worked out really well though as the preset numbers listed are only one out from how A3 refers to them via PC number so switching between presets is pretty painless.

I'm having great fun playing with this fantastic synth- can't believe its free! They've ported it to iOS now - wonder if they'd be interested in doing an LV2 port? ;)

Think you're safe to resolve this now.

danboid

2010-12-28 00:47

reporter   ~0009709

I have now also tried this with wine 1.3.10 (latest to date) and 8343 under Deb Squeeze only to have the same problem.

I have informed the plugin developer of this problem. If it is upstreams fault and he can't easily get save and restore of presets to work under the VST (if he does actually try it this way) then maybe we won't have to suffer for too long as he is looking into the possibility of an LV2 port.

danboid

2010-12-28 11:36

reporter   ~0009710

Might be an idea to remove the 'Crystal' from the subject of this bug report as it does in fact seem to be a problem common to all VSTis that I've tried today under 8343 w/ same setup as mentioned in my last note.

Other vsti's I have seen not have their chosen presets restored after re-loading a session include the TAL Elek7ro:

http://kunz.corrupt.ch/?Products:VST_TAL-Elek7ro

and basic64:

http://www.delamancha.co.uk/basic.htm

Also probably worth noting is that when I start ardevst I get 100's of:

librdf warning - Model does not support contexts

errors pumped to stdout- librdf has summat to do with the plugins doesn't it?

danboid

2010-12-28 23:18

reporter   ~0009722

Last edited: 2010-12-28 23:20

This bug is still present in 8354 so heres the slightly revised recipe:

execute ardevst and create new session
add a MIDI track with region and a note or two
add Crystal to track processor box/ mixer strip
open plugin gui
choose a preset from the drop-down to the left of the Add button- lets say 'Preset 103
(optionally play track to check plugin/preset is OK)
save session
quit A3
execute ardesvst
load previously created session
session loads fine and the preset name for the plugin 'Preset 103' is displayed correctly but you can verify by either playing the track or just looking at the visual representation of the preset that Preset 103 hasn't actually been loaded altough you can now re-select it yourself to get it working.

I say crystal although it seems you could do this with any vsti and have the same results- its the case on the few I've tried today.

cth103

2010-12-29 01:18

administrator   ~0009724

May be fixed in SVN.

danboid

2010-12-29 08:22

reporter   ~0009726

8357 is certainly working better now with restoring VSTi presets but it atm it only works correctly if you save your session with the window for each VSTi used open. If you save your session with any plugin windows closed, when you come to loading that session you have to open the plugin window once for each VSTi used that isn't already open in order to get the correct preset to load.

cth103

2010-12-30 00:54

administrator   ~0009744

The situation may be improved under SVN, but I'm finding it difficult to be sure.

danboid

2010-12-30 16:46

reporter   ~0009748

Last edited: 2010-12-30 17:10

No better under 8382 unfortunately- tried with both Crystal and TAL-Elek7ro. The only vsti I've tried that doesn't suffer from this problem is the sfz soundfont player:

http://www.cakewalk.com/support/project5/sfz.aspx

With sfz, and prob others like it that share the following property, I can save my session with the sfz plugin window closed, shut a3 then reload the session and have the plugin playback with the correct settings without having to open the plugin window first. This is because at no stage in using sfz do I ever need to use the patch/preset selector drop-down thats part of the A3 VST plugin GUI which is what I use to select my patches under other vstis like the two synths mentioned previously.

danboid

2010-12-30 21:46

reporter   ~0009753

Surely you'll be delighted to hear there's another problem with VST presets- its very closely related to this so I think this belongs in the same thread.

The problematic behaviour described above (ie havingto save with window open) only applies to in-built plugin patches- custom ones are even more problematic. With custom created patches (ie those added via the A3 VST GUI 'Add' button) it doesn't matter if the plugin window is open or closed when you save your session as when you re-open the session the plugin preset will only be restored in as much as you see its name in the box but the preset doesn't actually get loaded. For all such patches you must select a different one then re-select the intended, custom preset to get it to function properly again after session load.

As an aside, I'm a bit confused as to why the sfz plugin should retain its setting perfectly but if you choose a patch within crystals gui instead of doing it with the A3 GUI it doesn't save/restore it? I'm not so bothered about that not working so long as I can use the A3 one fine but I do wonder why it is - maybe sfz is more compliant to VSTi spec or its using an older version of the spec? Wine oddity?

danboid

2011-03-05 13:45

reporter   ~0010289

Last edited: 2011-03-05 13:46

Carl - I'm sure you'll be delighted to hear that we can finally resolve this one as the restoring of VSTi presets seems to be working well as of late and thats whether you save your session with the plugin window open or not and that goes for the Crystal synth too!

What I've NOT been testing or depending upon recently is the A3 plugin preset manager- instead I do all the loading, saving and managing of presets using the features provided within the VSTi, which would seem to be the most sensible thing to do in most cases anyway as you'll be using the native preset file format then too.

system

2020-04-19 20:14

developer   ~0022299

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2010-12-13 23:11 danboid New Issue
2010-12-15 02:59 cth103 cost => 0.00
2010-12-15 02:59 cth103 Note Added: 0009635
2010-12-15 02:59 cth103 Status new => resolved
2010-12-15 02:59 cth103 Resolution open => fixed
2010-12-15 02:59 cth103 Assigned To => cth103
2010-12-15 15:55 danboid Note Added: 0009636
2010-12-15 16:39 cth103 Note Added: 0009638
2010-12-15 16:39 cth103 Status resolved => feedback
2010-12-15 16:39 cth103 Resolution fixed => reopened
2010-12-15 19:30 danboid Note Added: 0009639
2010-12-16 21:27 cth103 Target Version => 3.0-beta1
2010-12-26 13:48 danboid Note Added: 0009707
2010-12-26 13:49 danboid Note Edited: 0009707
2010-12-28 00:47 danboid Note Added: 0009709
2010-12-28 11:36 danboid Note Added: 0009710
2010-12-28 23:18 danboid Note Added: 0009722
2010-12-28 23:19 danboid Note Edited: 0009722
2010-12-28 23:20 danboid Note Edited: 0009722
2010-12-29 01:18 cth103 Note Added: 0009724
2010-12-29 08:22 danboid Note Added: 0009726
2010-12-30 00:54 cth103 Note Added: 0009744
2010-12-30 16:46 danboid Note Added: 0009748
2010-12-30 16:48 danboid Note Edited: 0009748
2010-12-30 16:49 danboid Note Edited: 0009748
2010-12-30 17:10 danboid Note Edited: 0009748
2010-12-30 21:46 danboid Note Added: 0009753
2011-03-05 13:45 danboid Note Added: 0010289
2011-03-05 13:46 danboid Note Edited: 0010289
2011-10-24 21:41 cth103 Status feedback => resolved
2011-10-24 21:41 cth103 Resolution reopened => fixed
2020-04-19 20:14 system Note Added: 0022299
2020-04-19 20:14 system Status resolved => closed