+- XOR Userforum (https://xor-electronics.com/forum)
+-- Forum: Products (https://xor-electronics.com/forum/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://xor-electronics.com/forum/forumdisplay.php?fid=6)
+---- Forum: NerdSEQ Expanders (https://xor-electronics.com/forum/forumdisplay.php?fid=22)
+---- Thread: I2C Expander (/showthread.php?tid=512)
RE: I2C Expander - XORadmin - 09-13-2023
distingEX -> Check!
6 Voice Polyphonic Sequencing from one track using I2C:
https://youtube.com/shorts/zOY0NgLWSMY?si=h1ZcAvfveVmji0dG
RE: I2C Expander - dborowik - 09-14-2023
(09-13-2023, 01:26 PM)XORadmin Wrote: distingEX -> Check!
6 Voice Polyphonic Sequencing from one track using I2C:
https://youtube.com/shorts/zOY0NgLWSMY?si=h1ZcAvfveVmji0dG
Nice one!
How do you like the Disting Ex? By the way on Lines Scanner Darkly and Oz are talking about introducing algorithm specific command like
<address> 0x6C <sub cmd> <data> <data>
to allow for non-Teletype devices to control it via i2c
https://llllllll.co/t/teletype-disting-ex-integration/33929/213
RE: I2C Expander - XORadmin - 09-14-2023
I will not support the algorithmic specific commands as this is a hell to program. Just think about an implementation for every gear out there that has its own specific commands and packets for every specific function…and for every gear it is different. Which is already a fact and the worst thing about I2C.
I’ve gone through all these discussions already and talked with Os about what would be needed (also here I can’t learn every single module to find out how they implemented I2C and how the module works. I tried that with Just Friends and it is very esoteric to understand what it is doing at all. Disting took also quite some time). I will do subsets of selected modules which I think are important for sequencing notes/pitches/drums. And for special stuff you can use the custom commands and generate your bytes yourself. So the fact of totally different I2C implementations and finding out how it’s done (reading manuals and often go through other peoples source code to get some information) is one of the reasons it takes so long.
For the disting I support Voice pitch, Voice velo (and combined with pitch ), voice off, controllers (from the mapping and there you can select all these things from the algorithms), Parameter change (both commands, also here all parameters of the algorithms). So in fact most of it should be covered and as a side-note: I only borrowed a distingEX from someone to get it working and didn’t have time to get into the algorithms to find out what they do and how they work. Just imagine I would dive into any module for that..it would never be finished and I would be out of buisness!! In the end the NerdSEQ is a sequencer and the functions must make sense for the sequencing, it is not a Teletype where you only would need to implement the commands and give it a name without the need to know of what it is doing.
Allright, this being said. I am very happy about the results with the distingEX and I want to have one only for the polyFM :-) (my cheesy DX7 heart is beating doubleclock)
RE: I2C Expander - dborowik - 09-14-2023
Awesome work Thomas!
I can't even start to imagine how time consuming it would be to implement commands for every single i2c module..!
Still, is this something the community could help with in the future?
In terms of the Disting Ex, how could we support you in getting one? Do you have a donation box somewhere, Patreon or else?
RE: I2C Expander - XORadmin - 09-14-2023
(09-14-2023, 08:22 AM)dborowik Wrote: Awesome work Thomas!
I can't even start to imagine how time consuming it would be to implement commands for every single i2c module..!
Still, is this something the community could help with in the future?
In terms of the Disting Ex, how could we support you in getting one? Do you have a donation box somewhere, Patreon or else?
Forgot about also Preset for the disting is in there too.
The main point is not only to get all the gear, but also work with it, understanding it and find the needed information. I got loads of modules here which I traded occasionally for a possible future use and I can't even find the time to play with these or even get them out of the box and connect them once!! Same for some synths which are still unpacked from moving one year ago.
So getting more modules is nice, but only if I get time to play with them
(AND I WILL!!!)Thanks for the offer/idea. But generally I would rather get all the I2C using manufacturers into discussion to make a 'one fits all' protocol like midi is for decades.
RE: I2C Expander - nsolarz - 09-14-2023
(09-14-2023, 06:30 AM)XORadmin Wrote: I will not support the algorithmic specific commands as this is a hell to program. Just think about an implementation for every gear out there that has its own specific commands and packets for every specific function…and for every gear it is different. Which is already a fact and the worst thing about I2C.
Is there the potential to have a "definition" file format to handle some of these things? could work for midi too; I know other sequencers use similar systems to store things like which MIDI CC map to which parameter etc. that way the community would be able to "crowdsource" the more involved/esoteric I2C implementations. just an idea
RE: I2C Expander - dborowik - 09-14-2023
I really hope you manage some time to finally settle and appreciate your gears
RE: I2C Expander - XORadmin - 09-14-2023
(09-14-2023, 05:29 PM)nsolarz Wrote:(09-14-2023, 06:30 AM)XORadmin Wrote: I will not support the algorithmic specific commands as this is a hell to program. Just think about an implementation for every gear out there that has its own specific commands and packets for every specific function…and for every gear it is different. Which is already a fact and the worst thing about I2C.
Is there the potential to have a "definition" file format to handle some of these things? could work for midi too; I know other sequencers use similar systems to store things like which MIDI CC map to which parameter etc. that way the community would be able to "crowdsource" the more involved/esoteric I2C implementations. just an idea
That is something for DAWs but not for embedded systems with chronically low memory. And it would definitely not solve the problem to get a good implementation. Often you got to combine packets to get the needed results etc.
So in my opinion this is not an option. Still the custom commands let you define commands which are not there in case you would need them.
RE: I2C Expander - Morim - 09-22-2023
Hi.
Any plans to make a 2hp, only I2C (as the midi expander)?
RE: I2C Expander - XORadmin - 09-22-2023
(09-22-2023, 09:35 AM)Morim Wrote: Hi.
Any plans to make a 2hp, only I2C (as the midi expander)?
No