Spectral warping wavetable synth

Related tags

Compilers vital
Overview

Vital

Vital is a spectral warping wavetable synthesizer. This is the source.

Code Licensing

If you are making a proprietary or closed source app and would like to use Vital's source code, contact [email protected] for non GPLv3 licensing options.

Installing

Create an account and download Vital at vital.audio

Issues

Report bugs (e.g.non-code and non-compiling issues) to https://forum.vital.audio

Feel free to report issues on building/compiling here but note that I'm not prioritizing them.

Pull requests

I will not take any pull requests.

What can you do with the source

The source code is licensed under the GPLv3. If you download the source or create builds you must comply with that license.

Things you can't do with this source

  • Do not create an app and distribute it on the iOS app store. The app store is not comptabile with GPLv3 and you'll only get an exception for this if you're paying for a GPLv3 exception for Vital's source (see Code Licensing above).
  • Do not use the name "Vital", "Vital Audio", "Tytel" or "Matt Tytel" for marketing or to name any distribution of binaries built with this source. This source code does not give you rights to infringe on trademarks.
  • Do not connect to any web service at https://vital.audio, https://account.vital.audio or https://store.vital.audio from your own builds. This is against the terms of using those sites.
Issues
  • Allow distribution with Vital name

    Allow distribution with Vital name

    Hi, thanks a lot for making vital opensource!

    I was about to try it out, but readme states:

    Do not use the name "Vital", "Vital Audio", "Tytel" or "Matt Tytel" for marketing or to name any distribution of binaries built with this source

    Would be weird to have vital packaged but having to use an alternative name.

    opened by falkTX 28
  • can*t compile  VST/juce_VST_Wrapper.cpp:87:10: Error

    can*t compile VST/juce_VST_Wrapper.cpp:87:10: Error

     make
    ....
    make -C standalone/builds/linux CONFIG=Release SIMDFLAGS="-msse2" GLFLAGS="" BUILD_DATE="2021 03 27 00 37"
    make[1]: Verzeichnis „/usr/src/fremd/vital/standalone/builds/linux“ wird betreten
    make[1]: Für das Ziel „all“ ist nichts zu tun.
    make[1]: Verzeichnis „/usr/src/fremd/vital/standalone/builds/linux“ wird verlassen
    make -C plugin/builds/linux_vst VST3 CONFIG=Release AR=gcc-ar SIMDFLAGS="-msse2" GLFLAGS="" BUILD_DATE="2021 03 27 00 37"
    make[1]: Verzeichnis „/usr/src/fremd/vital/plugin/builds/linux_vst“ wird betreten
    Compiling include_juce_audio_plugin_client_VST3.cpp
    In Datei, eingebunden von ../../../third_party/JUCE/modules/juce_audio_plugin_client/juce_audio_plugin_client_VST3.cpp:26,
                     von ../../JuceLibraryCode/include_juce_audio_plugin_client_VST3.cpp:9:
    ../../../third_party/JUCE/modules/juce_audio_plugin_client/VST3/juce_VST3_Wrapper.cpp:32:24: Warnung: mehrere Token am Ende der Direktive #include
       32 |  #include <arpa/inet.h>^M
          |                        ^
    In Datei, eingebunden von ../../../third_party/JUCE/modules/juce_audio_plugin_client/juce_audio_plugin_client_VST3.cpp:26,
                     von ../../JuceLibraryCode/include_juce_audio_plugin_client_VST3.cpp:9:
    ../../../third_party/JUCE/modules/juce_audio_plugin_client/VST3/juce_VST3_Wrapper.cpp:33:7: Warnung: mehrere Token am Ende der Direktive #endif [-Wendif-labels]
       33 | #endif^M
          |       ^
    In Datei, eingebunden von ../../../third_party/JUCE/modules/juce_audio_plugin_client/juce_audio_plugin_client_VST3.cpp:26,
                     von ../../JuceLibraryCode/include_juce_audio_plugin_client_VST3.cpp:9:
    ../../../third_party/JUCE/modules/juce_audio_plugin_client/VST3/juce_VST3_Wrapper.cpp:69:11: schwerwiegender Fehler: pluginterfaces/vst2.x/vstfxstore.h: Datei oder Verzeichnis nicht gefunden
       69 |  #include "pluginterfaces/vst2.x/vstfxstore.h"
          |           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Kompilierung beendet.
    make[1]: *** [Makefile:206: build/intermediate/Release/include_juce_audio_plugin_client_VST3_dd633589.o] Fehler 1
    make[1]: Verzeichnis „/usr/src/fremd/vital/plugin/builds/linux_vst“ wird verlassen
    make: *** [Makefile:100: vst3] Fehler 2
    
    
    opened by artbody 8
  • Vitalium for Debian

    Vitalium for Debian

    I posted this Standalone and VST3 build

    I did my best to remove the instances of Vial and Vital and rendered it to Vitalium Turned of the Authorization, no VST2 or LV2

    If anyone wants to look at the vitalium-1.0.6 branch is where the changes I made are.

    I am not a developer. Merely a Linux audio user that knows how to compile software and tweak code a bit (blunt hacking is more like it)

    If there are changes that need to be made to comply with your wishes Matt please let me know and if you want me to take the builds down will do so in a jiffy.

    Thanks

    opened by tank-trax 6
  • Permission to fork and use github actions to build binaries for StudioRack

    Permission to fork and use github actions to build binaries for StudioRack

    Thank-you for the great plugin work.

    I would like to promote it by adding it to my site/app/command line tool: https://studiorack.github.io/studiorack-site

    This would involved forking your plugin and building binaries using GitHub actions. I have an example template here: https://github.com/studiorack/studiorack-plugin-juce

    Source code to the GitHub workflow which builds the JUCE plugin: https://github.com/studiorack/studiorack-plugin-juce/blob/main/.github/workflows/release_projucer.yml

    StudioRack is only for open-source plugins where there are direct links to binaries (no signups). However it looks like you prefer users to signup to download binaries? I don't want to circumvent your marketing activities.

    Let me know your thoughts! Kim

    opened by kmturley 5
  • License for presets

    License for presets

    I have a question regarding the license of presets shipped with Vital. Can those be redistributed? If so, under what terms?

    Currently any vital fork builds do not have any presets. Would be nice to have at least a few of them, best if it would match the official "free" pack.

    opened by falkTX 5
  • juce_VST_Wrapper.cpp: 'pluginterfaces/vst2.x/aeffect.h' file not found

    juce_VST_Wrapper.cpp: 'pluginterfaces/vst2.x/aeffect.h' file not found

    Hi,

    I have been trying to build the XCode project found in the plugin/builds/osx folder but it fails with the error above.

    The vst2.x folder mentioned is in the Steinberg VST SDK which I have pasted into the third_party/VST_SDK/VST3_SDK/pluginterfaces folder of the project but, it is still not compiling.

    Any clues you could share on how to get this done?

    opened by vegapit 2
  • Licensing of presets included with free version

    Licensing of presets included with free version

    Is it permissible to distribute LV2 versions of the Factory Content patches availble with the free version of Vital? Users may wish to run the LV2 plugin headless and hence be unable to access the .vital patches. (This is my use case.) We have vitalium running on Zynthian and it would be cool to be able to distribute the presets too for good out-of-box-experience for users.

    opened by riban-bw 2
  • Please create a versioned source tarball/zip

    Please create a versioned source tarball/zip

    Some Linux distributions require one in their package inclusion guidelines. For example: Solus package request guidelines

    Releasing these will surely be a boon to the widespread adoption of this incredible software. Thanks for reading.

    opened by alphabitserial 2
  • License with additional terms?

    License with additional terms?

    The README currently notes additional restrictions on top of the GPL3 license being used. However, the GPL3 license specifically states:

    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.

    As such, any additional conditions being added are null and void. You should consider if you want to change your license or if you are okay with dropping your additional terms.

    As a side note, because of this clause, distributing on iOS may in fact be possible without violating the license on your software. For further information, I refer you to an article on Stack Exchange discussing the problem.

    opened by rdrpenguin04 2
  • strange build error

    strange build error

    the error is

    make -C standalone/builds/linux CONFIG=Release SIMDFLAGS="-msse2" GLFLAGS="" BUILD_DATE="2022 06 28 10 27"
    make[1]: Entering directory '/home/moth/vital/standalone/builds/linux'
    make[1]: Nothing to be done for 'all'.
    make[1]: Leaving directory '/home/moth/vital/standalone/builds/linux'
    make -C plugin/builds/linux_vst VST CONFIG=Release AR=gcc-ar SIMDFLAGS="-msse2" GLFLAGS="" BUILD_DATE="2022 06 28 10 27"
    make[1]: Entering directory '/home/moth/vital/plugin/builds/linux_vst'
    Compiling include_juce_audio_plugin_client_VST2.cpp
    In file included from ../../../third_party/JUCE/modules/juce_audio_plugin_client/juce_audio_plugin_client_VST2.cpp:26,
                     from ../../JuceLibraryCode/include_juce_audio_plugin_client_VST2.cpp:9:
    ../../../third_party/JUCE/modules/juce_audio_plugin_client/VST/juce_VST_Wrapper.cpp:87:10: fatal error: pluginterfaces/vst2.x/aeffect.h: No such file or directory
       87 | #include "pluginterfaces/vst2.x/aeffect.h"
          |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    compilation terminated.
    make[1]: *** [Makefile:201: build/intermediate/Release/include_juce_audio_plugin_client_VST2_dd551e08.o] Error 1
    make[1]: Leaving directory '/home/moth/vital/plugin/builds/linux_vst'
    make: *** [Makefile:97: vst] Error 2
    
    opened by OHNONOTAMOTH 0
  • Web Audio Module support

    Web Audio Module support

    I would love to see this compiled to WASM for a WAM for use in web-daws. Has this been done yet? If not, is there's any interest in seeing this happen?

    opened by FractalHQ 0
  • Incompatible with newer juce

    Incompatible with newer juce

    Latest juce has quite some opengl fixes. Sadly even after applying the juce patches from vital, the gui does not look right.

    image

    Have you seen this? Will it be fixed in the next code update perhaps? This issue prevents me from updating juce on the distrho-ports project. I did test other GUIs, they work, seems there is something specific on the way VItal deals with OpenGL that no longer works with latest JUCE, even with Vital-specific patches applied :(

    opened by falkTX 0
  • Key-tracking with custom tuning messes up plugin state

    Key-tracking with custom tuning messes up plugin state

    Hi, I like to use custom SCL scala tuning files with vital. If I make a patch that relies on key-tracking, such as key-tracking a filter for white noise to do some physical modelling type thing, it will work beautifully at first. The filter frequency will respect my custom tuning.

    But, if I save the ardour project, close it, and return to it again, it's a different story. The filter will behave entirely unlike it did — often a nasty noisy mess — until I reinitialize the patch. I needn't even reset the tuning or reimport my SCL file or anything, but I do need to reinitialize the patch. Weird, right? I wonder if you can reproduce this.

    If I save the patch as a vital-internal preset, then when I open ardour and vital is misbehaving, I can reload the vital-internal preset and everything will be in order once again. So I believe that there is a discrepancy between the state vital saves internally to its own presets and the state vital gives over to the DAW to save and reload.

    I will try to remember to update this issue with screenshots and audio later, but my house has construction right now and I don't have ready access to that PC.

    opened by maemunman 0
  • Lock when multiple VST instances of Vital are shown in the same process

    Lock when multiple VST instances of Vital are shown in the same process

    Here are the suspicious backtraces:

    this one holds the XScopedLock: a

    this one tries to acquire it: b

    this one seems locked deeper ? the lock occurs on a glDisable call c

    (neither of these three threads seem to make any progress)

    opened by jcelerier 0
  • Vital on Wine 6.14/FL Studio 20 - GUI Flickers like crazy

    Vital on Wine 6.14/FL Studio 20 - GUI Flickers like crazy

    When adding an instance of Vital in FL Studio 20, the GUI flickers when:

    1. Playing a note (midi)
    2. Moving/resizing the window

    I am using Wine 6.14 on Manjaro 21.1.1 KDE.

    opened by lylythechosenone 2
Owner
Matt Tytel
Matt Tytel
Open-source Qt Quick & c++ wavetable synthesizer

?? OOSC! OOSC is a two-oscillator wavetable driving synthesizer written with Qt, QML and C++. Have some included effects like a Reverb, Flanger, EQ et

Roma 3 May 14, 2022
straightforward CLI tool for spectral analysis of sound files

dowser dowser is (presently) a quick and simple low-level utility for performing spectral analysis of sound files. usage dowser

ezra buchla 12 Dec 18, 2021
A Simple Spectral Renderer

Simple Spectral This is a simple multithreaded spectral pathtracer implementing the algorithm (linear combination of bases) described in our EGSR 2019

Ian Mallett 156 May 13, 2022
C library for audio noise reduction and other spectral effects

libspecbleach C library for audio noise reduction and other spectral effects Background This library is based on the algorithms that were used in nois

Luciano Dato 24 Jun 10, 2022
Code for the paper Succinct k-mer Set Representations Using Subset Rank Queries on the Spectral Burrows-Wheeler Transform (SBWT)

SBWT This is the code for the paper Succinct k-mer Set Representations Using Subset Rank Queries on the Spectral Burrows-Wheeler Transform (SBWT). The

Algorithmic Bioinformatics Group @ University of Helsinki 14 Jun 18, 2022
SynthLab is a synth plugin framework for developing software synthesizers.

SynthLab SynthLab is a synth plugin framework for developing software synthesizers.

willpirkleaudio 52 Jun 11, 2022
A library for using real OPL2 synth chips via ALSA's hwdep interface.

oplhw: A library for using real OPL2 synth chips via ALSA's hwdep interface ==========================================================================

David Gow 1 Nov 30, 2021
C/C++ library for converting a stream of OPL FM synth chip commands to the OPB music format

OPBinaryLib C/C++ library for converting a stream of OPL FM synth chip commands to the OPB music format Basic usage Store your OPL commands as a conti

Emma Maassen 10 Feb 2, 2022
Single file synth + demo song

P.S. is a music track written from scratch using the C programming language. All sounds and notes were entered manually without using any music progra

NightRadio 35 May 29, 2022
Helm - a free polyphonic synth with lots of modulation

Helm Helm is a free, cross-platform, polyphonic synthesizer that runs on GNU/Linux, Mac, and Windows as a standalone program and as a LV2/VST/AU/AAX p

Matt Tytel 2.1k Jun 20, 2022