Overnight my Sibelius/LoopBe30/MIR set up which had been working good for months has stopped working and I don't know why.
Does anyone know of any other solution other than LoopBe to get Sibelius and MIR communicating. I'm on W7 prof
193,971 users have contributed to 42,905 threads and 257,889 posts.
In the past 24 hours, we have 5 new thread(s), 16 new post(s) and 82 new user(s).
Overnight my Sibelius/LoopBe30/MIR set up which had been working good for months has stopped working and I don't know why.
Does anyone know of any other solution other than LoopBe to get Sibelius and MIR communicating. I'm on W7 prof
Supposing that all of these components reside on the same machine, you could still di it the old-school way and use an ordinary MIDI-cable routed from the MIDI OUT to the MIDI IN of the same hardware interface. ... which of course means that you will have to have one, in the first place. 8-)
That's an interesting idea Dietz. this is my card I think I could only do one cable which is ok for smaller projects but I need up to four at the moment and when I've got 24GBs of RAM i'll need more ports.
And I'd reallt like to know why a perfectly stable set up has just stopped working - but I'll probably never work that out.
Oh, I see. One port is not especially luxurious. 8-)
Re: "a perfectly stable set up has just stopped working" - is this machine connected to the Internet? Did Windows (or any other application) undergo an update recently? You could always try to use Window's built-in "System Recovery" feature*), to get the whole machine back to a status where it was still working properly.
*) Sorry - I can't look up the actual English name for this feature at the moment - the Windows installation I'm working on right now talks German with me.
HTH,
Resolved the problem this morning - turns out, for no reason - or at least reasons i do not understand - Sibelius decided to change it's preferences to allow LoopBe as an input device[:@]
So I can play with my toys again now.
Thanks for the ideas though.