Let’s hope the presets (general, LFO and wavetables) will be available to everybody at some point (for Mac users, they are apparently missing for most people). That’d at least allow for a little reverse engineering of some patches.
Yes, I just learned that LIFT is release velocity (I think it borrows that name from some other MPE product). I have a release velocity keyboard (Kurzweil PC3K), and LIFT works!!!
1 Like
Just to give everyone in this thread an update, an official Manual is being worked on but takes time! Do expect it somewhere in the upcoming weeks
9 Likes
Great!
Should you ever need help translating it to german (in case that’s part of your evil plans), feel free to shout.
He’s a good guy. I was getting suggestions for his “In the mix” channel before Vital appeared. For one so young, he knows what he’s talking about on the videos I’ve watched. He’s a very good teacher.
Vital is very simple considering how much potential it has, and it’s incredibly well thought out and implemeted. I have Arturia Pigments too, but Vital is so much easier.
A manual would be good for beginners, but the tutorial video up there is great and covers everything really well.
1 Like
Well, I think there’s plenty of things that could be covered better in a manual, which you could always reference to. Also, I think quite some things are a little above beginner level, such as the various shaping options for the wavetables.
And then there’s also the little things no tutorials can cover in their entirety. Such as possible key combinations and shortcuts. For example, is there any tricks to quickly draw in rhythmically repeating patterns in the LFOs and envelopes? Can you select various nodes in them at once and move them all together? Etc.
Really, there’s quite some things that would do better in a manual rather than in some video - because I like looking at manual sections repeatedly, but I hate having to scroll through videos all the time just to find a 30 second thing that I don’t remember.
While we wait on a full product manual…
6 Likes
Agreed… I tried loading some of the factory presets in today, to see if I could “dissect” how they work… And man, those patches are doing some wild, convoluted things that are definitely not “intuitive” to figger out…
I’m discovering more of the functinality by way of trial and error, however a well written manual would be a good addition because there are functionality features that are as yet undoumented, which means for the time being I am cataloguing the discoveries as i learn. so maybe a “missing manual” might emerge over time, who knows.
I don’t know how to start a WIKI, but I think it is a great idea. I know we can help each other out. I am a beginning beginner, so at the moment I don’t have much to offer. I am using Vital with an analog breath controller; someday I will be able to add to conversations/articles about that - give me a couple hundred hours of Vital time!
I have the beginnings of an unofficial guide in the works. Any suggestions for a collaborative platform would be great as I am literally learning this synth by the seat of the pants.if interested I am happy te post the ( very short) draft and people are welcome to make edits and add content. @Tytel, I am not trying to compete with you on this one😀
1 Like
So February 2021 now - still no manual.
@waveshaper any progress on yours ? I would put it into google docs - then people who want to contribute can do easily.
Christoph
i like the idea. would put some work in that if im not the only one writing there.
@SerErris can you edit it like a “pro” manual/wiki in google docs? (and can you turn it into pdf, so you can use it offline, too?)
would prefer a free/ open source site, but i have no knowledge on that so google will do.
if you link it here i put something in. maybe add a picture with numbers on all the knobs and stuff, so you can use the numbers in the description.
Google Docs is like a word document, where multiple people can edit at the same time. However it is not a wiki, but more like a document with classic structure.
Advantages:
- It can be very easily exported to any other format (e.g. PDF, WORD, plain text and a lot of others)
- It is free of cost
- It can be copied easily to someone else
- WebBrowser is the only thing you need.
- No Website Hosting required.
- Absolutely the simplest Version to setup.
- Usermanagement very easy.
Cons:
- Not a WIKI, potentially more difficult to maintain (e.g. links). Crosslinking is possible to sections and paragraphs, but is more difficult than a simple WIKI.
- Not a website, you need to have the link to access it. however you also need the website link to access it. Still a website is easier to find with google search.
- You need a google account to work on it (edit).
I looked up in the internet if there are any free opensource sides available to have that hosted. But there is actually not a free Wiki useable for dokumentation. I can host a Dokuwiki on my webserver not a problem.
DokuWiki should be good enough for us to enable proper user dokumentation.
Let me know what you think.
Those are for if you have a special keyboard.
google documents
pro: convert to pdf/text (so you can edit /use it offline)
easy setup/managment.
easy export would probably good if we have to move it later for some reason.
con: need google account (but you could update it if someone works on it with pdf an put it here for example?)
dokuwiki
pro: better acessability, less google
con: don´t know if offline use/edit and/or converting to pdf is possible.
you need to do all the setup, and if your server goes down the project is gone?
that would be the most important points for decision, i think.
offline work/use would be important for me.
I tend to start with google docs.
- it is already there, we can immediately start.
- it is a document. It is meant to get PDFfed and read online.
- creating a structured document out of a Wiki is a nightmare. That needs additional programming.
So I start a google document, and later on that could still get transported into a wiki if required.
1 Like
i´ll start as soon as the link is up.
Thank you for the initiative.
While the writing starts on a Google Doc… is there an interest in investigating a git based approach for the long run? Using e.g. GitLab or GitHub has the advantage of better revision control and permissions. The use of git-based tools to write manuals and documentation is increasing.
People (including total strangers) could contribute improvements (from a typo to a chapter) without having to learn about git itself, just editing text online. The project could include the possibility to submit issues or request to expand chapters or cover new areas.
GitHuB/lab sounds better to me than google.
can you set it up on github/lab?
is easy export to text/pdf possible?
is 500 mb from free version enough for everything?
1 Like