library icon indicating copy to clipboard operation
library copied to clipboard

Database for the VCV Library

Results 46 library issues
Sort by recently updated
recently updated
newest added

Source: https://github.com/aetrion-music/aetrion-modular Version 2.0.0 Commit: f31aa021ed71663b0b130af30761851f0e30e4c1

Hello, I'd like to submit my plugin to Vcv library url: https://github.com/sickozell/SickoCV commit: 839a970e97490a6b7790123d296d0fcf4ffc3a7e

plugin

Plugin Submission: https://github.com/bVidDa/Orbital-Rack [v1.2.1] https://github.com/bVidDa/Orbital-V2 [v2.1.2] https://github.com/bVidDa/Orbital-Rack/commit/c79c097b0fbe3a2c6244ce5eae762c19e6c8a143 https://github.com/bVidDa/Orbital-V2/commit/610aadaf17fc732db611c6caf420711a4c17dfdd Brand: bVidDa Author: Metaly Name: Orbital Modules: . Extasis . Jigsaw

Migration of `ArableInstruments` to version 1.0.0 of Rack. Source: https://github.com/adbrant/ArableInstruments.git Branch: master SHA: 03a07ee2efc1e03e6ebfd63447e8deed0adcf360 Version: 1.0.0

plugin

Migration of `ParableInstruments` to version 1.0.0 of Rack. Source: https://github.com/adbrant/ArableInstruments.git Branch: parable SHA: a41c6d32d9f74257c7de11dc4aebbc20dea16ef4 Version: 1.0.0

plugin

Rack v2 is roughly a year away, but the plan is to be mostly API-compatible with v1 plugins, or at least 90% of them. However, the version strings of plugins...

discussion

@AndrewBelt I created a project board for library maintenance (right now for v0.6, later for v1.0): https://github.com/VCVRack/library/projects/2 If an existing issue assigned to this project gets reopened, it gets automatically...

discussion

The Review team is responsible for updating and adding plugin source code to `repos/`, making sure the source code is not malicious. ## Workflow Begin by checking this repo's issues...

community

Participating in the Library team is the simplest of the four. Requires knowledge of submitting PRs and editing JSON in the `manifests/` directory. ## Tasks - Keep plugin manifests correct...

community

Time to start discussing the migration to Rack v1 and the changes required in this repo! 1. When the v1 API is stabilized, we should make a new branch `v1`...

discussion