Cantabile not releasing resources? (Resolved - Don't use creators update on a Surface Pro 4)

1

Hi Guys,

I am very new to all this ( including playing keyboards ) and just starting to experiment.

The machine I use for running Cantabile 3 is a W10 Surface Pro 4 that I use for a limited selection of other things ( including listening to music ).

However, what I am finding is this;

When I start Cantabile 3 and load in a VST ( something like VB3 ), all plays well until I close down the program and then try to use the machine for something else.
What I then find is that other programs can no longer access the sound device, and should I then re-start Cantabile, the right channel produces a very loud hiss whenever any notes are played.
This is using the devices internal sound card via ASIO rather than driving an external interface device.

Restarting the machine normally has no effect, and up to now, the only way I have been able to reset everything is by doing a hard restart.

Any Ideas?

Thanks, Peter.

2

Could you clarify how you are doing that? Is it via ASIO4ALL? Voicemeeter? VB HiFi Cable?

Sounds like sync is being lost during a transition after shutting down Cantabile and never regains stability.

Terry

3

I tend to suspect this will come down to a audio driver issue. Definitely need to know what you’re using. :wink: By and large, the interanal card is not the way to go, though using ASIO4ALL can do a decent job.

4

I’d be suspicious of the audio driver too. Make sure you’ve got any available updates for it installed.

Also, it’d be interesting to check Cantabile’s log file to make sure the driver is being correctly cleaned up and unloaded when Cantabile is closed. Try this:

  1. Reset your machine to get things back to normal.
  2. Start Cantabile
  3. From the Tools menu, choose Open Settings Folder.
  4. Close Cantabile.

From the folder opened in step 3, take a look at the file log.txt. You should see something like this:

00025216        4   [14132:2]:     asio - Stopping driver...
00025237       21   [14132:2]:     asio - Disposing buffers...
00025242        5   [14132:2]:     asio - Stopped.

and then a little further down this:

00025343        1   [14132:2]:   asio - Releasing asio driver

If these are missing then possibly Cantabile’s fault. If they’re there then almost certainly a driver issue.

Does the same problem happen with WASAPI driver?

Are you using ASIO4ALL or a specific asio driver?

Brad

5

@terrybritton I am using ASIO4ALL.

@FredProgGH I agree 100% with you regarding not the internal card, however I ( did ) find it very useful for quick tests and stuff. Normally I use a Peavey USB-P and a small mixer deck to get the ‘real’ sound out.

@brad All the lines you highlighted are present in the log file, so I guess this point to a driver issue. However the same behaviour is exhibited irrespective of the driver I use.

I am starting to suspect the latest W10 update may have a hand in this somewhere as I don’t remember coming across this with earlier releases.

I would also like to thank everyone for their efforts on this.

Best regards,

Peter.

6

Ah, the Creators update? I don’t remember where but I read on another forum that was causing some problems for people.

7

@Peter_Garlick

I’m running the Creators update here on my dev machine and haven’t had any issues like this with ASIO4ALL. Most likely suspect is the Windows audio drivers I’d say.

Brad

8

This is beginning to look like a Surface Pro 4 problem.

I downloaded the demo versions of Cantabile and VB3 onto my desktop machine which is also running Creators update, and it all works as it should using the windows drivers ( and all others as well ).

I will have to see if I can back-level the machine and keep it well away from any online connection that would allow it to ‘upgrade’

I will keep plugging away at the problem and should I resolve it will post here as it may help others.

Thanks,

Peter.

9

This does indeed seem to be the fault of a combination of Surface 4 and the Creators update.

I have just reverted my device back to the previous version of Windows, and all is now working once again as it should.

It seems people with the same configuration as mine should stay well away from this update until Microsoft address the issue.

Thanks to everyone who attempted to help.

Peter.

1 Like