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
]]>
]]>
Statistics: Posted by sm_jamieson — 02 May 2026, 18:56
]]>
We need a new forum section "Usine Hacking"
Statistics: Posted by sm_jamieson — 30 Apr 2026, 18:03
]]>
and then, in each rack, I get the Global Array value(s) wich I need to control my faders and knob
eg something like choosing in a combo box the first instrument : Tuba > all my faders are feeded from values 1 = volume, 9 (1+8) reverb, 17 (1+16) delay
choosing the second instrument : Serpent > all my faders are feeded from values 2 = volume, 10 (2+8) reverb, 18 (2+16) delay
(this way I can also feed one value in the GA from 2 separated controllers.
Here I just tried some stuffs to help find a solution to your problem
Statistics: Posted by grego mondo — 30 Apr 2026, 13:06
]]>
]]>
If you create a midi in device getting a midi bus (called "virtual" for eg) the midi learn goes the same way with no name
but if you add the midi bus "virtual" to IN MIDI LAN & BRIDGE then it's learned with the name "MIDI LAN & BRIDGE"
Then if you plug a real midi device (let's say "MPK MINI") and put the "virtual" bus in it
As long as the MPK MINI is plugged to the computer all the learn using "virtual" values go through it and are learned with its name (MPK MINI)
Then if you unplugged the MPK MINI all the learns still works and you can make new learns ...
I added a pass flow between "virtual" bus and "MIDI TO USINE" in the MPK MINI input device so I can turn the "virtual" going through "MPK MINI" on and off
it means you need to have unused controllers that you'll plug once and then put back in your drawer ...
Statistics: Posted by grego mondo — 29 Apr 2026, 10:18
]]>
I did some experiments with fake devices (a patch receiving from a midi bus dropped into the devices area of a rack).
If the real midi input devices are removed, you can actually midi learn from the fake devices but they have no real device behind them
and the the wkp file they are stored as
Tdevice name =
instead if something like Tdevice name=FOCUSRITE USB MIDI
If you learn from another fake device in the same way, it is also stored without a name so they are really clones of each other,
both with device name of "nothing", and both sliders move together.
But in principle if there was a way to give the fake device a fake external device name, this could be supported by Usine.
Note - the input device patch as seen in the devices section may be called "IN FOCUSRITE USB MIDI" but the real
device behind it is called "FOCUSRITE USB MIDI" - they are not the same thing.
If the midi was sent out and looped back in via a virtual midi cable, of course this would work, since then there is a real midi device.
Interesting anyway.
Statistics: Posted by sm_jamieson — 29 Apr 2026, 03:19
]]>
Olivier SENS ( alias @senso le créateur du logiciel) ) et moi organisons depuis plus de 15 ans une formation au Studio Lakanal à Montpellier.
Elle aura lieu cette année ➜ du 28 sept au 2 octobre 2026.
L'idée est de se former sur le logiciel tout en échangeant avec tous les participants et faire progresser ou émerger son projet avec Usine. Olivier s'adapte au niveau de chacun.
Cette formation est éligible aux OPCO, AFDAS, (Auteur compositeur, technicien, musicien...), plan de formation entreprise, France Travail, Auto-entrepreneur et tarif spéciaux en autofi.
Le nombre de place est limitée à 6 pour pouvoir échanger ensemble efficacement, et possibilité d’hébergement sur place type gite urbain s'il reste des places.
Vous pouvez nous contacter au 0467842989 pour toutes questions sur le financement ou à formation@studiolakanal.com pour toutes autres questions.
Bonne journée & à bientôt !
Pierre ||| Studio Lakanal ||| Montpellier
Statistics: Posted by Pierre Lakanal — 28 Apr 2026, 17:43
]]>
do the midi learns once and for all (here they are patched from CC1 to CC8
++
Olivar
see examples :
Statistics: Posted by oli_lab — 28 Apr 2026, 00:26
]]>
]]>
Je vais essayer tout cela sur mon workspace.
encore merci
Statistics: Posted by rlgsbt — 27 Apr 2026, 16:22
]]>
There is no MIDI Learn function specific to racks.
However, for each MIDI Learn, you can specify the device.
As for using MIDI In/Out modules, this allows you to retrieve data within patches. This enables more precise and potentially complex control than simply mapping a MIDI Learn, but it requires patching.
MIDI Learn allows for quick and flexible setup.
In some cases, it can be difficult to manage—for example, if a device keeps sending data. However, you can simply turn off the corresponding device (in Usine).
Happy patching !
Baptiste
Statistics: Posted by BM2F — 27 Apr 2026, 12:18
]]>
so that all lower patches in the rack get the midi data for that rack.
I want to do midi learn only on the midi data in that rack, but Usine midi learn is global.
Is there any way to have rack specific midi learn ?
If not, this may be something for HH7.
Thanks,
SImon.
Statistics: Posted by sm_jamieson — 27 Apr 2026, 02:51
]]>
Statistics: Posted by oli_lab — 26 Apr 2026, 18:02
]]>
Statistics: Posted by titl — 26 Apr 2026, 17:13
]]>
https://www.youtube.com/watch?v=Hgf7nXyLGJ8
Think wasnt ever hh at the time, prob v5 and older liveosc
But can go pretty deep with osc and scripting, accessing all devices, tracks,sends ect params
Then using virtual midi ports like loopmidi could send all midi stuff
Statistics: Posted by 23fx23 — 25 Apr 2026, 22:32
]]>
Actuellement, même avec les sampler configurés en lecture sur disque, Usine garde les samples en mémoire et ne joue pas les nouveaux fichiers.
Une solution ?
merci
Statistics: Posted by rlgsbt — 25 Apr 2026, 09:45
]]>
here is the "NOT working" code :
CODE:
void diywt::writeWavFile(const std::string& filename) {realSize = m_maxWrite;sdkTraceInt(realSize);sdkTraceInt(m_lastMarkerNumber);// Structures pour les en-têtesstruct RiffHeader {char chunkId[4] = { 'R', 'I', 'F', 'F' };uint32_t chunkSize;char format[4] = { 'W', 'A', 'V', 'E' };};struct FmtChunk {char chunkId[4] = { 'f', 'm', 't', ' ' };uint32_t chunkSize = 16;uint16_t audioFormat = 3; // 32-bit floatuint16_t numChannels;uint32_t sampleRate;uint32_t byteRate;uint16_t blockAlign;uint16_t bitsPerSample;};struct DataChunk {char chunkId[4] = { 'd', 'a', 't', 'a' };uint32_t chunkSize;};std::ofstream outFile(filename, std::ios::binary);if (!outFile) {sdkTraceErrorChar("can't open file");return;}// Paramètres audioint numChannels = 1;int bitsPerSample = 32;int numSamples = m_markersStart[m_lastMarkerNumber];//realSize;// Calculer la taille des données audiouint32_t dataSize = numSamples * numChannels * bitsPerSample / 8;// Remplir les en-têtesRiffHeader riffHeader;FmtChunk fmtChunk;fmtChunk.numChannels = numChannels;fmtChunk.sampleRate = sdkGetSampleRate();fmtChunk.byteRate = fmtChunk.sampleRate * numChannels * bitsPerSample / 8;fmtChunk.blockAlign = numChannels * bitsPerSample / 8;fmtChunk.bitsPerSample = bitsPerSample;DataChunk dataChunk;dataChunk.chunkSize = dataSize;// Calculer la taille totale du fichieruint32_t totalFileSize = sizeof(RiffHeader) + sizeof(FmtChunk) + sizeof(DataChunk) + dataSize;// +sizeof(CueChunk) + cueChunkSize + sizeof(AdtlChunk) + adtlChunkSize;riffHeader.chunkSize = totalFileSize - 8; // Soustraire les 8 octets du chunkId et du chunkSize// Écrire les en-têtes dans le fichieroutFile.write(reinterpret_cast<char*>(&riffHeader), sizeof(RiffHeader));outFile.write(reinterpret_cast<char*>(&fmtChunk), sizeof(FmtChunk));outFile.write(reinterpret_cast<char*>(&dataChunk), sizeof(DataChunk));// Écrire les données audiofor (f = 0; f < numSamples; ++f) {outFile.write(reinterpret_cast<const char*>(&m_audioBuffer[f]), sizeof(float));}// Ajouter un padding si nécessaire pour aligner le chunk suivant sur un nombre pair d'octetsif (dataSize % 2 != 0) {outFile.put(0);}outFile.close();/*//mettre à jour la sortie markerOutint tempSize = m_lastMarkerNumber;markersOut.setSize(tempSize);for (int m = 0; m < tempSize; m++) {markersOut.setArrayData(m, float(m_markersStart[m])/float(numSamples));}*/if (!outFile) {sdkTraceErrorChar("Error closing file");return;}std::string s = fdrFileName.getPChar();s = s + " successfully created";sdkTraceChar(s.c_str());m_signalisation = 2;}Statistics: Posted by oli_lab — 21 Apr 2026, 19:41
]]>
But I think Usine should have read and write sample modules that support wav and aif at least and the metadata for looping
It could be written with the SDK ...
Statistics: Posted by sm_jamieson — 21 Apr 2026, 19:06
]]>
But I did an addon called "player with saved markers" that can save and retrieved markers.
It is not possible to do loops at sample level but.
for this king of thing, I rather use REAPER and make regionss to be render or a specialized sample editor.
Otherwise, I pretty much like the idea of using Usine as a modular studio to produce processed samples (just like with an old school hardware studio)
Statistics: Posted by oli_lab — 21 Apr 2026, 17:29
]]>
Can it or a patch do the following:
1. Set and play a loop
2. Add loop start and end cue points to metadata
3. Snap cue to zero crossing point
4. Modify sample to cross fade across loop points.
5. Save the sample in the same or different format with loop cue points in the metadata that can be used by another sampler ?
Thanks.
Statistics: Posted by sm_jamieson — 21 Apr 2026, 10:46
]]>
]]>
Statistics: Posted by sm_jamieson — 20 Apr 2026, 16:03
]]>