Garbled guitar signal in Ardour with JACK

Installation & Configuration Linux
#1

Hi, I recently bought an Audio Interface because I want to get into recording after playing guitar for 30 plus years. I got a Focusrite Scarlett 2i2 4th gen and I am using it under Arch Linux with Ardour 8.12 from the Arch repos. As the title says when I connect my guitar to the interface and open up Ardour, the guitar signal sounds completely garbled after I set the input to the Focusrite. I can “fix” the issue by changing the buffer size 1024 to anything else. Then my signal is clean all of a sudden and setting it back to 1024 is also clean. Any suggestions to what could be causing this initial distorted signal?

My second question is in regards to the neural plugin modeller plugin and its gui under Linux. I can lod the plugin with no issues and choose a .nam profile. My question is: there no way with gui to load an IR, so can anyone point me tro and IR loader plugin that works under Linux? Thankls again!!

#2

You need to deactivate MSD Mode on Scarlett 2i2 3/4 gen.
https://linuxmusicians.com/viewtopic.php?t=20669

#3

I have already done that…

#4

I have no issues with my scarlett 2i2 3rd gen and Ardour. Using CachyOS (Arch).
What backend? I’m using pipewire/jack. But also works with Alsa.

#5

Backend is jack/pipewire as well. ALSA for me doesn’t work at all.

#6

Please say more about this, and also mention the version of Pipewire.

#7

When I switch to ALSA I have no output at all. There is no error message or similar. Pipewire version is 1.4.9.

#8

When you switch to ALSA, do you pick the Scarlett device for output?

#9

No, I pick my wireless USB headphones. I set the Scarlett device as the input.

#10

“wireless USB headphones” seems impossible … USB Is a cable protocol … do you mean bluetooth?

#11

It is more specifically a Logitech G733 wireless headset that connect to my PC via a wireless receiver.

#12

Oh yeah, one of those. It shows up as a possible device with ALSA but doesn’t actually work ?

Ardour is really not designed to be used with this type of hardware. Audio production tends to require/work better with the right gear, and this is not that. It is likely responsible for at least some of your issues even when using Pipewire …

#13

No, ALSA says it is running but there is no sound. Switching back to JACK resolves the garbled sound from the guitar signal.

#14

Even if you get this to work, you will likely have too much latency , because of the Bluetooth, to monitor live input with.

#15

So wired headphones connected to the interface would be the best way to monitor the input? My second question regarding an IR loader any advice would be appreciated?

#16

Yes.

LSP plugins work well and have a mono or stereo version. Just be sure to turn down the DRY signal when using these for Speaker IR’s

https://lsp-plug.in/?page=manuals&section=impulse_responses_stereo

#17

Thanks for the link and suggestion. I am planning to buy wired headphones for the monitoring part of recording in the future. Right now I am just trying to figure out how to use Ardour and getting a decent guitar sound.

#18

Why would it be necessary to the DRY signal when using them for Speaker IR’s?

#19

On the LSP plugin for the IR, the default DRY setting allows the unaffected signal through, as well as the IR modified signal. You will get the harsh raspy tone from the Neural Amp mixed with the IR signal. I assume you are wanting to emulate a speaker cabinet for Neural ? So, when using the LSP Impulse Response for Guitar Cabinet IR’s, turn down the dry to zero to simulate an amp signal through the IR. It will sound like crap if you do not!

Also, you may already know, some Neural amps have the IR built in, so no need for the IR loader.

#20

OK, thanks for the clarification. I’ve seen on Tone3000 a few NAM files that are amp head only captures, hence the question regarding an IR loader. The ones I’ve tried so far have been full combo captures.