Easy Morph
    • Tutorials
    • Install
WinImages
    • Features
    • Animation
    • Adobe Offer
    • JASC Offer
    • Corel Offer
Opal
    • Effects
    • FAQ
Reflex
    • Download
    • Manual
HDocGen
    • Language

Black Belt Systems graphics products are widely compatible with all 32-bit Microsoft operating systems

Home Page

 


WinImages F.A.Q.
Frequently Asked Questions

Located at:
http://www.blackbeltsystems.com/bx_wi_fa2.html

Interactive Technical Support

What if your question isn't answered here?

Then just tell us what it is, and we promise to answer it as best we can. If it seems like a candidate for the FAQ, we'll add it immediately.

FAQ's Available

About the FAQ's

These FAQ's represent the most common or critical questions we receive about WinImages, from all sources: E mail, over the telephone, by fax, mail, etc. Over time, we extend the FAQ as we feel appropriate.

If there is an issue you feel should be dealt with here, please feel free to contact us detailing the question, and any information about the answer you feel we should be certain to include.

Thank you for using our FAQ!


Questions asked of our Sales Staff


Q: What is FX?
A: FX is a stand-alone application that provides the special effects component of the WinImages suite. FX is only available as part of WinImages.

FX does not use, or require, that you have any other software. It is not a plug-in.

FX allows you to apply effects such as lightning, fire, water effects and more in both still and animated forms.

More information on FX is available from the WinImages pages.

Q: What is Morph?
A: Morph is a stand-alone application that provides the image morphing and wapring component of the WinImages suite. Morph is only available as part of WinImages.

Morph does not use, or require, that you have any other software. It is not a plug-in.

More information on Morph is available from the WinImages pages.

Q: What is WinImages?
A: WinImages is a program suite that contains FX and Morph applications. More information on WinImages is available from our WinImages pages.

Q: What is Easy Morph?
A: Easy Morph is a very high quality morphing and warping application that has a simplified set of controls; it is specifically designed to be easy to use.

Easy Morph is not a plug-in, it is a stand-alone application. Easy Morph does not require any other application to work.

More information on Easy Morph is available from our Easy Morph pages.

Q: What are the System Requirements to Run Easy Morph?
A:
  • Windows 95, 98, Me, 2000, NT, or XP Operating System
  • Pentium or compatible processor, or better (Pentium II, II, IV etc.)
  • 16 Megabytes of RAM memory or more
  • 10 megabytes of free Hard Drive space
  • Internet Explorer or compatible Web Browser (to view documentation)

Q: What are the Requirements to Install Easy Morph?
A:
  • Internet Explorer or compatible Web Browser (to download archive)
  • WinZip 7 or later to extract the installation archive (free download here)
  • Pentium or compatible processor, or better (Pentium II, II, IV etc.)
  • Windows 95, 98, Me, 2000, NT, or XP Operating System to run the installer
  • 16 Megabytes of RAM memory or more
  • 10 megabytes of free Hard Drive space

Q: What are the System Requirements to Run WinImages?
A:To see a detailed list, Click Here

Q: Where can I learn cool tricks with WinImages?
A:They have their own page: Click Here

Q: How can I get a Demo Version of WinImages?
A: Want to try the software? Just Ask us

Also, the entire manual is online and you can read it starting at any of these pages:

Table of Contents
Index
Welcome

The manual contains at least one example image of every effect, lots of tutorials, many animations and much more. It's completely indexed, has a huge table of contents and is fully paginated. It's not PDF, it's HTML, so it is as small and fast as possible. You can page through it just like it was a book - give it a look!

Q: Do you make (whatever) product for the Mac?
A: No. However, you can run our products on your Intel-architecture Mac right now using Bootcamp or Parallels virtualized Windows 98 or Windows XP. Under Parallels, our software will act just like it does on a PC. We do not access system hardware directly in any of our software, and we use the system calls in as "vanilla" a manner as possible; we also generally stay away from the more exotic system functions, preferring to write our own code for that kind of thing. One interesting side-effect of this approach is that the same version of our software will run correctly under all versions of Windows 95, 98, Me, NT, 2000 and XP - as you can see, this means that we really do "toe the line" in using Windows OS system resources.

Q: Are there any tutorials or in-depth review pages online elsewhere?
A:Yes, there is an extensive review of R4 (which was three major releases back, but still makes very interesting reading):

Just Click Here

Q: What platforms is WinImages available for?
A: WinImages is available for the following Windows configurations:
  • Windows 95
  • Windows 98
  • Windows Me
  • Windows 2000
  • Windows XP
  • Windows NT 4.00 and later / Intel

Q:] How do Easy Morph and the Morph component of WinImages compare?
A:
Easy Morph is designed to do "classic" morphing and warping. The Morph application, part of our flagship WinImages suite, is able to do this, and adds motion morphing and layered morphing. Morph also adds a number of extra tools such as an additional working interface (Onionskin), and more comprehensive area selection tools. WinImages also provides a much wider range of file format compatibility, output options, special effects, image editing and more.

Motion morphing is morphing streams of images of subjects as they move from image frame to frame; think of it as taking two separate animations, and morphing each frame of one animation against the corresponding frame in the other animation. The end result is that one subject can change into another while walking down a street and talking, for instance. This has also been called "dynamic morphing", "stream morphing", and "sequence morphing."

Layered morphing allows you to morph areas in a single image separately from other areas - there is no interaction between layers at all. In Easy Morph, which does not have layer capabilities, when one area is morphed, it will affect regions close to it - all areas are connected. With Morph, you can morph regions in the same image independantly from one another.

 

Feature Comparison

  Easy
Morph
WinImages
Morph R7
Morphing Setup Wizard Yes No
Image Warping Yes Yes
Flat Morphing Yes Yes
Layered Morphing No Yes
Motion (dynamic, stream) Morphing No Yes
Start/End Swapping No Yes
Dual-Window Interface Yes Yes
Onion-Skin Interface No Yes
Polygon Area Controls Yes Yes
Elliptical Area Controls Yes Yes
Freehand Area Controls No Yes
Rectangular Area Controls No Yes
Spline Area Controls No Yes
Bezier Area Controls No Yes
Point Area Controls No Yes
Custom Area Controls No Yes
Area Re-editing Yes Yes
Area Transparency No Yes
Image Magnify Yes Yes
Resolution Independent Yes Yes
Alpha Channel Handling Yes Yes
Downloadable Yes Yes
Backup CD supplied No Yes
Image File Variants loads 41, saves 21 loads 340, saves 25
Add'l file formats via plug-ins No Yes
AVI Output Support Uncompressed 8- and 24-bit Any type of AVI, 8- or 24-bit, compressed or uncompressed, through any 32-bit CODEC

Click Here to Order

Q: Will installing WinImages impact my other software, like PhotoShop or PSP?
A: No. Absolutely not. WinImages is extremely careful not to affect to your operating system or your other software.

Want specifics? Here are some of the issues we've been careful of in the design of WinImages and its installation:

  • WinImages does not write its settings to the system registry. It uses .INI files, instead. Not only is this much safer than using the registry, it is also much, much faster, especially in a system that already has a lot of software installed. Sad to say, the registry was a pretty good idea, but the actual implementation by Microsoft was done very poorly, so it is very slow, and it is in fact dangerous to your system to write to it.

  • The WinImages installation is very conservative. Before a single file is written to your system, before any program groups are created or even one icon is installed, your system is examined to be sure that:

    • There is enough disk space for the install on each disk volume involved
    • There is enough disk space for the new program group and icons, if used
    • Your operating system level and revision are sufficiently recent

    ...Only then does the installer assume it's going to be ok, and offer you the opportunity to continue.

  • We don't use third-party installation software. Why? Our installer is custom-designed to do one thing, and one thing only: Put WinImages on your computer in a safe and precisely defined manner. That way, we (and you!) don't have to worry about 3rd party installation software bugs, or it's system requirements and interactions. Instead, we know exactly what's going to happen when the installer runs, because we custom-wrote every line of code in it. If there ever is a problem with a current version of our installation software, you can expect it to be fixed and made available to you immediately, without any excuses or untoward delays.

  • WinImages does not share DLL's or other files with other programs. At all. The DLL's that WinImages uses are custom-made for it, and are installed with it for its exclusive use, so they cannot interfere with other DLL's in your system.

  • WinImages does not snoop on other program installations for any reason; it doesn't read anyone else's settings. The only thing it reads from your system is the location of your Windows and System directories so it can learn where to put it's program files in your system during installation, according to how your system is set up.

  • WinImages doesn't write anything to your system settings - you won't see the dreaded "Windows is updating it's settings, please wait" message the next time you reboot. And you won't have to reboot to use WinImages after you install it, either, because we didn't change your system so profoundly that it has to be restarted, like a lot of other software does.

  • WinImages does not install any software that affects your system globally. The only executables that run are the main program executables. When you quit, there are no programs "hanging around" watching you or otherwise affecting what your system does. When WinImages is running, the only thing that is running is the main application. No little "helpers", no "big brother" monitors, no nothing. Just graphics software. Isn't that what you wanted?

  • WinImages does not "associate" any file types. Why? Because Windows, bless it's unsophisticated little heart, doesn't actually understand "file types". No. Not at all. What Windows understands are filename extensions, which are simply labels anyone or any program can (and does!) put on filenames. So it's not safe to assume that something with a particular file extension is "our" file, and we make any such assumptions. As a related matter, when WinImages attempts to read an image file, it doesn't just read the file extension and assume it's a good image. Instead, we go deep inside the image file, every time, and analyze the file contents and try to make sure it's an image - before we try to read it. That solves lots of problems, and it also makes sure that we can read a JPEG image of a horse even if someone has renamed it "wordsort.exe", which definitely has its uses. File names of user files are pretty meaningless under Windows, as there is no enforcement of naming conventions, so we don't depend on them in any way.

  • WinImages does not use any 3rd-party DLL's or encapsulated objects for which we do not have the entire source code. This is so we can fix the third party code if there are problems with it (and yes, we've had to do that more than once.)

  • We have actually taken the time to analyze, in detail, the source code of what little 3rd party software that we do use (JPEG, MNG, PNG, ZLIB and Twain) in our products and made very certain that none of it is doing anything to, or with, your system that is unethical or sneaky. Some of it - JPEG in particular - we have re-written to the point that it is hardly recognizable as the original software in the first place. But it is all very safe, very high-quality code. We made sure of it. No guessing involved, no presumptions made.

  • WinImages does not use any encapsulated objects - such as those found in C++ based applications - that would put us in the position of using code we do not have complete control over. We even wrote our own "treeview" manager from dead scratch to avoid using Microsoft's treeview object. A good thing, too. Microsoft's is buggy - and considering it's been eight years since we reported the first bug in Microsoft's File dialogs, and that they still have not fixed it, it's a good thing, too. Who knows when they'll fix the treeview control? Or if? If you find a bug in ours, we can fix it, because it is ours and we have the source code. We know how it works and we know how to work with it if it needs attention.

  • The only system DLL that WinImages installs is the Visual C runtime, and that is only installed if a version of it isn't already on your system. We can use any version, so we don't need to replace yours if it's already there. If it's not already there, then there is no harm in installing it.

  • Bugs? Sure, our customers run into bugs. WinImages is one of the most complex applications available for Windows. So it's inevitable. We try to fix them within a few days, and get the fix to you. When's the last time you had that kind of service from a major software manufacturer? Our commitment is, you find a bug in a current release, and we promise we'll do our level best to fix it and get the fix to you, ASAP. So far, our record is very good. It's simple, really: You find 'em - we'll fix 'em. Fair enough?
In short, WinImages is a very safe, very conservatively created and administered application. You don't have to be concerned about it making your system unstable. We want it to be the best it can be, and as you can see, we've taken many effort-intensive steps to see that the odds are definitely in your favor.

Q: How do Opal and the F/X component of WinImages compare?
A:

 

Opal is designed to provide basic special effects for atomic (single layer) still images. It's great for adding special effects to JPEG images and other standard image types.

The R7 F/X application, part of our flagship WinImages suite, is able to do this, and adds a huge number of other capabilities centered around the ideas of more effects, broad animation of both effect parameters and effect regions, scripting, and the most powerful layered image handling in the industry.

F/X is a complete image editing suite (for both atomic and layered images), a special effects suite, an animation generator, a 3D renderer, a color reduction tool, a batch processing engine, an image manager and much, much more.

Check out the feature list at the right to see what Opal and F/X can do for you!

 

Feature Comparison

  Opal WinImages
F/x R7
Still Image Editing Yes Yes
Layered Image Editing No Yes
Effects Area Selection Yes Yes
Photoshop-compatible Area Selection No Yes
Ultra-Zoom Technology Yes Yes
Resolution Independent Yes Yes
Animated Effects Parameters No Yes
Extremely High-Speed Yes Yes
Animated Area Selections No Yes
Unlimited Undo and Redo Yes Yes
Scripting Language No Yes
Plug-in Support No Yes
HTML Gradient Text No Yes
Hot Upgrade Checking No Yes
Antialiasing Yes Yes
Feathering No Yes
Clipboard Operations Yes Yes
Warp Layers™ No Yes
Fluid™ Font Engine Yes Yes
Aspect Ratio Aware Yes Yes
Filmstrip Recorder No Yes
Timeline / Batch Manager No Yes
Image Manager No Yes
Image Grids Yes Yes
Most Recent 10 Directories No Yes
JPEG Save Quality Preview No Yes
JPEG Chroma Encoding Control No Yes
Heightfield Generator No Yes
CMYK Printer Separations No Yes
Project File Support No Yes
Stroked Area Selections No Yes
Global Transparency Controls No Yes
Alpha Channel Editing No Yes
3D Ray Tracer No Yes
Screen Grabbing No Yes
Ghost-Writing No Yes
Image Barrels No Yes
Particle System No Yes
Landscape Renderer No Yes
Bluescreen / Color Keying No Yes
Cloning No Yes
Compositing No Yes
Printing Engine No Yes
Color Reduction No Yes
Morphing Engine No Yes
Number of Image Operators 29 148
Number of Operator Controls 127 1,013
Number of Area Selection Tools 7 28
Number of Color Transfer (Blend) Modes 1 (Matte) 92
Number of File Types Loaded 89 340
Number of File Types Saved 21 25

Click Here to Order

Q: Where can I learn about Black Belt System's Company Policies?
A:They have their own page: Click Here


Issues and Answers from our Technical Support Group


Q: How do I get updates for R7?
A:

Programs

The latest downloadable update of the R7 FX.EXE is R750[g] (about 1 megabyte - to download from within Internet Explorer, just right click on this link and select "Save Target As...")

Check your version using the Help/Learn About Updates (via Internet) menu item. If there are features or fixes you want in the list, we suggest you download, unzip, and replace your fx.exe file and any other files that are in the updater archive. When you choose to download, you will usually find the files which you need to replace, here...

    c:\Program Files\Winimage7\

...if you accepted the installation defaults. If you installed somewhere else, then locate the new fx.exe and any other updated files wherever you put your installation, and replace those files with the new versions from the updated ZIP archive you just downloaded.

R7 FX Update History

Click on the version of WinImages indicated by your Help/About menu selection

Morph Updates

The latest downloadable update of the R7 MORPH.EXE is Morph R7[l] (about 400k - to download from within Internet Explorer, just right click on this link and select "Save Target As.")

Check your version using the Help/About menu item. If your version is less recent (indicated by a smaller number or letter), we strongly suggest you download, unzip, and replace your morph.exe file. When you choose to download, you will usually find morph.exe, which you need to replace, here...

    c:\Program Files\Winimage7\

...if you accepted the installation defaults. If you installed somewhere else, then locate the new morph.exe where ever you put it, and replace it with the version from the updated ZIP archive you just downloaded.

R7 Morph Update History

VersionDetails
7.00[l] Morph 7.00[l] forces file extensions to ".avi" when saving filmstrips. This is a work-around for a Windows bug in the Microsoft AVI code that will not allow use of filenames without .avi on the end. Copyright strings have also been updated.
7.00[k] The very bottom and very top layers would not re-position in the layer dialog layer order list in some layer situtations, especially new projects. This update fixes that.
7.00[j] Reads importer path before trying to create a list of importers. This was a problem if the importer path is not selected as the default used by in the installation.
7.00[i] Reads importer types for progress bar correctly - used to give wrong type name.
7.00[h] Adds loading of EXIF JPEG files (these are generally produced by digital cameras.) Formats nominally supported are standard, progressive, color, and B&W.
7.00[g] Adds swapping of start and end images, start and end control objects, or both. Use SHIFT-s, CTRL-s, and SHIFT-CTRL-s, respectively.
7.00[f] Initially shipped version

Documentation

The latest downloadable update of the text of the R7 documentation is available here (about 1.2 megabytes.)

Note that this does not include any new images that may be part of the documentation. If you find an area where the images in the documents do not seem up to date, or are missing, you can go to that page on our site and save the image from the online version. We change the text a lot more than we change the images, so don't worry about it too much! Extract the new files directly over the old ones.

NOTE: If you're using the docs from the actual CD, rather than from your hard drive, you can't use the update directly. You'll have to copy the documentation to your computer, change where FX looks for the documents (using the dialog just mentioned, above) and then update the files. In that case, you need to copy the html_docs directory and its images and animations subdirectories.

Q: How do I get updates for R6?
A:

Programs

R6 is no longer available. Upgrade to R7.

R6 FX Update History

Click on the version of WinImages indicated by your Help/About menu selection

Documentation

The latest downloadable update of the R6 documentation is Document Release 6.03 (about 770k.) Check your version by looking at the bottom of any page in the docs other than the table of contents or index. If your version is earlier than this, we suggest you download, unzip, and replace all .html files which you can locate by looking where the Help/Help Location dialog indicates for your system (this is an FX menu command.)

Extract the new .HTML files directly over the old ones.

NOTE: If you're using the docs from the CD, you can't use the update directly. You'll have to copy the documentation to your computer, change where FX looks for the documents (using the dialog just mentioned, above) and then update the files. In that case, you need to copy the html_docs directory and its images and animations subdirectories.

R6 FX Documentation Update History

VersionDetails
6.03 Added page numbering to the TOC, the Index and all page headers and footers. This was done to assist those who print any portion of the documentation. Please be aware that as the documentation is updated, the relationship between the page numbers and the index and TOC will change, so page numbers can only be relied on when all printed results are from the same release of the documentation. For this reason, for most users, this is not an update that they really need to get.
6.02 Initially shipped version

R6 Morph Update History

VersionDetails
6.00 Initially shipped version

Q: How do I get Technical Support?
A: Details on technical support are here.

Q: I can't seem to download the product ZIP file. What's wrong?
A: The best way to download any ZIP in an HTTP link as ours are is to right-click on the download link, and select "Save Target As" and then save the file to your hard drive, rather than select "Open from it's current location", using Internet Explorer. However, with some versions of Internet Explorer, sometimes this seems to result in a partially downloaded file, and further attempts to download always fail.

What is happening is that Internet Explorer has "Cached" (that means, saved) a copy of the .ZIP file, which is only partially downloaded, and Internet Explorer is not smart enough to go out and get it again even if you tell it that's what you want.

The solution is to go to the tools menu in Internet Explorer and select "Internet Options". On the first TAB of the dialog (General) you'll see a section headlined "Temporary Internet Files". This is where Internet Explorer is keeping the incompletely downloaded copy of the ZIP file. Press the "Delete Files" button, and wait for all temporary files to be deleted. This can take quite a while, especially if you've done a lot of web browsing. 20 minutes is not out of the question.

When this operation completes, go back to the Product download page and right-click on the download link again, select "Save Target As" again, and choose to save the file - do not choose "Open File From it's Current Location"!

When the download completes, you should be able to unzip the file into a temporary directory and run the installer normally.

Q:Easy Morph won't load some JPEG files. What's going on?
A: The broad standard for JPEG files is the original JFIF standard. Easy Morph supports this standard. However, some companies have, for their own reasons, decided to create variants of standard JPEG, despite the fact that doing this severely inconveniences users of their products.

Easy Morph, like many other applications, is unable to load these files.

Possible solutions for loading non-JFIF JPEG files, or non-standard JFIF files:

  • Load your JPEG file with another application that does support the variant JPEG file format you have (some experimentation may be required on your part to determine what applications actually do support the files) and then re-save the JPEG file as a standard type using that same application. Easy Morph will probably be able to load the newly saved file, as most image applications, including our own, save only in standard JPEG format. If in doubt, check the save options in the application, make sure that "progressive" is not selected, as progressive JPEGs are both non-standard and completely unnecessary for any purpose whatsoever.

  • We do offer considerably more extensive JPEG variant support in our flagship image processing suite, WinImages. WinImages, and its associated Morph application, aside from offering many advanced features far beyond Easy Morph's, can read a wide variety of JPEG variants, including progressive JPEGs, EXIF (digital camera) JPEGs, Penthouse paletted JPEGs variants 1, 2 and 3, and even platform-specific Mac-formatted JPEGs (these contain "fork" information required by the Mac operating system.) Upgrading to WinImages is quick and easy, and we give you 100 percent credit for what you have already spent on Easy Morph, so you don't lose a penny of your investment.

    Just click here to upgrade to WinImages from Easy Morph, and select WinImages (Crossgrade from Easy Morph) once the shopping cart is open.

Q:I'm having trouble controlling morphs or warps in Easy Morph
A: See This page for a tutorial on creating a morph (do this tutorial first.)
See This page for a tutorial on creating a warp (do this tutorial second.)

Q:I'm having trouble saving my work in Morph
A: Morph handles files in a very flexible way that can be confusing if you don't take a few minutes to study how the project and object files work. Everything you need to know can be found here.

Q:My downloaded R6 installation complains that the "CD is Corrupted" - What's wrong?
A: The ZIP archive must extracted to the root of a drive (for instance, C:\ or some other filesystem device.) If you extract it into a subdirectory (as WinZip's "Wizard Mode" will do if it is allowed to manage the extraction and/or execution of the archive) then the installation will not work.

To resolve this problem, delete the first extraction and re-extract directly to the root of the drive, then run the setup.exe again from the root as required. The installation should run without any errors at this point.


Example 1

The resulting extraction must produce the following structure, assuming C:\ is the drive chosen:

C:\setup.exe
C:\Fx.ico
C:\autorun.inf
C:\bbsi_logo.trm
C:\nt9895 (a directory containing other files)


Example 2

If you used another hard drive, perhaps called D:\ then extracting to D:\ to the result would be:

D:\setup.exe
D:\Fx.ico
D:\autorun.inf
D:\bbsi_logo.trm
D:\nt9895 (a directory containing other files)


When the installation (which you start by running setup.exe ) is complete, you may delete these four files and the nt9895 directory and all it's contents. We do recommend you archive the .ZIP file on your hard drive or on a CD-R for quick access in case of system problems.

Q:Some paths don't seem to work for saving particle systems?
A: Don't use spaces in path names. This is generally a good practice anyway, as many other applications don't handle spaces in paths or filenames either. Using spaces in path names and/or filenames can cause many applications to be unable to process those files - it is one of the very bad problems that the Windows filesystem has. Windows itself can fail to properly handle filenames with spaces in many cases.

Q:Why are the RISC versions (Alpha, MIPS, PowerPC) still at the R4 level?
A: Details on RISC versions are here.

Q:Ellipse to Australia Tutorial section unexpectedly fades ellipse to upper left
A:Bug in FX: We have a workaround for this:

When the details dialog is open, instead of setting the transparency for the Australia IShape to 0, press the TR button next to it. Set the trend to a Max-to-Min slope using the icon with the slope on it (\) in the trend dialog. This will have the effect described in the tutorial, and further offers a more powerful and general way of setting transparency.

Q:How do I use the Timeline to operate on multiple image files?
A:See this Quick Tutorial page.

Q:What about Photoshop compatible "Plug-ins"?
A:Photoshop plug-ins have a number of limitations, among which is one very serious problem as far as the WinImages suite goes:

Photoshop plug-ins are not designed to be used in an animated manner. They require user interaction for every frame, which pretty well makes them useless to implement in WinImages, which has to be able to process frames in large groups and sequences, as well as one at a time.

Since Photoshop plug-ins are unworkable, we offer a more advanced plug-in design that takes animation into account, is completely scriptable by the end-user, is far easier for developers to create plug-ins with, and is a free and completely open standard that developers can implement without fee or obligation.

Developers can learn about the new plug-in standard here.

Q: What display card will WinImages perform best with?
A: WinImages has some of the best display technology in any software for windows.

It has a display menu that allows you to select the type of display mode you are using (24 bit, 256 color, LCD gray scale, 16-bit, etc.) and it then uses a special set of drivers to generate at the highest speed possible for that environment. So for any display card, in any display mode, you'll get optimized performance; We'll get the best performance out of it that it is possible to get for those conditions.

Still, there is a "best of the best" situation. For editing images, a display card with 32 or 24 bit display is what we recommend. There are two reasons for this. First, since WinImages' job is reduced to simply moving the image from memory to the display, this is the fastest display mode to update (all images are kept in 32-bits internally, which is actually 24-bit mode plus an alpha channel). Secondly, this allows you to see the image without dither or other elements which a display driver must introduce to improve the apparent fidelity of the image for the observer when less than 24-bit display modes are used.

A good question to ask when choosing a display card to work with WinImages is:

What is the display card with the highest 24 bit resolution, coupled with the fastest 2-d performance, that will work with your computer?

When you pick that card, you'll enjoy the best display fidelity and performance, period.

Q:What CODECs is WinImages compatible with?
A: WinImages uses Windows 32-bit CODEC interface. WinImages can not use 16-bit CODECs from the Windows 3.1 era.

Using Windows 32-bit CODEC mechanism means that Windows actually handles the CODECs themselves; they are not handled by WinImages. WinImages just hands basic images back and forth between it and Windows one after another, until the entire animated image stream is complete.

For loading AVI files into the timeline, or for loading individual frames from an AVI, this approach is almost transparent to the user. Because WinImages does not know what kind of AVI is being handled, nor does it need to know this. It's simple: If the proper 32-bit CODEC is present in the system, Windows will fetch it, use it to decode the AVI data, and then give the AVI data to WinImages. Since WinImages can load images of any size and bit depth, there are rarely any compatibility issues with loading AVI data as long as the right CODEC is in-system.

For saving AVI data using a particular CODEC, things generally also work transparently, unless the CODEC has specific requirements about the type of image(s) that are to be fed to it. For instance, a CODEC that creates animations intended to run on your computer desktop, or on a web page, will generally write animations of any size. However, a CODEC that is intended to create video for output to video tape may require that the images be a specific size - NTSC might be 768x482, for instance - and if you don't provide it with images of that size, it simply won't work.

Since WinImages does not actually handle the CODECs, but rather simply sends data to Windows to put into one by name, or asks Windows for data that came out of one, again by name, we generally can't do anything about CODEC compatibility. The people to ask about any particular CODEC are the people who wrote it. For instance, if you're using Pinnacle video software, and a Pinnacle video CODEC, then you'd want to talk to Pinnacle about the requirements for images that are sent to their CODEC, and so on.

As of 2002, we know that some fairly exotic CODECs do work fine, such as the Video Toaster CODEC; we also know that many of the standard CODECs work fine as well. If you use a particular CODEC and you find that you need to make images of a particular size, or make images meet some other requirement in order to make a CODEC work, we would appreciate it if you'd let us know what you've found out. We'll place that information here in the FAQ for all to benefit.

Q:How do I operate on batches of files?
A:See this Quick Tutorial page.

Q:How do I turn on the GIF and TIFF file capabilities in R4?
A:Edit the .INI files winfx.ini and morph.ini

Add the following line to these files with a text editor:

ChopMem=1

Q:I can't load a different end frame if Distortion Morph is selected: Transition Morph works fine! Is this a bug or a feature?
A: It's a feature. The idea is, if you're doing a distortion morph, often known simply as a a "warp", your intent is to distort the original image. So you use the original to place the start objects, then the end image is the same as the source so you can see how far away an object is positioned, or in other words, the linear amount of the warp.

If you're trying to create a distortion morph, or warp, from one set of features to another, the way you want to do that is using the transition morph, with the "normal" transparency curve set flat.

  1. Open Morph.
  2. Begin the project by...
    1. If the project is already set up, load it now. If it was set up (mistakenly) as a distortion morph, change it to a Transition morph after loading using the option in the Settings menu
    2. If the project is not set up, select Transition morph now, and load your start and end frames.
  3. Under settings, select Set Transparency
  4. The "Normal" curve will be displayed. Press the button at the lower left; it sets the curve to zero, and this forces the result image(s) to have the colors of the start image all through the morph; essentially the same behavior as a distortion morph.

The benefit of this technique is it allows you to use a second image as a "guide" for point setting in a distortion morph.

Note that you can restore the original "Normal" transparency curve by selecting Set Transparency in the Settings menu, and pressing the upper left button to reset the normal ramp.

Q:Sometimes when I load images, the shape is distorted. What's wrong?
A: WinImages is an aspect-correct program. It reads the DPI (dots-per-inch) settings from an image file and uses them to set the ratio of width to height for display. Some programs do not set these values in the image file correctly, and as a result, the image will appear distorted. The solution is to select "Change Image Info" from the menus and edit the DPI setting. If you want the change to be permanent, you'll need to re-save the image. Keep in mind that with JPEG images, each time you save the image, it loses quality.

Q: In R4 FX or Morph, when I save, it seems to be the wrong type of file. What's wrong?
A: This problem occasionally surfaces; when it does, you should download the update for Morph or FX (or both), whichever one(s) that you are having the problem with. In the meantime, you can usually work around the problem by selecting the file type that is one away in the types list. In other words, a file type that is next to the one you want in the list.

Q:Other applications complain about no "stripbytecount" when I save TIFF.
A: For example, PageStream presents this complaint. FX does not put the "stripbytecount" tag in uncompressed TIFF files. Save compressed TIFF files instead. FX does put the "stripbytecount" tag in compressed TIFF files.

Q: I can't load certain JPEG files with FX.
A: FX 7.01[o] and previous had a bug that required you to "refresh" the importer list before the program could read progressive JPEGs if your importers were placed anywhere but the default location, which was "c:\data\plugins". This was fixed in 7.01[p].

Versions of FX earlier than release 7 cannot read progressive JPEG files at all. To work around this, load the progressive JPEG file in another application and re-save it as a non-progressive JPEG.

Some general information about progressive JPEGS:

Progressive JPEG files have little utility at this time, as few applications support the progressive decoding sequence properly. The intent of a progressive JPEG is to have a file that can be displayed progressively as it is received online (for instance, in a web browser), with detail and resolution improving as more and more of the file comes in. Internet Explorer 5 actually behaves worse with progressives; with a normal JPEG, you can see the file line by line as it comes in. With a progressive, nothing at all is visible until the entire file has been received. Leave it to the experts at Microsoft to make something good, into something terrible. :)

Q:My Timeline area selections don't work - what's wrong?
A: Look at the left edge of the timeline. For each action, there should be a "level" indication. For any action, they should be the same. If they are not, you need to rebuild the timeline. Simply drop actions, area selects and so forth on top of each other and they will end up in the same level, which will eliminate this type of problem.

Q:How do I get updates for R4?
A:Select the appropriate file set from the following groups: NOTE: These files are ZIP files that have been compressed with different passwords. In order to extract the files, you must have the correct passwords. Registered users can get these by e-mailing us at sales@blackbeltsystems.com.

When you e-mail us, make sure you tell us what version (Win95, etc.) of the update you wish to receive a password for, as they are all different. Also be certain to tell us the name that you wrote on the registration you mailed in to us, or we won't be able to locate your registration and so be unable to provide you with the password.

Please note that our FTP server is extremely busy, and you may have difficulty if you attempt these downloads during business hours. Your best bet is to try late in the evening. All files are online and available to download.

  1. Connect to our ftp server using anonymous FTP with your registered user name as the password, making sure that PASV mode is disabled in your FTP software. Our ultra-secure FTP server is behind several firewalls, and you cannot use PASV mode to access it. Only port 21 is open. Connect to this address:

        blackbeltsystems.com

  2. Next, navigate the directory structure to:

        /pub/blackbeltsystems.com/

  3. Download the files you need according to the following groupings:
    Alpha NT alpha40.zip
    pkunzip.exe
    bugfixes.txt
    Executable (FX)
    Required extraction tool (you must use this!)
    Explanatory text file
    MIPS NT No update available, version 4.0 is the latest current version
    PowerPC NT No update available, version 4.0 is the latest current version
    Intel NT fxnir406.zip
    mnt.zip
    MSVCRT40.DLL
    pkunzip.exe
    new400.txt
    Executable (FX)
    Executable (Morph)
    Required DLL (place in Windows/System)
    Required extraction tool (you must use this!)
    Explanatory text file
    Windows 95 fx95r406.zip
    m95.zip
    MSVCRT40.DLL
    pkunzip.exe
    new400.txt
    Executable (FX)
    Executable (Morph)
    Required DLL (place in Windows/System)
    Required extraction tool (you must use this!)
    Explanatory text file
    Windows 3.1 m31.zip
    MSVCRT40.DLL
    pkunzip.exe
    new400.txt
    Executable (Morph)
    Required DLL (place in Windows/System)
    Required extraction tool (you must use this!)
    Explanatory text file

  4. To extract the files, once you have downloaded the correct version of PKUNZIP.EXE as shown below and have the appropriate password, go to a DOS prompt. Make sure that the version of PKUNZIP.EXE that you downloaded from here is in the Commands folder that is inside your Windows folder. Change directories to the location where the downloaded .ZIP file is located, and type the following at the DOS prompt:

    PKUNZIP -sPassWord FileName.ZIP

  5. Once the file(s) you need have been extracted, copy them to the appropriate locations. For the Morph and FX EXE files, place them in the install location where WinImages R4 is. For the DLL files, place them in Windows/System (or the equivalant location under NT.)

Q:FX's main window acts oddly after window resize
A:Bug in R4 FX: We have a workaround for this in R4; fixed in R5 and later

To get around this problem, size the window to the size you want, then quit FX. Restart the program, and the window will open at the new size without problems.

Q:FX 4.x "GPF"'s on Exit with Timeline open
A:Bug in R4 FX: We have a workaround for this; fixed in R5 and later

To prevent this problem, close the timeline window manually using the "close box" at the upper right of the timeline window before exiting the main FX program.

Q:FX 4.x "GPF"'s the first time anything is clicked on after being started
A:Bug in FX: We have a workaround for this; fixed in R5 and later

This problem is caused by having DPI open when you quit FX. FX cannot restart properly if it tries to open DPI on startup.

To fix the problem, open the FX .ini file named WINFX.INI, usually located in c:\windows. Find the line that says Operation= and delete only that line. Save the WINFX.INI file back. FX should now start normally.

To avoid this problem, select another operation prior to exiting FX.

Q: My image manager thumbnails are "squished"
A: The Image Load dialog has a checkbox called "proportional".

This type of thumbnail is generated when that checkbox is not checked.

Solution: Select File/Load Image and check the proportional option, then cancel the dialog (or load an image, it'll work either way.)

The setting will be saved when you next quit FX.