Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Clock Output
#1
the clock output does not seem to be registering in the mordax data clock divider setting?  I measured a voltage output of 4.74 from the clock output of the nerdseq vs. 5.67 coming out of the Ultra Random Clock out which the Mordax does read as an external clock

I boosted the clock signal with a vca to about 5.23 (hard for me to dial this in exactly...davies FML) and seems to do the trick.

Can this be adjusted in a firmware fix?
Reply
#2
I don't see any bug here, neither a crash, so i moved this to General Questions.

The clock voltage is around 5 Volt (a bit less here) which is totally fine. If the Mordax can't read it, then the settings in the Mordax have to be changed if possible.

Check the Doepfer Eurorack Specs for Clock / Trigger voltages.
Beyond 3 Volt should be treated as 'High' and below 1 Volt should be treated as 'Low'. Between is undefined and can be different with every module.

http://www.doepfer.de/a100_man/a100t_e.htm
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#3
(08-11-2018, 06:19 PM)XORadmin Wrote: I don't see any bug here, neither a crash, so i moved this to General Questions.

The clock voltage is around 5 Volt (a bit less here) which is totally fine. If the Mordax can't read it, then the settings in the Mordax have to be changed if possible.

Check the Doepfer Eurorack Specs for Clock / Trigger voltages.
Beyond 3 Volt should be treated as 'High' and below 1 Volt should be treated as 'Low'. Between is undefined and can be different with every module.

http://www.doepfer.de/a100_man/a100t_e.htm

thanks.  i reported it to Mordax along with your link to the doepfer standard.

I see the part about "Within the A-100 usually any voltage beyond about +3V is treated as "high" (e.g. +5V, +8V, +10V, +12V will work) and will trigger an ADSR or any other module with a Gate or Clock input (e.g. trigger delay, sequencer, clock divider, clock sequencer). Any voltage below 1V is treated as "low". If the specification of a module differs from this voltage standard it is mentioned in the description of the module in question."

Hopefully Mordax will get this adjusted

Cheers
Reply
#4
Mordax hasn't responded on this one Sad

however at least one person is hinting that 0-5v is the standard Sad (regardless of the doepfer standard, idk).

https://www.muffwiggler.com/forum/viewto...78#2890778
Reply
#5
(08-19-2018, 02:05 PM)digitalohm Wrote: Mordax hasn't responded on this one Sad

however at least one person is hinting that 0-5v is the standard Sad (regardless of the doepfer standard, idk).

https://www.muffwiggler.com/forum/viewto...78#2890778

In fact he is wrong. They are always threshold voltages with digital inputs.(which trigger inputs are)
And the levels mentioned by Doepfer are very common. Handling only 0 and 5 Volt would be a bad plan as they are always little differences in voltages. Handling a reasonable threshold is essential.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#6
I am getting a minus 2-3 BPM through both MIDI out and the clock out. I also get a 2-3bpm difference when receiving MIDI. This is consistent every time, is there a way to fix inside the NerdSeq?
Reply
#7
(12-23-2018, 08:53 AM)mpiecora Wrote: I am getting a minus 2-3 BPM through both MIDI out and the clock out. I also get a 2-3bpm difference when receiving MIDI. This is consistent every time, is there a way to fix inside the NerdSeq?

The BPM output is still in investigation. However, it is absolutely stable in sync with slaves, so there is in fact no issue beside that it might (and i still can't confirm this) show the wrong value.

For Midi reception, how do you know that there is a difference? If the NerdSEQ is set to slave then it doesn't show the BPM. Also here, being master and slave it is always perfectly synced and not running off.

I get onto the exact BPM measuring again after the christmas days.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#8
I noticed recently that Make Noise LXD and Optomix dont go as brighter when stroke with Nerdseq triggers compared with triggers from another modules. So it makes sense now knowing that the triggers have slightly lower voltage.
Reply
#9
(12-27-2018, 03:11 PM)premini Wrote: I noticed recently that Make Noise LXD and Optomix dont go as brighter when stroke with Nerdseq triggers compared with triggers from another modules. So it makes sense now knowing that the triggers have slightly lower voltage.

The voltages are in the correct range / not too low!! I think you trigger them too short...

Again: +3Volt and higher must be treated as 'High/ trigger'.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#10
(12-27-2018, 03:47 PM)XORadmin Wrote:
(12-27-2018, 03:11 PM)premini Wrote: I noticed recently that Make Noise LXD and Optomix dont go as brighter when stroke with Nerdseq triggers compared with triggers from another modules. So it makes sense now knowing that the triggers have slightly lower voltage.

The voltages are in the correct range / not too low!! I think you trigger them too short...

Again: +3Volt and higher must be treated as 'High/ trigger'.

The trigger works, no doubt. but LPG are higly senitive of the voltage amount of a trigger. I even pass them thru an attenuator sometimes to get different tones.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)