Andy Campbell - Posted - 08/02/2015:  03:45:57

Hi there

I upgraded to windows 10 yesterday and now have a problem with playback of the midi. I get no sound when I first open Tabledit.

When I open a tef it has the speaker icon crossed out. If I go in and pretend to make changes I can get it to remove the check from the speaker and play sound. However, if I close Tabledit and come back in again, the sound is off again.

I tried running the program as an administrator, but it didn't help.

Has anyone come across this and a solution?

Many thanks

Texasbanjo - Posted - 08/02/2015:  05:05:09

I don't have a solution, but that's one reason why I don't download Windows 10 -- not until they get all the bugs fixed.   There are always problems with a new system and that's probably one of them. 

kmwaters - Posted - 08/02/2015:  08:33:53

matt0308@tabledit.com if you want to email and see what they say but I suspect there are compatibility issues as Sherry mentioned.

Matthieu is quite responsive to email.

Andy Campbell - Posted - 08/02/2015:  11:33:48

Thanks Ken.

I wrote to Matthieu before I posted as I realised it was a problem with TablEdit.

I have no other sound issues. Thanks again.

Kstevensmd - Posted - 08/03/2015:  15:44:07

Hi, I have found the same problem and just posted a topic; I didn't see this thread first!  So, if I find out anything I'll let you know.  I did send an email to Keith at TablEdit.  I'm sure there will be a fix arriving soon!  Thanks!

RedStar - Posted - 08/03/2015:  16:25:13

Upgrades... Not always so. Especially in windows case... GL

BanjerKen - Posted - 08/03/2015:  17:08:30

I had the same problem but it's an easy fix. Click on the play tab at the top left of the page. On the drop down menu select Midi Setup and then click OK.  The X on your little speaker symbol should be gone and your audio restored. Worked on both my laptop and desktop

Foote - Posted - 08/03/2015:  21:01:42

I love Banjo Hangout!  I had the same problem as above, remembered seeing the post, and learned the easy fix from Ken.  Thanks, Ken.

BanjerKen - Posted - 08/03/2015:  21:07:39

I'm sad to report that my fix has to be done every time you open a tab so it's just a work around allowing us to use it until there is a permanent solution. Sorry!!! I thought I had it figured out.

Andy Campbell - Posted - 08/04/2015:  00:39:53

Sorry about that Foote

I wouldn't' have posted the problem if my fix had worked. (See OP)

I have logged this with Microsoft and the yahoo group for TablEdit.

I also sent an email to Mathieu on Sunday, but as yet no reply. It is the holiday season after all.

Just for completeness, I have found no issue at all with all other software and hardware I use.

Paulf - Posted - 08/04/2015:  00:54:45

I fixed mine with a little bit of learning.  1st, I removed Tabledit and then I went into the settings and changed my music and video defaults from Groove to Windows Media Player and then followed the instructions in this link; ​

  thomas.vanhoutte.be/miniblog/d...-10-apps/

This is the line that need to be copied to Powershell  from that list      ​Get - AppxPackage *zune*  Remove - AppxPackage

Once this is done then reload Tabledit again and it should work.

Andy Campbell - Posted - 08/04/2015:  05:39:30

Thanks Paul

I resolved it by downloading Coolsoft's VirtualMIDISynth  coolsoft.altervista.org/en/vir...midisynth

and then some soundfonts to with it. It's fun playing around with different fonts.

Jack Baker - Posted - 08/04/2015:  09:27:09

Hi Sherry,

I think people play with their toys too much and this is what happens ...Jack

Andy Campbell - Posted - 08/04/2015:  09:34:09

Yes, but it's fun Jack. ...Andy

SteveMcBill - Posted - 08/04/2015:  15:51:33

The issue is a known MIDI problem with the MIDI implementation in Windows-10 - it was reported to Microsoft back in December 2014  and on a number of occasions since but has not (yet) been resolved.  Here is hoping that they fix it soon though I did read somewhere that Microsoft would like to see MIDI phased out.

However, installing Coolsoft Virtual Midi Synth and a Sound Font (Timbres of Heaven is a good one) will allow the playback to sound without problems and will not witch off between loading of TablEdit.  Both the software and the sound-font are FREE.

This MIDI problem in Windows-10 is NOT confined to TablEdit (and TefView) but also manifests in other programs using MIDI output (e.g. Notation Composer).  The folks at Notation Composer are now busy writing routines to allow use of a sound-font of their own development in their program which they expect will be ready in October 2015.  I also hear that Microsoft expect their first 'big' update to Windows-10 to be ready sometime in October.

Hope the above helps people.

 Steve

Kstevensmd - Posted - 08/05/2015:  05:49:03

Hopefully TablEdit can figure this out and get a fix sent to all users or they will be out of business! 

SteveMcBill - Posted - 08/05/2015:  08:11:53

As far as I understand it there is nothing that TablEdit or any of the other music programs which use MIDI for playback can do about it - it is a Microsoft Windows issue.

However, TablEdit and TefView already allow use of Soundfonts so it is an easy fix from the point of view of these programs.  Just download Coolsoft Virtual MIDI Synth and a Soundfont (e.g. Timbres of Heaven) and install and you can have better sounds than pure MIDI sounds plus it will work on Widows-10 without any problems at all !!

Steve

By the way Windows-10 has a "GOD-mode" where you can gain access to 260 new settings which normal Windows-10 does not provide.  Here is how to get it:  winsupersite.com/windows-10/en...indows-10

Edited by - SteveMcBill on 08/05/2015 08:14:05

TablEdit - Posted - 08/24/2015:  16:30:12

The sound works fine in Windows 10. The problem is that the midioutopen command (the one that starts the MIDI driver) works only once. I've updated the current version to allow the user to set the sound driver easily. That's all I can do.
It is an obvious bug from Microsoft. It would be good that users show their dissatisfaction with this regression. If there is a workaround, I would implement it immediately. But I've not found any explanation from MS about this curious situation and how to fix it.
To permanently resolve the problem, you can install VirtualMIDISynth as Steve said. In addition you will a much better sound than the one offered by the standard Windows sound bank.