Midi device names are not unique

Bug #309318 reported by Sean M. Pappalardo
2
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Undecided
Albert Santoni
1.8
Invalid
Undecided
Unassigned

Bug Description

When connecting multiple MIDI devices of the same type (on different MIDI channels) they both are given the same device name in the MIDI Device Selection preferences pane: the reported device name, the text "MIDI", and the number 1. E.g. "SCS.3d MIDI 1"

It would be nice if they instead showed up as <reported device name> (Channel <#>).

Tags: midi
description: updated
Revision history for this message
Albert Santoni (gamegod) wrote : Re: [Bug 309318] [NEW] Midi device names are not unique

My PortMidi stuff lists the devices as:
[system device index (unique)]. [device name]

eg. "1. Akai MPD24"

... which makes them all unique. Will this solve the problem? (I'm not
quite sure I understand what you mean by channel - do you mean midi
channel?)

If you had two SCS.3d's hooked up, they'd look like:
"1. Stanton SCS 3.d"
"2. Stanton SCS 3.d"

Thanks,
Albert

On Thu, Dec 18, 2008 at 7:15 AM, Pegasus <email address hidden> wrote:
> Public bug reported:
>
> When connecting multiple MIDI devices of the same type (on different
> MIDI channels) they both are given the same device name in the MIDI
> Device Selection preferences pane: the reported device name, the text
> "MIDI", and the number 1. E.g. "SCS.3d MIDI 1"
>
> It would be nice if they instead showed up as <reported device name>
> (Channel <#>).
>
> ** Affects: mixxx
> Importance: Undecided
> Status: New
>
> ** Description changed:
>
> When connecting multiple MIDI devices of the same type (on different
> MIDI channels) they both are given the same device name in the MIDI
> - Devices preferences pane: the reported device name, the text "MIDI", and
> - the number 1. E.g. "SCS.3d MIDI 1"
> + Device Selection preferences pane: the reported device name, the text
> + "MIDI", and the number 1. E.g. "SCS.3d MIDI 1"
>
> It would be nice if they instead showed up as <reported device name>
> (Channel <#>).
>
> --
> Midi device names are not unique
> https://bugs.launchpad.net/bugs/309318
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
>

Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote :

I meant MIDI channel. But since we'll store that in the MidiDevice object anyway, the way PortMidi displays it will be fine. It would be helpful if we can also access just the device name (for things like a default mapping/script file name look up table.)

Changed in mixxx:
assignee: nobody → gamegod
status: New → In Progress
Revision history for this message
Albert Santoni (gamegod) wrote : Re: [Bug 309318] Re: Midi device names are not unique

Hold up - The MIDI channel is just a field inside MIDI messages, it's
not something that gets set at the device level. If you want to do
fancy stuff based on the MIDI channel, it should be handled in the
upper half of our midi stuff. When we open a device, we receive
messages from ALL channels.

On Thu, Dec 18, 2008 at 9:34 AM, Pegasus <email address hidden> wrote:
> I meant MIDI channel. But since we'll store that in the MidiDevice
> object anyway, the way PortMidi displays it will be fine. It would be
> helpful if we can also access just the device name (for things like a
> default mapping/script file name look up table.)
>
> --
> Midi device names are not unique
> https://bugs.launchpad.net/bugs/309318
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
>

Changed in mixxx:
milestone: none → 1.8.0
Changed in mixxx:
status: In Progress → Fix Committed
RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/5072

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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