- VERSION 4 IMPLICATIONS FOR SCOPISTS
Total Eclipse has recently updated from Version 3 to Version 4. This
change has some implications for scopists, which I will now explain.
First of all, Version 4 and later use a different dictionary structure
than earlier versions. This was done to make the dictionary more
powerful. You can now sort, filter, and customize the display of the
dictionary. For full details on what's new, view Help/New Version Changes.
- TRANSITIONING TO VERSION 4
The first time you enter a user in V4, Eclipse will establish a backup
version of each of your users. It will have the same name as your
original user, but with a "3" attached. It makes a new .ini (user
settings) file with that name, and makes a jobs folder with that name as
well. For example, if your user name is Bob, you will now have a Bob3
folder and a Bob3.ini file when you look at your list of users. Be sure
to go into the Bob user when you are using V4.
After you update to Version 4, any time you attempt to open a 3.X
dictionary, Eclipse will ask if you wish to convert it. If you answer
yes, the old dictionary will be placed in the backup folder, and the new
one will take its place. This includes the Main dictionary (also known
as the Edit dictionary for scopists).
Whenever 4.X opens a 3.X dictionary, it will copy the original
dictionary to the appropriate backup folder for the current user.
Remember, the program will always ask before converting any dictionary,
so even if you accidentally go into the wrong user and it asks to
convert your main dictionary, you can always answer "no" to get out of it.
If you need to go back and run 3.X for any reason, you can pick your
User3.ini file and it will have all of the correct settings, the old
main dictionary, and if you need to get into any jobs or into any
dictionaries that have not yet been converted, you can navigate to the
new jobs folder and either use the files directly or copy the files to
the backup user. Once you are entirely comfortable with 4.0, you can
delete the backup User3.ini file and it will no longer appear on the
list, but the backup folder will still exist with the backed up 3.X
As far as most of the program goes, the new dictionary works much like
the old one. The dictionary syntax is the same, globals are still done
the same way, selecting dictionaries for translation is still done the
same way, etc. This new dictionary will allow many new features to be
created in the long run, but for now, the main differences are in the
file size (new dictionaries are half the size of old ones) and in the
dictionary editor itself.
- IF YOUR REPORTER IS ON V4, AND YOU ARE NOT
If the V4 reporter wants you to give you a dictionary, the reporter will
have to convert it to RTF first. Attempting to open a V4 dictionary in
V3 will give you a "this is not an Eclipse file" error. Have the
reporter export to RTF. You import the dictionary from RTF as normal.
When returning dictionaries to the reporter, you need take no additional
steps. When the reporter gets it and tries to open it, they will be
prompted to convert it to V4.
- IF YOU ARE ON V4, AND YOUR REPORTER IS NOT
The process is the reverse of what was just described. Any dictionaries
you receive, you will be prompted to convert to V4 format. When
returning them to the reporter, you'll have to export to RTF to make
them usable for the reporter.
- SCOPIST CONFLICT ISSUES
If you're used to having your reporter check Make Edit Station Info so
you can give them back their conflicts, this is a little problematic if
you are on different versions. The AI data won't go through the RTF
conversion (it's not part of the RTF/CRE standard) so if you're on V4
and they're on V3, they won't be able to benefit from your selections.
If you're on V3 and they're on V4, though, you'll be okay. Check Make
Edit Station Info and have the reporter include the job dictionary as
normal. When you make selections, they are compiled in the Edit
(scopist's Main) dictionary. When you give the Edit dictionary to the
reporter, they can convert it from V3 to V4, and merge it with their
Main. The conflict data will increment as usual.
- CONVERTING THE ECL (TRANSCRIPT) FILE
It does not have to be converted. Only dictionaries differ between V4
and previous versions. No additional steps need be taken. If you're not
sharing dictionaries with the reporter, you can ignore this whole document.
- VERSIONS EARLIER THAN TOTAL ECLIPSE VERSION 3
The V3 instructions apply. The ECL/DIX/NOT file formats never changed
between Eclipse NT Version 1 and Total Eclipse Version 3. So if you or
the reporter is on Eclipse NT Version 2 or Version 1, follow the V3
If you or the reporter is still on the DOS-based Eclipse 8, you'll still
have to do RTF conversions for all file transactions with the
Windows-based Eclipse software. So from your perspective, nothing changes.
- AUDIO CONSIDERATIONS
After you update to Version 4, you need to reselect your codec. (A codec
is a protocol for compressing and decompressing audio files.)
To do this:
1. Go to User Settings/Realtime tab.
2. Click Compression button.
3. You may be asked to select a sound device. Pick the sound card. (If
you're not sure, uplug any microphones or external USB sound devices,
exit the dialog, and start again from Step 1.)
4. The "Select Compression" dialog will appear. You will be asked to
enter Name, Format, and Attributes. If you're not sure, select Format as
PCM, and Attributes as "11.025 KHz 8 Bit Mono 10 KB/sec" or "8.000 Khz 8
Bit Mono 8 KB/sec". (You can leave Name as "Untitled.")
5. Click OK to exit the dialog.
Here's why this matters: when you update from V3 to V4, the Speex codec
is installed. This can change the codec the reporter uses to record
audio in Eclipse. If the reporter updates to V4 and doesn't reselect
their codec in Eclipse, it can cause any newly-recorded audio files to
have incorrect information in them. In turn, when you try to play the
file, it can cause the error messages that have been described recently
in this forum.
I should point out that it's more important for the REPORTER to reselect
the codec than the scopist. If this situation is going to cause a
problem, it's going to be on the recording side, not the playback side.
So if you have any clients that have recently upgraded to V4 or are
still on V3, you might want to share this message with them.
That's all I can think of to tell you. If any questions, please post
them at SSG and I'll do my best to respond.
Gary Stephen Jr.
gary at eclipsecat dot com