Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Obs Studio | 48,049 | 6 hours ago | 603 | gpl-2.0 | C | |||||
OBS Studio - Free and open source software for live streaming and screen recording | ||||||||||
Docker Selenium | 1,435 | 2 years ago | 35 | other | Shell | |||||
[NOT MAINTAINED] Please use <https://github.com/SeleniumHQ/docker-selenium> | ||||||||||
Gpuvideo Android | 570 | 4 months ago | 71 | mit | Java | |||||
This library apply video filter on generate an Mp4 and on ExoPlayer video and Video Recording with Camera2. | ||||||||||
Androidrecording | 396 | 5 years ago | 14 | apache-2.0 | Java | |||||
Android Recording library offers convenient tools for audio/video recording and playback | ||||||||||
React Media Recorder | 234 | 4 | 5 | a year ago | 36 | May 14, 2022 | 40 | mit | TypeScript | |
react-media-recorder is a react component with render prop that can be used to record audio/video streams using MediaRecorder API. | ||||||||||
Reporting | 208 | 4 | 2 | 2 months ago | 40 | October 12, 2020 | 4 | apache-2.0 | Shell | |
Zebrunner Reporting Tool | ||||||||||
Ofxvideorecorder | 204 | 3 years ago | 17 | other | C++ | |||||
A fast multi-threaded video recording extension using ffmpeg | ||||||||||
Horizonsdk Ios | 171 | 10 months ago | 17 | January 26, 2018 | other | HTML | ||||
Horizon SDK for iOS | ||||||||||
Screen Recorder Ffmpeg Cpp | 63 | 3 years ago | 7 | mit | C++ | |||||
*Multimedia project* A screen recording application to capture your desktop and store in a video format. Click here to watch the demo | ||||||||||
Safari Audiorecord Io6 | 61 | 11 years ago | 1 | PHP | ||||||
Let's you record audio directly into a web app using ios6. |
Android video recording and annotation app for construction.
Please use the latest Android Studio version from the stable channel.
build.gradle
file in the project root directory.You can launch Ach so! just to play singular Ach so!-videos. (if e.g. some other service finds Ach so! videos as resources and wants to show them for the user)
If you provide generic Intent.VIEW with an uri using the 'achso:'-scheme, Ach so! will load the uri and play the video:
Intent intent = new Intent(Intent.ACTION_VIEW);
// we have a video with id "2de064a5-cb38-4c04-9fde-502ab619fc46"
// uri will be "achso:2de064a5-cb38-4c04-9fde-502ab619fc46"
Uri uri = Uri.fromParts("achso", "2de064a5-cb38-4c04-9fde-502ab619fc46", null);
intent.setData(uri);
startActivity(intent);
Another way to show a single video is to specifically ask Ach so! to play a .mp4 -video. In this case Ach so! looks if there are annotations available for this video file in the default server and fetches those.
Intent intent = new Intent("fi.aalto.legroup.achso.action.VIEW");
Uri uri = Uri.parse("http://www.sample-videos.com/video/mp4/720/big_buck_bunny_720p_1mb.mp4");
intent.setDataAndType(uri, "video/mp4");
startActivity(intent);
There are libraries to launch intents in PhoneGap/Cordova. If you want to play Ach so! videos in non-android environments, use video player in Achrails.
Loosely based on Thoughtbot’s Git protocol.
The master
branch mirrors the currently stable version, i.e. the one that is
currently on Google Play. The history on this branch is final and must never be
rewritten.
The integration
branch hosts the current development version. Rebasing this
branch is discouraged, but it can be done if there’s a good enough reason and
contributors are consulted with beforehand.
Other branches are working branches. You can expect their history to be rewritten at any time.
Create a new branch based off integration
before starting work. Use a
traceable name like feature/LL-123
or bugfix/LL-123
, where the number
after the prefix is the issue number in JIRA. Use
feature/summary-of-feature
if the feature doesn’t have JIRA ticket.
Do your work in the new branch and commit often with good, descriptive commit messages. The first line of your commit message should not exceed 50 characters.
Check your commit history when you’ve finished work. Use interactive rebase
git rebase -i integration
to clean it up. Your commits should be atomic:
each commit should contain one change that doesn’t depend on other commits
to build. This is easier if you commit often and then rebase.
Create a pull request against integration
when your commits are clean. If
you accidentally mistarget the pull request, against master
for example,
close it and create a new one.
Mark the JIRA issue as resolved
.
Other contributors will review your changes. If they need more work, push additional commits to the working branch.
The reviewer marks the JIRA issue as closed
and merges the pull request.
Delete your working branch when it’s no longer needed. This can be done easily from the pull request page.
When the changes in the integration
branch are deemed stable, they will be
merged into master
and a new version is released.
Since v0.10.0, Ach so! releases follow semantic versioning and each
release is tagged in the master
branch.
Ach so! is developed by the Learning Environments research group at the School of Arts, Design and Architecture of Aalto University, Finland.
Copyright 2013–2017 Aalto University
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.