Afesta Tools#

PyPI Status Python Version License

Read the documentation at https://afesta-tools.readthedocs.io/ Tests Codecov

pre-commit Black

Library and tools for AFesta.tv

Features#

  • Login to Afesta/LPEG API and register as a new player/client

  • Re-use existing 4D Media Player installation + login credentials when available (Windows only)

  • Download Afesta videos via CLI (requires valid account and appropriate purchases/permissions)

  • Download and extract interlocking goods scripts from Afesta vcz archives (supports extracting scripts in both Vorze CSV and Funscript formats)

Note: 8K downloads are not currently supported, as 4D Media Player only downloads the 4K version for 8K videos. Interlocking goods vcz download and extraction are supported for 8K videos downloaded via the Afesta website.

Requirements#

  • Python 3.9+

  • Valid Afesta account

Installation#

You can install Afesta Tools via pip from PyPI:

$ pip install afesta-tools

Usage#

Login to Afesta via CLI (not required on Windows if 4D Media Player is installed and logged into Afesta):

$ afesta login
Afesta username: username
Afesta password:

List purchased videos which can be downloaded:

$ afesta list
PRVR-050-Takumi: 【4K匠】指名No. 1泡姫・涼森れむの中出しソ...
3DSVR-1393: 【8KHQ】【紗倉まな8K解禁】妻に捨てられ、残...
...

$ afesta list -d
PRVR-050-Takumi:
  【4K匠】指名No. 1泡姫・涼森れむの中出しソープ濃厚ご奉仕SEX!
  Parts: 3
  Actresses: 涼森れむ
  Genres: 女優
  Release date: 01/29/21 10:00:00 JST
  Duration: 1:16:26
...

$ afesta list -l en
PRVR-050-Takumi: [4K Takumi] Hardcore Cre...
3DSVR-1393: 8KHQ] [8K Liberation of ...
...

$ afesta list -d -l en
PRVR-050-Takumi:
  [4K Takumi] Hardcore Creampie with the Best Girl in the Brothel, starring Remu Suzumori
  Parts: 3
  Actresses: Remu Suzumori
  Genres: AV Actresses
  Release date: 01/29/21 10:00:00 JST
  Duration: 1:16:26
...

Download videos:

$ afesta dl PRVR-050                                                                                                           Downloading PRVR-050-Takumi: 【4K匠】指名No. 1泡姫・涼森れむの中出しソ... (3 parts):   0%|           | 97.7M/19.6G [00:15<50:15, 6.48MB/s]

$ tree .
.
├── PRVR-050-Takumi-R1_sbs.mp4
├── PRVR-050-Takumi-R2_sbs.mp4
└── PRVR-050-Takumi-R3_sbs.mp4

Download vcz archives for Afesta video files:

$ afesta dl-vcz PRVR-050-Takumi-*.mp4
100%|██████████████████████████████████████████████████| 430k/430k [00:00<00:00, 740kB/s]
100%|██████████████████████████████████████████████████| 509k/509k [00:00<00:00, 852kB/s]
100%|██████████████████████████████████████████████████| 454k/454k [00:00<00:00, 752kB/s]

$ tree .
.
├── PRVR-050-Takumi-R1_sbs.mp4
├── PRVR-050-Takumi-R1_sbs.vcz
├── PRVR-050-Takumi-R2_sbs.mp4
├── PRVR-050-Takumi-R2_sbs.vcz
├── PRVR-050-Takumi-R3_sbs.mp4
└── PRVR-050-Takumi-R3_sbs.vcz

Extract CSV scripts from vcz archives:

$ afesta extract-script --format csv --format funscript PRVR-050-Takumi-*.vcz
Extracted PRVR-050-Takumi-R1_sbs_cyclone.csv
Extracted PRVR-050-Takumi-R1_sbs.funscript
Extracted PRVR-050-Takumi-R1_sbs_piston.csv
Extracted PRVR-050-Takumi-R1_sbs_onarhythm.csv
...

$ tree .
.
├── PRVR-050-Takumi-R1_sbs.funscript
├── PRVR-050-Takumi-R1_sbs.mp4
├── PRVR-050-Takumi-R1_sbs.vcz
├── PRVR-050-Takumi-R1_sbs_cyclone.csv
├── PRVR-050-Takumi-R1_sbs_onarhythm.csv
├── PRVR-050-Takumi-R1_sbs_piston.csv
├── PRVR-050-Takumi-R2_sbs.funscript
├── PRVR-050-Takumi-R2_sbs.mp4
├── PRVR-050-Takumi-R2_sbs.vcz
├── PRVR-050-Takumi-R2_sbs_cyclone.csv
├── PRVR-050-Takumi-R2_sbs_onarhythm.csv
├── PRVR-050-Takumi-R2_sbs_piston.csv
├── PRVR-050-Takumi-R3_sbs.funscript
├── PRVR-050-Takumi-R3_sbs.mp4
├── PRVR-050-Takumi-R3_sbs.vcz
├── PRVR-050-Takumi-R3_sbs_cyclone.csv
├── PRVR-050-Takumi-R3_sbs_onarhythm.csv
└── PRVR-050-Takumi-R3_sbs_piston.csv

Please see the Command-line Reference for details.

Contributing#

Contributions are very welcome. To learn more, see the Contributor Guide.

License#

Distributed under the terms of the MIT license, Afesta Tools is free and open source software.

Issues#

If you encounter any problems, please file an issue along with a detailed description.

Credits#

This project was generated from @cjolowicz’s Hypermodern Python Cookiecutter template.

Usage#

afesta#

Afesta Tools.

afesta [OPTIONS] COMMAND [ARGS]...

Options

--version#

Show the version and exit.

dl#

Download an afesta video.

Requires an account with permissions to download the video (either via standalone purchase or monthly subscription DL benefits).

If 4D Media Player is installed and the current user is logged in via the player, the existing 4D Media Player credentials will be used. Otherwise, the ‘afesta login’ command must be run before downloading.

afesta dl [OPTIONS] [CODE_OR_FID]...

Options

-q, --quality <quality>#
Options:

h264 | h265

-c, --code#

Download explicit purchase code(s) instead of video FID (i.e. cc123…_0000)

-l, --lang <lang>#
Options:

jp | en

Arguments

CODE_OR_FID#

Optional argument(s)

dl-vcz#

Download vcz files for an afesta video.

Requires an account with permissions to download the video (either via standalone purchase or monthly subscription DL benefits).

If 4D Media Player is installed and the current user is logged in via the player, the existing 4D Media Player credentials will be used. Otherwise, the ‘afesta login’ command must be run before downloading.

afesta dl-vcz [OPTIONS] [VIDEO_ID]...

Arguments

VIDEO_ID#

Optional argument(s)

extract-script#

Extract interlocking goods script files from a VCZ file.

afesta extract-script [OPTIONS] [FILENAME]...

Options

--format <fmt>#

Script format (defaults to CSV). –format can be specified multipletimes to extract more than one format.

Options:

csv | funscript | vcsx

Arguments

FILENAME#

Optional argument(s)

list#

List available afesta video downloads.

Requires an account with permissions to download the video (either via standalone purchase or monthly subscription DL benefits).

If 4D Media Player is installed and the current user is logged in via the player, the existing 4D Media Player credentials will be used. Otherwise, the ‘afesta login’ command must be run before downloading.

afesta list [OPTIONS]

Options

-l, --lang <lang>#
Options:

jp | en

-d, --detail#

List detailed video information.

--tv#

List AfestaTV/2D videos (defaults to VR).

login#

Login to Afesta and register afesta-tools as a new player.

If username and/or password are not specified, they will be prompted via the command-line.

Login is not required if 4D Media Player is installed and the current user has logged into 4D Media Player and registered it with an Afesta account.

Note that afesta-tools only stores username and API tokens (password will not be saved to disk).

afesta login [OPTIONS]

Options

-u, --username <username>#

Afesta username.

-p, --password <password>#

Afesta password.

-f, --force#

Overwrite existing credentials.

Reference#

afesta_tools#

Afesta Tools.

Contributor Guide#

Thank you for your interest in improving this project. This project is open-source under the MIT license and welcomes contributions in the form of bug reports, feature requests, and pull requests.

Here is a list of important resources for contributors:

How to report a bug#

Report bugs on the Issue Tracker.

When filing an issue, make sure to answer these questions:

  • Which operating system and Python version are you using?

  • Which version of this project are you using?

  • What did you do?

  • What did you expect to see?

  • What did you see instead?

The best way to get your bug fixed is to provide a test case, and/or steps to reproduce the issue.

How to request a feature#

Request features on the Issue Tracker.

How to set up your development environment#

You need Python 3.7+ and the following tools:

Install the package with development requirements:

$ poetry install

You can now run an interactive Python session, or the command-line interface:

$ poetry run python
$ poetry run afesta-tools

How to test the project#

Run the full test suite:

$ nox

List the available Nox sessions:

$ nox --list-sessions

You can also run a specific Nox session. For example, invoke the unit test suite like this:

$ nox --session=tests

Unit tests are located in the tests directory, and are written using the pytest testing framework.

How to submit changes#

Open a pull request to submit changes to this project.

Your pull request needs to meet the following guidelines for acceptance:

  • The Nox test suite must pass without errors and warnings.

  • Include unit tests. This project maintains 100% code coverage.

  • If your changes add functionality, update the documentation accordingly.

Feel free to submit early, though—we can always iterate on this.

To run linting and code formatting checks before committing your change, you can install pre-commit as a Git hook by running the following command:

$ nox --session=pre-commit -- install

It is recommended to open an issue before starting work on anything. This will allow a chance to talk it over with the owners and validate your approach.

Contributor Covenant Code of Conduct#

Our Pledge#

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards#

Examples of behavior that contributes to a positive environment for our community include:

  • Demonstrating empathy and kindness toward other people

  • Being respectful of differing opinions, viewpoints, and experiences

  • Giving and gracefully accepting constructive feedback

  • Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience

  • Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

  • The use of sexualized language or imagery, and sexual attention or advances of any kind

  • Trolling, insulting or derogatory comments, and personal or political attacks

  • Public or private harassment

  • Publishing others’ private information, such as a physical or email address, without their explicit permission

  • Other conduct which could reasonably be considered inappropriate in a professional setting

Enforcement Responsibilities#

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Scope#

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement#

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at bhrevol@gmail.com. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines#

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction#

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2. Warning#

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban#

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent Ban#

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution#

This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct/.

Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

MIT License#

Copyright © 2022 byeonhyeok

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

The software is provided “as is”, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.