1
UrlSnooper / Re: OTA program (URLSnooper and rtmpdump)
« on: November 21, 2009, 10:35 PM »
Thanks, I'll look into that if time permits (don't read German though).
I *_think_* I've got it now. Someone at another forum posted a link to some guides and software at other audio/video sites (this one and this one, rtmpdump gets good mention on both).
Another product may have already captured the content for me*, but in doing so, I learned some interesting stuff. The "encryption" is another layer of protection Adobe has added (if you find an RTMPE URL instead of an RTMP one). This may be the same as "authentication" that URLSnooper's help screen talks about. Anyway, it does not appear to be in use in this case.
The name of the actual media file (on the content provider's hard drive) may be inside .smil files or other places in the interaction (packets, GET requests) with your computer. The other product found the name and I wrote it down. Some of the characters are missing (.../.../subdirectory/name-of-flashfile.flv) but I have enough to do a search in URLSnooper.
Still not sure what RTMPApp is, maybe the software that serves the flash to me (rtmp://123.123.123.123:443/...vhost=*******.edgefcs.net). That last part may be the "host" that rtmpdump wants (edgefcs.net). The port is 443.
I will likely try URLSnooper soon.
I think both sites mentioned earlier (this one and this one) mention WMCapture as good "framegrabber" software (off my video card's memory chips) but I don't know that that would be any better. The original flash had a certain limited quality (and I'm playing it as large as I can in my browser window), and I can't "make up" picture details that weren't there, right?
*Does 205 megs sound right for a one-hour US network TV program? Why do I have two files, one 201 megs and one 205 megs?
I'll let you know....
I *_think_* I've got it now. Someone at another forum posted a link to some guides and software at other audio/video sites (this one and this one, rtmpdump gets good mention on both).
Another product may have already captured the content for me*, but in doing so, I learned some interesting stuff. The "encryption" is another layer of protection Adobe has added (if you find an RTMPE URL instead of an RTMP one). This may be the same as "authentication" that URLSnooper's help screen talks about. Anyway, it does not appear to be in use in this case.
The name of the actual media file (on the content provider's hard drive) may be inside .smil files or other places in the interaction (packets, GET requests) with your computer. The other product found the name and I wrote it down. Some of the characters are missing (.../.../subdirectory/name-of-flashfile.flv) but I have enough to do a search in URLSnooper.
Still not sure what RTMPApp is, maybe the software that serves the flash to me (rtmp://123.123.123.123:443/...vhost=*******.edgefcs.net). That last part may be the "host" that rtmpdump wants (edgefcs.net). The port is 443.
I will likely try URLSnooper soon.
I think both sites mentioned earlier (this one and this one) mention WMCapture as good "framegrabber" software (off my video card's memory chips) but I don't know that that would be any better. The original flash had a certain limited quality (and I'm playing it as large as I can in my browser window), and I can't "make up" picture details that weren't there, right?
*Does 205 megs sound right for a one-hour US network TV program? Why do I have two files, one 201 megs and one 205 megs?
I'll let you know....