Hi,
Im using my Nord Modular as master midi clock with modular II drum box .......so the problem is that the modular II doesnt play with the right midi clock, the bpm that the modular II receives its always changing, you can see on the midi clock module the bpm changing. Because of that the bpm sometimes get diferent, and its dificult to work.........any sugestions or ideas please say something.
Thanks a lot
PS- I already put Modular II as master clock but the problem is that when i stop the drum box the last note of the Nord Modular( midi slave) continues to play...
Modular II drum box external midi clock problems
-
SonicTransportSystem
- Posts: 69
- Joined: Sat Oct 14, 2006 4:00 pm
- Location: Portugal
- Contact:
The clock is seen to shift around as the incoming messages shift slightly in time. The midi messages being sent to determine 'midi clock' are sent 24 times per quarter note (24ppq) and must contend with all other messages being sent through the midi port (notes & automation data will cause things to shift around especially as the amount of midi data increases). As the amount of data on a midi port/cable increases, the serial nature of midi insures that all the data must vie for a place in the outgoing data stream. The messages that establish midi clock are subject to shifting around (jitter), The computer's midi handling is also a factor, and a large one. The buffers for midi i/o and the processing of midi data on the cpu have overhead especially as the usage increases. Most modern software actually fares worse with stability of a midi stream than computers made 12-15 years ago (which were made to be realtime and not 'share' resources).
Scope's midi timing is actually quite decent, faring better than almost all usb devices i've seen, but since Mod II does no 'smoothing' or 'chasing' of the midi clock stream it reveals the jitter directly. The usual solution is to clock your modII/III patches internally and use specific external events to retrigger envelopes/lfo's etc so that things don't fall out of sync over time.
Scope's midi timing is actually quite decent, faring better than almost all usb devices i've seen, but since Mod II does no 'smoothing' or 'chasing' of the midi clock stream it reveals the jitter directly. The usual solution is to clock your modII/III patches internally and use specific external events to retrigger envelopes/lfo's etc so that things don't fall out of sync over time.
-
SonicTransportSystem
- Posts: 69
- Joined: Sat Oct 14, 2006 4:00 pm
- Location: Portugal
- Contact:
i've been out of scope for a while (due to 'other interests' but i'm planning to come back this summer with a new system), but i have seen atom building super tight patches with flexor modules from the ramp family. they take saw waves from your sequencer (make them with a rise that's 1 measure long). DON'T route these to channels that go to your monitors, but to an audio input on the modular. this will make your modules connected to the ramp in sync with the sequencer. how to route in modular and use of dividers etc, consult the real mod gods...
andy
the lunatics are in the hall
the lunatics are in the hall
That's essentially it. There's a ramp module in flexor that you can use to generate the ramp & record into your sequencer.
However he's interested in syncing to his nord I think, which means he'll need to use the ramp tool internally in the mod shell and drive it from gate messages triggered by an external note. 1 note per bar would do it, coming from the nord. I've got a pm here where he says that the nord has internal modules that send midi clock, but surely you can use the nord to sequence externally as well.
In fact using gate messages triggered by the notes on the nord in general would be enough to get things in better sync, even without using the ramp tools and flexor's sequencers that are driven by ramp. In fact retriggering things at intervals not on the bar alone does interesting things as well. Having filters & lfo's & envelopes retrigger as needed is a fairly straightforward task, whether it's mono, portamento or poly.
However he's interested in syncing to his nord I think, which means he'll need to use the ramp tool internally in the mod shell and drive it from gate messages triggered by an external note. 1 note per bar would do it, coming from the nord. I've got a pm here where he says that the nord has internal modules that send midi clock, but surely you can use the nord to sequence externally as well.
In fact using gate messages triggered by the notes on the nord in general would be enough to get things in better sync, even without using the ramp tools and flexor's sequencers that are driven by ramp. In fact retriggering things at intervals not on the bar alone does interesting things as well. Having filters & lfo's & envelopes retrigger as needed is a fairly straightforward task, whether it's mono, portamento or poly.
-
SonicTransportSystem
- Posts: 69
- Joined: Sat Oct 14, 2006 4:00 pm
- Location: Portugal
- Contact:
My friends, it seems that sync scoope modular II and other scoope devices with external master clock its a really dificult and complicated task....i dont understand why cause creamware soundcards are very good, but things happen.
i sync my nord modular with some of my other hardware synths and works perfectly, even with a standalone vst instrument works perfectly.....just with modular II and scoope devices doesnt work
Midi clock module with external bpm and freq divider module should do their job!! Other thing my friend valis i think that the Nord Modular analog style sequencers dont sequence external devices........Just Nord G2 can do that
i sync my nord modular with some of my other hardware synths and works perfectly, even with a standalone vst instrument works perfectly.....just with modular II and scoope devices doesnt work
Midi clock module with external bpm and freq divider module should do their job!! Other thing my friend valis i think that the Nord Modular analog style sequencers dont sequence external devices........Just Nord G2 can do that