Cue file conversion

SteveB

Well-Known Member
And while we are on the subject of file conversion, I just got a call from one of my freelancers, who wanted to know about converting from an Express/ion Off-Line .shw file to Obsession 600.

I told her "FahGedAboutIt".

I recall that Obsession I consoles used the DOS only Obsession Off-Line editing program (so good luck finding a puter with old DOS on it), which had limited (if any) ASCII capabilities.

Does this sound correct ?

I did tell her that West Side Systems and Second Cut both do file conversions, but I doubt they want to lay out the cash.

Steve B.
 
I tried to go the other way once . . . Obsession to Express/ion impossible to just convert the file, ETC laughed at me. But yes companies will be happy to convert for a large fee.
 
If I may, what is the actual thing that prevents this from happening? I know that Ion can read ASC II, so I guess i am assuming that obsession cannot?
 
If I may, what is the actual thing that prevents this from happening? I know that Ion can read ASC II, so I guess i am assuming that obsession cannot?

The expert on all this is a guy named Tim Buchman, now retired as console operator at NY City Center and the owner of Second Cut.

My recollections from many of his posts (which I have trouble searching for) is that the early generation Obsession I 600/1500 consoles, as well as the OB-I Off-Line Editor were pre- USITT ASCII cue standards, and thus were essentially before the ability to readily transfer files between platforms.

In general, the route that ETC and Strand took, was rather then do the conversions within the console, was to have an off-line-editing program read the console disks and then convert to USITT ASCII. The original OB I OLE program was written in DOS as well, which now makes it difficult to access, as few Windowz machines have DOS since XP's intro.

Note that I have been specific in calling it "USITT ASCII" as that is a very specific data format using the ASCII format. Some folks conversant in ASCII are able to do some file conversions, with Tim, as well as Eric Cornwell, a NYC based LD and owner of West Side Systems, writing their own software to make conversions between platforms.

If memory serves, the ETC program ETC Edit didn't support ASCII and it was only when Obsession II and the later software for Expression II/III/Express with Expression Off-Line came out (mid 90's) did USITT ASCII support become functional between ETC consoles and Strand, using Showport. Note also that even the Obsession II files are problematic and I recall that the OB II OLE (which finally ran under Windows without DOS) could not export in ASCII, which is a function ETC has only recently added to get OBII files over to Eos.

That's about all I know and will attempt to get Tim's input as well.

Steve B.
 
And while we are on the subject of file conversion, I just got a call from one of my freelancers, who wanted to know about converting from an Express/ion Off-Line .shw file to Obsession 600.

I told her "FahGedAboutIt".

I recall that Obsession I consoles used the DOS only Obsession Off-Line editing program (so good luck finding a puter with old DOS on it), which had limited (if any) ASCII capabilities.

Does this sound correct ?

I did tell her that West Side Systems and Second Cut both do file conversions, but I doubt they want to lay out the cash.

Steve B.


I would say if you dealing with just conventional fixtures then just set the patch up to be the same on bolth consols and reprogram the obsession by hand using the channel levels on the screen. It doesn't take as long as you might think however if your dealing with intelligent fixtures well that's another story.
 
For DOS you can always use dosbox which is a pretty complete cross platform (linux/windows/mac/beos/more) open source DOS-emulator, you can run most(/all) DOS programs on.
Chech out DOSBox, a x86 emulator with DOS for more info, the latest version etc.
[edit]
Dosbox was recently mentioned in a post related to how to run Strand 500 OLE...
[/edit]

The problem I have heard about with assorted DOS eumulators, is trying to get the DOS side to see hardware that is specific to Windows XP/Vista, such as USB floppy drives.

Thus, with out the 3.5" external floppy drive, you are dead in the water as you cannot read to or write from the console diskette.

It's very specific to the computer you are using, thus it's hot or miss.

SB
 
On windows I don't know how it would work, but on linux you can have dosbox mount any path on your computer to any drive-letter.

According to my sources it is also fully possible to do so on windows.

The command would be something like:
mount a A:\
To get your real floppy to be treated as A: by dosbox.
 

Users who are viewing this thread

Back