When using cortex, if you disconnect the output from media player, you must restart the media server to make it function again

[SeanCollins]

If you disconnect the output from media player to the mixer, you must restart the media server and media server add-on to get mediaplayer to work. I am unsure of wether this is a bug in the mediakit or media player, but it also effects other applications like soundplay. I would assume it could be a bug in both the media kit and mediaplyer however. the transport function also seems to cuase problems as well.

hrev44678 gcc2h

[3dEyes]

Restart media services is not required. Enough to make a Stop-Start Transport after reconnecting player to mixer.

[SeanCollins]

I have to restart the media server when attempting to do anything with cortext that disconnects/reconnects. could this be a driver issue ? I connect/disconnect between the application and the mixer.Disconnecting the mixer from the driver, cuases the same problems however.

[Pete]

I was just about to report much the same bug myself, when I found this recent ticket.

I don't have to restart Media Services to recover -- just close and reopen to source app (MediaPlayer, SoundPlay, whatever) -- but the failure is otherwise the same.

If, in Cortex, I try to disconnect the auto link from source to mixer, and then reconnect it -- to the mixer or anywhere else -- the reconnection is completely dead. I've found no way to revive it; I just have to close the app and start over. Which -- as it automatically re-links to the mixer -- is not much use if I want to drive anything else!

I've tried opening the Cortex Transport window and using the buttons there, but that doesn't work for me. In fact it seems rather confused! Even if the source is playing (through a working link) it's the 'Start' button that's enabled, not 'Stop'. Clicking Start enables Stop, and vice-versa, but otherwise seems to have no effect. Except quite probably locking up Cortex... (:-/)

This is not a new problem BTW. I've tried a few times in the past to, say, connect the synth to SoundRecorder, and failed. [Apologies for not reporting it, but it was tangential at the time.] However it seems to me a fairly major bug, as it negates the whole BeOS MediaKit conception of being able to connect media processors in arbitrary chains! For instance, on BeOS it's trivial to use Cortex to redirect SoundPlay's output to the SoundRecorder. (And also I notice on BeOS that the source keeps playing even when its output is disconnected. In Haiku, cutting the link stops the source.)

As Cortex is the only way I know of to do this sort of thing, I can't tell if the problem is there or more basic to the MediaKit, but the symptoms look more like the latter.

[leavengood]

Yes, this is likely a core Media Kit problem, and is probably related to #12776 and #12777.