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.

Sign up for GitHub

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

Jump to bottom

STATUS command gives error in 2.0, worked in 1.8 #2

Closed
CasparCGImport opened this issue Mar 26, 2013 · 3 comments
Closed

STATUS command gives error in 2.0, worked in 1.8 #2

CasparCGImport opened this issue Mar 26, 2013 · 3 comments
Labels
type/bug

Comments

@CasparCGImport
Copy link

Converted from SourceForge issue 3529443, submitted by hummelstrand

"After I installed the server 2.0, I have trouble getting the STATUS command to work. Sends the STATUS 1 and get back 400 ERROR."

Robert suggested: "Try INFO instead."

From http://casparcg.com/forum/viewtopic.php?f=10&t=734
@CasparCGImport
Copy link
Author

Submitted by ronag

This is not a bug. STATUS was renamed to INFO between the alpha and beta releases of CasparCG 2.0.

@CasparCGImport
Copy link
Author

Submitted by hummelstrand

AMCP protocol documentation updated: http://casparcg.com/wiki/CasparCG_2.0_AMCP_Protocol#STATUS

@CasparCGImport
Copy link
Author

Submitted by hummelstrand

Documentation added for INFO: http://casparcg.com/wiki/CasparCG_2.0_AMCP_Protocol#INFO

@kormikk kormikk mentioned this issue Apr 12, 2019
Closed
gizahNL added a commit to odmanaged/server that referenced this issue Mar 2, 2021
@gizahNL
Fix copyright CasparCG#2
9ab03bc
@tvadi tvadi mentioned this issue Dec 16, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CasparCGImport