#SoundScape – DMCS
3 messages in this thread
Rick,
I finally got a chance to try sending DMCS tracks to SounsScape without
turning on the DMCS "Send Midi Clock" option. It worked fine and I got all
the tempo changes. I don't have any explanation for why I couldn't get it to
work before.
The only hitch was that when I closed down SoundScape (by QUITing DMCS) I got
the usual visit from our old friend the guru. I say usual, because I'm used
to getting a guru while using DMCS with SoundScape. (Actually, I think that
it's probably caused by DMCS and not SoundScape.) Sometimes, when I think of
it, I use the patch_1 utility that's available in one of the DL's (DL9, I
think) first. That usually postpones the visit for awhile.
Thanks again for the tip.
David
How are you starting DMCS? It seems to be VERY finicky in this configuration.
I've found it to be most stable by opening a new cli, CDing to the directory
which contains the DMCS stuff, then typing DELUXEMUSIC. Trying to RUN it
almost guarantees me a crash on exit. (This should auto-load your Pro MIDI
for you.)
Rick
Rick,
I'm starting by clicking on the DMCS icon, DMCS in df1: and Workbench (as
built by Soundscape's install program) as boot disk in df0:
Configuration: A500, 1meg, 2 floppy's – FYI
As I said, if I remember to run patch_1 beforehand, it seems to last a lot
longer. In any configuration, DMCS seems to cause a guru if anything out of
the ordinary happens. (as I remember) In the session in question, a Do You
Want to Save requester was thrown up automatically when I exited. I think
that might be what caused the problem. If I hit a CANCEL gadget on a file
requester, I'm guaranteed a guru at shutdown, although the program runs fine.
Running patch_1 seems to fix that problem, which, judging from the
description of patch_1, is probably realted to the Alert function.
It's also possible that DMCS doesn't like things to change after it starts
up. (i.e. memory allocations) When I multi-task with DMCS is when I get the
most problems.
David