cheers !
Olivar
Statistics: Posted by oli_lab — 04 May 2026, 21:26
]]>
The setting might best be in the container properties e.g. "Offset container in Poly" vertical and horizontal pixels. The first poly voice container would stay where it is and the others offset by the offset setting multiplied by the (voice number - 1).
Thanks.
Statistics: Posted by sm_jamieson — 04 May 2026, 18:47
]]>
But I would like a button that can be pressed to give high priority to that VST so snappy interaction is possible e.g. when editing patches etc.
Statistics: Posted by sm_jamieson — 11 Apr 2026, 15:45
]]>
if they are the same, a good idea would be to use the procedure thing : one procedure can be used in as much instances that you need.
cheers.
Olivar
Statistics: Posted by oli_lab — 12 Dec 2025, 21:33
]]>
At present, I have 277 scripts in my wkp. So to change the debug method for all of them would be a huge hassle. And if I think of another change to it, I can make that change again 277 times. For instance, using usine objects, I am able to turn on and off debugging from a button in the toolbox. This works on the half-dozen scripts that implement it, but not on any of the rest.
It would be really nice to be able to keep common methods like this in a separate file.
Statistics: Posted by woodslanding — 11 Dec 2025, 01:26
]]>
This special subpatch will need a combobox to choose between various samplerates.
Thanks
Statistics: Posted by oli_lab — 11 Nov 2025, 13:05
]]>
so I could enter 2 color Array, one Yellow and Red and one Black & White
so I could read my text in black in the first (yellow) column and in white in the second (red) column.
Statistics: Posted by grego mondo — 07 Nov 2025, 19:10
]]>
]]>
]]>
midi trace on wire shows module still sends AFT messages:
also could be cool to be able to have some kind of multi filter that allows for ex ON, PB, or OFF, AT, whatev, in any configurations
by this i mean like multi "sections" whith msg type, (not just ie multi CC like current multi filter behaviour).
no big deal tho, we can drop several filter modules and recombine, more a workflow/opti thing sugg
Statistics: Posted by 23fx23 — 07 Oct 2025, 12:43
]]>
]]>
it is here :
https://www.dropbox.com/scl/fi/km6qnnsx ... zimw0&dl=0
Statistics: Posted by oli_lab — 05 Sep 2025, 21:28
]]>
but for ex tablets screens using pressure pens (MPP) usually expose pressure.
(here a vid ex of what i mean with juce , with my screen and an mmp 2 stylus, aroud 30" in the vid)
https://drive.google.com/file/d/1laCCAh ... sp=sharing
would be cool to be able to get that info in usine in same way (maybe not all modules, but some new extra global mouse variant or device module? just an idea..)
Statistics: Posted by 23fx23 — 31 Aug 2025, 21:10
]]>
IMO, but to avoid any mistake an compatibilities issues, the best is to include the version number in the filename.
Statistics: Posted by senso — 31 Jul 2025, 09:12
]]>
You mean you feed a step sequencer with your Array and move your cursor where you want to ?
...
I think I already asked for that, it would be really more efficient to quickly read an array and find the value you're looking at ...
It's just for visualisation purpose. otherwise I'll use "get element value"...
I think I already asked for that, it would be really more efficient to quickly read an array and find the value you're looking at ...
As Senso explained to me, colors are a "settings" that are refreshed at refreshed rate (usually every 25ms) and not audiorate. Making them array compatible will take too much CPU time. maybe we could hack a matrix for individual color cells ?"Also it would be fun to be able to set the steps colour individually with a color array." +1
See you soon !
Olivar
Statistics: Posted by oli_lab — 28 Jun 2025, 13:07
]]>
"Also it would be fun to be able to set the steps colour individually with a color array." +1
I think I already asked for that, it would be really more efficient to quickly read an array and find the value you're looking at ...
Statistics: Posted by grego mondo — 27 Jun 2025, 17:14
]]>
]]>
Also it would be fun to be able to set the steps colour individually with a color array.
Cheers
Olivar
Statistics: Posted by oli_lab — 26 Jun 2025, 18:09
]]>
]]>
cheers
Olivar
Statistics: Posted by oli_lab — 03 Jun 2025, 11:24
]]>
Statistics: Posted by sm_jamieson — 28 May 2025, 19:01
]]>
]]>
const AnsiCharPtr UserModuleBase::MODULE_NAME = "my test module"
const AnsiCharPtr UserModuleBase::MODULE_DESC = "my test module is very useful"
const AnsiCharPtr UserModuleBase::MODULE_VERSION = "2.0"
But when the module is used or examined in Usine, this information is not available anywhere.
e,g, when you look at a module in the Browser you get a description box - for a SDK User Module the box is empty.
If you have several versions of a User Module it is impossible to tell which version you are using.
For example, for HH6 SDK I have to modify one of my user modules because of the change in the Event class.
I then need to know which version is being picked up in my HH6 workspace.
Please can you
1. Display the MODULE_NAME, MODULE_DESC and MODULE_VERSION in the browser description box.
2. Display the information in the (i) information tab in the settings
Thanks.
Simon.
Statistics: Posted by sm_jamieson — 28 May 2025, 02:26
]]>
]]>
https://www.audiomasterclass.com/blog/a ... whats-that
did you try the example or just the module ?
Statistics: Posted by oli_lab — 23 May 2025, 16:40
]]>