Bug 213 - Audio Device Number and the MIDI Device Number is displayed in wrong order (upside down)
Summary: Audio Device Number and the MIDI Device Number is displayed in wrong order (u...
Status: CLOSED WORKSFORME
Alias: None
Product: QSampler
Classification: Unclassified
Component: qsampler (show other bugs)
Version: 0.2.1
Hardware: All All
: P5 critical
Assignee: Rui Nuno Capela
URL:
Depends on:
Blocks:
 
Reported: 2014-01-12 19:34 CET by octron
Modified: 2021-05-11 13:49 CEST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description octron 2014-01-12 19:34:36 CET
Hi,
the Qsampler GUI has one bug.
The Audio Device Number and the MIDI Device Number is displayed in wrong order (upside down),
This happens, if you use the Linuxsampler as a Plugin and configure more than one output or input device.
(I do not know, if the qsampler has the same bug whend configured with asio drivers.

First this is no problem for me, if you know this bug and just want to insert a new channel with a new instrument, you just make you choose in the dropdown-list upside down and try to take the "wrong" device number. But if you try afterwards to change for example the midi channel nummer (what is allowed) Qsampler will send not the correct device number to linuxsampler, which results in an ugly Error-Message Box, that the device could not be changed in the Linuxsampler track.
Okay, I can live with that, but its not handy at all. And for my students it is confusing! :?

Please fix this bug. ;)
Pictures are attached in the following Fourm-Thread:

https://bb.linuxsampler.org/viewtopic.php?f=2&t=750&p=6868#p6868

Best Regards.
Comment 1 Christian Schoenebeck 2019-03-10 17:20:21 CET
For some reason the screen shot you mentioned is no longer visible from the forum thread you linked. So currently I can't see what you actually had in mind.

Does this problem actually still persist for you or can this report be closed? If it still persists, you might attach a screen shot for making this issue more clear.
Comment 2 Christian Schoenebeck 2019-04-23 19:56:42 CEST
I am going to close this report, since I received no further feedback from your side. Feel free to reopen this bug in case you think this issue persists.