|
|
Post by crony on Aug 24, 2018 17:15:05 GMT
Hi Nic, Coud it be possible to have a virtual port on SreamByter AUv3 ? Maybe that should be an instrument with a virtual port ? (to keep it light ?) In fact, into AUM I may assign the clock only to instruments with a virtual port, but I can only assign the clock to 1 instrument... The purpose here would be to "plug" the AUM's clock into SB, then SB would send to multiple synths or midi stuffs... Even with a quite direct clock (just one "hop") I have variations off 1 bpm on the receiving synths, it's quite good ok, but it's not perfect...That's why I'd like to send the clock from the iPad "locally" from AUM which is sync with Link and have the tempo set and fixed (or seems...) Hope that makes sense...  |
|
|
|
Post by crony on Aug 24, 2018 17:45:18 GMT
Ok, my bad, the clock moves from 0.1 to 0.3 bpm, that's causing the variations...
But still, a virtual host for SB would be useful to me...
|
|
nic
Soapbox Supremo 
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Aug 25, 2018 8:01:43 GMT
Hi crony , I think you mean that the StreamByterAU advertises (and operates on) a CoreMIDI virtual port? In my mind, I thought an AU would not be technically allowed to do this, but I see there is an app that does, so I think it could be done. However, in AUM why would you need to distribute the clock with StreamByter? Can you simply route the AUM clock to the various destinations directly? I guess something like this would be possible: - Each AU instance advertises a virtual input and output and gives them a unique number so they can be distinguished by the user. - It listens to both sources of events (AU and CoreMIDI) in parallel and sends outgoing events to both destinations. I will look into this for a future release, but cannot make any promises. Regards, Nic. |
|
|
|
Post by crony on Aug 25, 2018 15:02:49 GMT
Hello Nic, Yes, as a CoreMIDI with a virtual port. But if possible, to keep it super light, and not having dozens of SB virtual ports to choose within synths,(that would generate bugs, I know that for sure for at least one synth : DRC that can't show more than 10 midi devices, they'll correct that, but not until next year...) it would be a different kind of AUv3 instrument (instrument / generator / instrument with virtual port ?) In AUM you may choose to send his internal clock to 1 virtual or hardware port only... As AUM got Link, I suppose his clock will be the most solid and consistent I could get locally. I'm using 4 iPads, and clock is drifting a bit between 2 iPads, even with one midi hop. Using bluetooth is tighter, but I don't "trust" bluetooth for long sessions with a clock. So, in my mind I'd use midi interfaces for midi controllers (cc, notes...no hop here, direct connection) then midi notes and cc's for midi tracks using bluetooth, then clock distributed locally coming from each iPad from AUM dispatched by StreamByter... Very specific demand indeed...I might find a workaround...I keep testing... |
|
|
|
Post by crony on Aug 25, 2018 15:43:31 GMT
Ok...
I tried to send clock from Xequence to AUM, then send to SB, then to bluetooth.
Clock is chaotic...
Seems logical as input should not meant to be a clock initially (AUM does not receive clock...it can generate it, but not designed to receive it at all, relay it between other stuff, yes, but not directly getting it)
So only solution here, seems, SB with CoreAUDIO.
Going to ask Jonatan if AUM could at least relay the clock even if he doesn't generate it...
|
|
|
|
Post by crony on Aug 26, 2018 10:59:53 GMT
Ok stupid previous statement... I had some other mdi in/out running from other apps and hardware... AUM seems to relay a kind of stop message, but is not relaying the play. I managed to have one clock locally on each ipad but some synths app are just not stable enough (with Link) but it works quite fine. I guess my demand is a bit useless...or far too specific... Anyway thanks for your amazing support as usual |
|
