FoxDotMultiBank - Add and use multiple sample banks
Instalation
pip install FoxDotMultiBank
# or
pip install git+https://codeberg.org/FoxDotExtensions/FoxDotMultiBank
Usage
Import lib
from FoxDotMultiBank import *
This will overwrite the Samples object and the Player.new_message_header method so that players can use the keyword bank=0 (or spack=0 or sdb=0).
Use print(Samples.banks) to see all available banks.
d1 >> play('x-o-', bank=1)
Add your own bank:
The folder's structure should look like the default bank:
├── _
│ ├── 1/
│ ├── ampersand/
│ │ ├── '&_0.wav'
│ │ └── '&_1.wav'
│ ├── asterix/
│ ...
├── a/
│ ├── lower/
│ │ ├── 'gb_hihat 0.wav'
│ │ └── 'gb_hihat 1.wav'
│ └── upper/
│ ├── 0_dist_kick.wav
│ └── 1_dist_kick.wav
├── b/
│ ├── lower/
│ └── upper/
...
Samples.addBank(absolute_path)
d1 >> play('x-o-', bank=2)
If there is a folder _loop_/ it will be added with Samples.addPath('/bank/_loop _'), so on loop() you can access the loop without the argument bank=1.
Public banks
Dirt-Samples
Set of samples used in SuperDirt and the TidalCycles tutorials.
Can be used with loop()/ stretch() / gsynth()
Run on SuperCollider:
Quarks.install("Dirt-Samples");
Or on your terminal:
git clone https://github.com/tidalcycles/Dirt-Samples /path/to/Dirt-Samples
Then add the loops to the sample manager:
Samples.addPath('/path/to/Dirt-Samples')
Use print(Samples.loops) to see all available loops.
l1 >> loop('kurt', dur=PDur(3,8))
Using the keyword pshift you can change the note you are playing.
This change is made as in the chromatic scale.
g1 >> gsynth('gtr', pshift=[0,2,4,5,7,9,11,12])
FoxDot PitchGlitch SampleDB
Bank of samples and loops to use in FoxDot.
Run on your terminal:
git clone https://gitlab.com/iShapeNoise/foxdot_sampledb_pitchglitch /path/to/foxdot_sampledb_pitchglitch
Then add the bank:
Samples.addBank('/path/to/foxdot_sampledb_pitchglitch/1')
Then set the bank dynamically:
d0 >> play('W', bank=1)
d1 >> play('x-o-', bank=P[:2].stutter(16), sample=P[:4].stutter(4))
Metadata
Release files for FoxDotMultiBank 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| foxdotmultibank-0.1.0.tar.gz | 8.5 kB | Without provenance | Details for foxdotmultibank-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| foxdotmultibank-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for foxdotmultibank-0.1.0-py3-none-any.whl |
Total release size: 17.6 kB
Release files / foxdotmultibank-0.1.0.tar.gz
| Download URL | foxdotmultibank-0.1.0.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7054ffde71e5272999a5b56a0e554c2d5f7b5da76f755b078b92eded13e90430
|
|
BLAKE2b-256 checksum How to use checksums |
34a62c2ae91fccc78df63f129a1b8eac63c5f4e03f78b2ca28b71e4c45052eec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.13.7 Linux/6.17.9-arch1-1
|
Release files / foxdotmultibank-0.1.0-py3-none-any.whl
| Download URL | foxdotmultibank-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
43323ee790db181c93d0eadad6d1b3e54f3b2c19666f58e759fe2757bdd215b4
|
|
BLAKE2b-256 checksum How to use checksums |
70feb51e3b990bcb32a6d1a88db845a494e7082d573cf3065e4599a2a24fba42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.13.7 Linux/6.17.9-arch1-1
|
Security for FoxDotMultiBank 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.