I recently got an Intensity Pro 4k to replace my Intensity Pro, which served me well for more than 6 years. It has mixed reviews on the internet, but mostly because of one of two reasons:
- Noise, which was indeed terrible but is fixed completely by updating the firmware.
- Software compatibility, which I can’t speak for. I only use one piece of software and I make that one compatible if it isn’t.
BMI Pro 4k to the left, BMI Pro to the right
I have to say that the device has worked pretty flawlessly for me. Nice to finally get full RGB input and 1080p60 capture.
Of course, to actually make use of those features I had to release a new version of PtBi. Since it’s a pretty major upgrade I decided to call it version 6 now. More specifically, the release is 6.1877. In addition to supporting the new pixel formats PtBi should now also produce somewhat more useful messages on errors.
It’s still not quite user-friendly though. You have to select the pixel format and video mode with command line parameters, e.g. PtBi.exe -disable-audio -pf=ARGB -mode=1080p5994. The supported modes are ARGB, BGRA and YUV (which is the default and only option in previous versions). I don’t support 10bit modes since I don’t need it — if anyone really does it shouldn’t be too hard to add.
I also pushed the current source to GitHub, what was there was completely outdated. It’s still terrible though, which is about what you’d expect from a project developed for a few days here and there over 6 years, and built on code even older than that. However, it does it’s job, and it’s the only thing which does that particular job, and I still use it all the time, so perhaps it’s useful to someone.
I have the intensity shuttle too and would like to know where would you place that line to get PTBI working?
Try whether the latest version works for you.
I don’t know if its BMD’s drivers or what at this point. I’ve yet to get any kind of RGB input working on the Intensity 4k through HDMI from my PS3, PS4 or my video card over the last several months since I got it.
Using my video card YCbCr 4:4:4 works in PtBi and YCbCr 4:2:2 has messed up colors. Both RGB 4:4:4 Limited and Full don’t work and give a black screen using either modes in PtBi which is needed for the PS3 and PS4 over HDMI.
Hmm, I’ll give my PS3 a try. So far I’ve only used the 4k with the Wii U.
ou are using some kind of HDCP stripper I assume? The output from the PS3 is encrypted.
Yeah, I’ve been using a Monoprice 105369 for HDMI on the PS3. It was working properly with the Intensity Pro and the PS4 just has an option to turn HDCP off.
It’s awesome to get an update and I’m going to order a 4k almost immediately. This new version still has the issue where anyone using a USB intensity shuttle can’t get audio through the device. It immediately crashes and gives this error:
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 0 < (7000 * 2)
NOW BUFFERED: 2000
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 2000 < (7000 * 2)
NOW BUFFERED: 4000
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 4000 < (7000 * 2)
NOW BUFFERED: 6000
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 6000 < (7000 * 2)
NOW BUFFERED: 8000
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 8000 < (7000 * 2)
NOW BUFFERED: 10000
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 10000 < (7000 * 2)
NOW BUFFERED: 12000
———- 2015-07-16_18-05-35
AUDIO BUFFER OVERRUN: 18404 > (AUDIO_BUF_OVERRUN_LIMIT * 2)
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 10148 < (7000 * 2)
NOW BUFFERED: 12140
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 0 < (7000 * 2)
NOW BUFFERED: 2000
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 2000 < (7000 * 2)
NOW BUFFERED: 4000
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 4000 < (7000 * 2)
NOW BUFFERED: 6000
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 6000 < (7000 * 2)
NOW BUFFERED: 8000
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 8000 < (7000 * 2)
NOW BUFFERED: 10000
———- 2015-07-16_18-05-35
AUDIO BUFFER UNDERRUN: 10000 < (7000 * 2)
NOW BUFFERED: 12000
Yeah, I’ve heard of this issue before. Still haven’t tracked it down though. I don’t have a Shuttle, and as I said in the post, the PtBi code base is a bit of a mess. I’ll try to look into it.
I get the same error sometimes on an Intensity Pro 4K.
I tracked it down to audioPacket sometimes being NULL in VideoInputFrameArrived when the program is just starting up.
I just added ” && audioPacket” to “if(!disableAudio)” and it seems to fix it. Not sure if that has an effect on audio latency though.
Good catch! Thanks for that.