Category: Blog

  • features-starter

    Visit original content creator repository
    https://github.com/devcontainers-community/features-starter

  • terraform-aws-ecs-fargate-eventbridge

    Geek Cell GmbH

    Code Quality

    License GitHub release (latest tag) Release Validate Lint

    Terraform AWS ECS Fargate EventBridge

    This module creates an AWS EventBridge (formerly known as CloudWatch Events) rule and target to run a task on an ECS Fargate cluster. This is useful for running tasks periodically, like cleanup CRON jobs.

    Inputs

    Name Description Type Default Required
    assign_public_ip Assign a public IP address to the ENI. bool false no
    container_overrides The container overrides for the ECS task. list(any) [] no
    ecs_cluster_arn The ARN of the ECS cluster to run the task in. string n/a yes
    ecs_target_group The name of the ECS task group for the task. string null no
    enable_ecs_managed_tags Specifies whether to enable Amazon ECS managed tags for the task. bool false no
    enable_execute_command Whether to enable the execute command functionality for the ECS task. bool false no
    platform_version Platform version on which to run your ECS task. string "1.4.0" no
    propagate_tags Specifies whether to propagate the tags from the task definition the ECS tasks. string null no
    rule_description Description of the rule. string null no
    rule_is_enabled Whether the rule is enabled. bool true no
    rule_name Name of the rule. string n/a yes
    rule_role_arn The ARN of the IAM role associated with the rule. string null no
    rule_schedule_expression The scheduling expression. For example, cron(0 20 * * ? *) or rate(5 minutes). string n/a yes
    security_group_ids Security groups associated with the ECS task. If you do not specify a security group, the default security group for the VPC is used. list(string) [] no
    subnet_ids Subnets associated with the ECS task. list(string) n/a yes
    tags Tags to add to the created resources. map(any) {} no
    target_name Name of the target. string n/a yes
    target_policy_name The name of the policy to create. string null no
    target_policy_name_prefix Whether to use the target_policy_name as a prefix or not. bool false no
    target_role_name The name of the EventBridge target role. string null no
    target_role_name_prefix Whether to prefix the EventBridge target role name. bool false no
    task_count The number of tasks to create based on the task definition. number 1 no
    task_definition_arn The ARN of the task definition to use. string n/a yes
    task_execution_role_arn The ARN of the IAM role to use as execution role for the ECS task. string null no
    task_role_arn The ARN of the IAM role to use as task role for the ECS task. string null no
    use_rule_name_prefix Use the rule_name attribute as prefix for the rule name. bool false no

    Outputs

    No outputs.

    Providers

    Name Version
    aws >= 4.36

    Resources

    • resource.aws_cloudwatch_event_rule.main (main.tf#7)
    • resource.aws_cloudwatch_event_target.main (main.tf#20)

    Examples

    Complete

    module "example" {
      source = "../../"
    
      rule_name                = "run-cleanup-script-on-midnight"
      rule_schedule_expression = "cron(0 0 * * ? *)"
    
      target_name = "ecs-fargate-taskdef"
    
      ecs_cluster_arn     = "arn:aws:ecs:us-east-1:123456789012:cluster/ecs-cluster"
      task_definition_arn = "arn:aws:ecs:us-east-1:123456789012:task-definition/ecs-task"
    
      security_group_ids = ["sg-12345678"]
      subnet_ids = [
        "subnet-12345678",
        "subnet-87654321",
      ]
    }
    Visit original content creator repository https://github.com/geekcell/terraform-aws-ecs-fargate-eventbridge
  • terraform-aws-ecs-fargate-eventbridge

    Geek Cell GmbH

    Code Quality

    License GitHub release (latest tag) Release Validate Lint

    Terraform AWS ECS Fargate EventBridge

    This module creates an AWS EventBridge (formerly known as CloudWatch Events) rule and target to run a task on an ECS Fargate cluster. This is useful for running tasks periodically, like cleanup CRON jobs.

    Inputs

    Name Description Type Default Required
    assign_public_ip Assign a public IP address to the ENI. bool false no
    container_overrides The container overrides for the ECS task. list(any) [] no
    ecs_cluster_arn The ARN of the ECS cluster to run the task in. string n/a yes
    ecs_target_group The name of the ECS task group for the task. string null no
    enable_ecs_managed_tags Specifies whether to enable Amazon ECS managed tags for the task. bool false no
    enable_execute_command Whether to enable the execute command functionality for the ECS task. bool false no
    platform_version Platform version on which to run your ECS task. string "1.4.0" no
    propagate_tags Specifies whether to propagate the tags from the task definition the ECS tasks. string null no
    rule_description Description of the rule. string null no
    rule_is_enabled Whether the rule is enabled. bool true no
    rule_name Name of the rule. string n/a yes
    rule_role_arn The ARN of the IAM role associated with the rule. string null no
    rule_schedule_expression The scheduling expression. For example, cron(0 20 * * ? *) or rate(5 minutes). string n/a yes
    security_group_ids Security groups associated with the ECS task. If you do not specify a security group, the default security group for the VPC is used. list(string) [] no
    subnet_ids Subnets associated with the ECS task. list(string) n/a yes
    tags Tags to add to the created resources. map(any) {} no
    target_name Name of the target. string n/a yes
    target_policy_name The name of the policy to create. string null no
    target_policy_name_prefix Whether to use the target_policy_name as a prefix or not. bool false no
    target_role_name The name of the EventBridge target role. string null no
    target_role_name_prefix Whether to prefix the EventBridge target role name. bool false no
    task_count The number of tasks to create based on the task definition. number 1 no
    task_definition_arn The ARN of the task definition to use. string n/a yes
    task_execution_role_arn The ARN of the IAM role to use as execution role for the ECS task. string null no
    task_role_arn The ARN of the IAM role to use as task role for the ECS task. string null no
    use_rule_name_prefix Use the rule_name attribute as prefix for the rule name. bool false no

    Outputs

    No outputs.

    Providers

    Name Version
    aws >= 4.36

    Resources

    • resource.aws_cloudwatch_event_rule.main (main.tf#7)
    • resource.aws_cloudwatch_event_target.main (main.tf#20)

    Examples

    Complete

    module "example" {
      source = "../../"
    
      rule_name                = "run-cleanup-script-on-midnight"
      rule_schedule_expression = "cron(0 0 * * ? *)"
    
      target_name = "ecs-fargate-taskdef"
    
      ecs_cluster_arn     = "arn:aws:ecs:us-east-1:123456789012:cluster/ecs-cluster"
      task_definition_arn = "arn:aws:ecs:us-east-1:123456789012:task-definition/ecs-task"
    
      security_group_ids = ["sg-12345678"]
      subnet_ids = [
        "subnet-12345678",
        "subnet-87654321",
      ]
    }
    Visit original content creator repository https://github.com/geekcell/terraform-aws-ecs-fargate-eventbridge
  • rime-configuration

    Rime Configuraion

    本仓库用于存放自用 Rime 配置

    文件说明

    rime
    ├── Android
    │  ├── backgrounds
    │  ├── trime.yaml
    │  ├── 单静.trime.custom.yaml
    │  └── 单静.trime.yaml
    ├── Common
    │  ├── build
    │  ├── custom_phrase_double_pinyin.txt
    │  ├── default.yaml
    │  ├── dictionary
    │  ├── double_pinyin.custom.yaml
    │  ├── double_pinyin.schema.yaml
    │  ├── key_bindings.yaml
    │  ├── lua
    │  ├── melt_eng.custom.yaml
    │  ├── melt_eng.schema.yaml
    │  ├── opencc
    │  ├── punctuation.yaml
    │  ├── radical_pinyin.custom.yaml
    │  ├── radical_pinyin.dict.yaml
    │  ├── radical_pinyin.schema.yaml
    │  ├── rime.lua
    │  ├── rime_cn.dict.yaml
    │  ├── rime_en.dict.yaml
    │  ├── symbols.yaml
    │  ├── zh-hans-t-essay-bgc.gram
    │  └── zh-hans-t-essay-bgw.gram
    ├── Darwin
    │  └── squirrel.custom.yaml
    ├── iOS
    ├── Linux
    └── Windows
       └── weasel.custom.yaml

    仓库中 Rime 目录下为 Rime 所有配置文件,其中:

    • Common 目录为所有平台共享内容;
    • 其余指定平台类型文件夹内容为该平台独享

    配置说明

    输入方案

    输入扩展功能

    Lua 脚本说明

    脚本名 脚本说明
    datetime 用于输入日期、星期、时间
    unicode 用于输入 unicode
    rime_lua_select_character 以词定字
    reduce_english_filter 用于降低部分英语单词的权重
    insert_space_between_words 候选词中英文间增加空格
    number_translator 对输入的数字进行大写转换
    autocap_filter 英文大写转换,首字符大写转换小写单词为首字母大写,前 2 个字符大写转换小写单词为全大写
    moran* 魔然 方案相关 lua 脚本

    词库

    使用说明

    环境准备

    由于 万象语法模型 体积较大,需自行下载至 Rime/Common 目录下。

    桌面平台

    # 克隆当前项目
    git clone https://github.com/WithdewHua/rime-configuration.git
    
    # 复制所有文件至 Rime 用户目录
    # 注意:
    #   - Windows 平台需注意先退出算法服务
    #   - Linux 适配 fcitx5
    python3 init_rime.py
    
    # deploy&enjoy!

    移动平台

    通用

    将仓库 Rime/CommonRime/<平台类型> 文件夹内容复制到 Rime 用户文件夹中,重新部署即可。

    仓 (Hamster)

    前提条件:

    • 仓中启用 iCloud
    • 联网的 Mac

    使用方法:

    # 在 Mac 上克隆当前项目
    git clone https://github.com/WithdewHua/rime-configuration.git
    
    # 复制 rime 配置文件到仓的 iCloud 目录中
    python3 init_rime.py --os ios
    
    # 确认 iCloud 文件同步至手机后,进入仓中重新部署即可

    更多

    增加输入方案、添加词库、设置同步等自定义配置可参考 Rime 输入法配置记录

    感谢

    Rime

    字体

    Visit original content creator repository
    https://github.com/WithdewHua/rime-configuration

  • libsbgn

    LibSBGN

    Software support library for the Systems Biology Graphical Notation (SBGN).

    Documentation about LibSBGN and the development process is available from the Wiki
    https://github.com/sbgn/sbgn/wiki/LibSBGN
    Documentation about SBGN is available from the SBGN homepage
    http://sbgn.org

    How to cite

    Software support for SBGN maps: SBGN-ML and LibSBGN
    van Iersel MP, Villéger AC, Czauderna T, Boyd SE, Bergmann FT, Luna A, Demir E, Sorokin A, Dogrusoz U, Matsuoka Y, Funahashi A, Aladjem MI, Mi H, Moodie SL, Kitano H, Le Novère N, Schreiber F.
    Bioinformatics, 28(15):2016-2021, 2012 PubMed

    Using libsbgn

    As of milestone 3, thanks to jitpack.io, it is easy to use libsbgn right away withL

    gradle:

    Step 1. Add the JitPack repository to your build file

    Add it in your root build.gradle at the end of repositories:

    allprojects {
    	repositories {
    		...
    		maven { url 'https://jitpack.io' }
    	}
    }
    

    Step 2. Add the dependency

    dependencies {
            implementation 'com.github.sbgn:libsbgn:Tag'
    }
    

    Maven

    Step 1. Add the JitPack repository to your build file

    <repositories>
    	<repository>
    	    <id>jitpack.io</id>
    	    <url>https://jitpack.io</url>
    	</repository>
    </repositories>
    

    Step 2. Add the dependency

    <dependency>
        <groupId>com.github.sbgn</groupId>
        <artifactId>libsbgn</artifactId>
        <version>Tag</version>
    </dependency> 
    

    sbt

    Add it in your build.sbt at the end of resolvers:

    resolvers += "jitpack" at "https://jitpack.io"
    

    Step 2. Add the dependency

    libraryDependencies += "com.github.sbgn" % "libsbgn" % "Tag"
    

    leiningen

    Add it in your project.clj at the end of repositories:

    :repositories [["jitpack" "https://jitpack.io"]]
    

    Step 2. Add the dependency

    :dependencies [[com.github.sbgn/libsbgn "Tag"]]	
    

    Share this release:

    Example code

    If you would like to see how to use libsbgn, have a look at some of the examples:

    How to build

    To build the java version of LibSBGN, you need to have installed:

    Building with Maven

    First clone the repository via

    git clone https://github.com/sbgn/libsbgn.git
    cd libsbgn
    

    then compile using mvn install.

    Building with Ant

    Add Git, Java JDK, and Ant to your path

    First clone the repository via

    git clone https://github.com/sbgn/libsbgn.git
    cd libsbgn
    

    Get the latest stable release otherwise you will work with the unstable development version

    git fetch
    git checkout milestone-2
    

    Than build the library with ant from the source directory

    ant -f ant-build-script.xml
    

    This will result in the creation of /dist/org.sbgn.jar which you can include in your project.

    To build the documentation in /docs/ use

    ant -f ant-build-script.xml doc
    

    To run the tests use

    ant -f ant-build-script.xml test
    

    Files

    Here is an explanation of the directories in this project:

    cpp_binding    - C++ version of LibSBGN  
    example-files  - some example SBGN-ML files, larger and more complete than the test-cases  
    licenses       - license information  
    org.sbgn       - LibSBGN source code (Java version)  
    resources      - general resources, including XML Schema (SBGN.xsd)  
    specifications - Auto-generated documentation for the XML Schema  
    test-files     - SBGN-ML test cases and reference images  
    tools		   - 
    validation     - schematron validation rules, test-cases and resources  
    

    Authors

    Alice Villeger
    Augustin Luna
    Frank Bergmann
    Martijn van Iersel
    Sarah Boyd
    Tobias Czauderna
    Stuart Moodie
    Matthias König

    Contact

    Contact our mailinglist:
    sbgn-libsbgn@lists.sourceforge.net

    Our official website:
    https://github.com/sbgn/libsbgn

    Visit original content creator repository https://github.com/sbgn/libsbgn
  • node-babel

    Node.js Babel Boilerplate

    A minimal boilerplate for running Node.js with Babel, Webapck 4 or Rollup. I started this project because there are some universal or near universal patterns that all node project share in common (like building). Rather than continuously rebuild these, I decide to collect in one repo, which I can pull and then start modifying it.

    What you get:

    • a simple Babel configuration
    • a simple Webpack 4 configuration with sourcemaps
    • a simple Rollup configuration with sourcemaps
    • a simple setup for testing with Mocha

    1. Clone project

    git clone git@github.com:pmcalabrese/node-babel.git
    

    2. Install dependencies

    npm install
    

    3. Start work (Babel by default)

    The workflow consist of running the compiler with:

    npm run watch
    

    This command will watch the files in the src folder and automatically compile them and put in the dist folder.
    When you are done you can run your application with:

    npm start
    

    You also have the option to build your app once with:

    npm run build
    

    4. Build with Webpack 4

    If Babel is not your thing, a minimal configuration for Webpack 4 has been added. This allow you to use webpack for build and bundle your application. The script build will generate source map.

    The commands are:

    • npm run webpack:build
    • npm run webpack:watch
    • npm run webpack:buildprod

    5. Build with Rollup

    You also have the choice to bundle your application with Rollup. The script build will generate source map.

    The commands are:

    • npm run rollup:build
    • npm run rollup:watch
    • npm run rollup:buildprod

    6. Run tests

    Test are written in the test folder can are bundled with Rollup as default, the destination folder for the tests is test_dist. You can write ES6 and import source straight from the src folder. For run the test type:

    npm test
    

    Visit original content creator repository
    https://github.com/pmcalabrese/node-babel

  • stemgen

    🎛 Stemgen

    Stemgen is a Stem file generator. Convert any track into a Stem and have fun with Traktor.

    A Stem file is an open, multi-channel audio file that contains a track split into four musical elements – bass, drums, vocals, and melody, for example. With each element available independently, you have more control over the music you play.

    Stemgen uses bs_roformer or demucs to separate the 4 stems and ni-stem to create the Stem file.

    Screenshot Before Screenshot After

    Our new file contains four stems: drums, bass, other (melody) and vocals.

    Note

    Traktor Pro 4 includes stem separation! Fortunately, it is backward-compatible and you can upgrade without any issue. But unfortunately, Stemgen still makes sense because:

    • Stemgen is the only way to create lossless ALAC stem files… for now! Please make yourself heard on the forum if you think lossless stems matters
    • Stemgen is the only way to create your own stem files from Ableton Live and from a CLI
    • Stemgen writes the metadata of the original files to the stem files, so you can easily sync them between computers

    Why?

    “It’s no secret that I’m fully behind the approach to encourage individuality in creativity and for artists to play differently. Stems is a new format that mirrors my constant quest for spontaneity to drive the art of performance forwards. I hope that releasing my album From My Mind To Yours in this format, mastered by LANDR, inspires others to support the approach and bring even more flexibility to the art of DJing amongst its most progressive supporters.” – Richie Hawtin

    Stems are fun but nobody’s releasing them. Stemgen is a way to create your own stems with only one command.

    Note

    May 2023 Update: I saw François K last week in Paris at the Loft Babies party and I discovered that he’s playing with Stems. I highly recommend checking out his videos on YouTube: https://www.youtube.com/playlist?list=PLCr4LSsJFk48tmNoKn-l7mgsB5XUd2Af9. He’s a legend and a true pioneer. I’m so happy to see him having fun with Stems. And trust me: it’s even better in real life. Can’t wait to see him again!

    “There is a really big difference between using a tool, a computer as a tool, to make it do specific things we want it to do, in the manner in which we want it to accomplish it. In most other situations, we all find ourselves dealing with a pre-programmed or pre-determined path that the software designer has decided we must use the software in order to get certain things done. And I think that makes it that we, little by little, become controlled by the path that was designed by the people who wrote the software and forced into these gullies that they created of usage, that this is how we are supposed to be doing things. And after a while I think it’s making us forget who we were and what the essence of what the music was supposed to be about and really represented.

    And this right here — I have to be honest — it’s groundbreaking to me in that sense. It’s putting me back in touch with using these tools that I’m using right now as mere instruments of my will, rather than me being forced around the way they were designed to be operated, and in the process losing the very essence of what I was trying to express. Goddammit!” – François K, Expansions (Live Stems Dub and Talk)

    What?

    • Highest quality: ALAC stems by default, or AAC using the best encoder and quality possible.
    • Automatic metadata tagging: scraping metadata from the master file and writing it back to the stem file.
    • Batching: you can use this CLI to batch your stem creation and/or create a powerful workflow.
    • Universal: works on macOS, Windows and Linux.

    Requirement

    Usage

    You can use stemgen.py to generate stems:

    • $ python3 stemgen.py track.wav
    • Have fun! Your new .stem.m4a file is in output dir
    • Supported input file format are .wav .wave .aif .aiff .flac

    Bring your own stems

    Manually

    You can use stem.py to create stems:

    • $ python3 stem.py -i track/track.0.wav
    • You need to follow this naming convention: [TRACK_NAME].[TRACK_NUMBER].[FILE_EXTENSION]
    • TRACK_NAME should be identical for all files
    • Please use 0 as the TRACK_NUMBER for the master track. Example: 'track.0.wav' for the master file then 'track.1.wav' for the first stem, etc…
    • Have fun! Your new .stem.m4a file is in output dir
    • Supported input file format are .wav .wave .aif .aiff .flac

    With Ableton Live

    You can use Ableton Live to create stems:

    • $ python3 ableton.py

    Quick install on macOS

    • python3 -m pip install -U demucs
    • python3 -m pip install mutagen
    • brew install coreutils ffmpeg sox

    Quick install on Linux

    Long install on Windows

    qaac

    If you plan to encode in AAC, you should install qaac. Here is a quick guide:

    Then, to use Audio Toolbox from Apple:

    • git clone https://github.com/nu774/makeportable.git
    • cd makeportable
    • Download the iTunes installer from https://www.apple.com/itunes/download/win64
    • Copy the iTunes installer to the makeportable folder
    • makeportable.cmd
    • Copy the newly created folder QTfiles64 to your C:\Program Files\qaac folder

    Then, to support FLAC files:

    • Download FLAC from https://github.com/xiph/flac/releases
    • Copy the libFLAC.dll file from the Win64 folder (or Win32 depending on your system)
    • Paste it in your C:\Program Files\qaac folder

    Enjoy! You can now encode AAC stems with Apple Audio Toolbox, the highest quality AAC encoder.

    Performance

    • Stem and Stemgen supports 16-bit and 24-bit audio files!
    • Stemgen needs to downsample the track to 44.1kHz to avoid problems with the separation software because the models are trained on 44.1kHz audio files. Stem uses the original sample rate.
    • You may notice that the output file is pretty big. Apple Lossless Codec (ALAC) for audio encoding is used for lossless audio compression at the cost of increased file size.

    Screenshot Input Screenshot Output

    Disclaimer

    If you plan to use Stemgen on copyrighted material, make sure you get proper authorization from right owners beforehand.

    License

    MIT

    Visit original content creator repository https://github.com/axeldelafosse/stemgen
  • stemgen

    🎛 Stemgen

    Stemgen is a Stem file generator. Convert any track into a Stem and have fun with Traktor.

    A Stem file is an open, multi-channel audio file that contains a track split into four musical elements – bass, drums, vocals, and melody, for example. With each element available independently, you have more control over the music you play.

    Stemgen uses bs_roformer or demucs to separate the 4 stems and ni-stem to create the Stem file.

    Screenshot Before Screenshot After

    Our new file contains four stems: drums, bass, other (melody) and vocals.

    Note

    Traktor Pro 4 includes stem separation! Fortunately, it is backward-compatible and you can upgrade without any issue. But unfortunately, Stemgen still makes sense because:

    • Stemgen is the only way to create lossless ALAC stem files… for now! Please make yourself heard on the forum if you think lossless stems matters
    • Stemgen is the only way to create your own stem files from Ableton Live and from a CLI
    • Stemgen writes the metadata of the original files to the stem files, so you can easily sync them between computers

    Why?

    “It’s no secret that I’m fully behind the approach to encourage individuality in creativity and for artists to play differently. Stems is a new format that mirrors my constant quest for spontaneity to drive the art of performance forwards. I hope that releasing my album From My Mind To Yours in this format, mastered by LANDR, inspires others to support the approach and bring even more flexibility to the art of DJing amongst its most progressive supporters.” – Richie Hawtin

    Stems are fun but nobody’s releasing them. Stemgen is a way to create your own stems with only one command.

    Note

    May 2023 Update: I saw François K last week in Paris at the Loft Babies party and I discovered that he’s playing with Stems. I highly recommend checking out his videos on YouTube: https://www.youtube.com/playlist?list=PLCr4LSsJFk48tmNoKn-l7mgsB5XUd2Af9. He’s a legend and a true pioneer. I’m so happy to see him having fun with Stems. And trust me: it’s even better in real life. Can’t wait to see him again!

    “There is a really big difference between using a tool, a computer as a tool, to make it do specific things we want it to do, in the manner in which we want it to accomplish it. In most other situations, we all find ourselves dealing with a pre-programmed or pre-determined path that the software designer has decided we must use the software in order to get certain things done. And I think that makes it that we, little by little, become controlled by the path that was designed by the people who wrote the software and forced into these gullies that they created of usage, that this is how we are supposed to be doing things. And after a while I think it’s making us forget who we were and what the essence of what the music was supposed to be about and really represented.

    And this right here — I have to be honest — it’s groundbreaking to me in that sense. It’s putting me back in touch with using these tools that I’m using right now as mere instruments of my will, rather than me being forced around the way they were designed to be operated, and in the process losing the very essence of what I was trying to express. Goddammit!” – François K, Expansions (Live Stems Dub and Talk)

    What?

    • Highest quality: ALAC stems by default, or AAC using the best encoder and quality possible.
    • Automatic metadata tagging: scraping metadata from the master file and writing it back to the stem file.
    • Batching: you can use this CLI to batch your stem creation and/or create a powerful workflow.
    • Universal: works on macOS, Windows and Linux.

    Requirement

    Usage

    You can use stemgen.py to generate stems:

    • $ python3 stemgen.py track.wav
    • Have fun! Your new .stem.m4a file is in output dir
    • Supported input file format are .wav .wave .aif .aiff .flac

    Bring your own stems

    Manually

    You can use stem.py to create stems:

    • $ python3 stem.py -i track/track.0.wav
    • You need to follow this naming convention: [TRACK_NAME].[TRACK_NUMBER].[FILE_EXTENSION]
    • TRACK_NAME should be identical for all files
    • Please use 0 as the TRACK_NUMBER for the master track. Example: 'track.0.wav' for the master file then 'track.1.wav' for the first stem, etc…
    • Have fun! Your new .stem.m4a file is in output dir
    • Supported input file format are .wav .wave .aif .aiff .flac

    With Ableton Live

    You can use Ableton Live to create stems:

    • $ python3 ableton.py

    Quick install on macOS

    • python3 -m pip install -U demucs
    • python3 -m pip install mutagen
    • brew install coreutils ffmpeg sox

    Quick install on Linux

    Long install on Windows

    qaac

    If you plan to encode in AAC, you should install qaac. Here is a quick guide:

    Then, to use Audio Toolbox from Apple:

    • git clone https://github.com/nu774/makeportable.git
    • cd makeportable
    • Download the iTunes installer from https://www.apple.com/itunes/download/win64
    • Copy the iTunes installer to the makeportable folder
    • makeportable.cmd
    • Copy the newly created folder QTfiles64 to your C:\Program Files\qaac folder

    Then, to support FLAC files:

    • Download FLAC from https://github.com/xiph/flac/releases
    • Copy the libFLAC.dll file from the Win64 folder (or Win32 depending on your system)
    • Paste it in your C:\Program Files\qaac folder

    Enjoy! You can now encode AAC stems with Apple Audio Toolbox, the highest quality AAC encoder.

    Performance

    • Stem and Stemgen supports 16-bit and 24-bit audio files!
    • Stemgen needs to downsample the track to 44.1kHz to avoid problems with the separation software because the models are trained on 44.1kHz audio files. Stem uses the original sample rate.
    • You may notice that the output file is pretty big. Apple Lossless Codec (ALAC) for audio encoding is used for lossless audio compression at the cost of increased file size.

    Screenshot Input Screenshot Output

    Disclaimer

    If you plan to use Stemgen on copyrighted material, make sure you get proper authorization from right owners beforehand.

    License

    MIT

    Visit original content creator repository https://github.com/axeldelafosse/stemgen
  • rtt-ds3231

    DS3231 驱动软件包

    1 介绍

    ds3231软件包是针对RT-Thread驱动框架实现的实时时钟驱动,遵循RT-Thread RTC框架,可以从芯片内置RTC无缝切换使用外置高精度ds3231 RTC。软件包支持实时时钟和闹钟功能。

    1.1 目录结构

    名称 说明
    ds3231.h 头文件
    ds3231.c 源文件
    README.md 软件包使用说明
    ds3231_datasheet.pdf 芯片中文手册
    SConscript RT-Thread默认构建脚本
    LICENSE 许可证文件

    1.2 许可证

    ds3231 软件包遵循 Apache license v2.0 许可,详见 LICENSE 文件。

    1.3 依赖

    • RT-Thread 3.0+
    • RT-Thread I2C设备驱动框架
    • RT-Thread RTC设备驱动框架

    2 获取 ds3231软件包

    使用 ds3231 package 需要在 RT-Thread 的包管理器中选择它,具体路径如下:

    RT-Thread online packages --->
        peripheral libraries and drivers --->
            [*] extren rtc drivers  --->
                [*] ds3231:External RTC drivers fo ds3231
                     Version (latest)  --->
    

    然后让 RT-Thread 的包管理器自动更新,或者使用 pkgs --update 命令更新包到 BSP 中。

    3 使用 ds3231 软件包

    3.1 初始化

    首先需初始化ds3231驱动,可以手动在初始化线程调用“rt_hw_ds3231_init()”初始化,也可以直接使用“INIT_DEVICE_EXPORT”自动初始化。

    注意:如果开启了芯片内部RTC,需先禁止内部RTC

    3.2 使用方式

    获取当前时间

    time_t time(time_t *t)
    time_t now;      
    now = time(RT_NULL);
    

    设置时间

     #define RT_DEVICE_CTRL_RTC_SET_TIME     0x11        /**< set time */
     rt_err_t rt_device_control(rt_device_t dev, int cmd, void *arg);
    

    获取闹钟时间

     #define RT_DEVICE_CTRL_RTC_GET_ALARM    0x12        /**< get alarm */
     rt_err_t rt_device_control(rt_device_t dev, int cmd, void *arg);
    

    设置闹钟时间

     #define RT_DEVICE_CTRL_RTC_SET_ALARM    0x13      /**< set alarm */
     rt_err_t rt_device_control(rt_device_t dev, int cmd, void *arg);
    

    提供一个获取内部温度接口

    float ds3231_get_temperature(void);
    

    详细用法可以参考“/components/drivers/rtc.c”和“/components/drivers/alarm.c”源码。

    3.3 msh/finsh测试

    /*msh获取时间*/
    msh >date
    Sun Mar  1 12:01:13 2020
    ........
    /*msh设置时间*/
    msh >date 2020 03 01 20 00 00 
    msh >date
    Sun Mar  1 20:00:03 2020
    ........
    /*finsh获取时间*/
    finsh >list_date()
    Sun Mar  1 20:17:13 2020
    ........
    /*finsh设置时间*/
    finsh >set_date(2020,3,2)
            0, 0x00000000
    finsh >set_time(12,0,0)  
            0, 0x00000000
    finsh >list_date()
    Mon Mar  2 12:00:04 2020
    ........
    /*msh打印温度*/
    msh >list_ds31_temp
    ds3231 temperature: [29.0C]
    ........
    /*finsh打印温度*/
    finsh >list_ds31_temp()
    ds3231 temperature: [29.0C] 
    

    4 注意事项

    使用RT-Thread的RTC框架,RTC设备注册名称为“rtc”,注意需先屏蔽内置芯片RTC驱动。

    5 联系方式

    Visit original content creator repository
    https://github.com/Prry/rtt-ds3231

  • ImageViewer

                        GNU GENERAL PUBLIC LICENSE
                           Version 3, 29 June 2007
    
     Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
     Everyone is permitted to copy and distribute verbatim copies
     of this license document, but changing it is not allowed.
    
                                Preamble
    
      The GNU General Public License is a free, copyleft license for
    software and other kinds of works.
    
      The licenses for most software and other practical works are designed
    to take away your freedom to share and change the works.  By contrast,
    the GNU General Public License is intended to guarantee your freedom to
    share and change all versions of a program--to make sure it remains free
    software for all its users.  We, the Free Software Foundation, use the
    GNU General Public License for most of our software; it applies also to
    any other work released this way by its authors.  You can apply it to
    your programs, too.
    
      When we speak of free software, we are referring to freedom, not
    price.  Our General Public Licenses are designed to make sure that you
    have the freedom to distribute copies of free software (and charge for
    them if you wish), that you receive source code or can get it if you
    want it, that you can change the software or use pieces of it in new
    free programs, and that you know you can do these things.
    
      To protect your rights, we need to prevent others from denying you
    these rights or asking you to surrender the rights.  Therefore, you have
    certain responsibilities if you distribute copies of the software, or if
    you modify it: responsibilities to respect the freedom of others.
    
      For example, if you distribute copies of such a program, whether
    gratis or for a fee, you must pass on to the recipients the same
    freedoms that you received.  You must make sure that they, too, receive
    or can get the source code.  And you must show them these terms so they
    know their rights.
    
      Developers that use the GNU GPL protect your rights with two steps:
    (1) assert copyright on the software, and (2) offer you this License
    giving you legal permission to copy, distribute and/or modify it.
    
      For the developers' and authors' protection, the GPL clearly explains
    that there is no warranty for this free software.  For both users' and
    authors' sake, the GPL requires that modified versions be marked as
    changed, so that their problems will not be attributed erroneously to
    authors of previous versions.
    
      Some devices are designed to deny users access to install or run
    modified versions of the software inside them, although the manufacturer
    can do so.  This is fundamentally incompatible with the aim of
    protecting users' freedom to change the software.  The systematic
    pattern of such abuse occurs in the area of products for individuals to
    use, which is precisely where it is most unacceptable.  Therefore, we
    have designed this version of the GPL to prohibit the practice for those
    products.  If such problems arise substantially in other domains, we
    stand ready to extend this provision to those domains in future versions
    of the GPL, as needed to protect the freedom of users.
    
      Finally, every program is threatened constantly by software patents.
    States should not allow patents to restrict development and use of
    software on general-purpose computers, but in those that do, we wish to
    avoid the special danger that patents applied to a free program could
    make it effectively proprietary.  To prevent this, the GPL assures that
    patents cannot be used to render the program non-free.
    
      The precise terms and conditions for copying, distribution and
    modification follow.
    
                           TERMS AND CONDITIONS
    
      0. Definitions.
    
      "This License" refers to version 3 of the GNU General Public License.
    
      "Copyright" also means copyright-like laws that apply to other kinds of
    works, such as semiconductor masks.
    
      "The Program" refers to any copyrightable work licensed under this
    License.  Each licensee is addressed as "you".  "Licensees" and
    "recipients" may be individuals or organizations.
    
      To "modify" a work means to copy from or adapt all or part of the work
    in a fashion requiring copyright permission, other than the making of an
    exact copy.  The resulting work is called a "modified version" of the
    earlier work or a work "based on" the earlier work.
    
      A "covered work" means either the unmodified Program or a work based
    on the Program.
    
      To "propagate" a work means to do anything with it that, without
    permission, would make you directly or secondarily liable for
    infringement under applicable copyright law, except executing it on a
    computer or modifying a private copy.  Propagation includes copying,
    distribution (with or without modification), making available to the
    public, and in some countries other activities as well.
    
      To "convey" a work means any kind of propagation that enables other
    parties to make or receive copies.  Mere interaction with a user through
    a computer network, with no transfer of a copy, is not conveying.
    
      An interactive user interface displays "Appropriate Legal Notices"
    to the extent that it includes a convenient and prominently visible
    feature that (1) displays an appropriate copyright notice, and (2)
    tells the user that there is no warranty for the work (except to the
    extent that warranties are provided), that licensees may convey the
    work under this License, and how to view a copy of this License.  If
    the interface presents a list of user commands or options, such as a
    menu, a prominent item in the list meets this criterion.
    
      1. Source Code.
    
      The "source code" for a work means the preferred form of the work
    for making modifications to it.  "Object code" means any non-source
    form of a work.
    
      A "Standard Interface" means an interface that either is an official
    standard defined by a recognized standards body, or, in the case of
    interfaces specified for a particular programming language, one that
    is widely used among developers working in that language.
    
      The "System Libraries" of an executable work include anything, other
    than the work as a whole, that (a) is included in the normal form of
    packaging a Major Component, but which is not part of that Major
    Component, and (b) serves only to enable use of the work with that
    Major Component, or to implement a Standard Interface for which an
    implementation is available to the public in source code form.  A
    "Major Component", in this context, means a major essential component
    (kernel, window system, and so on) of the specific operating system
    (if any) on which the executable work runs, or a compiler used to
    produce the work, or an object code interpreter used to run it.
    
      The "Corresponding Source" for a work in object code form means all
    the source code needed to generate, install, and (for an executable
    work) run the object code and to modify the work, including scripts to
    control those activities.  However, it does not include the work's
    System Libraries, or general-purpose tools or generally available free
    programs which are used unmodified in performing those activities but
    which are not part of the work.  For example, Corresponding Source
    includes interface definition files associated with source files for
    the work, and the source code for shared libraries and dynamically
    linked subprograms that the work is specifically designed to require,
    such as by intimate data communication or control flow between those
    subprograms and other parts of the work.
    
      The Corresponding Source need not include anything that users
    can regenerate automatically from other parts of the Corresponding
    Source.
    
      The Corresponding Source for a work in source code form is that
    same work.
    
      2. Basic Permissions.
    
      All rights granted under this License are granted for the term of
    copyright on the Program, and are irrevocable provided the stated
    conditions are met.  This License explicitly affirms your unlimited
    permission to run the unmodified Program.  The output from running a
    covered work is covered by this License only if the output, given its
    content, constitutes a covered work.  This License acknowledges your
    rights of fair use or other equivalent, as provided by copyright law.
    
      You may make, run and propagate covered works that you do not
    convey, without conditions so long as your license otherwise remains
    in force.  You may convey covered works to others for the sole purpose
    of having them make modifications exclusively for you, or provide you
    with facilities for running those works, provided that you comply with
    the terms of this License in conveying all material for which you do
    not control copyright.  Those thus making or running the covered works
    for you must do so exclusively on your behalf, under your direction
    and control, on terms that prohibit them from making any copies of
    your copyrighted material outside their relationship with you.
    
      Conveying under any other circumstances is permitted solely under
    the conditions stated below.  Sublicensing is not allowed; section 10
    makes it unnecessary.
    
      3. Protecting Users' Legal Rights From Anti-Circumvention Law.
    
      No covered work shall be deemed part of an effective technological
    measure under any applicable law fulfilling obligations under article
    11 of the WIPO copyright treaty adopted on 20 December 1996, or
    similar laws prohibiting or restricting circumvention of such
    measures.
    
      When you convey a covered work, you waive any legal power to forbid
    circumvention of technological measures to the extent such circumvention
    is effected by exercising rights under this License with respect to
    the covered work, and you disclaim any intention to limit operation or
    modification of the work as a means of enforcing, against the work's
    users, your or third parties' legal rights to forbid circumvention of
    technological measures.
    
      4. Conveying Verbatim Copies.
    
      You may convey verbatim copies of the Program's source code as you
    receive it, in any medium, provided that you conspicuously and
    appropriately publish on each copy an appropriate copyright notice;
    keep intact all notices stating that this License and any
    non-permissive terms added in accord with section 7 apply to the code;
    keep intact all notices of the absence of any warranty; and give all
    recipients a copy of this License along with the Program.
    
      You may charge any price or no price for each copy that you convey,
    and you may offer support or warranty protection for a fee.
    
      5. Conveying Modified Source Versions.
    
      You may convey a work based on the Program, or the modifications to
    produce it from the Program, in the form of source code under the
    terms of section 4, provided that you also meet all of these conditions:
    
        a) The work must carry prominent notices stating that you modified
        it, and giving a relevant date.
    
        b) The work must carry prominent notices stating that it is
        released under this License and any conditions added under section
        7.  This requirement modifies the requirement in section 4 to
        "keep intact all notices".
    
        c) You must license the entire work, as a whole, under this
        License to anyone who comes into possession of a copy.  This
        License will therefore apply, along with any applicable section 7
        additional terms, to the whole of the work, and all its parts,
        regardless of how they are packaged.  This License gives no
        permission to license the work in any other way, but it does not
        invalidate such permission if you have separately received it.
    
        d) If the work has interactive user interfaces, each must display
        Appropriate Legal Notices; however, if the Program has interactive
        interfaces that do not display Appropriate Legal Notices, your
        work need not make them do so.
    
      A compilation of a covered work with other separate and independent
    works, which are not by their nature extensions of the covered work,
    and which are not combined with it such as to form a larger program,
    in or on a volume of a storage or distribution medium, is called an
    "aggregate" if the compilation and its resulting copyright are not
    used to limit the access or legal rights of the compilation's users
    beyond what the individual works permit.  Inclusion of a covered work
    in an aggregate does not cause this License to apply to the other
    parts of the aggregate.
    
      6. Conveying Non-Source Forms.
    
      You may convey a covered work in object code form under the terms
    of sections 4 and 5, provided that you also convey the
    machine-readable Corresponding Source under the terms of this License,
    in one of these ways:
    
        a) Convey the object code in, or embodied in, a physical product
        (including a physical distribution medium), accompanied by the
        Corresponding Source fixed on a durable physical medium
        customarily used for software interchange.
    
        b) Convey the object code in, or embodied in, a physical product
        (including a physical distribution medium), accompanied by a
        written offer, valid for at least three years and valid for as
        long as you offer spare parts or customer support for that product
        model, to give anyone who possesses the object code either (1) a
        copy of the Corresponding Source for all the software in the
        product that is covered by this License, on a durable physical
        medium customarily used for software interchange, for a price no
        more than your reasonable cost of physically performing this
        conveying of source, or (2) access to copy the
        Corresponding Source from a network server at no charge.
    
        c) Convey individual copies of the object code with a copy of the
        written offer to provide the Corresponding Source.  This
        alternative is allowed only occasionally and noncommercially, and
        only if you received the object code with such an offer, in accord
        with subsection 6b.
    
        d) Convey the object code by offering access from a designated
        place (gratis or for a charge), and offer equivalent access to the
        Corresponding Source in the same way through the same place at no
        further charge.  You need not require recipients to copy the
        Corresponding Source along with the object code.  If the place to
        copy the object code is a network server, the Corresponding Source
        may be on a different server (operated by you or a third party)
        that supports equivalent copying facilities, provided you maintain
        clear directions next to the object code saying where to find the
        Corresponding Source.  Regardless of what server hosts the
        Corresponding Source, you remain obligated to ensure that it is
        available for as long as needed to satisfy these requirements.
    
        e) Convey the object code using peer-to-peer transmission, provided
        you inform other peers where the object code and Corresponding
        Source of the work are being offered to the general public at no
        charge under subsection 6d.
    
      A separable portion of the object code, whose source code is excluded
    from the Corresponding Source as a System Library, need not be
    included in conveying the object code work.
    
      A "User Product" is either (1) a "consumer product", which means any
    tangible personal property which is normally used for personal, family,
    or household purposes, or (2) anything designed or sold for incorporation
    into a dwelling.  In determining whether a product is a consumer product,
    doubtful cases shall be resolved in favor of coverage.  For a particular
    product received by a particular user, "normally used" refers to a
    typical or common use of that class of product, regardless of the status
    of the particular user or of the way in which the particular user
    actually uses, or expects or is expected to use, the product.  A product
    is a consumer product regardless of whether the product has substantial
    commercial, industrial or non-consumer uses, unless such uses represent
    the only significant mode of use of the product.
    
      "Installation Information" for a User Product means any methods,
    procedures, authorization keys, or other information required to install
    and execute modified versions of a covered work in that User Product from
    a modified version of its Corresponding Source.  The information must
    suffice to ensure that the continued functioning of the modified object
    code is in no case prevented or interfered with solely because
    modification has been made.
    
      If you convey an object code work under this section in, or with, or
    specifically for use in, a User Product, and the conveying occurs as
    part of a transaction in which the right of possession and use of the
    User Product is transferred to the recipient in perpetuity or for a
    fixed term (regardless of how the transaction is characterized), the
    Corresponding Source conveyed under this section must be accompanied
    by the Installation Information.  But this requirement does not apply
    if neither you nor any third party retains the ability to install
    modified object code on the User Product (for example, the work has
    been installed in ROM).
    
      The requirement to provide Installation Information does not include a
    requirement to continue to provide support service, warranty, or updates
    for a work that has been modified or installed by the recipient, or for
    the User Product in which it has been modified or installed.  Access to a
    network may be denied when the modification itself materially and
    adversely affects the operation of the network or violates the rules and
    protocols for communication across the network.
    
      Corresponding Source conveyed, and Installation Information provided,
    in accord with this section must be in a format that is publicly
    documented (and with an implementation available to the public in
    source code form), and must require no special password or key for
    unpacking, reading or copying.
    
      7. Additional Terms.
    
      "Additional permissions" are terms that supplement the terms of this
    License by making exceptions from one or more of its conditions.
    Additional permissions that are applicable to the entire Program shall
    be treated as though they were included in this License, to the extent
    that they are valid under applicable law.  If additional permissions
    apply only to part of the Program, that part may be used separately
    under those permissions, but the entire Program remains governed by
    this License without regard to the additional permissions.
    
      When you convey a copy of a covered work, you may at your option
    remove any additional permissions from that copy, or from any part of
    it.  (Additional permissions may be written to require their own
    removal in certain cases when you modify the work.)  You may place
    additional permissions on material, added by you to a covered work,
    for which you have or can give appropriate copyright permission.
    
      Notwithstanding any other provision of this License, for material you
    add to a covered work, you may (if authorized by the copyright holders of
    that material) supplement the terms of this License with terms:
    
        a) Disclaiming warranty or limiting liability differently from the
        terms of sections 15 and 16 of this License; or
    
        b) Requiring preservation of specified reasonable legal notices or
        author attributions in that material or in the Appropriate Legal
        Notices displayed by works containing it; or
    
        c) Prohibiting misrepresentation of the origin of that material, or
        requiring that modified versions of such material be marked in
        reasonable ways as different from the original version; or
    
        d) Limiting the use for publicity purposes of names of licensors or
        authors of the material; or
    
        e) Declining to grant rights under trademark law for use of some
        trade names, trademarks, or service marks; or
    
        f) Requiring indemnification of licensors and authors of that
        material by anyone who conveys the material (or modified versions of
        it) with contractual assumptions of liability to the recipient, for
        any liability that these contractual assumptions directly impose on
        those licensors and authors.
    
      All other non-permissive additional terms are considered "further
    restrictions" within the meaning of section 10.  If the Program as you
    received it, or any part of it, contains a notice stating that it is
    governed by this License along with a term that is a further
    restriction, you may remove that term.  If a license document contains
    a further restriction but permits relicensing or conveying under this
    License, you may add to a covered work material governed by the terms
    of that license document, provided that the further restriction does
    not survive such relicensing or conveying.
    
      If you add terms to a covered work in accord with this section, you
    must place, in the relevant source files, a statement of the
    additional terms that apply to those files, or a notice indicating
    where to find the applicable terms.
    
      Additional terms, permissive or non-permissive, may be stated in the
    form of a separately written license, or stated as exceptions;
    the above requirements apply either way.
    
      8. Termination.
    
      You may not propagate or modify a covered work except as expressly
    provided under this License.  Any attempt otherwise to propagate or
    modify it is void, and will automatically terminate your rights under
    this License (including any patent licenses granted under the third
    paragraph of section 11).
    
      However, if you cease all violation of this License, then your
    license from a particular copyright holder is reinstated (a)
    provisionally, unless and until the copyright holder explicitly and
    finally terminates your license, and (b) permanently, if the copyright
    holder fails to notify you of the violation by some reasonable means
    prior to 60 days after the cessation.
    
      Moreover, your license from a particular copyright holder is
    reinstated permanently if the copyright holder notifies you of the
    violation by some reasonable means, this is the first time you have
    received notice of violation of this License (for any work) from that
    copyright holder, and you cure the violation prior to 30 days after
    your receipt of the notice.
    
      Termination of your rights under this section does not terminate the
    licenses of parties who have received copies or rights from you under
    this License.  If your rights have been terminated and not permanently
    reinstated, you do not qualify to receive new licenses for the same
    material under section 10.
    
      9. Acceptance Not Required for Having Copies.
    
      You are not required to accept this License in order to receive or
    run a copy of the Program.  Ancillary propagation of a covered work
    occurring solely as a consequence of using peer-to-peer transmission
    to receive a copy likewise does not require acceptance.  However,
    nothing other than this License grants you permission to propagate or
    modify any covered work.  These actions infringe copyright if you do
    not accept this License.  Therefore, by modifying or propagating a
    covered work, you indicate your acceptance of this License to do so.
    
      10. Automatic Licensing of Downstream Recipients.
    
      Each time you convey a covered work, the recipient automatically
    receives a license from the original licensors, to run, modify and
    propagate that work, subject to this License.  You are not responsible
    for enforcing compliance by third parties with this License.
    
      An "entity transaction" is a transaction transferring control of an
    organization, or substantially all assets of one, or subdividing an
    organization, or merging organizations.  If propagation of a covered
    work results from an entity transaction, each party to that
    transaction who receives a copy of the work also receives whatever
    licenses to the work the party's predecessor in interest had or could
    give under the previous paragraph, plus a right to possession of the
    Corresponding Source of the work from the predecessor in interest, if
    the predecessor has it or can get it with reasonable efforts.
    
      You may not impose any further restrictions on the exercise of the
    rights granted or affirmed under this License.  For example, you may
    not impose a license fee, royalty, or other charge for exercise of
    rights granted under this License, and you may not initiate litigation
    (including a cross-claim or counterclaim in a lawsuit) alleging that
    any patent claim is infringed by making, using, selling, offering for
    sale, or importing the Program or any portion of it.
    
      11. Patents.
    
      A "contributor" is a copyright holder who authorizes use under this
    License of the Program or a work on which the Program is based.  The
    work thus licensed is called the contributor's "contributor version".
    
      A contributor's "essential patent claims" are all patent claims
    owned or controlled by the contributor, whether already acquired or
    hereafter acquired, that would be infringed by some manner, permitted
    by this License, of making, using, or selling its contributor version,
    but do not include claims that would be infringed only as a
    consequence of further modification of the contributor version.  For
    purposes of this definition, "control" includes the right to grant
    patent sublicenses in a manner consistent with the requirements of
    this License.
    
      Each contributor grants you a non-exclusive, worldwide, royalty-free
    patent license under the contributor's essential patent claims, to
    make, use, sell, offer for sale, import and otherwise run, modify and
    propagate the contents of its contributor version.
    
      In the following three paragraphs, a "patent license" is any express
    agreement or commitment, however denominated, not to enforce a patent
    (such as an express permission to practice a patent or covenant not to
    sue for patent infringement).  To "grant" such a patent license to a
    party means to make such an agreement or commitment not to enforce a
    patent against the party.
    
      If you convey a covered work, knowingly relying on a patent license,
    and the Corresponding Source of the work is not available for anyone
    to copy, free of charge and under the terms of this License, through a
    publicly available network server or other readily accessible means,
    then you must either (1) cause the Corresponding Source to be so
    available, or (2) arrange to deprive yourself of the benefit of the
    patent license for this particular work, or (3) arrange, in a manner
    consistent with the requirements of this License, to extend the patent
    license to downstream recipients.  "Knowingly relying" means you have
    actual knowledge that, but for the patent license, your conveying the
    covered work in a country, or your recipient's use of the covered work
    in a country, would infringe one or more identifiable patents in that
    country that you have reason to believe are valid.
    
      If, pursuant to or in connection with a single transaction or
    arrangement, you convey, or propagate by procuring conveyance of, a
    covered work, and grant a patent license to some of the parties
    receiving the covered work authorizing them to use, propagate, modify
    or convey a specific copy of the covered work, then the patent license
    you grant is automatically extended to all recipients of the covered
    work and works based on it.
    
      A patent license is "discriminatory" if it does not include within
    the scope of its coverage, prohibits the exercise of, or is
    conditioned on the non-exercise of one or more of the rights that are
    specifically granted under this License.  You may not convey a covered
    work if you are a party to an arrangement with a third party that is
    in the business of distributing software, under which you make payment
    to the third party based on the extent of your activity of conveying
    the work, and under which the third party grants, to any of the
    parties who would receive the covered work from you, a discriminatory
    patent license (a) in connection with copies of the covered work
    conveyed by you (or copies made from those copies), or (b) primarily
    for and in connection with specific products or compilations that
    contain the covered work, unless you entered into that arrangement,
    or that patent license was granted, prior to 28 March 2007.
    
      Nothing in this License shall be construed as excluding or limiting
    any implied license or other defenses to infringement that may
    otherwise be available to you under applicable patent law.
    
      12. No Surrender of Others' Freedom.
    
      If conditions are imposed on you (whether by court order, agreement or
    otherwise) that contradict the conditions of this License, they do not
    excuse you from the conditions of this License.  If you cannot convey a
    covered work so as to satisfy simultaneously your obligations under this
    License and any other pertinent obligations, then as a consequence you may
    not convey it at all.  For example, if you agree to terms that obligate you
    to collect a royalty for further conveying from those to whom you convey
    the Program, the only way you could satisfy both those terms and this
    License would be to refrain entirely from conveying the Program.
    
      13. Use with the GNU Affero General Public License.
    
      Notwithstanding any other provision of this License, you have
    permission to link or combine any covered work with a work licensed
    under version 3 of the GNU Affero General Public License into a single
    combined work, and to convey the resulting work.  The terms of this
    License will continue to apply to the part which is the covered work,
    but the special requirements of the GNU Affero General Public License,
    section 13, concerning interaction through a network will apply to the
    combination as such.
    
      14. Revised Versions of this License.
    
      The Free Software Foundation may publish revised and/or new versions of
    the GNU General Public License from time to time.  Such new versions will
    be similar in spirit to the present version, but may differ in detail to
    address new problems or concerns.
    
      Each version is given a distinguishing version number.  If the
    Program specifies that a certain numbered version of the GNU General
    Public License "or any later version" applies to it, you have the
    option of following the terms and conditions either of that numbered
    version or of any later version published by the Free Software
    Foundation.  If the Program does not specify a version number of the
    GNU General Public License, you may choose any version ever published
    by the Free Software Foundation.
    
      If the Program specifies that a proxy can decide which future
    versions of the GNU General Public License can be used, that proxy's
    public statement of acceptance of a version permanently authorizes you
    to choose that version for the Program.
    
      Later license versions may give you additional or different
    permissions.  However, no additional obligations are imposed on any
    author or copyright holder as a result of your choosing to follow a
    later version.
    
      15. Disclaimer of Warranty.
    
      THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
    APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
    HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
    OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
    THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
    PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
    IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
    ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
    
      16. Limitation of Liability.
    
      IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
    WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
    THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
    GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
    USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
    DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
    PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
    EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
    SUCH DAMAGES.
    
      17. Interpretation of Sections 15 and 16.
    
      If the disclaimer of warranty and limitation of liability provided
    above cannot be given local legal effect according to their terms,
    reviewing courts shall apply local law that most closely approximates
    an absolute waiver of all civil liability in connection with the
    Program, unless a warranty or assumption of liability accompanies a
    copy of the Program in return for a fee.
    
                         END OF TERMS AND CONDITIONS
    
                How to Apply These Terms to Your New Programs
    
      If you develop a new program, and you want it to be of the greatest
    possible use to the public, the best way to achieve this is to make it
    free software which everyone can redistribute and change under these terms.
    
      To do so, attach the following notices to the program.  It is safest
    to attach them to the start of each source file to most effectively
    state the exclusion of warranty; and each file should have at least
    the "copyright" line and a pointer to where the full notice is found.
    
        <one line to give the program's name and a brief idea of what it does.>
        Copyright (C) <year>  <name of author>
    
        This program is free software: you can redistribute it and/or modify
        it under the terms of the GNU General Public License as published by
        the Free Software Foundation, either version 3 of the License, or
        (at your option) any later version.
    
        This program is distributed in the hope that it will be useful,
        but WITHOUT ANY WARRANTY; without even the implied warranty of
        MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
        GNU General Public License for more details.
    
        You should have received a copy of the GNU General Public License
        along with this program.  If not, see <http://www.gnu.org/licenses/>.
    
    Also add information on how to contact you by electronic and paper mail.
    
      If the program does terminal interaction, make it output a short
    notice like this when it starts in an interactive mode:
    
        <program>  Copyright (C) <year>  <name of author>
        This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
        This is free software, and you are welcome to redistribute it
        under certain conditions; type `show c' for details.
    
    The hypothetical commands `show w' and `show c' should show the appropriate
    parts of the General Public License.  Of course, your program's commands
    might be different; for a GUI interface, you would use an "about box".
    
      You should also get your employer (if you work as a programmer) or school,
    if any, to sign a "copyright disclaimer" for the program, if necessary.
    For more information on this, and how to apply and follow the GNU GPL, see
    <http://www.gnu.org/licenses/>.
    
      The GNU General Public License does not permit incorporating your program
    into proprietary programs.  If your program is a subroutine library, you
    may consider it more useful to permit linking proprietary applications with
    the library.  If this is what you want to do, use the GNU Lesser General
    Public License instead of this License.  But first, please read
    <http://www.gnu.org/philosophy/why-not-lgpl.html>.
    

    Visit original content creator repository
    https://github.com/sklprogs/ImageViewer