reFX NEXUS5 is out now!

[N 4 LIFE]

Bought it, it sounds good. But I've been installing the packs that come with it in the reFX Cloud app and a lot of the presets from those packs give an error saying "A file is missing.....". Is this happening to anyone else? Lots of missing files from the free packs so far, I haven't gotten to the factory pack so I'm hoping it's not the same with that. I tried "verifying" the installed packs from the app but that didn't do anything to fix the issue. Is anyone else seeing missing files for some presets and does anyone know a way to resolve that? Thanks.

Edit: This reFX Nexus Cloud downloader "app" is garbage, sorry have to say it. It keeps failing on the install along with other issues trying to download the packs. Is there any way to install the content directly from the reFX site? Looks like I'm going to have to open a ticket unfortunately because I can't get any of the packs to work right now.

that's a bummer, no issues here at all. works great.

[Hanz Meyzer]

Are there specific FX you would want as individual plugins? Or all the FX in a multifx/rack style plugin?

I think both would be great, but a multifx/rack style thing might be the most handy, maybe you even could load in Nexus synth presets? All the plugins, all are said to be very good. For breaking out the synth, it would be helpful. Always wondered why this is not a standard. I only know Zebra2 also providing an fx version of it. Ah, and phaseplant.

[Syngularity]

Just discovered the Christmas Expansion 2024. Thank you

[C-quence]

Are there specific FX you would want as individual plugins? Or all the FX in a multifx/rack style plugin?

All the FX in a multifx plugin would be amazing!

[wintoid]

Can someone confirm for me how automation works with Nexus? It looks to me like layer parameters (for example filter cutoff) cannot be automated from the DAW, and I'd have to map them to (for example) Macros or Modwheel etc in order to automate them. Does that sound right, or am I missing some setting somewhere? Seems a bit restrictive/fiddly if so.

[wintoid]

Ah, answering my own question, looks like you have to use these "host automation parameter" things to do it, and the mod matrix. That's fine, I guess, but a bit fiddly.

[FigBug]

Can someone confirm for me how automation works with Nexus? It looks to me like layer parameters (for example filter cutoff) cannot be automated from the DAW, and I'd have to map them to (for example) Macros or Modwheel etc in order to automate them. Does that sound right, or am I missing some setting somewhere? Seems a bit restrictive/fiddly if so.

That's basically how it works. There are also automation parameters that are explicitly for this purpose, so you don't need to use up a macro. Yes, it's an extra step when setting up automation, but exposing 21,834 parameters to the DAW has significant performance implications, as well, it would restrict the ability to add new features, as most DAWs don't like it when you add new parameters or move them around.

[wintoid]

Thanks FigBug, that's a LOT of parameters

[Touch The Universe]

How many parameters are open to the DAW?

[revvy]

Upgraded and treated myself to a discounted pack. The N5 content downloaded automatically with the synth update. Personally, never had issues with the cloud app.

Very impressive new version and at the (discounted?) current upgrade price, was a no-brainer for me.

[Vlades41]

Dear FigBug please zoom in,the macro buttons are very small,inconvenient.There are 24 inches on the screen, it's hard to see them.

[inaheartbeat]

Can someone confirm for me how automation works with Nexus? It looks to me like layer parameters (for example filter cutoff) cannot be automated from the DAW, and I'd have to map them to (for example) Macros or Modwheel etc in order to automate them. Does that sound right, or am I missing some setting somewhere? Seems a bit restrictive/fiddly if so.

That's basically how it works. There are also automation parameters that are explicitly for this purpose, so you don't need to use up a macro. Yes, it's an extra step when setting up automation, but exposing 21,834 parameters to the DAW has significant performance implications, as well, it would restrict the ability to add new features, as most DAWs don't like it when you add new parameters or move them around.

Perhaps you could adopt the model used by Omnisphere for making parameters visible to host automation. They make them visible by right clicking on them and then selecting the option to make the parameter visible for host automation. This way, they don't by default have parameters visible to avoid the same problem you have which is thousands of potential parameters visible by default that must be selected.

[Turpo]

@msvs hi Manuel, I noticed a couple of Vintage Synths 3 presets in the Christmas expansion, are you planning on releasing the Vintage Synths 3 expansion during the discount period? Just to know when to time my purchases.

[msvs]

depends when its finished

[Turpo]

Roger. As I recall from past years, the discounts last until early January, so I'll be patient.