Mixcraft 9 build 449 - Total failure to render Program changes

[Ian Craig]

Using the concert feature of Analog Lab 4 I set up a line of presets that could be cycled through via Mixcraft program changes. The left hand side of the audio is mostly the playback of the VST and on the right is mostly what it sounds like when rendered, both via 'mix to stem files' and 'mixdown to wav'. The Preset changes are not being rendered using either method of rendering.
(Windows 10, Mixcraft 9, 64 bit, build 449)
https://youtu.be/gFA8Bpl2FZ8

[Acoustica Greg]

Hi,

Try mixing down to a wav file with the same sample rate you're using in Mixcraft's sound device preferences. For example, if you're using a sample rate of 48000 Hz, try mixing down to a wav file with a sample rate of 48000 Hz. Click "Edit Details" when you go to mix down to change the sample rate.


Greg

[Ian Craig]

Hello Greg,

I always do. I only use 44khz unless a device or driver demands otherwise and that's how everything was set, I just checked. I had to use Videomeld to capture the sound (which is a ridiculous thing to have to do).

[Acoustica Greg]

Hi,

Program changes seem to come across just fine if I mix down using Acoustica Instruments. So, the problem isn't with rendering program changes in general.

When I try using program changes on Analog Lab 4, I'm not noticing any effect from them. How do you get program changes to change presets?

Does the same thing happen in Mixcraft 8?

Greg

[Ian Craig]

No it doesn't render to the mixed files in Mixcraft 8 either
...
Note the bit that mentions 'concerts'

2020-01-24 20_18_37-.jpg (362.12 KiB) Viewed 4325 times

Go to the upper left menu, click on Analog Lab, go down to 'tutorials', select 'Concert tutorial'. It shows in 17 steps how it works (except that Program changes do not render to saved files in Mixcraft 8 or 9)

2020-01-24 20_19_35-.jpg (265.57 KiB) Viewed 4325 times

[Ian Craig]

Has this bug been reported or do I have to remember how to do it ?

[Acoustica Greg]

Hi,

The first question the dev's will ask is whether it happens in build 450.

Greg

[Ian Craig]

Yes it happens in build 450, it was the first thing I checked.
The only way round it without a fix is to 'record all FX and instrument automation'. Unfortunately that records approximately 628 lines of automation, which take forever to disarm as for some reason the automation lanes do not appear to support clicking the top one (impossible) and scrolling down to the bottom one and 'shift' clicking to apply the same disarming to all at once.
(opening up the 'go on stage' section on Analog Lab 4 & pressing playback enables visual monitoring of the presets changing)
...
Even that didn't render the changes to the resultant wav file, so there is no way of getting it to work without a fix to the rendering to wav or stem files