Ask Your Question
1

Problems initialising MIDI in Windows 10

asked 2016-08-22 14:55:18 -0500

heavy-lifting gravatar image

updated 2016-08-22 14:58:06 -0500

Hi all

wondering if I could get some advice... I'm using tidal via Atom in Windows 10 (64 bit) and I'm struggling with MIDI. I can get it to work about 25% of the time.... even if I run the exact same code I would say 3/4 times the code just seems to stop running before getting to the 'initialised device' message. If I try to run any other code I get an angry red error and have to reboot Tidal.

Any ideas?

Screenshots of the errors...

image description

image description

edit retag flag offensive close merge delete

Comments

I have the same error, also win 10. Haven't seen Tidal get past it yet.

Bespectacled gravatar imageBespectacled ( 2016-08-27 18:07:24 -0500 )edit

Hi @Bespectacled - are you using SuperDirt (via SuperCollider) or classic Dirt (via Cygwin). I'm using the latter as my computer is a bit slow running Atom and SC together. Trying to work out if that is part of the problem...

heavy-lifting gravatar imageheavy-lifting ( 2016-08-30 08:56:43 -0500 )edit

yep, regular dirt via cygwin.

Bespectacled gravatar imageBespectacled ( 2016-08-30 17:33:49 -0500 )edit

@Bespectacled cool, thank you. I don't think it should make any difference but worth knowing! I will keep you posted if I get anywhere.

heavy-lifting gravatar imageheavy-lifting ( 2016-08-31 07:36:34 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-08-25 04:49:52 -0500

heavy-lifting gravatar image

OK just to follow up with my troubleshooting for this problem....

I uninstalled and reinstalled everything (including updating my version of Haskell) which has caused a different kind of error WSANOTINITIALISED - documented here: http://ask.tidalcycles.org/question/3...

I did some reading around this and used a tool called CCleaner to clear up my registry. I'm not necessarily advocating this particular tool (probably riddled with viruses haha!). But it was free and did the job. I think you can do this manually too.

OK! So this fixed the WSANOTINITIALISED error, but I was still getting a segmentation fault error. Groan. So I uninstalled everything again, including deleting all tidal files off my computer (other than my code) and reinstalled.

TIDAL MIDI WORKED PERFECTLY FIRST TIME, hooray.....

Except not hooray because after a fun practice and me feeling very smug that I'd fixed my issues I thought to myself, hmmm, maybe I'll just reboot and see where I get to...

An lo and behold I'm back with WSANOTINITIALISED.

Anyway it was bedtime so I didn't get any further. I will keep experimenting but if anyone has any bright ideas they would be gratefully received :)

My next steps are: Run CCleaner again and see if that gets me anywhere Check out tidal midi on my boyfriend's computer (I installed tidal on there for the workshop last week but haven't tried midi) - we are both windows 10 64 bit so I can see if the problem is general or specific to me. ????? beyond that I'm pretty out of ideas so will keep reading and see if I get anywhere.

edit flag offensive delete link more

Comments

1

I had the exact same problem, but resolved it. The solution was to uninstall the 64-bit Haskell Platform and install the 32-bit version. Now it works perfectly without the WSANOTINITIALIZED error.

kindohm gravatar imagekindohm ( 2016-09-10 14:46:31 -0500 )edit

Question Tools

Stats

Asked: 2016-08-22 14:55:18 -0500

Seen: 896 times

Last updated: Aug 25 '16