how to send Midi Message

[Nowhk]

Be sync with sample rate doesn't mean that "control rate" in Ruby (100hz) runs at the same speed (else Ruby will run at 441khz, destroying CPU), just that it sync/align audio with events (handled at 100hz, down to 10 MS as Tom said), for what I see. Since an event can occurs at different sample/time, it quantize the timestamp I guess (I dont know, I ask you).
But this seems to works only for generated audio within FlowStone.

My problem, as stated in the other topic, is that MIDI outside FlowStone are not sync... (and Malc seems to confirm this in a recent mail; even if I need a confirm).

So, those "gazillion" of arpeggiator you are talking about could (in fact) be not solid.

Have you an example that I can try? I dont find any honestly...

[Nowhk]

But this seems to works only for generated audio within FlowStone.

I quote myself, because I've already try this, and it seems thats also not true

Check this schematic (or directly the FL12 project) in your DAW (there is a Playing prim):

Internal MIDI Sync.fsm

(163.35 KiB) Downloaded 969 times

Internal MIDI Sync (FL12).zip

(334.75 KiB) Downloaded 908 times

Press play, and record 2 shoot. Than compare them: reverse phase of one and play together (or just press play on the FL 12 project where I've already set all): null test FAILS. You can hear audio.

Thus, MIDI are not triggered at the same time, neither within FlowStone.
(note: I'm on 3.0.8, but from the Version list I don't see any update in 3.0.9 that could fix this).

Follow 2 recordings I've already made, so you can compare them directly if you don't want to test all...

[Nowhk]

Here's two recordings of the "same" session. 120BPM, 4 bars:

rec 001.zip

(1.3 MiB) Downloaded 920 times

rec 002.zip

(1.3 MiB) Downloaded 874 times

they seems equal, but they are not (try the null test I've suggested above). Thus, neither inside FlowStone MIDI/Ruby/Audio seems to be SYNC

[nix]

Here is the null->

null_0.png (15.64 KiB) Viewed 18009 times

original->

null_original.png (12.01 KiB) Viewed 18008 times

[Nowhk]

Here is the null->

null_0.png

Thats not null Theres a problem... isn't?

Can you post please to me that module to check "null"? So I wont use FL for tests...

[nix]

mem subtractor_0.fsm

(9.29 KiB) Downloaded 916 times

it's not user friendly,
just a quick sampler mod

Yeah- something's up, it is very close though and almost cyclical

[Nowhk]

I'll check it out, thanks.
Yes its cyclical, but for "Session". I mean, those shot are recorded in parallel. If I record other 2 rec, the cyclical is again, but on different point.

Its a "random cyclical".

Even if its close, under heavy distortion plugin that could make huge differences...

[tulamide]

Check this schematic (or directly the FL12 project) in your DAW (there is a Playing prim):

Internal MIDI Sync.fsm

Your schematic once again tries to take over control against the DAW. As long as you try that, you will have issues.
(1) You are not sync'ing at input, you are just asking if the DAW is playing.
-> You should have asked if there is a midi note incoming.
(2) You are not sync'ing to PPQ, instead you just sync'ing to time.
-> You need to sync to PPQ
(3) You don't use frame sync, which is what the outputs (here DS Out) are using. A frame is the buffer, to which all audio data is written.
-> Use frame sync

If you do all three, you are sample precise in sync (minus all imprecisions that may be introduced by the DAW).

[Nubeat7]

beside tulamide's explanation about sync to daw, i tested your schematic in cubase:

i exported your testschematic over 4 beats (using one of my fs synths) to audiofile (2 times)- loaded both files - inverted the phase of one file - exported the summed output - and what a surprise, null! just a zero line on both channels!
so 2 times recorded and the files are exactly identical, which proofs the stability of the ruby timing!
here are both recordings, so you can proof yourself....

btw. sorry walter, looks like your thread was hijacked
maybe nowhk wants to continue on his original thread now

[Nowhk]

btw. sorry walter, looks like your thread was hijacked
maybe nowhk wants to continue on his original thread now

Yeah sorry, I guessed it was a related problem, thus I wrote here. My problem follow here viewtopic.php?f=2&t=3959&p=23686#p23686