[sc-users] Re: MIDIClockOut not working

[ddw_music <jamshark70@xxxxxx>]

Ofelia Negrete wrote
> I'm trying to send Midi Clock messages to an external DAW, Im on windows
> and don't know anything about IAC Drivers/buses but I found that LoopBe
> works as a virtual midi port. Maybe in this I am wrong about this from the
> beggining, but I
> tried the next code
> 
> m = MIDIClockOut("LoopBe Internal MIDI", "LoopBe Internal MIDI");
> 
> m.play
> 
> After evaluating the second line the post window displays
> Interpreter has crashed or stopped forcefully. [Exit code: -1073741819]
> 
> What is going on?

I'm afraid you may be out of luck. I've found that MIDI between applications
is extremely unstable in Windows, and I don't believe it's SC's fault.

When I tried it a couple of years ago, SC and Cubase were both freezing when
I ran SC MIDIOut --> LoopBe --> Cubase. I tried to work around it by SC
sending OSC --> Max MIDI --> LoopBe --> Cubase and Cubase *still* froze...
meaning that even commercial software developers can't get inter-app MIDI to
work in Windows.

That's bad news, but I don't think there's anything SC developers can do
about it.

What you want should be pretty easy in Linux and MacOS though.

hjh



--
View this message in context: http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/MIDIClockOut-not-working-tp7629775p7629787.html
Sent from the SuperCollider Users New (Use this!!!!) mailing list archive at Nabble.com.

_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/