Ubuntu
ubuntustudio-controls package

a2jmidid checkbox do not work correctly

Bug #1884472 reported by Anagram3K on 2020-06-22

6

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ubuntustudio-controls (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Because the default setting for the jack midi driver is "raw", the a2jmidid can't connect to the jack midi hardware ports.

After changing the midi driver in ~/.config/jack/conf.xml to seq or none and restarting jack the ports are exported correctly

After clicking the a2jmidid checkbox, the program should check if the jack midi is raw and change it to seq or none.

System info:
Ubuntu Studio 20.04 LTS
ubuntustudio-controls 1.12.6~20.04.1

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntustudio-controls 1.12.6~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
Uname: Linux 5.4.0-37-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sun Jun 21 23:28:55 2020
InstallationDate: Installed on 2020-01-18 (155 days ago)
InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: ubuntustudio-controls
UpgradeStatus: Upgraded to focal on 2020-04-24 (58 days ago)

Tags:

Revision history for this message

Anagram3K (anagram3k) wrote on 2020-06-22:

#1

Dependencies.txt Edit (9.6 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (346 bytes, text/plain; charset="utf-8")

Revision history for this message

Erich Eickmeyer (eeickmeyer) wrote on 2020-06-22:

#2

I have no issues connecting my MIDI hardware to any software and therefore cannot reproduce.

Please note that development of this application is not done specifically for Ubuntu anymore and has become an upstream project as Studio Controls (https://github.com/ovenwerks/studio-controls). Because we cannot backport studio-controls into the Ubuntu repositories for Ubuntu 20.04, this is likely a bug, if it even is a bug (bugs are reproducible on all hardware), that is not going to get fixed until there is a new release of Studio Controls which would be backported into the Ubuntu Studio Backports PPA.

In your case, it is likely you ran qjackctl at some point (NOT recommended) before running (Ubuntu) Studio Conrols.

Revision history for this message

Len Ovens (len-ovenwerks) wrote on 2020-06-22:

#3

The default setting for jackdbus for midi is none, not raw. However running any other jackdbus startup utility in the past will create ~/.config/jack/conf.xml. An upgrade from to 19.10 to 20.04 will not reset that file as it is not an installed file.

That said, because controls sets all controls it needs to every time it starts and starting jackdbus rewrites that file, future versions of studio-controls will remove that file before starting to avoid mis-settings made by other utilities.

Revision history for this message

Erich Eickmeyer (eeickmeyer) wrote on 2020-06-22:

#4

Based on Len's response, this is not a bug, but more of a misconfiguration that may be mitigated by a future feature, and a support request. Marking as invalid as support requests are not appropriate on a bug tracker.

Changed in ubuntustudio-controls (Ubuntu):
status:	New → Invalid

Revision history for this message

Anagram3K (anagram3k) wrote on 2020-06-22:

#5

Thanks!

But just to help anyone finding this later, removing ~/.config/jack/conf.xml resolves the issue.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.