Thank for users who try to help. But it doesn’t work (e.g. what your explained in your post). Was I not clear enough? Do I have to explain the situation once again? Not only that I can’t use some paid presets (and all the future presets). I have the pro version (paid) with this commercial commitment of support, But no way to get support, and no answer from Vital.
All these posts are just to make Mister Tytel react, not to disturb the “community”. As you know, I’m not the only one concerned, Maybe the only that doesn’t accept it. So I would be happy to get a way (an email adress ?) to contact directy mister Tytel. His behaviour is not acceptable. He sold me his stuff, with support. What should I do ? Complain on Youtube, KVR Audio, Gearspace, Musicradar, Audiofanzine (french), etc. : “Vital : the dark side” ? It’s not (yet) my choice, but the silence of Vital Audio and the lie about support is a shame. On the Vital website, there is no link to this (virtual) “prioritized support”, except to this forum. That’s why I complained here.
Mister Tytel, I don’t expect refund because I use Vital on several projects. The problem must be fixed.
You said patience. My custommer and user patience has also its limits!!! This message is not for “the community”. It is so obvious (no to you?) but for the developer, editor, seller of Vital.
Written wihout online translation (sorry for mistakes).
Ok, this makes sense, I understand better now what you were trying to do. It’s less about the bug and more about the support, is what I got from what you said. I can see your frustration and the needed translations could have made that seem more like entitlement; its a tough line to walk and a translator doesn’t help. You could always try contacting Tytel via Discord or directly on Twitter, i’m not currently aware of a suppory email.
Usually bugs like this tend to get resolved in a matter of days or even hours so that could also contribute to why you havent seen direct support. I think that it would definitly be a good idea for Tytel to describe exactly what “prioritized support” means and how to access it. Good luck with however you proceed.
Did you try just mailing support@vital.audio ? I found it in 5 seconds from my “verify-your-mailadress” e-mail. Also I get that you’re frustrated (I felt the same frustration with Steve Duda from Xfer), but we’re here to try and help you as well. But it feels insulting that you don’t report back what you DID try instead and thereby help us, help you.
Sorry, I don’t understand what is insulting and what should I report. I said that I tested every tip given on this forum, and none worked.
No, I did not find the support adress (I’m not smart enought!), and I thank you for your information. Normaly, this information should be obvious, so the client does not have to look after it.
I’ll mail to support@vital.audio (if it works), but I’m sure M Tytel is informed. Something is not very fair in it’s behaviour. Should I accept it? Should any client accept it? NO!
What is important is that those who have bought the paid version may be concerned by the attitude of Mister Tytel, who seems to behave as if he was only offering a free product: no invoice for custommers, no support (the famous “prioritized support” seems to be a fiction, therefore a false advertisement, because this support cannot be limited to the users’ forum), refusal to deal with a problem which concerns only his one and only product…
Yes, this is a real problem.
As SlavaCat wrote : “It is strange that @Tytel hasn’t commented in this tread as prioritized support is part of the package.”
I use Reaper with an intel i5 Graphics 4600.
On Linux under WINE. And it should be impossible because of OpenGL requirements, but I hacked my system into thinking it had the proper version of OpenGl. That thread’s on this forum.
I had lots of problems getting it to work, on Linux! (!!!) , but I managed.
It seemed to matter most to me whether I was running as a separate, native or default process in Reaper.
I’m afraid I don’t agree with this statement. As I have said before other vst’s (e.g. Scaler) do appear to be affected. One of the common factors appears to be that the users have configuration that include OpenGL on Windows 10/11 and possibly older graphics cards.
The issue does appear to be intermittent in that it affects a small number of configurations, but not all, thus making it harder to identify the problem and solve.
For example I have a configuration that includes an NVIDIA GeForce GTX 1660 Ti graphics card on a Windows 10 HOME OS, and have no issues.
EDIT: I must emphasise that I and most users also have no issues running Scaler 2 on Windows. This issue does seem to be confined to a few users with OpenGL.
I have the same problem with crashing and only 1.08 works.
Running 64bit windows 7 and 10 with Nvidia Geforce GTX 560 TI. T some point i will upgrade my system and buying a sh graphics card so i hope i don’t have the same problem again. Triad all fixes mentioned but to no avail.
Apparently, a day or so ago, I read on KVR that Steinberg’s contracted online site went offline and they may not have been honouring software purchases through it and, to boot, passed the buck to the contractor. Perhaps it will be resolved, eventually.
I don’t think I need to say much about the issues behind Massive X or its rollout?
One has to wonder if some threatened corporates send some shills to FLOSS places to harass its community and/or devs and/or deliberately cause problems to make the software look bad.
It’s possible.
And it does make me wonder, now that I think about it, what happened to Ronan Fed.
Anyway, since Vital is ostensibly FLOSS, and since it has a fork, failing an immediate red-carpet for Les Rois (translate: The Kings) from the dev(s) or community, one can always…
– Ask around-- politely/helpfully/humbly-- at Vitalium (Vital’s fork) about the issue (assuming it’s real and has to do with Vital).
– Find a coder/troubleshooter to find the apparent bug and maybe fix it if it is not the problem with some proprietary black-box product that Vital runs on/under. Last I looked, they have sites where one can contract a coder.
– Reinstall Vital.
– Rollback Vital to an earlier version.
– Do a proper maintenance, survey and research of your own system and look/ask around the sites of those responsible for those software.
– Understand and accept (‘Suck it up, buttercup.’) that reality doesn’t always operate the way you would like it to. Have fallbacks/alternatives in place for when that happens. Roll with the punches.
– And things like the above-- you know, remove your little boy/girl diapers and put on your big boy/girl shorts?
– Even consider taking the issue up with an AI like ChatGPT. I hear it’s pretty good with code and since Vital is open source, you never know. A longshot for now perhaps, but that could soon change.
…
– Pay through the nose for alternative proprietary software you can do less about and hope that you get a better deal and that it doesn’t go belly-up, taking its code and everything else along with it. And/Or make a tantrum if you don’t get your way, and maybe threaten to return to FLOSS/Vital.
Bonne chance ma cherie.
Addendum:
I have Vital’s most recent running, sans problem, on both my MacBook Air M1 and Yoga 7i Windows 11.
