Studio66tv problem

Re: Studio66tv problem

 

no news at all? pm guys, please, thanks.

Re: Studio66tv problem

 

I am interested in the pervecam work around and is will to pay for the pleasure.

Re: Studio66tv problem

 

you have pm

Re: Studio66tv problem

 

My attempt at auto-fixing their terrible orange hue, when they have the lights directly shining into the camera. I guess they do it to hide the cheap buck50 boobjob scars :rolleyes:

Without


With

Re: Studio66tv problem

 

please help. i don't get this to work anymore.

Re: Studio66tv problem

 

Hi guys,

Not sure if i have linked the above image correctly.

Anyways, i can get the Rtmpdump to connect, however the connection gets rejected (see attached screenshot)

I also have wireshark packets pre- and post- patch, if anyone is interested let me know.

Anyone have any ideas?

Cheers

Re: Studio66tv problem

 

I believe we are on the same boat....... This is what I managed:

DEBUG: app : leah/
DEBUG: flashVer : LNX 22,0,0,209
DEBUG: live : no
DEBUG: timeout : 30 sec
DEBUG: SWFSHA256:
DEBUG: 6c 17 f2 66 0f 54 25 b3 04 42 1e 59 bb 6e 63 83
DEBUG: 86 69 50 a9 87 34 dc 67 40 56 d2 cf 1b 5f 55 88
DEBUG: SWFSize : 4218025
DEBUG: Setting buffer time to: 36000000ms
Connecting ...
DEBUG: RTMP_Connect1, ... connected, handshaking
DEBUG: HandShake: Client type: 03
DEBUG: HandShake: Client digest offset: 417
DEBUG: HandShake: Initial client digest:
DEBUG: 0c db 24 7d 09 83 9d c8 b6 28 2d 09 83 e4 68 61
DEBUG: 0e 63 a3 ca 6c c3 f0 7d be 24 2b f5 73 69 10 76
DEBUG: HandShake: Type Answer : 03
DEBUG: HandShake: Server Uptime : 96850052
DEBUG: HandShake: FMS Version : 3.0.1.1
DEBUG: HandShake: Calculated digest key from secure key and server digest:
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 163 bytes
DEBUG: (object begin)
DEBUG: Property: <Name: no-name, STRING: _error>
DEBUG: Property: <Name: no-name, NUMBER: 1.00>
DEBUG: Property: NULL
DEBUG: Property: <Name: no-name, OBJECT>
DEBUG: (object begin)
DEBUG: Property: <Name: level, STRING: error>
DEBUG: Property: <Name: code, STRING: NetConnection.Connect.Rejected>
DEBUG: Property: <Name: description, STRING: Connection failed: Application rejected connection.>
DEBUG: (object end)
DEBUG: (object end)
DEBUG: HandleInvoke, server invoking <_error>
ERROR: rtmp server sent error
DEBUG: RTMP_ClientPacket, received: invoke 18 bytes
DEBUG: (object begin)
DEBUG: Property: <Name: no-name, STRING: close>
DEBUG: Property: <Name: no-name, NUMBER: 0.00>
DEBUG: Property: NULL
DEBUG: (object end)
DEBUG: HandleInvoke, server invoking <close>
ERROR: rtmp server requested close
DEBUG: Closing connection.

Re: Studio66tv problem

 

: server BW = 2500000
DEBUG: HandleClientBW: client BW
= bwcheck app?

'rtmp://51.254.198.110/bwcheck/'

it seems to use this as well as leved
'rtmp://51.254.198.110/leved/'

or rtmp://??.???.???.???/????/ in the case of private cams.

Re: Studio66tv problem

 

yeah... mostly :
"or rtmp://??.???.???.???/????/ in the case of private cams."

Re: Studio66tv problem

 

/leved is the app that is used for the free streams
/leah is used for the private cam-streams

long time ago i was able to sniff a stream using the bwcheck app as well. it went offline after a minute. i guess it is used for testing purpose?

regarding the IP address: 51.254.198.110 is used for the free streams. for the private cams they use 178.33.229.31 instead


is the server asking for some sort of session cookie or md5-key? i've read that some websites use this method. and people could enter these cookies into livestreamer. BUT i personally do not know how to solve it -.-