MUFF WIGGLER Forum Index
 FAQ & Terms of UseFAQ & Terms Of Use   Wiggler RadioMW Radio   Muff Wiggler TwitterTwitter   Support the site @ PatreonPatreon 
 SearchSearch   RegisterSign up   Log inLog in 
WIGGLING 'LITE' IN GUEST MODE

FH-1 LFO
MUFF WIGGLER Forum Index -> Expert Sleepers  
Author FH-1 LFO
JoPo
Hello !
I've got another question about the FH-1.

What does trigger the LFO ?
Suddenly, an output was oscillating slowly : its LFO started but I'm unable to understand why, when and how it has been triggered.

How lfo are triggered and how can I stop them ?

Thank you !

................

Ah ! I noticed that the LFO starts when I send a "init midi" from cubase. I guess it sends 'note off' message = cc123 and maybe cc121 & 122 = init controlers & all sound off.
But I don't see those midi cc's in the script page. So, I don't know.

I show you the script I entered in the module (with 2 expanders I just want the FH-1 + its 2 expander to react to midi cc 12-->35 on outputs 1-->8 from each module) :

FH-1 script v1
MCV1:
MCV2:
MCV3:
MCV4:
MCV5:
MCV6:
MCV7:
MCV8:
MCV9:
MCV10:
MCV11:
MCV12:
MCV13:
MCV14:
MCV15:
MCV16:
RC1
CC12-35:1:0
RC3
CC12-35:3:0
RC5
CC12-35:5:0
HEXB04032
HEXB04132
HEXB04232
HEXB04332
HEXB04432
HEXB04532
HEXB04632
HEXB04732
HEXB04832
HEXB04932
HEXB04A32
HEXB04B32
HEXB04C32
HEXB04D32
HEXB04E32
HEXB04F32
HEXB05032
HEXB05132
HEXB05232
HEXB05332
HEXB05432
HEXB05532
HEXB05632
HEXB05732
os
CCs 121-123 correspond to items on expanders 3 & 7, according to the chart.
JoPo
Ah... So I don't understand why a cubase midi initialisation triggers the LFO.
Gonna use a midi monitor to see what cubase send when initialising midi.
So, apparently, cubase sends :
- CC1 = 0
- CC2 = 0
- CC64 = 0
- CC121 = 0
- CC 123 = 0
- aftertouch = 0
- pitch wheel = 0
on each midi port / channel of used midi track when initialising midi :




(And same or all other channels & other midi ports)

So, I've got 2 questions :

- Would that triggers FH-1 lfo ?
- Is there a way to stop the lfo or at least to set its depth to 0 when it accidently started ?

Thank you !
os
CC 64 value 0 on MIDI channel 9 would activate a sawtooth LFO (most LFOs are disabled by value 0, but sawtooth is centred around 64).

The easiest way to work around this would probably be to activate the 'sustain' option on the MIDI/CV converters, which then remaps CC 64.
JoPo
I did it !! I remaped channel 9 cc64 to cc65.
But there is something very weird ! When I set the script generator to remap channel 9 cc64 to cc65, it write those 2 lines :
RC9
CC65:9:64.

But according to the FH-1 manual,
« RC3
CC2:1:5 means remap CC 2 (on MIDI channel 3, as set up by the RC
command) to CC 5 on MIDI channel 1 ».

For the manual, CC65:9:64 should remap CC65 to CC64, right ? So I inverted (because CC65:9:64 didn't avoid the saw lfo to start) and writed this line : CC64:9:65 and yeah ! The saw lfo doesn't start anymore when the FH-1 receives a 0 value on channel 9 CC64 !

Unless I missed something, which is strongly possible (!), the script generator didn't give me the right remapping code !
I took a screen pic to show you (those 2 lines didn't avoid the lfo to start) :



Anyway... I'm glad I achieved to do as I wanted ! Thanks a lot !
os
That looks right to me. 'CC65:9:64' means take an incoming CC 65 and map it onto CC 64. It doesn't say anything about what to do with an incoming CC 64, which is your situation.
JoPo
Ah ! Ok. So, CC64:9:65 avoid to trigger the lfo because cubase sends a 0 value on CC64, which becomes 65 and the lfo remains asleep.

Ok. I understand ! d'oh!

Thanks a lot !

I've got another question but I'll start a new topic.
MUFF WIGGLER Forum Index -> Expert Sleepers  
Page 1 of 1
Powered by phpBB © phpBB Group