View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008523 | ardour | bugs | public | 2020-12-26 14:03 | 2020-12-27 21:57 |
| Reporter | magnetophon | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | Linux | OS | NixOS | OS Version | unstable |
| Product Version | 6.5 | ||||
| Summary | 0008523: Ardour does not load Surge VST3 sounds correctly. | ||||
| Description | When I create an ardour session using surge nightly, it does not recall the patch properly. I spoke to the surge devs; they think that perhaps (perhaps) the fact that they use VST3 IDs which are not the same as positional IDs is the problem. And wonder if you are taking the port stuff that you store and applying it after the chunk incorrectly. I attached a small session to demonstrate. | ||||
| Steps To Reproduce | 1. Load the attached session 2. Hear a saw wave, expected to hear a deep bass. 3. Recall the attached surge preset from within surge 4. Hear a deep bass. | ||||
| Tags | No tags attached. | ||||
|
|
|
|
|
Ah, forgot to mention: on request by the surge devs, I tried the same thing using Reaper, and it works fine. |
|
|
Is this still an issue with Ardour/git (6.5.66)? There have been various VST3 fixes since 6.5.0 that also fixed identical issues with other plugins. Then again, Ardour 6 does not support loading VST2 FXP (effect programs), nor VST2 FXB (banks) for VST3 plugins. Those are optional. So far Ardour only support VST3's .vstpreset files for VST3 plugins. |
|
|
Heya the FXP thing is a bit of a red herring. Surge stores its patches on disk for itself that way but it streams everything it needs into the vst3 chunk so if you use Reaper or whatever and make a VST track preset it contains a uunencoded blob (which happens to be fxp format of an xml file with wavetables). I think this really is just params being re-applied out of order so if you've fixed it with others I bet it would fix surge too (although I don't have a running ardour-from-git so I can't test myself). Thanks! |
|
|
I Just compiled commit 9ba8166ae8c0a8974496ebda0689ca384a18bbbf and it still has the issue. |
|
|
@magnetophon I fixed a surge bug this morning which was causing an out of order param load in bitwig - are you at head of surge? This one may be mine |
|
|
Yup, all good now. Thanks guys! |
|
|
Cool thanks @magnetophon and sorry for the noise @x42 |
|
|
Surge side problem sorry! |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-12-26 14:03 | magnetophon | New Issue | |
| 2020-12-26 14:03 | magnetophon | File Added: bugreport.ardour | |
| 2020-12-26 14:03 | magnetophon | File Added: instant.xml | |
| 2020-12-26 14:03 | magnetophon | File Added: bugreport.ardour.bak | |
| 2020-12-26 14:03 | magnetophon | File Added: bugreport.pending | |
| 2020-12-26 14:03 | magnetophon | File Added: bugreport.history | |
| 2020-12-26 14:03 | magnetophon | File Added: bugreport.history.bak | |
| 2020-12-26 14:03 | magnetophon | File Added: Surge-2.mid | |
| 2020-12-26 14:03 | magnetophon | File Added: FiltaWreckaBassDark.fxp | |
| 2020-12-26 14:05 | magnetophon | Note Added: 0025355 | |
| 2020-12-26 15:56 | x42 | Note Added: 0025356 | |
| 2020-12-26 15:56 | x42 | Note Edited: 0025356 | |
| 2020-12-27 02:47 | baconpaul | Note Added: 0025357 | |
| 2020-12-27 20:32 | magnetophon | Note Added: 0025360 | |
| 2020-12-27 20:47 | baconpaul | Note Added: 0025361 | |
| 2020-12-27 21:33 | magnetophon | Note Added: 0025362 | |
| 2020-12-27 21:57 | baconpaul | Note Added: 0025363 | |
| 2020-12-27 21:57 | baconpaul | Status | new => closed |
| 2020-12-27 21:57 | baconpaul | Resolution | open => fixed |
| 2020-12-27 21:57 | baconpaul | Note Added: 0025364 |
