Make your own free website on Tripod.com

FxToy v0.2a  *New*


-------------------
FxToy v0.2 (alpha)
-------------------

Thank you for your interest in our efforts.

This is another Emu10k1 Independent Programmers ALPHA release; help us develop it into a BETA version. Comments and feedback are welcome; visit the EIP site for the latest updates and more information.
http://emu10k1.tripod.com

Take a second & email me to let me know what FxToy does (or doesn't do) for you - feedback is crucial to further development.
emu10k2@hotmail.com

Good luck!

/HANz

--------
Contents
--------

1. Description
2. Features
3. Limitations
4. Known Problems
5. System Requirements
6. Contact
7. Acknowledgements
8. Version History
9. Source Code
10.Technical Description
11.Warranty

1. Description
--------------

FxToy v0.2a is an early development tool for exploring the potential of some of the APS FxEngineServer functions.
FxToy is designed for use with the E-mu Audio Production Studio (APS) soundcard.

2. Features & Usage
-------------------

Current features include:

-Access to several DSP Program functions, including Start, Stop, Ramp-up, Ramp-down, Program Patching and Unpatching.

-Error message returned when function call is unsuccessful.

Usage:

-Fx Programs are identified by number, selectable via edit boxes. Set desired ProgramID, then click action button.

-Conventional names for currently known standard ProgramIDs are listed at right of dialog (if you find an error, or discover anything new, please let us know).

-There appear to be 32 programs pre-loaded by the SoundScene Server. Programs 1 to 18 are listed on the dialog. Programs 21 & 22 appear to correspond to analog-outs 1 & 2. Programs 19, 20 and 24-32 are also likely to be physical outputs (no confirmed mapping yet).

-Use Start and Stop to (..you guessed it..) start or stop a given Program. Warning: Stop function seems to sometimes cause sudden jumps in volume - keep your output levels down while experimenting, and avoid using headphones.

-Use Ramp-down and Ramp-up to "mute" or "un-mute" a given program which is still running. Note that these two functions do not seem to work on all programs. Any insights welcome.

-Use the Patch function to patch the output of a given Program into the input of any other Program, on a specified set of channels. Note that there is a danger of creating feedback loops here; avoid patching yourself into a digital feedback loop. :-P

-Carefully planned patching appears to allow effects chaining possibilities not normally available with the Econtrol mixer. For example, it appears to be possible to apply compression to a mix by inserting the compressor into an un-used strip, then patching from the output of another Program to the Compressor Program's input. 

-It is possible, as another example, to patch the Raw Mix (program 1, channels 0 & 1) or the Mixer (wet) output (program 2, channels 0 & 1) directly to a physical output (e.g. programs 21 & 22, channel 0 = analog-out 1 & 2). Play around, experiment, then *let us know what you discover*. I can't stress this enough - if you're interested in seeing further development, then drop us a line; *feedback is crucial!*

3. Limitations 
--------------

Program limitations include:

-Wet/Dry program mix level functions are available, but have not yet been implemented.

-At present there is some error-checking, but not much. Bug reports welcome. :-)

-"Load file" button loads an RIFX DSP file from disk (fuzz.fx), but we haven't yet figured out how to get it to "do" anything; we probably need to figure out how the FxParamManager works first... :-P

4. Known Problems
-----------------

-Manual data entry must be followed by a carriage return (due to missing UpdateData call - oops).

-I am overworked and underpaid. (hehe - no joke ;-). Development tends to be kinda slow, but then, you get what you pay for. :-P

-The GUI and Icon still aren't too pretty.. 

5. System Requirements
----------------------

-E-mu APS drivers and applications must be installed and running correctly (note that there are currently no WinNT or Win2k drivers for the APS).

-This application uses Micro$oft C++ Foundation Classes (MFC). Most users will already have the required DLL files (MFC42.DLL, MSVCP60.DLL, etc.) in their windows\system\ directory.

6. Contact
----------

Send comments & bug reports to: emu10k2@hotmail.com

Visit the Emu10k1 Independent Programmers site for the latest updates and more information:
http://emu10k1.tripod.com

7. Acknowledgements
-------------------

Thanks go out to all those who have dropped by the EIP site or contributed in one way or another to making further EIP development possible.

Thanks to Daniel (I don't do windows) B. & Max (disable that damned record dither) M. for their helpful insights.

Thanks to sonix for keeping the spirit alive. Greetz dude.

Global thanks to all those people all over the world who have made their various projects' code available to the public. Open-source baby! Yeah!

Thanks to the guys & gals over at E-mu for going COM! 

Note that we are in no way affiliated with or endorsed by either E-mu Systems or Creative Labs.

8 Version History
-----------------

-29.11.2000 FxToy v0.2a (alpha) released, complete with C++ source code.
-17.11.2000 FxToy v0.1a (alpha) released, C++ source code available upon request.

9 Source Code
-------------

This is an open-source freeware application. Note however that some of the included source files may be governed by a licensing agreement (GNU or otherwise).

You should have received the C++ source code together with this application. Visit the Emu10k1 Independent Programmers site for the latest sources and more information:
http://emu10k1.tripod.com

Users are encouraged to help in the development of this application with bug reports, feature suggestions, code improvement suggestions and/or coding of additional features, where possible.

If you wish participate and/or contribute, contact us at emu10k2@hotmail.com.

If you do add to or modify the code, please keep us posted so as to avoid any duplication of effort, and to let others benefit from your (hard) work. :-P

10 Technical Description
------------------------

FxToy takes advantage of the APS FxEngineServer COM library functions.

On startup, we get an interface to the COM library and proceed to call functions from it as needed. Refer to the FxServer Interface header files to be found at the EIP site for a complete listing.

The "File Load" button loads a Creative/E-mu RIFX format DSP file (as found in the Fx DLLS) from disk, by calling the FxEngine "Load" function. We are currently attempting to complete our understanding of the RIFX format, at which point we hope to be able to gain proper control over custom-loaded Fx programs and parameters.


11 Warranty (blurb)
-----------

EXCEPT AS OTHERWISE RESTRICTED BY LAW, THIS WORK IS PROVIDED
WITHOUT ANY EXPRESSED OR IMPLIED WARRANTIES OF ANY KIND, INCLUDING
BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF FITNESS FOR A
PARTICULAR PURPOSE, MERCHANTABILITY OR TITLE. EXCEPT AS
OTHERWISE PROVIDED BY LAW, NO AUTHOR, COPYRIGHT HOLDER OR
LICENSOR SHALL BE LIABLE TO YOU FOR DAMAGES OF ANY KIND, EVEN IF 
THEY HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.