03-04-2021, 04:19 AM
(This post was last modified: 03-04-2021, 04:29 AM by MrBlaschke.
Edit Reason: Spelling errors
)
Hi Jesse.
Actually no. It plays at the correct speed.It seems to be only the display.
I know and understand that there is no benefit in connecting all 4 ports for that and there is NO PROBLEM in AUM as AUM can address each port separately and can only send a clock signal to one external device, at least without custom scripting technologies.
Like i mentioned the problem occurs with, for example, Cubasis 2 on iOS. You can only enable „Send clock“ but no possible setting to where or what ports. It just sends. So a test in AUM is not necessary at all as it works there.
But i think there is more out there that just does not have the possibility to specifically send something like the clock to a dedicated channel/virtual input.
So this should possibly tracked down inside the NDLR to just accept 1 clock signal and not sum them up if there are “several”.
I can make screenshots and everything you want/need - but i think the problem is pretty straight forward.
The signal chain/connections are:
iPad -> CameraConnectionKit -> USB Hub -> NDLR
The HUB is not affecting it in any way! Even a direct connection from the CCK -> NDLR does the same thing.
Thanks for investigating!
Actually no. It plays at the correct speed.It seems to be only the display.
I know and understand that there is no benefit in connecting all 4 ports for that and there is NO PROBLEM in AUM as AUM can address each port separately and can only send a clock signal to one external device, at least without custom scripting technologies.
Like i mentioned the problem occurs with, for example, Cubasis 2 on iOS. You can only enable „Send clock“ but no possible setting to where or what ports. It just sends. So a test in AUM is not necessary at all as it works there.
But i think there is more out there that just does not have the possibility to specifically send something like the clock to a dedicated channel/virtual input.
So this should possibly tracked down inside the NDLR to just accept 1 clock signal and not sum them up if there are “several”.
I can make screenshots and everything you want/need - but i think the problem is pretty straight forward.
The signal chain/connections are:
iPad -> CameraConnectionKit -> USB Hub -> NDLR
The HUB is not affecting it in any way! Even a direct connection from the CCK -> NDLR does the same thing.
Thanks for investigating!