Notifications
Clear all
Questions about UNIFY
19
Posts
9
Users
2
Likes
251
Views
Topic starter
May 13, 2023 1:44 pm
Hi,
since I have migrated in 10, have a lot of prob with VST3 plugins ,
after migrating in v10
Valhalla supermassive VST3, do not work , (so signal in the Fx section)
everything was ok in 9.X. have a lot of patches impacted
tested with another configuration and have exactly same issues.
any Idea ?
THX
May 13, 2023 2:34 pm
SIGH... This is why we beta-test. Unfortunately, our beta-test period was severely limited for v1.10, and it looks like this was missed.
Please stand by for Unify 1.10.1, once I find the problem...
May 13, 2023 5:36 pm
On my Mac, Supermassive version 2.5.0 works perfectly fine... can you please update to the newest version and see if that helps it work for you?
Maybe it's just a PC thing, but it's working fine here.
Life is Sound / Sound is Divine
www.pluginguru.com
Topic starter
May 13, 2023 6:14 pm
Hi,
I just installed supermassive V2.5 and it doesn't change anything. When I create a new patch it works (both VST2 & VST3) , but when I use patches from 1.9 (VST3) it doesn't work. I have the same issue with other VST3s like Ozone which also don't work. This issue is not related to Valhalla. I have attached a patch template (which works with Zebra) that I use to design my libraries and reproduces the problem I encounter with V1.10.
THX.
May 14, 2023 12:37 pm
Hi, I tested some of my old patches created with v.1.9.1 containing Retrologue and Reason Rack VST3 - I have no issues when opening them with Unify 1.10.0.
May 14, 2023 12:45 pm
Hi, I tested some of my old patches created with v.1.9.1 containing Retrologue and Reason Rack VST3 - I have no issues when opening them with Unify 1.10.0.
This is wonderful news, but please specify which operating system (and DAW, if applicable) you're working with, so I can develop an idea of what is working and what is not.
I just posted a new beta which our testers will be looking at. So far in my testing, it seems to solve the VST3 issue, but time will tell.
May 14, 2023 1:22 pm
This is wonderful news, but please specify which operating system (and DAW, if applicable) you're working with, so I can develop an idea of what is working and what is not.
I just posted a new beta which our testers will be looking at. So far in my testing, it seems to solve the VST3 issue, but time will tell.
Widows 10 Pro 21H2, Unify Standalone and Unify VST2/VST3 in Studio One 6.1.1
May 15, 2023 12:34 am
So pleased the *.vstpreset finally works, without the inevitable crash, I was experiencing. 70% of my saved presets are in this format, and many converted from FXB/FXP, years ago, the rest have their own preset mangement. so I have fully tested the worst offenders (bx...) and then more in Instrument=/, Aux=/, Master=/ 🙂
getdunne reacted
May 15, 2023 7:47 am
on my side I tested patches that contain Titrik irid VST3 ,Valhallasupermassive and Valhallashimmer in VST2 and everything works (win 10 Reaper).
I took the opportunity to try other effects (Triad, Blackhole, Ultrachannel, Focusrite, Rapid Parawave, SSLchannel Wave and many others) everything works
Dominique
WIND 10 Reaper 6 Kronos / Osmose / Omnisphere 2.8 / Keyscape / Nylon sky / Undercurrent /Stylus / UVI Ravenscroft & Orchestral suite, Spitfire Originals collections & Labs , BBCSO core ,Abey road 2, Frozen strings , Albion Tundra , Solo strings, Chamber strings evolution, British drama tool kit, Fragile strings evolution , Aperture , Appassionata ,Mercury Solar, Orchestral tool Habitat & Salu, Arturia Pigments , Rapid Parawave , Plasmonic, Surge , Descent Sampler, Flow motion, Pianoteq pro, Memorymode, Sine ,Bx_Oberhausen, FM8, Eight voices, Dreamsynth, Lion, Triad, Royal Albert hall Organ, Kniffonium, Vital, Minimonsta 1&2 , Imposcar ,Surge
May 16, 2023 12:48 am
Windows 11 - Unify 1.10 - No Valhalla VST3's are passing audio for me. Via Aux or "In-Line"...Standalone & Reaper
This post was modified 4 months ago by Waveform
May 16, 2023 1:01 pm
Windows 11 - Unify 1.10 - No Valhalla VST3's are passing audio for me. Via Aux or "In-Line"...Standalone & Reaper
A fix for this is on the way!
May 22, 2023 9:50 am
Hi - I reported last week that Steinberg Retrologue VST3 was broken in 1.10 update; I now understand this was part of a wider VST3 issue with the update. Unfortunately I have installed 1.10.1 update, and this has not fixed the issue - both Retrologue and Pad Shop fail to load still.
May 22, 2023 10:30 am
Hi, @robertpeveler I know that this doesn't help you but I write it as input to Shane. I have no problems with either Retrologue or Padshop.
Win 10 PRO, Unify 1.10.1 standalone/Unify plugin in Cubase PRO 12.
Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc
May 22, 2023 10:36 am
Should perhaps add that this is Unify in standalone mode, in Win 10 on i7 PC with 32GB RAM.
May 22, 2023 11:38 am
Retrologue and Padshop VST3s are both working for me in Windows 11.
All I can suggest is that you ensure you have the very latest versions of these plug-ins, then go to the Known Plug-Ins List in Unify, delete the entries for both, then drag the VST3's in manually to re-scan them. I don't yet know why, but I have seen cases where this solves plug-in loading issues.
May 22, 2023 11:53 am
Thanks will give that a go. Have also now also found my first failing VST3 audio effect - Sixth sample Deelay doesn’t load, though interestingly their Cramit works fine - I think the latter was more recently updated.
