KVR Audio

Kypresso · Post by **Kypresso** » Wed Jul 07, 2021 10:23 am

@otristan

Any idea when native M1 support will appear?

otristan · Post by **otristan** » Wed Jul 07, 2021 2:37 pm

Kypresso wrote: Wed Jul 07, 2021 10:23 am @otristan

Any idea when native M1 support will appear?

We already have a working version in house but we wait for PACE to finalise their wrapper on the M1 platform. hopefully 3rd quarter of 2021.

WatchTheGuitar · Post by **WatchTheGuitar** » Wed Jul 07, 2021 5:03 pm

Ah that's interesting, so pretty much anything that can use software iLok would be affected I guess.

pinki · Post by **pinki** » Wed Jul 07, 2021 5:53 pm

pinki wrote: Tue Jul 06, 2021 8:30 pm Take Asteroid for example: (and correct me if I'm wrong!) I want to assign the 7 volume faders to 7 physical faders on my midi controller. Open a patch, assign, all good. Then I load the next sound- all assignments lost. Because I'm actually loading another instrument instance.
So apart from overwriting every single patch in Asteroid, how do I achieve something so simple? It's a real workflow killer.

@otristan
Is there a workaround for this because I notice that Asteroid has the ability to load kits within a single instance? Can I save one and then use that as a basis for cc mapping for all kits and then use that in UVI Workstation.

Kypresso · Post by **Kypresso** » Wed Jul 07, 2021 6:06 pm

otristan wrote: Wed Jul 07, 2021 2:37 pm
Kypresso wrote: Wed Jul 07, 2021 10:23 am @otristan

Any idea when native M1 support will appear?
We already have a working version in house but we wait for PACE to finalise their wrapper on the M1 platform. hopefully 3rd quarter of 2021.

Thanks for the reply.

WatchTheGuitar · Post by **WatchTheGuitar** » Wed Jul 07, 2021 9:59 pm

I get this nagging script dialog in the new library, PX SunBox even though I seem to be on the latest version of Falcon.

uvi script error.png

Doesn't seem to affect anything noticeable yet, but I guess it'll go away after another update or two?

fairlyclose · Post by **fairlyclose** » Wed Jul 07, 2021 10:12 pm

WatchTheGuitar wrote: Wed Jul 07, 2021 9:59 pm I get this nagging script dialog in the new library, PX SunBox even though I seem to be on the latest version of Falcon.
uvi script error.png
Doesn't seem to affect anything noticeable yet, but I guess it'll go away after another update or two?

Does this synth become part of the Vintage Vault bundle for existing users or do they create a new upgrade of Vintage Vault after a year or two to include all the intervening models?

EvilDragon · Post by **EvilDragon** » Wed Jul 07, 2021 10:16 pm

The latter.

fairlyclose · Post by **fairlyclose** » Wed Jul 07, 2021 10:31 pm

EvilDragon wrote: Wed Jul 07, 2021 10:16 pm The latter.

thanks - presumably a reasonable upgrade price. I like these little vintage instruments though not bought one yet. Mainly I like the interfaces, UVI have excellent interface designers for creative usability

WatchTheGuitar · Post by **WatchTheGuitar** » Wed Jul 07, 2021 10:55 pm

I will upgrade Vintage Vault when v4 comes out, but will pick up a few things from UVI over the year if I really like the look of them and it all counts toward the voucher UVI sends you in the new year based on what you spent with them over the previous year.

UVI Doctor · Post by **UVI Doctor** » Wed Jul 07, 2021 11:27 pm

WatchTheGuitar wrote: Wed Jul 07, 2021 9:59 pm I get this nagging script dialog in the new library, PX SunBox even though I seem to be on the latest version of Falcon.
uvi script error.png
Doesn't seem to affect anything noticeable yet, but I guess it'll go away after another update or two?

Sounds like your DAW points to an old version of the Falcon DLL. Please locate the most recent version of the Falcon DLL (v2.1.7) on your system, then move it to your VST folder and rescan it via DAW settings.

Please note that the common default VST locations for UVI products are:
C:\Program Files\VSTPlugins
C:\Program Files\Steinberg\VSTPlugins

If you are unable to locate the Falcon DLL on your system, please open UVI Portal and disable 'Silent Install' in the Preferences, then reinstall Falcon. That way, you can select your custom VST location during the installation process.

Hope this helps!

trusampler · Post by **trusampler** » Thu Jul 08, 2021 12:06 am

You gonna answer that Global midi learn question? That's been a major PITA with Falcon.

WatchTheGuitar · Post by **WatchTheGuitar** » Thu Jul 08, 2021 12:08 am

UVI Doctor wrote: Wed Jul 07, 2021 11:27 pm Please locate the most recent version of the Falcon DLL (v2.1.7) on your system, then move it to your VST folder and rescan it via DAW settings.

Cheers, I think I may have had to do this before as I tend to try and shift anything off my C drive that’s not directly Windows system related.

otristan · Post by **otristan** » Thu Jul 08, 2021 7:18 am

pinki wrote: Wed Jul 07, 2021 5:53 pm @otristan
Is there a workaround for this because I notice that Asteroid has the ability to load kits within a single instance? Can I save one and then use that as a basis for cc mapping for all kits and then use that in UVI Workstation.

What you can do is save a UVIWorkstation multi with Asteroid loaded where you have linked your CC and always load this one and then use Asteroid own browser to load a custom kit.

HTH

pinki · Post by **pinki** » Thu Jul 08, 2021 8:22 am

otristan wrote: Thu Jul 08, 2021 7:18 am
pinki wrote: Wed Jul 07, 2021 5:53 pm @otristan
Is there a workaround for this because I notice that Asteroid has the ability to load kits within a single instance? Can I save one and then use that as a basis for cc mapping for all kits and then use that in UVI Workstation.
What you can do is save a UVIWorkstation multi with Asteroid loaded where you have linked your CC and always load this one and then use Asteroid own browser to load a custom kit.

HTH

Ah OK that will get me there, thanks

UVI Falcon - v4 = 2026 released - rumors, ads, praise, kindergarden, auto-sampling and off-topic inside!