Fader Automation

Well done! :smile:

 

 

I check different bit resolution, but when monitoring the value I can’t go better than 8bits ???

 

Which MIDI events are you using to send & receive the value?

 

For more than 7bit you need either NRPNs, Pitchbend or SysEx

 

Best Regards, Thorsten.

Well done! :smile:

 TKS !!!

without your system it will never happen

 

 

Which MIDI events are you using to send & receive the value?

 

For more than 7bit you need either NRPNs, Pitchbend or SysEx

 

Best Regards, Thorsten.

 

I use pitchbend of course

the AINSER respond to the bit resolution up to 8 bit but not more

if I set resolution=4 i got 16 PB value in the 16384 range, steeped by 1024, this is OK

If I set resolution =8, the step is 64 which mean 256 value in the16k PB range, this is OK

But if i set resolution= 9, 10, 11 or 12 the step 64 is the same as before with 256 value (8bit) !!! this is NOT ok

Any idea ?

Best

Zam

Nobody for my AIN resolution problem ? I have a look around here but find nothing

 

another “disappointment” I have since yesterday, It has nothing to do with MB_NG but it’s about the MCU protocol,

I discover that all the led for solo, mute, etc are updated in a 1/2 sec range, not when you press a button…

Consequence is that I can’t use any of this data to drive a relay driving an analog mute system.

By now my working solution is to use another midi port (not the same as MCU) and automate my mute in a midi track with midi note.

The less … it’s not user friendly like having the mute directly in the DAW channel, the same as fader and audio file

The more … as it is separate midi track, I can insert midi FX like time triming, or arpeggio like a pattern sequencer for mute automation

 

Zam

I’ve to check the resolution at my side, I’m surprised that it doesn’t work like intended

 

Best Regards, Thorsten.

I’ve to check the resolution at my side, I’m surprised that it doesn’t work like intended

 

Best Regards, Thorsten.

Yes it will be great

For info my configuration is STM32F4, AINSER64 and AOUT_NG

Best

Zam

I found the AINSER64 resolution bug and fixed it in this version:

http://www.ucapps.de/mios32/midibox_ng_v1_033_pre6.zip

 

Here a usage example:

http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fainserhq.ngc

 

Best Regards, Thorsten.

I found the AINSER64 resolution bug and fixed it in this version:

http://www.ucapps.de/mios32/midibox_ng_v1_033_pre6.zip

 

Here a usage example:

http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fainserhq.ngc

 

Best Regards, Thorsten.

Master Thorsten !!!

tks :slight_smile:

I confirm the bug correction, 1.033 pre6 work fine here

Now I need to lower the jitter :slight_smile:

Best

Zam

Proto 2

here it is !!!

 

quick spec:

-motor analogue PI driver

-analogue touch detection

-512 steep (9bit) without jitter (can be better with shielded cable from AOUT and to AINSER)

-cross talk digital/motor to audio … less than my console noise floor !!!

-acoustic noise… did the fader move ?

-response time better than 120ms for 100%travel 100mm

-response time better than 80ms for 100% travel 33mm

-never over shoot

-two automation pass with complex audio material result in null phase test 50dB below my line level, in static condition of course (when fader reach the target)

-to null audio under my console noise floor with two automation pass, I don’t need to trim one more than +/- 0.01 dB !!!

 

I stop talking, this is better than wordshttps://www.dropbox.com/s/o6v29atn209kyxi/proto%20II.mov?dl=0

 

Best

 

Zam

Some update

I just test the TKD fader

Amazing!

For those who can afford 5x the price of the cheap ALPS and need high-end spec, i recommend it.

It’s completely another league :slight_smile:

Best

Zam

where did you get your TKD Fader? And whats their price? 

where did you get your TKD Fader? And whats their price? 

Hello

 

For the CP line, as I say, it’s 5x the price of ALPS, around 110euros

Look at website http://www.tkd-corp.com/index-en.html you will find distributors depending of your location.

 

Best

Zam

Thank you zam,

 

i’ll have a look, and send the distributor an email… but 110e for one fader may be a bit too much for my purpose. i am actually using the ALPS one from reichelt, but it sounds like an old printer from the 90s… 

If you don’t need fader with audio track forget the TKD, or look at other series with only servo and touch.

The “old priner sound” is not due to fader nor the fitted motor, it’s linked to the PWM and H bridge.

Zam

Hey all

Long time without update on this topic, sorry for that.

In fact I just take the past few month to evaluate the prototype…daily use in a full album production.

The best possible crash test !

It’s a positive experience, even if it need little improvement here and there  (I’m working on it!!!) , the whole system run rock solid :slight_smile:

Zam

 

Hi Zam 

are you going to share your config and work somehow? 

Regards, novski

Hi Zam 

are you going to share your config and work somehow? 

Regards, novski

Hi Novski

What do you want to know ?

The config is the same as the begining.

the improvements are more in the interaction with analog side to reduce digital/analog cross talk.

Like shielded wire, frontpanel grounding etc. it’s so specific to my console mechanical integration, I don’t know what to say ?

Best

Zam

Hi

I still have digital noise crosstalk, it’s “acceptable”, but I really like to do better

I think I find the EMI sources, with the CLK at ribbon cable to J1.

I have some result with a grounded copper screen around the ribbon, but I would like to try to reduce the clock noise upstream.

So my question is simple,

I scope a 1.4us square wave (giving me 71.4kHz clock right ?), is that the SR scanning???

I’m little confused because at audio side I’v got 4.6kHz peak noise, with ALL the harmonics coming with

So if someone can confirm me the SR clock so I can calculate and try some filter in the clock line

Zam

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 :slight_smile:

Zam

some news

After one week fighting to recover my kicad project in the suddenly dead PC (exactly when I trace the last gerber pcb !!! unbelievable …), I finally was able to install stable Kicad to an OSX10.11.

I just ordered the PCBs :slight_smile:

Best

JS

I want to update but can’t insert pict :frowning: