MIDI errors for deck 3/4 when launching with Shade (2 decks)

Bug #1843649 reported by ronso0
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Medium
Unassigned

Bug Description

a MIDI error message is displayed when starting Mixxx with Shade and a controller attached that has a 4-deck MIDI mappping with LED output functions for decks 3/4, also the log is continously spammed with those messages.

Solution might be to read [Master],num_decks and deactivate output mappings for decks 3/4 if they're unavailable in the GUI.

A rare use case on the other hand:
A 2-deck skin shouldn't hinder that I use decks 3/4 as parking slots for tracks I come across that I want to store for later on. When I need them I simply pull them to main decks 1/2 with MIDI clone controls, and I actually don't need them in the GUI until then.
For that case decks 3/4 should be blocked for 'helpful' GUI & MIDI/HID controls like "load track to next free/stopped deck", but explicitely loading tracks to invisible decks should remain possible.

affected mappings:
* Reloop TerminalMix 2/4
* ?

ronso0 (ronso0)
description: updated
Revision history for this message
Daniel Schürmann (daschuer) wrote :

I am unsure here. Can't you just use a four deck skin in this case?
I guess a majority of users do not even have a controller attached, so it would be confusing for them to have access to invisible decks.

I can confirm this bug, because we should find a way to remove the log spam.

Changed in mixxx:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
ronso0 (ronso0) wrote :

yes, the use case of a 4-deck controller with a 2-deck skin can be ignored.

The log spam is avoided if the script reads [Master],num_decks on init and uses this variable for the timed LED flash functions (loop indicator, play_from_cue indicator, ...)

description: updated
tags: added: usability
removed: ux
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/9738

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.