QuickDisks were used by the S612 and the S10. QD: These are images representative of a QuickDisk, a strange 2.8 floppy device that is unlike anything. (We are doing our part by not allowing creation of DSS-1 DSK files.) It would have been easier to provide them as actual images, but he didn't, and as a result there are tons of DSK files around. A DSK file is CopyQM image file, which is the actual image encoded into this compressed thing. One person decided it'd be great to take all these Korg DSS-1 images and provide them on the Internet, but he used the CopyQM program to create the images. In the Translator interface, you will see what file types they are by the Icons and the Type column in the Object List.ĭSK: This is more a historical file format. So Translator peeks into these files and finds out what they are. Of course, the Already Established are self-identified, but IMG or HFE could be anything. Some of that calculation is on file size (the Mirage is an example), sometimes it's the structure and identifiers of the data. When Translator sees one of these extensions, it reads it and determines what sampler it's dealing with. Already Established Floppy Image Formats: EDE/EDA/GKH (Ensoniq EPS/ASR), OUT (Roland S5x/S7x), EMX/EM1 (Emu Emax), DSK (Korg DSS-1), QD (Akai S612, Roland S10).This is how Translator identifies floppy images: Floppy Images are not individually recognized by extension, however. We HIGHLY RECOMMEND making images and not dealing with floppy disks directly.įloppy Images are treated as Bank file formats - ones that handle multiple Programs that reference a pool of Samples. Translator 6 supports reading floppy disks, however only on Windows, and the support for it is mainly creating images and not reading the material. Regardless, all you have to know is that every Floppy Image represents a floppy disk.
#Floppy disk image creator freeware windows#
There's many ways of creating them, over the years, but most of them come from Windows and courtesy of a replacement floppy drive name OmniFlop. Floppy Images are now handled in the general area, under any normal folder or drive.įloppy Images mostly come from the floppy disks themselves. Virtual Drives are now defined as anything greater than 5mb, and are located only via the Images folders and listed under the Virtual Drives section of the Container Pane. The reason for the treatment is the huge explosion of interest in vintage samplers that only work with floppies, and that floppy emulators such as the Gotek have allowed massive access to these samplers.įloppy Images are now handled completely separately from Virtual Drives. Although floppies and floppy images have been support since the beginning, Translator now defines floppy images as a very specific object. Starting with Translator™ 7.1 and Translator™ 6.2, we have introduced the concept of Floppy Images.