Acoustica User Forums

After last update Mixcraft is not playing midi tracks from Heat Up VST.

All the tracks are there, when I open HU it gives the sound, but when I play the project the tracks are quiet.

When I play the clips they're quiet too.

Now I lost over a half of each project.

What to do to get it back??

POST UPDATE

It plays correct the tracks from Heat Up 2 (64bit) and not Heat Up 3 (64bit VST3).

I have them both installed. Just checked and duplicating the track seems to make the new one working!

I almost got the heart attack guys. Anyway, something is wrong after the update.

Also the new save versions of the project are not primarily going to the project parent folder, but everytime I have to go there manually.

That's also after the last update.

I never do the updates in the middle of big job and this time I did because support suggested that in connection with other problem.

Never again Now I've got to go, duplicate each of HU3 tracks and mix them down to wave tracks before new suprise comes...

Damn, not working

Duplicating the track makes it play, but mixdown to new gives empty wave track and duplicated track becomes broken again...

Has anyone got the installer one version before the 460??

And if I uninstall v460 to install the older one, will I lose all the paths to plugins or something else?

I've found the public beta 461 that says to fix not playing VST3 midi files, but when I try to install it with my Pro Sudio code, it says that it's the Record Studio installer. Are you gonna release that update for pro studio soon?

If not, I'd be really thankfull for MX9 64bit Pro Studio build 452 installer

Suggestion: Contact the HeatUp maker and ask them for help, and in the meantime, don’t use HU3 and just use UH2 instead.

jlouvar wrote: ↑Sun Jul 05, 2020 8:43 am Suggestion: Contact the HeatUp maker and ask them for help, and in the meantime, don’t use HU3 and just use UH2 instead.

What's the point contacting HeatUp maker as the fault is on Mixcraft side? Until last update (460) it was working perfect.

Acoustica probably know about it for at least two months now, this is description of public beta 461 released 7th of may: And using Heat Up 2 instead of HU3 is not an option, these are two different VSTs and tracks builded on HU3 need working HU3...

Yeah I read what you wrote.
And now a conspiracy theory lol.

Kuba W wrote: ↑Sun Jul 05, 2020 9:30 am What's the point contacting HeatUp maker as the fault is on Mixcraft side?

Because regardless of what you think, they may be able to help you. Anyway, sorry for the suggestion and good bye.

jlouvar wrote: ↑Sun Jul 05, 2020 9:51 am Because regardless of what you think, they may be able to help you. Anyway, sorry for the suggestion and good bye.

Yeah. You may be right. I'm just devastated by loosing few months of work... Thanks for the suggestion.

I've found installer for MX9 Pro 64 build 458 and it (HeatUp3) was not working too.

I've uninstalled again and came back to my very first version of MX9 - build 436 - and it's working again.

I think the last version I had before this unlucky update was 452, so it would be great to get the
installer for Pro Sudio 64 build 452 or if it's somehow possible - just the patch to version 452.

Hi,

Why just that version of that plugin? If there’s a problem with build 460, we want to fix it. Can you please send a simple example project file into support so we can see what’s going on?

Greg

Another factor that could be an issue is neither the plug-in or MC but W10 updates, they've had some well publicised doosies recently. I've had a couple issues with drivers and such but nothing drastic over the last few months that I'm sure are W10 related. Last thing is that individual computers can be a bit quirkie, I know I've had some odd ones with my 5 year old PC.

Hopefully you'll be able to sort it out, who knows a future W10 update could do it?

M

Acoustica Greg wrote: ↑Sun Jul 05, 2020 11:02 am Why just that version of that plugin?

No idea Greg. Heat Up 2 came as VST2 I think, and later upgrade to Heat Up 3 as the VST3 only. Maybe that's the reason, maybe something else, as they differ more than just version of vst. It's based on different engine and has new layout too. Up to build 452 it was working perfect for a long time. 458 & 460 open them silent.

Acoustica Greg wrote: ↑Sun Jul 05, 2020 11:02 am Can you please send a simple example project file into support so we can see what’s going on?

Yes, I'll prepare some simple project by slimming one of the existing and I'll send it through e-mail.

Rolling Estonian wrote: ↑Sun Jul 05, 2020 11:09 am Another factor that could be an issue is neither the plug-in or MC but W10 updates

I'm using Win7 and update manually, that's not the case. Failure happened since I've updated from 452 to 460 100%

Now I had to go back to build 460, as the 436 sees the newer files as corrupted, luckily I managed to recover all important tracks with 436 by mixing them to waves... So there's still a hope for my productions.

Another suggestion, install that v461 beta just to test that specific plug-in.
It would be helpful info for all interested parties.

There are still vst3 incompatibilities out there, and I have to give the team a lot of credit for their efforts to punch down those little gophers as they pop up. Its not as simple as a sweeping fix for all of them.

Mark Bliss wrote: ↑Sun Jul 05, 2020 11:50 am Another suggestion, install that v461 beta just to test that specific plug-in.
It would be helpful info for all interested parties.

That's right what you say, but the installer didn't let me do it using my password for Pro Studio.
Which is also strange, bacause when reinstalling different builds of PS it didn't even ask me once for a password.
It has to recognise it as a different product and I have no acces to it even if it's the lower version...