With iOS, as there is no Java virtual machine, there is a direct access to the hardware, so the latency is down to 5ms for a long time. If the latency is over 10ms, you can begin to feel a delay between, for example, the time you sing, and the time you hear what you're singing. There is not a lot of Android recording apps, multitrack recorder or things like that, because there has been a lot of work on the USB Audio specification ( which is part of all the USB specifications ) only in the latest Android OS, to allow the OS to work in realtime, with latency under 10ms. Oh, and moreover, that's not the first 24bit 96Khz device out there able to record on iOS. Januat 6:52PM, Edited September 4, 7:54AM Assuming it clocks well, which is another big question. To fix it you'd need to drag it into audio software to sync it, at which point why bother? PluralEyes would allow you to use the higher quality audio. I'm going to guess the processing speed on an iPhone isn't particularly fast, so you're probably looking at enough latency to make the audio incompatible - laying one on top of the other would result in comb filtering because of the delay. Even if it is close (and I would assume there's at least 10 ms being added in the first A/D conversion, so it wouldn't be that close), because of the multiple A/D/D/A conversions between the mic and the camera, the audio in the camera would be several ms off (latency). You could do it though, assuming that the audio is even audible out the headphone jack and that it's somewhat close to real time. Why would you want the same audio in both places, especially since the audio in the camera is going to be significantly lesser quality? If you're using the DSLR audio to try to resync the audio, it would make more sense just to record the crappy on-board camera mic and sync based on that.
0 kommentar(er)
