Hidden multitrack recorder

[broc]

Conversion to seconds could be the problem.
Try removing [/ 44100] and replace [+ 3] by [+ 128000].

EDIT:
I've recorded 2 files on separate tracks and got a length difference of exactly 4096 bytes.
It looks like a timing problem with internal buffers possibly related to multi-threading.

[qbas]

broc tank you for your last Edit.

Actually I have no other idea how to realize synchronization between m4l devices.
So if no other options, maybe I should use your earlier idea with synchro to “next bar”,
but yes, you mentioned earlier that it is no ideal, as some devices can receive message from MAIN device to SLAVE in different time (sometimes even before “real” next bar, and sometimes after) – then no way to synchronize.

[Valiumdupeuple]

I didn't read the whole thread, so forgive me if I'm out of the subject, but why no;t just simply use a 2nd instance of Live, which would receive audio using "external audio effect" devices and soundflower... ?
Like this:


With "agregated device" and soundflower you can have many virtual out/in ports.

[broc]

AFAIK, multiple instances of Live (or any other app) are not officially supported on Mac.
Are you sure that it doesn't produce some unwanted side-effects?

[qbas]

I didn't read the whole thread, so forgive me if I'm out of the subject, but why no;t just simply use a 2nd instance of Live, which would receive audio using "external audio effect" devices and soundflower... ?
Like this:


With "agregated device" and soundflower you can have many virtual out/in ports.

Thanks for suggestion.

Even if I will find similar solution for PC it will change performance of mine CPU/Live/ASIO driver.
Always is possible to buy next better laptop, surly it is a solution - but when main setup works.
Before buying next computer I would like to know that the money is the only problem.

Now I use 1.8 ms output latency and 3.2ms input (Roland OCTA-CAPTURE). I can go even lower value, but on mine C2D 2.4 lower latency produce too noticeable lag during switching programs in Zebra etc. On mentioned values (1.8 and 3.2 ms O/I) I have acceptable small drop in audio , which I will eliminate in future by buying faster computer. Best would be to record everything in Live, as it will manage disk usage together with other processes. Even separate recording in m4l will add next 20-40% usage of CPU (when will record on multiple tracks). Recording in Live is much easier for CPU as I checked.

Now I have Liveset consist from 4 Zebra tracks (input MIDI CH 1-4), 4 samplers tracks CH 5-8 (on each track is rack with many samplers, chain selector is remote changed via m4l device placed before, which receive Program Change). Nine track receive on 16 CH and have only Kapture modified to receive Program Change value. In other words on 9 track I receive MIDI CH 16 Program Change which change snapshots in Kapture. This way I use Live as host, mixer, instruments/effects, and editor for audio and MIDI files that I place in MC-808 (groovebox).

If I will not use Live to playback any clip during show, then probably it is OK for me to use Live as recorder also (because I don’t like to play and simultaneously record in Live during gig). This is my latest idea. This way I have some limitation (for example I have no warping in Live samplers), but we always have an compromise.

At this time I would like to thank you for your all attention, help and trying.
I’m OK with such limitation, it is still great setup for me.

Anyway if somebody have different idea, I will be thankful for share.