No midi sound on record or play.. SORTED (ish)

(fasteddy13) #1

Hi All…

Nuvva nooby prob here… Have now got Ubuntu Studio running nicely on my PC, got Ardour up and running under qjackctl, midi instruments working well with my midi keyboard controller… But as soon as I press play or record, my midi disappears… Actually, I sometimes get the first note and then it disappears… No sound, and no midi input showing on the track monitor. As soon as I stop play or record, my midi comes back and can hear it fine…

Could this be a jack config thing? or a setting in Ardour…?

0 Likes

(fasteddy13) #2

Update…
Problem still remains… Have chewed through lots of posts re midi, but can only find different problems to mine… Have read the manual but cant find anything related to my issue, am pretty sure it will turn out to be a simple click to switch on monitoring of some sort. Have tried switching on/off various monitoring options but to no avail… Have not messed with jack yet as it remains a somewhat confusing interface to me… Am still on the steepest bit of the learning curve methinks…

0 Likes

(Insignia) #3

Do you have the latest drivers installed for your audio interface? It also sounds like a problem with JACK. The default Ardour settings usually work fine.

0 Likes

(cooltehno) #4

Did you try this button?
in_button

0 Likes

(fasteddy13) #5

Hi Insignia, I use a Scarlett 2i4 usb and it seems to be all working fine… Fresh copy of Ubuntustudio which I have fully updated… You might be right about jack, but it would be nice to get that working so I can try syncing Hydrogen and other funky tools I have not been able to use with Ardour yet… I will try Alsa later this evening though and report back…

Hey there cooltehno… That button is for audio I believe… It is the midi I am having a prob with… I have the correct input selected on the channel, as I mentioned the midi is working perfectly (5.8ms latency) and sound banks and instruments all select and play fine… It is when I hit play or record that the midi drops out… Am pretty sure it is simply a matter of activating some sort of monitoring in Ardour, or Jack… Still head scratching on this one…

0 Likes

(Insignia) #6

Perfect, just let me know what you find. I also use a 2i4, so.

0 Likes

(fasteddy13) #7

First, apologies cooltehno, you were quite right to point to that button, it is on the midi channel although I had it selected on mine so it was not my issue, my comment was misleading and you were correct to highlight it as a possible cause of the problem…

Sorted…! Started Ardour in ALSA mode and it all worked…! So am assuming now that this was a JACK problem and that I am going to have to get my head around that a bit more… I do find it a confusing interface though, my setup of it is always based on someone elses that I pull off the net, I would not understand it well enough if I had no guidance. Is it me, or do the inputs/outputs seem to be the wrong way round on JACK…? Perhaps if I viewed my screen through a mirror while standing on my head…?

0 Likes

(fasteddy13) #8

A quick update…
The problems I am having using JACK all point to my graphics card (Nvidia 1080) constantly coming up as the primary soundcard… Been seeing a lot of stuff out there on the net about this and it seems to be problem for many folk trying to use JACK…
I did read (a little while back) about ‘blacklisting’ Nvidia devices (the audio part of them) which can keep the GPU out of the audio aspect of a PC… Once I have dug it up again, and got it to work will post a link or 2 as it may help other noobs out there.
I am sure there was some rational thinking behind making the graphics cards also an audio device, but I dont get it myself, it just gets in the way. Seems many people were hoping for an Nvidia driver which allowed us to switch off the audio but it never materialized and so the blacklisting became one of the options to work around this. Will post more as I get into this a bit further…

Ok, just done my blacklisting and found the article about it here;

https://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/

0 Likes

(Chris) #9

The solution to that is specify which audio device you want jackd to use rather than relying on the default.
To find out which ALSA devices are available the easiest is to use aplay -l, that tells alsaplayer to list the devices found.
For example, on my system I have a bunch of devices from the AMD graphics card (HDMI audio output), and then a couple from the USB interface I want to use:

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Lambda [Lexicon Lambda], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

So when starting jackd I specify as the ALSA device to use -dalsa -dhw:Lambda and that makes sure the audio goes to my Lexicon interface and not to my AMD graphics card.

0 Likes