Some (Messiah 2 related?) crashes and other little issues

[Kuba W]

Hi!

In the last hour I've experienced more Mixcraft crashes than in all friendship since v7
All of them happened during deleting of muted tracks recorded with Messiah 2 64.
I wasn't using M1 to much, but about 2 weeks ago I've started heavily testing the Messiah 2 as I fell in love with the sound of it.
I've made some new beats and now started cleaning them of unwanted midi-tracks.
Then Mixcraft randomly crashes on some deletes, resulting in fast clipping in speakers.
Once it is possible to close Mixcraft window, once not. Despite it, clipping doesn't stop, and it is not possible to end up the related processes in task manager. The only way is to restart the pc. That's with M2 64 / MC9 PS 64 v436 / Win7Pro
I've just noticed the new build, so I'm gonna try it too...

Another M2 issue is that it only plays right until recording. After record (and sometimes during) it starts sounding flat, completely 'plain', and I have to reload the preset for my midi record to start playing fat sound again. And that cancels all my adjustments, so now I have to do it after record and reload.

Next thing concerns Nectar 2. Three or four times, when stopped the playback and came back to Mixcraft after few minutes, I've found the message window saying that problem with N2 occured and it'll turn off. The other instances and the rest of the project were working fine, and the crashed one also fine after project restart. However, the project was very simple, just the beat and four vocal tracks with N2 applied separately.
Before, that never happened with massive projects in Mixcraft 8, and I was using N2 and N2 vst3 alternately to see if any can cause the problems.

Is any of the above possibly fixed in the new build?

[Acoustica Greg]

Is any of the above possibly fixed in the new build?

Hi,

Yes, the update (build 442) has lots of bug fixes. Give it a try, and if a problem occurs, quit Mixcraft and send us your log file.

To find the mixcraft-log file, highlight the following line and press Ctrl+C to copy it:

Code: Select all

%appdata%\Acoustica\Mixcraft\

Press the Windows Key+R to pop up the Run box in Windows. Click in the Run box and press Ctrl+V to paste in the line from above. Finally, click OK to go to the location of the mixcraft-log.txt file. Submit an Acoustica Support Request and attach the log file along with a brief description of the problem.

Greg

[Kuba W]

Ok, so I decided to update to new build.

I've checked the other new topic about updating, and wondered how's mine gonna go, but didn't expect this:

Update442.jpg (33.92 KiB) Viewed 3824 times

I have opened the project in Mixcraft 9 PS 64 v436 -> Check for updates
Build 442 was found, I've pressed 'next' or whatever to proceed and here's what came up:

The header says: 'Your version is the newest!',
and below: 'Please shut down Mixcraft 8 (!) to install this update'...

I still have v7 & 8 installed, but there was no problems ever before.
And now I'm confused what to do. Got some projects to finish, and I'd prefer to work with buggy build 436 or even v8, rather then mess up all Mixcraft enviroment.

What do you guys think about it?

[Mark Bliss]

Easiest solution:

Find your registration email from your MX9 purchase.
Use the link in the email to download the installer, which will be the current release version.
Run the installer.

[jlouvar]

Open a new project in Mixcraft 9, click on check for updates then immediately close Mixcraft, wait for update to finish installing then open new Mixcraft 9 project and it should be build 442.

Edit: I think Mark and I replied at the same time, but he types faster than me.

[Kuba W]

Greg, Mark, jlouvar - thanks for your replies.

I went the jlouvar's way and it's ok, i've got working build 442.

The Messiah 2 / tracks deleting problem seems to be gone: I've quickly cleaned 4 projects and no crash happened.
Yesterday it was not possible to finish even one.

About the Nectar 2 - don't know yet, as I can't cause the shutdown. It just happened when it happened.
But hopefully this one is gone too.

And, as we're here, let me ask one more thing:
The bottom bar in v9 shows 32 Bits (v8 displayed 24 Bits), even tho my Yamaha Audiogram 6 is only 16 Bits operating.
At first, I thought it just shows Mixcraft's possibility of working at this depth, but the rest of the info (sample rate, mono/stereo, latency) response correctly to my audio settings (for the bit depth there is no choosing option in my interface).

So: why is it this way, and does it have any impact on my work?

[Acoustica Greg]

Hi,

Are you using ASIO? It shows what the sound device reports, and most ASIO drivers seem to report 32-bit. It doesn't affect your work.

Greg

[Kuba W]

Hi!

Yes, I'm using ASIO. If that makes no problem, it's fine. Just wondered.

And about Messiah 2: the second described problem still exists, so I took a closer look on what's happening.

When I press the record button, sometimes the first note key (but only while recording), and sometimes right after I stop rec, M2 is changing settings in its LFO section. That's what flattens the sound, although it's still the same preset/instrument.

Any idea why is it happening? Would you point some software bug or rather something depending on me, like settings etc?

[Acoustica Greg]

Hi,

Does it do this even in a new, blank project?


Greg

[Kuba W]

Hi!

Yes, it does. Yesterday before posting I was playing in blank project just to see what's changing.

Looks like nothing outside LFO section is changing, or my eyes didn't catch that.

And inside LFO for shure everytime Rate knob turns itself and sync switches the values.

When I reload after recording, preset comes back to the correct settings and stay ok unless I record on the same track again.

[Acoustica Greg]

Hi,

Click on the Mix menu, select MIDI Control Surface... then click Reset All and see if that helps.

Greg

[Kuba W]

Will that cancel all my midi keyboard associations?
It would be a shame, as the problem occurs only with that one VST...

[Acoustica Greg]

Hi,

Yes, that would erase your MIDI mappings.

When I right-click on the LFO knob in Messiah Version 2, it is mapped to CC 118. Is that what you have? Do you have any devices that might be sending CC 118?

Greg

[Kuba W]

Yes, it shows CC: 118.

The only midi device I'm using is M-Audio Axiom2 25 if that's what you meant.

And I think I have only assigned the Mixcraft buttons, no VSTs, unless I don't remember that...

How can I check if CC: 118 is assigned to anything else?

[Acoustica Greg]

Hi,

The problem only happens when you start recording? How are you initiating recording? What else happens when you start recording?

Greg