Zam

Hi Chris To me DIN and DOUT share the same clock which is RC1 (core J8/9) pin 10 I don't know about J1 DIN rev 5 schematic, maybe a mistake, or compatibility with previous rev with single row J1 connector. If you look at DOUT rev5 or IOmatrix shemo, J1 clearly connect ONLY RC1 pin10 to the shift register device I think I read you can separate RC line for IN and OUT with appropriate modification at soft side, but I let this to the soft guys :) Best Zam

Of course you are right, sorry to not have been so clear. There is absolutly no problem if you send/receive the data to/from DAW midi track and/or any other midi device. As you talk about "automated mixing console" I have in mind the HUI MCU protocole (still midi), which in some way is not fully bidirectional in "real time". Solo and mute status led scanning is one example. Best Zam

Ok FET mute, maybe be careful with the relay even for gate switching it can be noisy at audio side, keep the optocouper option in mind. Also for info if you decide to use mute for mix automation, the feedback is not so fast ... if you press a mute button at controller side the DAW reply by a note on to light the mute led, and this happen only once per second. It's OK as a visual information for mute status, but not to control in real time (let say in the mS range) any kind of audio switching. Zam

What about the use of relay, is that for audio or logic/signaling function?

Hello Mickael welcome to the midibox forum, I see you already open the same topic in french section, I'm french too, but I think you will have more success with the english section. So to reply to your first question, I don't see any problem to replace led by transistor driving relay in a matrix, what function you want to do with matrixed relay? For the second question, yes you can use several core. To my knowledge you can output multiple chained core to a single midi channel as there is midi router in mios 32. You can also use them as completely separated midi device of course Best Zam

As ilmenaor say, best route for "music" studio is patch bay and cable, I never see any studio with active patchbay/router. Active patchbay aka matrix or audio router are only used in TV and broadcast (like the vikinx I quote), where audio fidelity come after ultra speed workflow and flexibility. Best Zam

Hi Not to discourage you at all, but maybe have a look at second hand audio router like vikinx. I believe they already have midi control option in addition with Ethernet and RS232. So as a software guy maybe you can take that route and dev a nice mios32 tool app remote for this. Just an idea ! Best Zam

Hi TK Just load it, work again with this pre15 ! Thanks :) I only test my .NGC. Will test with my NGR alternative using change command. Best Zam

Hi TK Here is the .NGC section, it's "beta", and it work with my actual DAW (not bidirectional for led unfortunately), It's under MCU protocol, it allow to switch between read and rec automation with 3 rec mod. One button select read or write, second is write mode (touch, latch, overwrite). Two led (green/red) follow the pattern to light in specific order. The specific "reset" function is red highlighted below. It force last MAP value to ensure first MAP value at next press. Work well with pre6 not with pre14 (I don't try other version). I also have a NGC+NGR allowing bidirectional operation, but it don't work well for the moment at LED side (button patter work fine with less code...). The only DAW return data for read touch or latch (for my led pattern) is a sysex for the mackie LCD update... I don't think it's relevant for the MAP problem we talk now. Best Zam

To be sure I just check I load again 1_033 pre6, it work. Something go wrong between pre6 and pre14 regarding toggeling button value with a map :(

Hi TK Ok I forget my scale table with NRG So you think real time scaling is better than hard table like the last MF_NG update. memory space VS cpu speed :) To come back with this new version, there is something strange about MAP. let say MAP 1 2 3 I have a button pattern command that involve to set button B to the last status (3) if button A is pressed, to ensure next time I press button B it send status 1 whatever status 1 2 or 3 he have before pressing button A Button A and B have the same "system" to ensure each other reset the other to 1 It worked well with sender/receiver at NGC. Yesterday with the update I try to "simplify" this with run section and conditional NGR, I try "change" command to do the same function, the button B status change to the respective value forced by button A (debug view) BUT if i press the button B it go cycle to it's own previous value (MAP 1 2 3) without considering what button A just set to him. I reload my previous NGC, it don't work any more ?!? Any idea? Best Zam

Hi I will try .ngr again for some cascade note command to active and flip automation mode with MCU protocole, I think it will save me lot of sender/receiver event and fwd command in my actual .ngc question: is it possible with ram .ngr to write something to scale data in efficient way? like "if Ain=x send midi pitchbend=y" in one direction and "if pitchbend=y send Aout=x" in other direction should be 1024 (9bit) x2 (in and out) x 8 (pitchbend fader) =16384 line of code for my usecase... doable ? Best Zam

Maybe it happen if I have lot of incoming data, like AINSER jitter, I should try now with my jitter improved. Zam

Hello TK I edit and save from the file browser (as I don't have SCS nor LCD hooked to the core) Not sure it's a "real" bug, sound like data transfer overload when both task are done simultaneously ? If this help, i run STM32 via USB, MIOS 2.4.6 and OSX 10.6.8 Best Zam

Some bug report If I let "debug mode on" in MIOS studio and in the mean time edit and save setting in the .NGC file, It result in a fail and disconnection, but also an empty .NGC file at reboot. Not a big problem as I generally set debug mod off before working on the configuration file, but sometime I forgot :) Zam

I just have a look for A1 danner, it's 190x40, do you know if it's front panel or cassette size? The TKD motor fader alone need 154x18x50

Hi there is some pics of the proto in another topic the main PCB is 240x85 and designed with low profil connector to fit in 20mm height, have to be hooked to core or line receiver. and 3 rail PSU Led button is 16x150 designed for 6 ormon square illuminated tact (B3W-9 series) motor driver and touch detection, is 34x120 Of cours it's HUI protocol About selling I don't know, option still open (few ppl at groupDIY follow with interest too), but I'm not sure my project is compatible with the midibox philosophy for what I read until now. -far from low cost idea of DIY here, estimation is in the 3k range for 8 fader pack... -I think I will not have the same devotion as our beloved TK to help and support this system which is somehow in the "expert" side, so ppl realy need to know how -producing a nice and detailed documentation will take me month. Anyway everything still possible !!! But first I have to validate the PCB and whole system, running one fader as I do now is not the same. I think within one month I'll be able to order and fully populated the PCB (I'm 6 month late regarding my initial calendar...), but I'll have fund issue in this time range to order 8 fader and 8 front panel so... Best Zam

Hi Koerschgen The motor driver work well hooked to Ain and Aout I redraw for about 10 time the PCB the last 6 month...but I'm very close. After lot of spring crash test (including a full album mixing with one fader loaded at the vox channel) I use most of my summer time to improve lot of little things. I still have mechanical integrations issue, which will be fixed soon with another frontpanel order. And the design now include 17 pcb for 8 fader pack, 8 for button/led, 8 for motor driver/touch sensor, and one with 64Din, 64Dout, 8Ain, 8Aout, also 5/+15/-15V distribution for the whole pack. Now I HAVE to order the pcb and stop to worries if i made mistake, I will rework the pcb if needed. What neumann model you have, with danner casette? any idea of room available for extra PCB in the frame? Zam

Hi all Just to tell that I achieve EXCELLENT jitter result at MCP3208 input with buffer and passive first order filter I have to say I run "long cable" (30-40 cm but shielded) Before testing the filter my jitter was around 5, allowing me to use 9 bit without jitter and 10 bit with low jitter, witch is enough for my need but I'm little perfectionist... Now, the jitter monitor don't return result for 70% of my fader scale (which is strange ? should be 0 ?), and only 1 for the top 30% area (certainly linked to the fact that we come closer to the positiv rail) Anyway I check in MIOS debug mod with AINSER set to 11bit, absolutely 0 value coming in (if I don't move the fader of course). 12bit still receive lot of random value, but in close range (jitter 1) Best JS

Ok, I think I find the solution... I just use my remaining spare time to redesign PCB that keep SR far from fader... 85x250mm with 64Din, 64Dout, 8Ain and 8Aout, fitted with micro-match and angled pin header to match the lack of room ... 2cm height available in the armrest of the console. Motor driver and led/button pcb stay in the fader module. Mechanical Integration Is a headache, but i'm close :) Zam

Just for info, there is a guy "rochey"at groupDIY, I believe he work at TI as dev or something like that, maybe he can help for specific info that are not so clear in datasheet. Best Zam

Hey New user with first post about 20 time the name of a pcb manufacturer... Is that just me ?!? Zam

Hi op amp with a gain around -15dB (30vpp-->5vpp) with also 2,5v offset (-2,5v/+2,5v-->0v/5V), in this case you have to use negative feedback for gain, scaling will be +15-->0 and -15-->5, but you can invert again at soft side. What is your CV out device? is the +/-15 CV rail to rail? Zam

jfet transistor !!! not op-amp :) i have in mind J112 or bf245 etc... I don't know now, maybe as John suggested, reed is certainly the easy solution if you need SPST only. He also made a point about ON resistance Don't have you some around to check commutation noise at audio side? can't be way worst than original mechanical switches! because all other solution event fet switching will have commutation noise 99% of the time. In fact each time you switch with the audio wave not null. A zero crossing detector switch is another story... (is max4066 fitted ???) 1.5euros reed with only 4 wire and one resistor to solder is maybe cheaper than IC or opto+fet with more complicated layout, reed give you isolation and no control voltage involved at audio side, that's two important requirement. Is that saving few euros interesting if you consume days and brain for a solution that maybe is not more efficient ? Zam

Yes I see you have a rythm trig at the top raw switch, so single pole is ok, but I still saw a dual throw switching ? Small signal jfet is easy to source, don't they have some at reichelt ?