Massive X is Out!

storyteller

Senior Member
Patch browser improvements and tagging them is another v1.0 thing that's still not there. Maybe also MPE. And personally, I really miss constant rate glide mode (currently glide only works in constant time mode).
Very true. Those should be on my list as well. I guess the lack of visual feedback was the most jarring to me. Glad to see the improvements coming along though! It feels like a new instrument with this last update.
 

EvilDragon

KSP Wizard
Actually personally I think they went a little overboard with visual feedback on envelopes. When you hover quickly above different envelope knobs, the diagram goes wild, swapping between all blue and some blue, some gray is quite jarring...

jarring.gif
 

storyteller

Senior Member
I agree - it is a bit much. It would probably have been better if they left everything blue, but on the highlighted portion, tint the line portion purple or something like that. It is the flickering that is poorly thought out. The intention behind it is good though! :thumbsup:
 

KarlHeinz

Senior Member
Really like the new and especially the more "real" sounding presets, I would have had hard time to go there all by myself, now I have something to start with. And even if preset browser might not been finished it helps that the new ones have their own category.
 

GuitarG

Giscard Rasquin
Does somebody else have problems with no sound from Massive X?
When I start it and select a preset, it´s fine, but when I switch to another VST and come back to Massive, there´s no sound. I have to change presets to get my sound back.
 

storyteller

Senior Member
Does somebody else have problems with no sound from Massive X?
When I start it and select a preset, it´s fine, but when I switch to another VST and come back to Massive, there´s no sound. I have to change presets to get my sound back.
I had this in Reaper using a track template and/or a saved project with massive X already preloaded on a track. I had to remove the plugin, put it back, then resave the project. It has worked since then. Not sure if it is the same problem you’ve been experiencing though.
 

GuitarG

Giscard Rasquin
I had this in Reaper using a track template and/or a saved project with massive X already preloaded on a track. I had to remove the plugin, put it back, then resave the project. It has worked since then. Not sure if it is the same problem you’ve been experiencing though.
Ah thanks. Yes, working with template so that´ll be it!
 

storyteller

Senior Member
Well.... Massive-X doesn't seem to recall the saved patches and play them back in new projects (in Reaper).... I have to manually reload the patches inside Massive-X each time Ugh. After working on several sessions and then going back to reload them... not fun. Love Massive-X otherwise... but still.
 

storyteller

Senior Member
Hmmm, that doesn't happen over here.
I wonder if it is patch specific... or possibly due to track structure or something. I can send ya a project file to see if it opens on your system? It hasn't been consistent. Other projects open saved massive-x presets just fine. But it has appeared on the Now Dystopia patch in the pads section on the last two projects.
 

storyteller

Senior Member
Additionally, the preset name shows something different when I open the project. The up/down arrows don't take you to the next preset and then back to your previous preset. I have tried replacing the plugin, re-saving, etc.
 

GuitarG

Giscard Rasquin
Still happens to me as well. Reloaded Massive X in my template after the update but keeps happening.

Edit: it actually also happens when I change to another track and back to Massive X again. Lot of times there’s no sound
 

EvilDragon

KSP Wizard
I tried loading 4-5 random patches and saving them to separate projects, they all loaded fine, then I did my own patch from blank template and it also loaded fine.

I did notice if I left the track armed and tried playing some notes immediately after project loaded, I just got a sine wave output, but it was only 2-3 seconds then the patch loaded. Apparently some time is necessary to update the synth engine?