MUX module ghost jacks
-
- KVRer
- 8 posts since 11 Sep, 2014
Sometimes when I delete an input or output inside a MUX module, it does not delete the corresponding input/output jack of the module. These "ghost" jacks remain, and there is no apparent way to get rid of them. Adding additional inputs/outputs will create new jacks in addition to the ghost jacks. So I end up having modules that I need to remember to ignore the first 4 inputs, for example, because they are dead. Is this a known issue?
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
-
- KVRer
- Topic Starter
- 8 posts since 11 Sep, 2014
Hi, thanks for the reply. Here is what I did to reproduce the issue, starting from a new project. MuLab version 6.4.18, 64-bit, running on Windows 7 64-bit.mutools wrote:What steps do i have to take to repeat this, ideally starting from a new project?
Steps to reproduce:
1. Create new project
2. Go to modular area.
3. Add module: MuTools->Modules->Others->MUX Modular
4. Open added module.
5. Delete connection between Audio Input 1 and Audio Output 1.
6. Delete Event Output.
7. Add Chorus. Connect Audio Input 1 -> Chorus -> Audio Output 1.
8. Add 3 new Audio Inputs, 3 new Choruses, and 3 new Audio Outputs. Connect each as in step #7.
9. Connect all Event Inputs to Chorus(1). Repeat for each Chorus (16 event connections total).
10. Add 2 modulation inputs.
11. Add 2 midi controller generators.
12. Connect Modulation Input 1 to MIDI Controller Generator 1.
13. Connect Modulation Input 2 to MIDI Controller Generator 2.
14. Save preset. Observe in main modular area that there are 4 audio input jacks, 4 event input jacks, 4 audio output jacks, and 2 modulation input jacks.
15. Select all event inputs and delete them.
16. Observe in the main modular area that there are still 2 event input jacks, even though all event inputs have been deleted (incorrect).
17. Delete the first 2 audio inputs. Observe that 2 input jacks were deleted, and 2 are remaining (correct).
18. Delete the first 3 audio outputs. Observe that only 2 output jacks were deleted, and 2 are still remaining, even though there is only 1 audio output jack left (incorrect).
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Hey darmusic, thx a lot for the step-by-step. Tried it but:
That's strange, i only see 1 event input at this point. Did you forget to include a step where you added event inputs?darkmusic wrote: 1. Create new project
2. Go to modular area.
3. Add module: MuTools->Modules->Others->MUX Modular
4. Open added module.
5. Delete connection between Audio Input 1 and Audio Output 1.
6. Delete Event Output.
7. Add Chorus. Connect Audio Input 1 -> Chorus -> Audio Output 1.
8. Add 3 new Audio Inputs, 3 new Choruses, and 3 new Audio Outputs. Connect each as in step #7.
9. Connect all Event Inputs to Chorus(1). Repeat for each Chorus (16 event connections total).
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
I did it exactly as described up to step 16 but still all ok here.
Question: In step 14 you save the patch. Did you reload it?
Question: If you still have that preset file you saved in step 14 and then if you start from a new session -> modular area and drop that preset file onto the modular area and then open that mux and do step 15, then is it also wrong like described in step 16?
If yes then please post that preset file here or email it to me. Thx!
Question: In step 14 you save the patch. Did you reload it?
Question: If you still have that preset file you saved in step 14 and then if you start from a new session -> modular area and drop that preset file onto the modular area and then open that mux and do step 15, then is it also wrong like described in step 16?
If yes then please post that preset file here or email it to me. Thx!
-
- KVRer
- Topic Starter
- 8 posts since 11 Sep, 2014
No, I did not reload it.mutools wrote:Question: In step 14 you save the patch. Did you reload it?
I started a new project and loaded the preset I saved in step 14, and the behavior is correct. However, if I load the previous preset I saved in step 16, the problem of too many jacks exists. Here is a zip archive containing the preset and screenshots with the issue:mutools wrote:Question: If you still have that preset file you saved in step 14 and then if you start from a new session -> modular area and drop that preset file onto the modular area and then open that mux and do step 15, then is it also wrong like described in step 16?
https://www.dropbox.com/s/6x2xnfyymz6uc ... t.zip?dl=0
I will see if I can create a preset that fails consistently in step 14.
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Thanks for the extra info, can repeat the prob, researching it now.
One extra question: Did you create the 3 extra event inputs by control-drag = copy ? If not how did you create the extra event inputs?
One extra question: Did you create the 3 extra event inputs by control-drag = copy ? If not how did you create the extra event inputs?
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Yes there clearly is a bug when creating inputs outputs by copy-paste or ctrl-drag. Please don't do it that way until that bug is fixed. Until then create a new input output via double-click -> new module, or drag-drop from browser "MUX Modules" onto modular area.
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
