On Tue, 2020-06-23 at 10:16 +1200, Ewen McNeill wrote: > On 2020-06-22 23:09, Andrew Ruthven wrote: > > Is there another way to display the encoded content since the newer > > firmware images have been used at conferences, they must be > > working! > > I'm not sure that anything newer than v0.0.4-487-g5940dcb (2019-06- > 02) > *has* been used at conferences *for video capture*. ISTR both Carl > and > Ryan saying that they'd stuck with an "older" release for their > production captures, and there are some issues in the GitHub project > about problems with newer versions.
Ah, that is interesting. I was going by the "Use at" column on this spreadsheet: https://docs.google.com/spreadsheets/d/e/2PACX-1vTmqEM-XXPW4oHrJMD7QrCeKOiq1CPng9skQravspmEmaCt04Kz4lTlQLFTyQyJhcjqzCc--eO2f11x/pub > FWIW, the LCA2020 uses of the Opsis was pretty minimal, as there > were > issues getting them to interoperate with the venue SDI video senders > (built into the venue rooms), and IIRC those SDI video senders were > 1080p rather than 720p (the Opsis can't do 1080p60 for capacity > reasons). So instead a commercial product was used to do video > capture > at LCA2020. IIRC the Opsises were used only for one side element > (and > "speaker video testing" (pass through to projector) at LCA2020, > rather > than being more fully used for video capture at previous LCA, etc. Interesting, and also disappointing. But I can certainly understand that if 1080p is required that makes life difficult with the Opsis. > Carl might remember more of those details. But I wouldn't assume > "newer > than v0.0.4-487-g5940dcb" "must have" been working at conferences. As stated, I was using the information on the Google spreadsheet for my statement. > As Carl's later reply says, maybe there's some additional parameter > tweaks required. But it's also possible something in the USB video > stream got subtly broken by later builds (which pulled in lots of > upstream Litex changes), so I wouldn't immediately rule out the idea > that the USB video output is somehow invalid in later builds. The difference between the working v0.0.4-487-g5940dcb build and the "broken" v0.0.4-489-geaab51f build in the git repo is a one line change that looks highly unlikely to be the cause. That was the first thing I went to check. My expectation is that other modules which are pulled in for the build have caused the breakage or change in behaviour. Perhaps the build process should use versioned dependencies on other modules? If that is possible of course. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz | -- You received this message because you are subscribed to the Google Groups "hdmi2usb - A HDMI capture solution" group. To unsubscribe from this group and stop receiving emails from it, send an email to hdmi2usb+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/hdmi2usb/0eb9d483fbb5b49b23165f91c2030dcdc11cd958.camel%40etc.gen.nz.
