Giter VIP home page Giter VIP logo

shellcasting's Introduction

The Shellcasting Project

A collection of shell scripts with the intent of making screencasting on Linux a simple and easy process. I'm also kinda learning how to write shell code as I go here, so pardon the rough edges.

What you will need

Currently, we depend on the following software packages:

More will probably be added as the project progresses.

screencast.sh

The primary application, it uses a daemon-like architecture to record audio and video from your system. You may choose to capture the whole screen or a specified region. Limited post-processing capabilities are available.

jack.sh

This script allows easy control of the JACK server and alsa-jack plugin, allowing the user to quickly enable it only when it is needed and disable it again once it is no longer required. The design is inspired largely by the design of Gentoo's init scripts.

shellcasting's People

Contributors

toksyuryel avatar sflavelle avatar

Stargazers

 avatar

Watchers

 avatar

Forkers

jesskay sflavelle

shellcasting's Issues

--config is currently ignored

screencast.sh currently does not appear to read from the specified --config option, or from its default setting. Additionally, attempting to specify --config manually simply brings up the usage information.

.screencastrc:

For Logitech USB Mic

MICCHANNELS = 1
MICSOURCE=hw:1,0

Other Settings

FPS=20

The resulting processed.mp4 file (using screencast start, screencast stop then screencast post) uses the default values issued by the script.

Post-processing picks up stray data files from earlier recordings

Current problem: remnants of older recordings (system audio, voice data) may get mixed in when post-processing a current recording.

Idea: record the options specified with screencast start to a temporary file (overwrite it if it already exists?). Read it (if it exists) when beginning post-processing, then remove the file when post-processing has completed with no errors.

Using the stop mode with the -p/--post option does not pass along any common options that appeared before.

Need to rewrite how this works. Currently we call the whole script again, passing along the arguments that come after the -p/--post option. I think the correct thing to do is to move the post_processing options into a function that can be called by either the post mode or the stop mode, allowing them to be set from either and thus preserving the common options (and allowing them to come later in the line for the stop mode as well).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.