How to get Ardour to work with my rig?

What other apps and distros do you use to round out your studio?

Moderators: MattKingUSA, khz

arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

I changed the asoundrc to HW:1 and HW:4.

I also did have capture set on in alsamixer.

Still no joy.

I really wonder if that loopback device is supposed to be in my hardware list, I'd swear before I had problems it wasn't in there.
merlyn
Established Member
Posts: 1392
Joined: Thu Oct 11, 2018 4:13 pm
Has thanked: 168 times
Been thanked: 247 times

Re: How to get Ardour to work with my rig?

Post by merlyn »

arpegadream wrote:Also Ardour stopped asking in startup what back end I want to use, how do I turn it on in the configurations so it shows at startup of Ardour?
Ideally you would do this the very first time you started Ardour, then Ardour would remember your settings and you wouldn't have to do it again.

But you can access that dialogue at any time through Window > Audio/MIDI Setup
arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

Ok, did that, excellent tip! When not using Jack the recording and audio work fine through alsa and I THINK I know I have it wired physically right and I know the 204HD works fine in Linux Mint. What's left is getting it to work with Jack so I can play to music on my computer and record to it, since alsa doesn't allow that. I really need to have jack work.
arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

Ok, here is my guess:

If I KNOW I am hard wired correctly

and

If I KNOW the 204HD works with Linux and Jack

and

If I can get Ardour to work and record my guitar playing when using alsa and not jack...

Could my problem with jack be a configuration issue? Where are the configuration files and what should I check for? I did a fresh install of jack but I didn't know where to remove configuration files when I removed jack before reinstall.

I do believe I am wiring using patchage correctly, and I've tried many different combinations, I don't think that is the problem. It seems something in the configuration of jack or the version of jack is the problem.

That is my guess.
arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

Here is my ~.asoundrc file contents (is that the configuraiton file or are there others?):

Code: Select all

ctl.mixer0 {
    type hw
    card 0
}

#The Following was added:

pcm.merge {
    type multi;
    slaves.a.pcm hw:0
    slaves.a.channels 2;
    slaves.b.pcm hw:3
    slaves.b.channels 2;
    bindings.0.slave a;
    bindings.0.channel 0;
    bindings.1.slave b;
    bindings.1.channel 0;
    bindings.2.slave a;
    bindings.2.channel 1;
    bindings.3.slave b;
    bindings.3.channel 1;
}


(END)
arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

And here is my cards list:

Code: Select all

wutsinterweb@wutsinterweb1 ~ $ pacmd list-cards
3 card(s) available.
    index: 0
	name: <alsa_card.pci-0000_01_00.1>
	driver: <module-alsa-card.c>
	owner module: 7
	properties:
		alsa.card = "2"
		alsa.card_name = "HDA ATI HDMI"
		alsa.long_card_name = "HDA ATI HDMI at 0xdfe40000 irq 41"
		alsa.driver_name = "snd_hda_intel"
		device.bus_path = "pci-0000:01:00.1"
		sysfs.path = "/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2"
		device.bus = "pci"
		device.vendor.id = "1002"
		device.vendor.name = "Advanced Micro Devices, Inc. [AMD/ATI]"
		device.product.id = "aa58"
		device.product.name = "Juniper HDMI Audio [Radeon HD 5700 Series]"
		device.string = "2"
		device.description = "Juniper HDMI Audio [Radeon HD 5700 Series]"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card-pci"
	profiles:
		output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5400, available: unknown)
		off: Off (priority 0, available: unknown)
	active profile: <output:hdmi-stereo>
	sinks:
		alsa_output.pci-0000_01_00.1.hdmi-stereo/#0: Juniper HDMI Audio [Radeon HD 5700 Series] Digital Stereo (HDMI)
	sources:
		alsa_output.pci-0000_01_00.1.hdmi-stereo.monitor/#0: Monitor of Juniper HDMI Audio [Radeon HD 5700 Series] Digital Stereo (HDMI)
	ports:
		hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: yes)
			properties:
				device.icon_name = "video-display"
    index: 1
	name: <alsa_card.usb-BEHRINGER_UMC204HD_192k-00>
	driver: <module-alsa-card.c>
	owner module: 8
	properties:
		alsa.card = "3"
		alsa.card_name = "UMC204HD 192k"
		alsa.long_card_name = "BEHRINGER UMC204HD 192k at usb-0000:00:14.0-9, high speed"
		alsa.driver_name = "snd_usb_audio"
		device.bus_path = "pci-0000:00:14.0-usb-0:9:1.0"
		sysfs.path = "/devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/sound/card3"
		udev.id = "usb-BEHRINGER_UMC204HD_192k-00"
		device.bus = "usb"
		device.vendor.id = "1397"
		device.vendor.name = "BEHRINGER International GmbH"
		device.product.id = "0508"
		device.product.name = "UMC204HD 192k"
		device.serial = "BEHRINGER_UMC204HD_192k"
		device.string = "3"
		device.description = "UMC204HD 192k"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card-usb"
	profiles:
		input:analog-stereo: Analog Stereo Input (priority 60, available: unknown)
		input:iec958-stereo: Digital Stereo (IEC958) Input (priority 55, available: unknown)
		output:analog-surround-40: Analog Surround 4.0 Output (priority 700, available: unknown)
		output:analog-surround-40+input:analog-stereo: Analog Surround 4.0 Output + Analog Stereo Input (priority 760, available: unknown)
		output:analog-surround-40+input:iec958-stereo: Analog Surround 4.0 Output + Digital Stereo (IEC958) Input (priority 755, available: unknown)
		off: Off (priority 0, available: unknown)
	active profile: <output:analog-surround-40+input:analog-stereo>
	sinks:
		alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40/#1: UMC204HD 192k Analog Surround 4.0
	sources:
		alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40.monitor/#1: Monitor of UMC204HD 192k Analog Surround 4.0
		alsa_input.usb-BEHRINGER_UMC204HD_192k-00.analog-stereo/#2: UMC204HD 192k Analog Stereo
	ports:
		analog-input-mic: Microphone (priority 8700, latency offset 0 usec, available: unknown)
			properties:
				device.icon_name = "audio-input-microphone"
		iec958-stereo-input: Digital Input (S/PDIF) (priority 0, latency offset 0 usec, available: unknown)
			properties:
				
		analog-output: Analog Output (priority 9900, latency offset 0 usec, available: unknown)
			properties:
				
    index: 2
	name: <alsa_card.platform-snd_aloop.0>
	driver: <module-alsa-card.c>
	owner module: 9
	properties:
		alsa.card = "1"
		alsa.card_name = "Loopback"
		alsa.long_card_name = "Loopback 1"
		alsa.driver_name = "snd_aloop"
		device.bus_path = "platform-snd_aloop.0"
		sysfs.path = "/devices/platform/snd_aloop.0/sound/card1"
		device.form_factor = "internal"
		device.string = "1"
		device.description = "Built-in Audio"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card"
	profiles:
		input:analog-mono: Analog Mono Input (priority 2, available: unknown)
		input:analog-stereo: Analog Stereo Input (priority 60, available: unknown)
		output:analog-mono: Analog Mono Output (priority 200, available: unknown)
		output:analog-mono+input:analog-mono: Analog Mono Duplex (priority 202, available: unknown)
		output:analog-mono+input:analog-stereo: Analog Mono Output + Analog Stereo Input (priority 260, available: unknown)
		output:analog-stereo: Analog Stereo Output (priority 6000, available: unknown)
		output:analog-stereo+input:analog-mono: Analog Stereo Output + Analog Mono Input (priority 6002, available: unknown)
		output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060, available: unknown)
		output:analog-surround-21: Analog Surround 2.1 Output (priority 800, available: unknown)
		output:analog-surround-21+input:analog-mono: Analog Surround 2.1 Output + Analog Mono Input (priority 802, available: unknown)
		output:analog-surround-21+input:analog-stereo: Analog Surround 2.1 Output + Analog Stereo Input (priority 860, available: unknown)
		output:analog-surround-40: Analog Surround 4.0 Output (priority 700, available: unknown)
		output:analog-surround-40+input:analog-mono: Analog Surround 4.0 Output + Analog Mono Input (priority 702, available: unknown)
		output:analog-surround-40+input:analog-stereo: Analog Surround 4.0 Output + Analog Stereo Input (priority 760, available: unknown)
		output:analog-surround-41: Analog Surround 4.1 Output (priority 800, available: unknown)
		output:analog-surround-41+input:analog-mono: Analog Surround 4.1 Output + Analog Mono Input (priority 802, available: unknown)
		output:analog-surround-41+input:analog-stereo: Analog Surround 4.1 Output + Analog Stereo Input (priority 860, available: unknown)
		output:analog-surround-50: Analog Surround 5.0 Output (priority 700, available: unknown)
		output:analog-surround-50+input:analog-mono: Analog Surround 5.0 Output + Analog Mono Input (priority 702, available: unknown)
		output:analog-surround-50+input:analog-stereo: Analog Surround 5.0 Output + Analog Stereo Input (priority 760, available: unknown)
		output:analog-surround-51: Analog Surround 5.1 Output (priority 800, available: unknown)
		output:analog-surround-51+input:analog-mono: Analog Surround 5.1 Output + Analog Mono Input (priority 802, available: unknown)
		output:analog-surround-51+input:analog-stereo: Analog Surround 5.1 Output + Analog Stereo Input (priority 860, available: unknown)
		output:analog-surround-71: Analog Surround 7.1 Output (priority 700, available: unknown)
		output:analog-surround-71+input:analog-mono: Analog Surround 7.1 Output + Analog Mono Input (priority 702, available: unknown)
		output:analog-surround-71+input:analog-stereo: Analog Surround 7.1 Output + Analog Stereo Input (priority 760, available: unknown)
		off: Off (priority 0, available: unknown)
	active profile: <output:analog-stereo+input:analog-stereo>
	sinks:
		alsa_output.platform-snd_aloop.0.analog-stereo/#2: Built-in Audio Analog Stereo
	sources:
		alsa_output.platform-snd_aloop.0.analog-stereo.monitor/#3: Monitor of Built-in Audio Analog Stereo
		alsa_input.platform-snd_aloop.0.analog-stereo/#4: Built-in Audio Analog Stereo
	ports:
		analog-input: Analog Input (priority 10000, latency offset 0 usec, available: unknown)
			properties:
				
		analog-output: Analog Output (priority 9900, latency offset 0 usec, available: unknown)
			properties:
				
wutsinterweb@wutsinterweb1 ~ $ 
arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

Please notice in that second part, the list, that my motherboard sound card is not listed. Why is that and could that be my problem?
merlyn
Established Member
Posts: 1392
Joined: Thu Oct 11, 2018 4:13 pm
Has thanked: 168 times
Been thanked: 247 times

Re: How to get Ardour to work with my rig?

Post by merlyn »

Are you using QjackCtl to start and configure JACK?

Have you heard any sound e.g. from a browser or media player?

Can you hear the metronome in Ardour?
arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

I was using patchage, I have qjackctl but am not familiar with how to use it, need guidance if it is needed.

While attempting recording with metronome with jack enabled, no sound.

Yes, audio, such as spotify, play when using jack enabled, but, not, of course, when using alsa alone.
arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

[img]
Screenshot from 2020-01-28 16-17-18a.png
Screenshot from 2020-01-28 16-17-18a.png (194.42 KiB) Viewed 1404 times
[/img]
arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

Also, with Jack enabled in Ardour, master does not appear, only audio 1 and audio 2 at least by default.
arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

Code: Select all

39:29.962 Statistics reset.
16:39:29.970 ALSA connection change.
16:39:29.973 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
16:39:30.051 D-BUS: JACK server could not be started. Sorry
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Tue Jan 28 16:39:29 2020: Starting jack server...
Tue Jan 28 16:39:29 2020: JACK server starting in realtime mode with priority 10
Tue Jan 28 16:39:29 2020: self-connect-mode is "Don't restrict self connect requests"
Tue Jan 28 16:39:30 2020: Acquired audio card Audio0
Tue Jan 28 16:39:30 2020: creating alsa driver ... hw:0|hw:0|1024|3|44100|0|0|nomon|swmeter|-|32bit
Tue Jan 28 16:39:30 2020: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 3 periods
Tue Jan 28 16:39:30 2020: ALSA: final selected sample format for capture: 32bit integer little-endian
Tue Jan 28 16:39:30 2020: ALSA: use 3 periods for capture
Tue Jan 28 16:39:30 2020: ALSA: final selected sample format for playback: 32bit integer little-endian
Tue Jan 28 16:39:30 2020: ERROR: ALSA: got smaller periods 2 than 3 for playback
Tue Jan 28 16:39:30 2020: ERROR: ALSA: cannot configure playback channel
Tue Jan 28 16:39:30 2020: Released audio card Audio0
Tue Jan 28 16:39:30 2020: ERROR: Cannot initialize driver
Tue Jan 28 16:39:30 2020: ERROR: JackServer::Open failed with -1
Tue Jan 28 16:39:30 2020: ERROR: Failed to open server
Tue Jan 28 16:39:31 2020: Saving settings to "/home/wutsinterweb/.config/jack/conf.xml" ...
16:39:32.262 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
16:39:56.092 ALSA connection graph change.
16:40:01.742 D-BUS: JACK server could not be started. Sorry
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Tue Jan 28 16:40:01 2020: Starting jack server...
Tue Jan 28 16:40:01 2020: JACK server starting in realtime mode with priority 10
Tue Jan 28 16:40:01 2020: self-connect-mode is "Don't restrict self connect requests"
Tue Jan 28 16:40:01 2020: Acquired audio card Audio0
Tue Jan 28 16:40:01 2020: creating alsa driver ... hw:0|hw:0|1024|3|44100|0|0|nomon|swmeter|-|32bit
Tue Jan 28 16:40:01 2020: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 3 periods
Tue Jan 28 16:40:01 2020: ALSA: final selected sample format for capture: 32bit integer little-endian
Tue Jan 28 16:40:01 2020: ALSA: use 3 periods for capture
Tue Jan 28 16:40:01 2020: ALSA: final selected sample format for playback: 32bit integer little-endian
Tue Jan 28 16:40:01 2020: ERROR: ALSA: got smaller periods 2 than 3 for playback
Tue Jan 28 16:40:01 2020: ERROR: ALSA: cannot configure playback channel
Tue Jan 28 16:40:01 2020: Released audio card Audio0
Tue Jan 28 16:40:01 2020: ERROR: Cannot initialize driver
Tue Jan 28 16:40:01 2020: ERROR: JackServer::Open failed with -1
Tue Jan 28 16:40:01 2020: ERROR: Failed to open server
16:40:03.767 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Tue Jan 28 16:40:03 2020: Saving settings to "/home/wutsinterweb/.config/jack/conf.xml" ...
This happened after trying to start qjackctl after closing it.
arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

Never mind that most recent post, I had changed a setting in qackctl from 2 buffer/period to 3 cause I read it was necessary somewhere. Set it back and jack started. But audio still not working in ardour when using jack.
merlyn
Established Member
Posts: 1392
Joined: Thu Oct 11, 2018 4:13 pm
Has thanked: 168 times
Been thanked: 247 times

Re: How to get Ardour to work with my rig?

Post by merlyn »

In the earlier screenshot you posted I can see the Ardour master bus. No master bus isn't a lot of use. Could it be the template you're using? You could try deleting .config/ardour5 again and see if the master bus comes back.
arpegadream
Established Member
Posts: 101
Joined: Wed Jul 24, 2019 9:34 pm

Re: How to get Ardour to work with my rig?

Post by arpegadream »

Yes, that fixes the missing master control, but jack still won't produce audio or recording when started with ardour.
Post Reply