Hi Jo,
I know where the desk is, but where is the rack panel?
MuLab 10.0.85
-
- KVRAF
- Topic Starter
- 13853 posts since 24 Jun, 2008 from Europe
The "Rack Panel" is the user Front Panel for a rack that you can add to a rack as of M10.
It appears at the left side.
Cfr the draft intro video on M10's modular racks:
It appears at the left side.
Cfr the draft intro video on M10's modular racks:
-
- KVRist
- 212 posts since 14 Feb, 2021
Hei,
I still find this confusing, especially now that both the audio stream and sequence share the same icon.
I still find this confusing, especially now that both the audio stream and sequence share the same icon.
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- Topic Starter
- 13853 posts since 24 Jun, 2008 from Europe
-
- KVRist
- 90 posts since 6 Apr, 2012
Quick question: when adding new slots to a rack, are they meant to not have any audio or events pass through them?
I noticed in the Rack Modular Area, deleting and adding new slots will not add any new cables, which can be exploited into not having new effects in the chain work. At worst, if you remove all but one slot, audio will simply bypass into the Rack's output, or in some configurations not work at all! This seems to create all sorts of funky interactions with the pre/post fader as well.
Below is a video showcasing what could happen that I believe is undesirable given the current state of how adding and deleting slots in racks works:
(Mind the audio bleeding from my monitors back into my mic...)
I would hate to have this be only solvable via the modular area if it's a front panel issue.
I noticed in the Rack Modular Area, deleting and adding new slots will not add any new cables, which can be exploited into not having new effects in the chain work. At worst, if you remove all but one slot, audio will simply bypass into the Rack's output, or in some configurations not work at all! This seems to create all sorts of funky interactions with the pre/post fader as well.
Below is a video showcasing what could happen that I believe is undesirable given the current state of how adding and deleting slots in racks works:
(Mind the audio bleeding from my monitors back into my mic...)
I would hate to have this be only solvable via the modular area if it's a front panel issue.
-
- KVRian
- 1125 posts since 30 Oct, 2013 from Scarborough
Confirmed the above. It's only when using the + button that no cables are added. Using right click to "Insert Slot" works fine as expected.
I also noticed that inserting a patch with multiple outputs into a rack slot e.g. a Mudrum kit adds the output pins to the slot in the modular area as you would expect, but using drag and drop into the rack slot from the browser for the same patch does not.
I also noticed that inserting a patch with multiple outputs into a rack slot e.g. a Mudrum kit adds the output pins to the slot in the modular area as you would expect, but using drag and drop into the rack slot from the browser for the same patch does not.
https://rjsemper.wixsite.com/website
One Synth Challenge - https://sites.google.com/site/kvrosc/about
One Synth Challenge - https://sites.google.com/site/kvrosc/about
-
- KVRAF
- Topic Starter
- 13853 posts since 24 Jun, 2008 from Europe
No.PelletProject wrote: Sat Nov 23, 2024 6:21 am Quick question: when adding new slots to a rack, are they meant to not have any audio or events pass through them?
Thx for the helpful video.I noticed in the Rack Modular Area, deleting and adding new slots will not add any new cables...
I would hate to have this be only solvable via the modular area if it's a front panel issue.
It's a dumb bug.
Will be fixed in M10.0.13, available very soon.
-
- KVRAF
- Topic Starter
- 13853 posts since 24 Jun, 2008 from Europe
Will also be fixed in M10.0.13.RichardSemper wrote: Sat Nov 23, 2024 12:45 pm I also noticed that inserting a patch with multiple outputs into a rack slot e.g. a Mudrum kit adds the output pins to the slot in the modular area as you would expect, but using drag and drop into the rack slot from the browser for the same patch does not.
Thx for reporting this!
-
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Minor spelling issue:
On the filterbank: Inactivate unused bands should be Deactivate unused bands
On the filterbank: Inactivate unused bands should be Deactivate unused bands
-
- KVRAF
- Topic Starter
- 13853 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
There's no such word as inactivate. Inactive is a word, the equivalent of inactivate is actually deactivate in English.
No. Hide Inactive Bands is correct, as Inactive is ok, but Inactivate is not. I know, English, right?!
No. Hide Inactive Bands is correct, as Inactive is ok, but Inactivate is not. I know, English, right?!
-
- KVRAF
- Topic Starter
- 13853 posts since 24 Jun, 2008 from Europe
A quick inet search tells me something else (inactivate is an existing word), but anyway i'm open for tweaking it but your last reply doesn't answer my question about "Hide Deactivated Bands", which sounds long to me.
Maybe "Enable" + "Disable" can be used?
It's not exactly the right meaning for what the function does, but it may be a pragmatic solution?
Maybe "Enable" + "Disable" can be used?
It's not exactly the right meaning for what the function does, but it may be a pragmatic solution?
-
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Oh ok, never heard of it before.
"Hide Inactive Bands" is same as "Hide Deactivated Bands"
I think it's ok as is, just that I would personally prefer "Deactivate Unused Bands" instead of Inactivate.
"Hide Inactive Bands" is same as "Hide Deactivated Bands"
I think it's ok as is, just that I would personally prefer "Deactivate Unused Bands" instead of Inactivate.
-
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Although I mentioned this before, but perhaps you dislike the idea...
When you have many menu items like this that all pertain to the same thing, it makes for less reading and reduces time to acknowledge each item in a menu due to less reading time if there were a heading.
In this example a menu such as this would be easier on the eye and quicker to read, while it's meaning remains full and clear:
(Heading in bold or underlined or both?)
Bands
Show all
Hide Inactive
Deactivate Unused
Activate All
There are many such instances where this could be improved:
The Presets menu when R-click on a Rack/Sequence.
GUI Colours. The word "Color" is really unnecessary on each and every item.
Well, you get the idea, There's more important stuff anyway so I'll leave it at that
When you have many menu items like this that all pertain to the same thing, it makes for less reading and reduces time to acknowledge each item in a menu due to less reading time if there were a heading.
In this example a menu such as this would be easier on the eye and quicker to read, while it's meaning remains full and clear:
(Heading in bold or underlined or both?)
Bands
Show all
Hide Inactive
Deactivate Unused
Activate All
There are many such instances where this could be improved:
The Presets menu when R-click on a Rack/Sequence.
GUI Colours. The word "Color" is really unnecessary on each and every item.
Well, you get the idea, There's more important stuff anyway so I'll leave it at that
-
- KVRAF
- 2469 posts since 25 Sep, 2014 from Specific Northwest
Inactivate really is a verb in English. (Edit: First attested in 1906.) It's the same as deactivate. Whichever you prefer is fine.
Make Work.
Make Not Work.
Make Work.
Make Not Work.
I started on Logic 5 with a PowerBook G4 550Mhz. I now have a MacBook Air M1 and it's ~165x faster! So, why is my music not proportionally better? 