Announcement

Collapse
No announcement yet.

GLCS: A Better Version Of GLC For Linux Game Capturing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • lano1106
    replied
    Originally posted by Mike Frett View Post
    With Linux as a growing market, it's just plain silly to make any new app and not have a GUI. People coming to Linux now expect a GUI and may very well happily go back to their slave chains if all the Linux programmers are going to offer are Shell Scripts and DIY Command Line typings. Think about it this way: If they leave, it's your fault for your 90's nostalgia of the Command Line. No disrespect intended, it's just the facts of the matter.
    Thank you for your very valid comment. Here is what I can say:

    1. GUI isn't my thing. Feel free to contribute your expertise!
    2. You do not appear to understand the UNIX philosophy

    glcs is providing a mecanism. Other programmers can take it and integrate into their own GUI. Monolitic design or software that tries to do everything is evil :-)

    I did apply this very principle by leveraging a specialized tool (ffmpeg) instead of attempting to do everything myself.

    In fact, I know at least 2 projects that provides a GUI for the original GLC:

    gamecaster: https://launchpad.net/gamecaster
    soulcapture: https://piga.orain.org/wiki/Soul%20Capture

    Leave a comment:


  • zanny
    replied
    Originally posted by TAXI View Post
    Look at it from this view: What's better, making a CLI app or making no app at all?
    Think about the possibility of a not-so-experienced developer writing a GUI for it, too. Nobody is stopping any developer from doing this and with all the IDEs out there it should be fairly simple, even a developer which sees a screen recorder over his head should be able to do it (I bet I could if I really wanted to and I'm all other than experienced).

    Also after all nobody forces you to use this. Feel free to ignore it.
    Best of all worlds - design your user-facing applications as API libraries, provide a CLI client if you don't want to write the GUI on top of that, or provide all 3. Keep them discrete projects, though - that way you can have all 3 primary consumers of your software satisfied (other programs via APIs, sysadmins by your CLI, and muggles by your GUI). And you can have your dependencies discretized, so that if someone just wants to use your application internally they can just bundle the library, or if you are putting it on a server just bundle the CLI and library.

    I also find that by designing software like this, it makes unit tests a cinch - you have your interaction firmly defined in an API, so it is really easy to add test harnesses there for conformance and boundaries checking to help avoid exploits.

    Leave a comment:


  • V10lator
    replied
    Originally posted by Mike Frett View Post
    With Linux as a growing market, it's just plain silly to make any new app and not have a GUI. People coming to Linux now expect a GUI and may very well happily go back to their slave chains if all the Linux programmers are going to offer are Shell Scripts and DIY Command Line typings. Think about it this way: If they leave, it's your fault for your 90's nostalgia of the Command Line. No disrespect intended, it's just the facts of the matter.
    Look at it from this view: What's better, making a CLI app or making no app at all?
    Think about the possibility of a not-so-experienced developer writing a GUI for it, too. Nobody is stopping any developer from doing this and with all the IDEs out there it should be fairly simple, even a developer which sees a screen recorder over his head should be able to do it (I bet I could if I really wanted to and I'm all other than experienced).

    Also after all nobody forces you to use this. Feel free to ignore it.

    Leave a comment:


  • Mike Frett
    replied
    Growing Market

    With Linux as a growing market, it's just plain silly to make any new app and not have a GUI. People coming to Linux now expect a GUI and may very well happily go back to their slave chains if all the Linux programmers are going to offer are Shell Scripts and DIY Command Line typings. Think about it this way: If they leave, it's your fault for your 90's nostalgia of the Command Line. No disrespect intended, it's just the facts of the matter.

    Leave a comment:


  • MickStep
    replied
    Originally posted by russofris View Post
    I believe that SSR is an initialism (or alphabetism), and not an acronym.... Unless you go around saying "Sir" or something, in which case I sincerely apologize for this interruption.
    I believe he was referring to it being similar to the USSR, to which I say, nonsense you beorgouis pig in fact the developer should embrace it and go one step further and turn it into a recursive backronym beginning with U and adopt the hammer and sickle for it's icon.

    Leave a comment:


  • zanny
    replied
    Originally posted by pandev92 View Post
    how to record game sound and voice sound? :/
    I do it by making a pulseaudio sink of my audio in and stereo out. Which is kind of ridiculous.

    Leave a comment:


  • pandev92
    replied
    how to record game sound and voice sound? :/

    Leave a comment:


  • russofris
    replied
    Originally posted by GreatEmerald View Post
    Also, the acronym "SSR" has some unfortunate connotations
    I believe that SSR is an initialism (or alphabetism), and not an acronym.... Unless you go around saying "Sir" or something, in which case I sincerely apologize for this interruption.

    Leave a comment:


  • GreatEmerald
    replied
    Originally posted by lano1106 View Post
    Audio encoder/video encoder is bundled. Personally, this scares me a little bit as if it crash or there is a bug, the whole host app (the game) goes with it
    easy to use but hard to adapt to special needs.
    What do you mean by "bundled" and "the whole host app goes with it"? If you're doing a non-accelerated recording, then if there is a crash, only the recorder crashes. If you're using OpenGL recording, it's using glinject just like GLCS, as far as I can tell. You don't need to autostart the game with SSR, you can launch it with the needed environment variables set manually. So if the recorder crashes, nothing should happen to the game.

    I agree with the second point, though. While the few settings SSR gives are the most important ones, ffmpeg offers a huge wealth of options. That's always nice to have.

    Also, the acronym "SSR" has some unfortunate connotations

    Leave a comment:


  • Marc Driftmeyer
    replied
    Originally posted by lano1106 View Post
    Maybe you are right. but since Crossfire is either broken or not widely supported on Linux, I have a GPU that sits idle most of the time so why not give opencl encoding a try....
    Yes it does bring benefits.

    Leave a comment:

Working...
X