chaturbate.com: SecureToken problems

(http://stream-recorder.com/forum/showthread.php?t=10869)

Re: SecureToken problems

using ffmpeg with libspeex installed you can convert it into aac or mp3, however, the video streams contain invalid timecodes so when you try to remux the h264 video into an mp4 container with your converted audio, the file will usually work but its still a broken file. i wish the flv that rtmpdump produced was more stable lol

Re: SecureToken problems

@greenybeasty

i tried that, but ffmpeg always complains about non monotone timestamps when i use the -vcodec copy, i guess to prevent invalid files.

what do u use?

Re: SecureToken problems

i use a custom built binary of ffmpeg that silences that error. the file is still technically invalid but it still works

Re: chaturbate.com: SecureToken problems

Hi folks. As of today, chaturbate streams return an error when using KSV's rtmpdump patch, which so far had worked quite well.

I am getting:

Code:

Connecting ...

WARNING: Trying different position for server digest!

INFO: Connected...

INFO: Model status is error

I am keeping up with the latest updates, by specifying e.g.:

Code:

-W ...snip.../CBV_2p607.swf

-C S:2.607

but the problem is also extensive to previous versions.

Has anyone sorted this out? Is this a SecureToken or connection related problem? Hints?

PS: the relevant verbose output

Code:

DEBUG: HandShake: Genuine Adobe Flash Media Server

DEBUG: HandShake: Handshaking finished....

DEBUG: RTMP_Connect1, handshaked

DEBUG: Invoking connect

INFO: Connected...

DEBUG: HandleServerBW: server BW = 2500000

DEBUG: HandleClientBW: client BW = 2500000 2

DEBUG: HandleCtrl, received ctrl, type: 0, len: 6

DEBUG: HandleCtrl, Stream Begin 0

DEBUG: HandleChangeChunkSize, received: chunk size change to 4096

DEBUG: RTMP_ClientPacket, received: invoke 34 bytes

DEBUG: (object begin)

DEBUG: Property: <Name:            no-name, STRING:        nfo>

DEBUG: Property: <Name:            no-name, NUMBER:        0.00>

DEBUG: Property: NULL

DEBUG: Property: <Name:            no-name, STRING:        version_too_old>

DEBUG: (object end)

DEBUG: HandleInvoke, server invoking <nfo>

DEBUG: RTMP_ClientPacket, received: invoke 349 bytes

DEBUG: (object begin)

DEBUG: Property: <Name:            no-name, STRING:        _result>

DEBUG: Property: <Name:            no-name, NUMBER:        1.00>

DEBUG: Property: <Name:            no-name, OBJECT>

DEBUG: (object begin)

DEBUG: Property: <Name:             fmsVer, STRING:        FMS/3,5,7,7009>

DEBUG: Property: <Name:       capabilities, NUMBER:        31.00>

DEBUG: Property: <Name:               mode, NUMBER:        1.00>

DEBUG: (object end)

DEBUG: Property: <Name:            no-name, OBJECT>

DEBUG: (object begin)

DEBUG: Property: <Name:              level, STRING:        status>

DEBUG: Property: <Name:               code, STRING:        NetConnection.Connect.Success>

DEBUG: Property: <Name:        description, STRING:        Connection succeeded.>

DEBUG: Property: <Name:               data, OBJECT>

DEBUG: (object begin)

DEBUG: Property: <Name:            version, STRING:        3,5,7,7009>

DEBUG: (object end)

DEBUG: Property: <Name:           clientid, NUMBER:        1337821364.00>

DEBUG: Property: <Name:     objectEncoding, NUMBER:        0.00>

DEBUG: Property: <Name:        secureToken, STRING:        3513ee84d54551afd230d86e9c78138941b6e8ca19c7513c97049a5ca78517358638c506>

DEBUG: (object end)

DEBUG: (object end)

DEBUG: HandleInvoke, server invoking <_result>

DEBUG: HandleInvoke, received result for method call <connect>

DEBUG: Invoking secureTokenResponse

DEBUG: sending ctrl, type: 0x0003

DEBUG: Invoking CheckPublicStatus

DEBUG: RTMP_ClientPacket, received: invoke 47 bytes

DEBUG: (object begin)

DEBUG: Property: <Name:            no-name, STRING:        ReceiveCheckPublicStatus>

DEBUG: Property: <Name:            no-name, NUMBER:        0.00>

DEBUG: Property: NULL

DEBUG: Property: <Name:            no-name, STRING:        0,error>

DEBUG: (object end)

DEBUG: HandleInvoke, server invoking <ReceiveCheckPublicStatus>

INFO: Model status is error

DEBUG: Closing connection.

Re: chaturbate.com: SecureToken problems

nothing fancy going on :D

Code:

rtmpdump -r "rtmpe://edge1-a.stream.highwebmedia.com/live-edge" -a "live-edge" -f "WIN 11,1,102,63" -W "http://chaturbate.com/static/flash/CBV_2p607.swf" -p "http://chaturbate.com/lilix/" -C S:AnonymousUser -C S:lilix -C S:2.607 -C S:anonymous -T "m9z#$dO0qe34Rxe@sMYxx%" --live -y "mp4:lilix-sd-2c42ecd59c03850eaee04fd89924ee5c3a24b1a41b56711cf3c0176135569ad8" -o "Test.flv"

Re: chaturbate.com: SecureToken problems

Quote:

Originally Posted by KSV (Post 46914)

nothing fancy going on :D

Code:

rtmpdump -r "rtmpe://edge1-a.stream.highwebmedia.com/live-edge" -a "live-edge" -f "WIN 11,1,102,63" -W "http://chaturbate.com/static/flash/CBV_2p607.swf" -p "http://chaturbate.com/lilix/" -C S:AnonymousUser -C S:lilix -C S:2.607 -C S:anonymous -T "m9z#$dO0qe34Rxe@sMYxx%" --live -y "mp4:lilix-sd-2c42ecd59c03850eaee04fd89924ee5c3a24b1a41b56711cf3c0176135569ad8" -o "Test.flv"

So it looks like the 4th -C parameter is new. Is that always S:anonymous or should I put a username there?

Re: chaturbate.com: SecureToken problems

it seems that first parameter is username, second is model name, third is player version and fourth is password.

Re: chaturbate.com: SecureToken problems

Quote:

Originally Posted by KSV (Post 46919)

it seems that first parameter is username, second is model name, third is player version and fourth is password.

Yup, that's the case. Still having problems though. The -y parameter seems to have changed. Using -y "mp4:public-lilix" always used to work but now it doesn't. Any ideas?

Re: chaturbate.com: SecureToken problems

you shouldn't care about -y parameter because it's dynamically retrieved from server.

Re: chaturbate.com: SecureToken problems

Quote:

Originally Posted by KSV (Post 46921)

you shouldn't care about -y parameter because it's dynamically retrieved from server.

Well I use an applescript that opens up an rtmpdump command with all the relevant information based on a username and it requires a -y parameter. Does that mean I'm out of luck now? Even in previous versions where the playpath was dynamically retrieved, the "mp4:public-<username>" still worked :/