Replies: 3 comments 9 replies
-
|
Hi Peter, so you would prefer having multiple parts with 8 voices each over having e.g., one performance with up to 16*4 voices (16 voices, each of which up to 4 times detuned and panned)? That is what I have running currently in my experimental Linux, macOS, Windows, FreeBSD, and Embedded Linux version. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for thinking on this and writing it down.
There are some performances that use multiple MIDI channels (Mkii Strgs+F3, Floating, Weekend, Flutter). Maybe it would be better to set an offset?
If someone wants to layer another performance, they can use the same one.
Good idea. Maybe 4 reverbs won't fit into the rpi3's performance, but it's worth a try. The performance file new parameters could be: Which word fits here better? The Bus or the Chain? I would love to do these, but I would have to integrate the previous PRs. I wonder where :)
If someone wants high polyphony, they can set the number of TGs to 8 and the polyphony to 32 and that's it.
Where is the source? |
Beta Was this translation helpful? Give feedback.
-
|
I don't know how you feel about it, but so far you've always done it this way. I would prefer to expand the project in small steps. e.g.
I actually prefer one part (TG1 - TG8) with the highest possible polyphony. But I think we could be very flexible and offer a suitable environment for every user. Performer Mode: Combo Mode: Of course, these are all just wild ideas; I have no idea what can actually be implemented. Ultimately, I'm very satisfied with the way the miniDexed already is, but I would never want to slow down @soyersoyer in his work and am looking forward to what's to come :-) Peter |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Ever since @soyersoyer introduced the parts for the miniDexed #950 , a few thoughts have been going through my head that I would like to share with you.
miniDexed – Mixer Extension
Definitions:
Preparing for Multiple Parts
Parts:
Each part gets a global MIDI channel that can be changed via the UI:
To allow all parts to use the same performances, they must have different MIDI channels.
Performances would need a placeholder MIDI channel that can either inherit the global MIDI channel or still work in older versions.
MIDI channel 17 could act as OMNI in older versions. In a future version, if MIDIChannel = 17, the system could internally replace it with the part’s Global MIDI Channel.
Example:
Part 1 loads a performance
In that performance, the active TGs are assigned to MIDI channel 17
If MIDIChannel = 17, assign the TG the value of GlobalMIDIChannelPart1
These global settings should be stored in a separate file (e.g. Global.ini). This file could also hold other global user-defined parameters, such as MasterVolume or other values currently in minidexed.ini.
Virtual Mixer for miniDexed
To capture the TX816 vibe, an 8-channel mixer would be ideal.
Inputs: 8 channels, grouped into 4 stereo busses
Each TG can freely select a bus and route to its left/right stereo input via PAN
Each bus has:
The four busses are summed, pass through a Limiter, and then go to Audio Out
For each bus, two effects can be chosen from a small set (Chorus, Delay, Reverb, …)
Mixer data would be saved within the Performance.ini
Another Idea for Multiple Parts: ALL/ODD/EVEN
The original DX7 could be set to ALL, ODD or EVEN note mode to increase polyphony — playing only odd or only even notes.
Example:
Loading the same performance in both parts would nearly double the effective polyphony.
It’s not easy to put all these ideas into words, so please feel free to ask for clarification if anything is unclear.
Peter
Beta Was this translation helpful? Give feedback.
All reactions