Quote:
Originally Posted by Xenicide
Sorry to bring this up again put i got some questions.
The link to flvtool++ doesnt work, but i found one in another place.
But all i got was some files, and you had to have 2 other programs.
One of thoose in turn required another thing called phyton.
Is it suppose to work that way?
In the hex editor i change the fifth byte (04) to 05 on all files, sound or not. Some plays and some dont.
The program i use is Real Player since its the only one i can seek.
But during some (mostly the long ones) it often after a while jump forward. Is that something that flvtool++ fixes?
Something that might matter is that i only let the stream start downloading (after restarting it), and then close the window.
Does it mather if the window is open once you get the stream in grab?
And if i restart the capture it can take a while before downloading, sometimes it wont even start even if the stream is there,
any reason for this?
Btw i got v2.7.6 and it woks.
(But maybe not as it should.)
Lots of questions but i hope i get some answers on some of them.
Thanks.
|
You may have ended up with the source code files. The executable is just 68k, and doesn't require other files. This link seems to work now:
http://rcdn.org:8080/images/3/34/Flvtool%2B%2B.zip
In my experience, the jumping forward seems to be a result of the freezing and dropouts you get in the stream from cam4. It is NOT fixed by flvtool++. When the cam4 servers are overloaded, and don't give you a continuous stream, the timestamps in the recorded flv file no longer make any sense to the player. Particularly if video and audio dropouts are independent, as they often are.
What we need is something that will fill in the missing packets with something that has continuous timestamps.
I haven't found a solution to this problem, and as as result I've reverted to using Cam Studio, a free screen capture program. Which, unfortunately, comes with its own sync problems.
I don't know about closing the window. I never tried that.
I also sometimes had the problem with the capture not starting even though the window is up and running. If you are right about being able to close the window, then it looks like Orbit is making a separate duplicate connection to the server to do the capture. And in that case, for some reason it just can't get in again. So, what you are watching is not really what's being captured.