Output on AJA IO 4K
Hi there,
We came across the Millumin software a few days ago and would like to use it only for the playback of video content at an event.
Our Setting is:
MacPro (Late 2013) with an AJA IO 4K connected via Thunderbolt 2.
We can see the AJA NTV2 at the inputs, but is there any way to use the AJA as an output?
Thanks in advance
best regards
Dennis
We came across the Millumin software a few days ago and would like to use it only for the playback of video content at an event.
Our Setting is:
MacPro (Late 2013) with an AJA IO 4K connected via Thunderbolt 2.
We can see the AJA NTV2 at the inputs, but is there any way to use the AJA as an output?
Thanks in advance
best regards
Dennis
Comments
thank you very much for the quick response!
At least we can see the IO 4K in the output popup with a variety of different output settings (resolutions & framerates).
That works!
Unfortunately there is a latency of approximately 15 frames and in addition the content looks very choppy, it seems like 12-15 fps to me (the result does not depend on which IO 4K output setting is selected – we tried several ones).
I think, we'll have to test a little bit.
If you have any idea, what will help here, please let us know.
Thanks and best regards
Dennis
some time has passed. Are there any news concerning the collaboration between Millumin and AJA?
Did you get a reply?
Our setting is:
MacPro (Late 2013) with an AJA IO 4K connected via Thunderbolt 2. Software is Millumin3 3.11.q
Unfortunately, we do not get a working 1080i50 signal from millumin.
There still is a latency of approximately 15 frames and the content looks very choppy, it seems like 12-15 fps to me.
Working with 1080i60 brings less choppiness and less latency, but is not perfect.
But anyway this is no solution for us - for one particular event we do need an output in 1080i50 since we provide the millumin signal to the main video event mixer that requires 1080i50.
Do you have any further suggestions or news concerning this issue?
Thanks in advance!
Best regards
Dennis
Best. Philippe
thanks in advance! Unfortunately, we didn't receive an email with the intermediate version.
But we downloaded and tested Millumin 3.12.o (beta), please see the results below.
Our hardware setup:
MacPro Late 2013 with macOS
10.14.6 (Mojave)
AJA IO 4K (Firmware 4K 2019/05/22), AJA drivers 15.2.3.2
Test results for Millumin 3.11.q
1080i50 / 1080p25 / 1080p50 (our relevant formats):
- latency of approximately 500-600ms
- content looks very choppy
720p50
- a little less latency and choppiness, but still useless
720p60
- not choppy, nearly no latency.
Test results for Millumin 3.12.o (beta)
1080i50 / 1080p25 / 1080p50 (our relevant formats):
- still a latency of approximately 500-600ms
- content does not look choppy!
So, with the 3.12 beta, the result looks just fine!
But the latency is still there in all 1080 output formats and 720p50.
No problems in 720p60.
Do you have any further suggestions?
Thanks and best regards,
Dennis
since we didn't come to a satisfactory result with the AJA IO 4K, we changed the output hardware to Blackmagic.
For us, only outputs in 1080i50 or 1080p25 are relevant. But nevertheless I'd like to share our test results:
Our hardware setup:
MacPro (Late 2013 with macOS 10.14.6 / Mojave)
Blackmagic Design UltraStudio Mini Monitor / Driver: BM Desktop Video Setup 11.4
Output connection: MacPro → Thunderbolt2 cable → BM Mini Monitor → SDI cable → Production Monitor / video mixer
Test results for Millumin 3.11.r (latest official)
SDI video output 1080p25:
- latency of approximately 2-3 frames, content still looks a little choppy
SDI video output 1080i50:
- latency of approximately 2-3 frames, content still looks a little choppy
- signal is technically interlaced, but looks like de-interlaced (see below)
Test results for Millumin 3.12.p (beta)
SDI video output 1080p25:
- latency of approximately 2-3 frames, NO choppyness
SDI video output 1080i50:
- latency of approximately 2-3 frames, NO choppyness
- signal is technically interlaced, but looks like de-interlaced (see below)
We than thought that the Millumin 3.12.p is the dealbreaker, so we also tried to use the AJA IO 4K for the video output again. The result:
SDI video output 1080p25
- latency of approximately 12-15 frames, NO choppyness
SDI video output 1080i50:
- latency of approximately 12-15 frames, NO choppyness
- signal is interlaced AND looks like interlaced!
For us a latency of 2-3 frames is acceptable, but 12-15 frames aren't.
So with the Blackmagic Moni Monitor and Millumin 3.12.p, at least we have a solution for our upcoming event in November, though we'll have to to take the risk of using the beta version for production.
But there is one more thing for the Blackmagic setup / 1080i50:
Within Millumin, we chose 1080i50 for the output format. Different Monitors recognized the incoming signal technically as 1080i50, but there seems to happen a conversion / de-interlacing between Millumin and the BM Mini Monitor as the content definitely doesn't look like 1080i50. To check that, we played the same content out of Premiere Pro via the Blackmagic Mini Monitor and that comes in a perfect 1080i50. And even with the AJA output, the 1080i50 looks like interlaced.
It's no problem for us, but strange.
I'd appreciate to get an answer to the following questions:
- when will the version 3.12 become official? Of course we would be more relaxed if we did not use a beta version in production
- if there was a possibility of delaying the audio of certain elements or even the entire output, this would be very helpful. Is this option possible or planned?
- do you have any idea why the AJA IO4K is able to deliver a perfect interlaced 1080 signal out of Millumin and the Blackmagic isn't? (the higher latency does not allow us to use the AJA)
Thank you very much in advance and best regardsDennis
# When will the version 3.12 become official ?
We hope very soon. In the next weeks.
However, delaying audio or video is a good idea. Feel free to submit it on Uservoice, so we could check if other people are interested.
From a technical point-of-view, we only pass the texture to Blackmagic library, that does the rest of the job (I guess, converting the texture for the device, then uploading it to the device).
So, I don't have an explanation, sorry. And I really don't understand why there is such a difference with Premiere (that is using the same Blackmagic library). Feel free to send us pictures of the phenomenom via email, so we could create a ticket for this.