Ardour and Surge XT

Hi,

I have installed Surge XT with Ardour, but :

  1. No Surge XT choice when I create a new MIDI track (pic1.png), so, I have to choose ACE FluidSynth.

  2. I can only drag and drop Surge XT in the mixer (pic2.png) ; I put it after FluidSynth.

It seems me strange, is that please right ?

Which Ardour version? It works for me in 8.1…
Also which platform is this (mine is Linux) and how did you install the Surge XT plugin in the first place (I did using the platform package manager, apt in my case)?

Last, but not least - are you sure you want more than one instrument plugins (Ace Fluid Synth and Surge XT) on one track?

Why not pick “none” (aucun)?

You can remove ACE Fluidsynth.

There was an issue a few years ago that SurgeXT was not correctly tagged as synth. I do not recall if this was an issue with Surge or Ardour.

It works for me as well (macOS and Linux).
@x42 the current surgeXT deliverable installs both, the instrument AND an effect.
But the thought makes sense. If these are remnants of an old bug, maybe removing all traces of surge XT, Cache deletion and rescan might solve this?

Hi,

Here is my Ardour version :

Ardour 6.5.0~ds0
“Old Land”
(rev 6.5.0~ds0-1)
Intel 64 bits

My os : debian 11.8

  • I installed Ardour through debian standard repository (apt install ardour), and

  • I installed Surge XT by downloading surge-xt-linux-x64-1.2.3.deb from https://surge-synthesizer.github.io/downloads (https://github.com/surge-synthesizer/releases-xt/releases/download/1.2.3/surge-xt-linux-x64-1.2.3.deb) ; and then :

    apt install ./surge-xt-linux-x64-1.2.3.deb

It looks me strange having more than one instrument in a track, I thing that something is wrong.

Hi,

I have no sound if I pick “none” or remove FluidSynth.

As @GenGen suggests, please try removing the plugin, rescanning, then installing back and rescanning plugins again.

Also, if you can, install the latest Ardour (8.1) - if there is any problem with plugin support in v6, you are not going to get it fixed on that version.

Yea… this needs to be updated honestly. Try the demo version from this website and report back if the problem persists.

His point was to pick "None’ in the dialog there, and then add the SurgeXT plugin to the track manually.

  Seablade

I see.

Since the plugin is not identified as Instrument it does not override “strict I/O” and hence cannot add audio-ports to the signal flow.

So in the new track dialog also disable that under “Connexion” (or in the context menu of the mixer-strip).

But really just update Ardour, 6.5 is ancient.

With 8.1. Surge XT works fine. Just make sure you use the VST3 version, the LV2 version has issues storing its state and reverts to the init state when you reopen a session that uses the LV2 version (as far as I can see due to the JUCE version used, not LV2 itself).

Another idea what might be going on.
Try choosing Surge directly in the add midi track menu.
When you add surge on a track where fluid synth is already inserted, the pin connections might be wrong. I am not infront of a computer to verify rn, so just an idea. The Ardour drop-down menus are a little confusing as most of them have no search or type to jump.

Thank you all.

I upgraded my debian os, so my new Ardour version is :

Ardour 7.3.0~ds0
“Nerve Net”
(rev 7.3.0~ds0-1)
Intel 64 bits

I uninstalled Surge, rescanned, reinstalled Surge, resanned again and now all is OK : I have Surge like only instrument in a midi track.

:slight_smile:

1 Like

Note that that is still old as Ardour is on v8 now. You can install from the website, and probably should, but at least that gets you more modern significantly and many bugfixes since that other version. Just keep in mind there will be that much more work between what you are running now and the current. So if you run across bugs, the first step is always going to be to check with a version from this website, even the free demo version and see if it persists there.

 Seablade
1 Like

As I have said before, I am using Debian 12 with package for Ardour 7.3. I prefer the major release stability of Debian Linux to a rolling distribution of Linux because there is always something not working on a rolling release and I am not a Linux system administrator. I have to wonder if Ardour 8.x on Debian 12 might not work because of dependencies on new libraries not part of Debian 12 and possibly not compatible with Debian 12. I don’t know anything specific about Ardour’s dependencies, but I do know that I avoid problems by using Debian stable.

The versions of ardour that we provide via Download Ardour | Ardour Community have no system dependencies except a C++ standard library and Xlib. They do not care what distro or version of a distro you are using (more or less).

1 Like

Debian 12 user here. Ardour 8.1 flies on my bookworm.

Good to know about the high portability of Ardour on Linux.