Reason updated and won't load previous VST

[Scoobyman II]

I wrote a song using MASSIVE X in it. Then recently updated and now REASON won't recognise the VST even though when I make a new song MASSIVE X will load. The problem is I don't remember what MASSIVE X patch I used in the song. I hope this makes sense.

[jam-s]

Could it be you used the VST2 version of Massive X in the first song and now only the VST3 version is installed?

[huggermugger]

I hope you solve your problem.

I often name tracks after the patch for this very reason. It has saved my a** more than once.

[DaveyG]

I also wondered whether it's a VST2/VST3 problem.

[Scoobyman II]

I also wondered whether it's a VST2/VST3 problem.

I'll check that. It's highly possible.

[Scoobyman II]

Thank you for all the replies.

[NoiseCrime]

I hope you solve your problem.

I often name tracks after the patch for this very reason. It has saved my a** more than once.

I'd love to see Reason add the capability to append meta data to a track, so we can avoid polluting the track name with other data. Add in some additional QoL features to add/update the metadata with the name of the device, perhaps version info etc, as well as custom user comments.

[buddard]

I wrote a song using MASSIVE X in it. Then recently updated and now REASON won't recognise the VST even though when I make a new song MASSIVE X will load. The problem is I don't remember what MASSIVE X patch I used in the song. I hope this makes sense.

I didn't see you mention anywhere which OS you're running, but if you are on a Mac with an Apple Silicon processor there could be a compatibility issue if your plugin doesn't support Apple Silicon natively.

[tiker01]

I wrote a song using MASSIVE X in it. Then recently updated and now REASON won't recognise the VST even though when I make a new song MASSIVE X will load. The problem is I don't remember what MASSIVE X patch I used in the song. I hope this makes sense.

I didn't see you mention anywhere which OS you're running, but if you are on a Mac with an Apple Silicon processor there could be a compatibility issue if your plugin doesn't support Apple Silicon natively.

If all.this than you need to turn on Rosetta mode for Reason.

[tiker01]

I wrote a song using MASSIVE X in it. Then recently updated and now REASON won't recognise the VST even though when I make a new song MASSIVE X will load. The problem is I don't remember what MASSIVE X patch I used in the song. I hope this makes sense.

I didn't see you mention anywhere which OS you're running, but if you are on a Mac with an Apple Silicon processor there could be a compatibility issue if your plugin doesn't support Apple Silicon natively.

If all.this than you need to turn on Rosetta mode for Reason.

[Scoobyman II]

I didn't see you mention anywhere which OS you're running, but if you are on a Mac with an Apple Silicon processor there could be a compatibility issue if your plugin doesn't support Apple Silicon natively.

If all.this than you need to turn on Rosetta mode for Reason.

I'm running the latest Sonoma OS on an M1 chip mac with Reason 12.

[hamsterfactor]

See the part about "Does your app need Rosetta?".
https://support.apple.com/HT211861

If all.this than you need to turn on Rosetta mode for Reason.

I'm running the latest Sonoma OS on an M1 chip mac with Reason 12.

[SynthGang]

I hope you solve your problem.

I often name tracks after the patch for this very reason. It has saved my a** more than once.

I'd love to see Reason add the capability to append meta data to a track, so we can avoid polluting the track name with other data. Add in some additional QoL features to add/update the metadata with the name of the device, perhaps version info etc, as well as custom user comments.

I'd love to be able to add comments in the sequencer window! I know there are rack extensions that allow you to do this but this is just not ideal and only serves as unnecessary clutter in the rack (though that frankly doesn't stop me from using them). This would easily allow you to append the kind of information you mention in addition to whatever else a user might find helpful (patch names, etc.)

Something similar (or even identical) to what you find in Pro Tools would be nice for this imo. I've longed to be able to add comments to comps especially if I'm working with multiple vocal takes for an artist.

[stillifegaijin]

I'd love to see Reason add the capability to append meta data to a track, so we can avoid polluting the track name with other data. Add in some additional QoL features to add/update the metadata with the name of the device, perhaps version info etc, as well as custom user comments.

I'd love to be able to add comments in the sequencer window! I know there are rack extensions that allow you to do this but this is just not ideal and only serves as unnecessary clutter in the rack (though that frankly doesn't stop me from using them). This would easily allow you to append the kind of information you mention in addition to whatever else a user might find helpful (patch names, etc.)

Something similar (or even identical) to what you find in Pro Tools would be nice for this imo. I've longed to be able to add comments to comps especially if I'm working with multiple vocal takes for an artist.

You could add labels to clips to accomplish this.

[SynthGang]

I'd love to be able to add comments in the sequencer window! I know there are rack extensions that allow you to do this but this is just not ideal and only serves as unnecessary clutter in the rack (though that frankly doesn't stop me from using them). This would easily allow you to append the kind of information you mention in addition to whatever else a user might find helpful (patch names, etc.)

Something similar (or even identical) to what you find in Pro Tools would be nice for this imo. I've longed to be able to add comments to comps especially if I'm working with multiple vocal takes for an artist.

You could add labels to clips to accomplish this.

I definitely do label my clips but I'd love to be able to have the option of adding comments at the track level since it just provides me with more flexibility in terms of what kind of info to put in there.. not to mention it can help with project collaboration if you're passing things on to somebody else who also uses Reason.