Xref: utzoo rec.music.synth:3923 comp.sys.amiga:20881 Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uwmcsd1!bbn!oberon!pollux.usc.edu!papa From: papa@pollux.usc.edu (Marco Papa) Newsgroups: rec.music.synth,comp.sys.amiga Subject: Re: MIDI Software for the Amiga - a brief review of PRO Midi Soundscape Keywords: SoundScape, MIDI, Amiga Message-ID: <10555@oberon.USC.EDU> Date: 9 Jul 88 07:31:07 GMT References: <786@rover.UUCP> Sender: news@oberon.USC.EDU Reply-To: papa@pollux.usc.edu (Marco Papa) Organization: Felsina Software, Los Angeles, CA Lines: 57 In article <786@rover.UUCP> mph@rover.UUCP (Mark Huth) writes: >I recently purchased the Mimetics PROMIDI SoundScape program for my >Amiga to use with my SQ-80. So far, I have used the tape deck for > ... >The second problem is that there are logical device names hard-coded >into the software. This makes it impossible to move everything but >the key onto a hard disk, as the device name is the same as the disk >name! I have spent many hours trying to move all but the key track >onto my hard disk, and still find that the libraries insist on loading >modules from the floppy. Yuck. It would be real nice if some thought >had gone into properly using the Amiga environment. I do not have SoundScape, but I found this from a flyer a picked up last year at COMDEX Cbooth: CUSTOMIZING Soundscape Start-up You might have noticed that Soundsape 1.4 uses the device Default: when you do Load and Save operations. It will load a nd save from the default : until change it to something else like a disk name. When you make a Soundscape workbench disk a file is ceratedd in the s directory called ss-modules. Soundscape looks in thi file for commands before loading. Two commands are e placed there when the file is created: assign Default: SoundScape: assign Help: Soundscape: Users can edit this file to change the default settings to customize their working environment. For instance, assign Default: Data: or assign Default: df1: [ or , I say, assing Default: dh0:SoundScape] [Similarly the article seems to imply that one could reassing where to look for the "soundscape.library" by doing: copy Soundscape: libs/soundscape.library to dh0:libs assign libs: dh0:libs run Soundscape:Soundscape This is pretty much standard with any program that uses custom lobarries: they must be in libs: Also if you boot from the Soundscape disk, the sSoundscape:libs will be the default libs:, until you do the above assign. The flyer implies that you should be able to put the executable of Sounscape in the c directory of another disk (possible dh0:c) and executit from there] I hope this helps. -- Marco Papa 'Doc' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= uucp:...!pollux!papa BIX:papa ARPAnet:pollux!papa@oberon.usc.edu "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=