Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Application is "vidmanlive" instead of "liveorigin" #9

Open
DmT021 opened this issue Feb 9, 2016 · 3 comments
Open

Application is "vidmanlive" instead of "liveorigin" #9

DmT021 opened this issue Feb 9, 2016 · 3 comments

Comments

@DmT021
Copy link

DmT021 commented Feb 9, 2016

Hey all,
Can you successfully start a broadcast from for example ffmpeg?
As I can see when you create a broadcast the application in the response is "vidmanlive" (but not "liveorigin"). When I try to start streaming to it I go the following error in ffmpeg:

Parsed protocol: 4
Parsed host    : vidman-eu-central-1.periscope.tv
Parsed app     : vidmanlive?t=...
RTMP_Connect1, ... connected, handshaking
HandShake: Type Answer   : 03
HandShake: Server Uptime : 0
HandShake: FMS Version   : 0.0.0.0
HandShake: Handshaking finished....
RTMP_Connect1, handshaked
Invoking connect
RTMP_ReadPacket, failed to read RTMP packet header
rtmps://vidman-eu-central-1.periscope.tv:443/vidmanlive?t=...: Unknown error occurred

Same for RTMP and RTMPS.
Do you get the same?

@DmT021
Copy link
Author

DmT021 commented Feb 9, 2016

I got it. I used to specify User Agent as "Periscope/2699 (iPhone; iOS 8.1.2; Scale/2.00)" within a request and periscope returns vidmanlive. If I do not specify anything periscope returns liveorigin.

@DmT021
Copy link
Author

DmT021 commented Feb 9, 2016

Probably the liveorigin is legacy now?

@MichaelZaporozhets
Copy link

@DmT021 I always get vidman. Although i'm getting an I/O error from that now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants