home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.audio
- Path: sparky!uunet!usc!wupost!spool.mu.edu!torn!nott!cunews!ags
- From: ags@scs.carleton.ca (Alexander G. M. Smith)
- Subject: Re: Digitizing from scripts..
- Message-ID: <1992Dec24.212628.21173@cunews.carleton.ca>
- Sender: news@cunews.carleton.ca (News Administrator)
- Organization: School of Computer Science, Carleton University, Ottawa, Canada
- References: <168C6C9FB.WALLY@UKCC.UKY.EDU> <1992Dec24.005304.6603@cunews.carleton.ca> <168C78B8.WALLY@UKCC.UKY.EDU>
- Date: Thu, 24 Dec 1992 21:26:28 GMT
- Lines: 27
-
- In article <168C78B8.WALLY@UKCC.UKY.EDU> WALLY@UKCC.UKY.EDU writes:
- >I can't think of a way to currently use break to stop AGMSRS because
- >unless the system is the same way each time, the process number will
- >be different. And I can't think of a way to use the 2.0 Status to
- >be able to "tell" break what number. (IE: Status->variable, then
- >break $variable)
-
- Bing! Isn't there some way of getting the process number inside a script?
- Some sort of magic word like "$$"? In AmigaDOS 2.0 there is an
- environment variable called "process" that contains the current CLI
- number. So, you could do something like:
-
- echo >t:temp.bat "wait 20*nbreak $process"
- run execute t:temp.bat
- agmsrecordsound blah hz 6000
-
- That script fragment makes a temporary batch file that will do a 20
- second time delay and then send a break to the main process. The main
- process meanwhile is recording sound, until the tempoary batch file
- sends it a break. Note the hz 6000 line used for AGMSRecordSound. If
- you use too high a recording rate, the Amiga's processing speed is
- slowed down and the temporary batch file might be delayed much longer
- than the requested amount of time.
-
- - Alex
-