Loaded Instruments with zero volume

[amanitamix]

I have been frustrated by a few instruments that default at zero volume when loaded onto a track. The fix is to delete the volume automation track associated with the instrument but this extra step interferes with my workflow. Are there any workarounds to this?

[crimsonwarlock]

I'm not aware of any Reason instrument that instantiate a volume automation track when loaded. Can you give am example?

[Rising Night Wave]

perhaps if you replace it with drag and drop function

[huggermugger]

I haven't experienced this once in 23 years of using Reason.

[Billy+]

I've not seen any device do this,

but I have seen midi files include volume automation lanes

[amanitamix]

Here's a vid demonstrating what I am experiencing with a few instruments.

[huggermugger]

Here's a vid demonstrating what I am experiencing with a few instruments.

In the video, you're dragging and dropping an instance of Europa on top of an instance of a VST (funky gtr copy). You're not adding a new instrument, you're replacing one that's already there with a different instrument. Any automation that's already in the track for the original instrument remains in the track when you replace the instrument with another one. It looks like the automation that's already in the track happens to map to Master Volume on Europa. I see that the Engine 1 Level also gets automation.

[pushedbutton]

I get this sort of thing when importing midi files, a lot of the time there is some automation data that seems not to be correctly importing and it sets device levels to zero. Quite often any drum tracks will have solo tracks on a kong that need removing, Europa's first sound generator often gets automated down to zero, sometimes thor is panned all the way to the right. I've just got used to checking for it but yeah, this happens a lot when you're working with imported midi files.