The headline: I rolled back to version 5.4.2 and PAYDIRT!! Immediately I got a round dot, I clicked the round dot, it changed to a square dot, I left it like that for about ten minutes, then clicked the square dot and, after a few seconds, I had a playable watchable file with 640 x 360 and AAC audio sampled at 48k. (One peculiarity: playing it in VLC resulted in audio that switched on and off at one-second intervals; then I switched to the GOM player and all was well.)
With Versions 5.5.0, 5.5.0a21, 5.6.0a1 and 5.6.0a2 the results were always the same: no live stream made available for capture but a bunch of files for download. I attempted to capture first the highest resolution version, which was 1280 x 720. The green bar moved steadily until about halfway through and then stopped moving. After waiting five minutes, I clicked the entry and I got the message that the file was finalizing, and then I waited for about anther ten minutes but nothing further happened. I clicked the X to stop the finalizing and that was that: no capture, no file.
Then I picked the 640 x 360 version to download. Same thing to start with, a steadily moving green bar, like everything was fine. I waited and watched as the green bar kept moving steadily, past the halfway mark, past the two-thirds mark, past the three-quarters mark, past the 90% mark, and, eventually, all the way. At which point, VDH announced the file was ready for playback; I opened it in both VLC and GOM with the same result: good audio, no video.
As you may recall, mig, some weeks ago I reported that a video site to which I had a subscription had similarly operated properly with 5.4.2 but had lost the ability to download with 5.5.0. Unfortunately, it was not accessible outside the United States, so you were not able to research it. Well, here, hopefully, is a site you can research. As you will almost certainly ascertain if you switch to version 5.4.2, this site does indeed download properly in 5.4.2, but is unable to do so with 5.5.0 or later.
The bottom line: somewhere between 5.4.2 and 5.5.0, it appears that VDH may have taken a wrong turn; hopefully, going back to 5.4.2, and rethinking the approach you used for 5.5.0, will be able to rectify the problem. Also, hopefully, this report will prove helpful in that process.