Yahoo Groups archive

Atari-Midi Archives

Index last updated: 2026-04-28 22:40 UTC

Message

Re: [atari-midi-archives] .SEQ files and YSEDITOR

2013-01-19 by charlie midi gfa

from my experience the seq.def  holds information relivent to the device 
being used but i could be wrong ,,
the tones can be changed by a programmer who programs atari apps...
i changed mine and have made a slightily different into as well .....
.if you really have the need for inputing values once the program starts, i 
think i can write this into martains code for you,,,,,

favorable?
charlie

----- Original Message ----- 
From: "mopuss_y" <mopuss_y@...>
To: <atari-midi-archives@yahoogroups.com>
Sent: Friday, January 18, 2013 2:11 PM
Subject: [atari-midi-archives] .SEQ files and YSEDITOR


> Hi, I'm new to Atari midi and have just started using the FB01-specific 
> version of YSEDITOR (http://www.home.zonnet.nl/m.tarenskeen/yseditor.htm) 
> in STEEM to create sounds on my Yamaha FB-01.
>
> Does anyone here use YSEDITOR? I am intrigued by the .SEQ file that 
> resides in the same folder. (DEF.SEQ). I guess it is a sequence file used 
> by YSEDITOR when you click the SEQ button in the editor to audition a 
> sound and I guess it's something like a MIDI file with note information 
> etc. Does anyone know more about this? Is .SEQ a standard file format that 
> Atari sequencers use? Sorry if this is a really basic question. I wonder 
> if I can edit this sequence in a sequencer and get YSEDITOR to play a 
> different one when I click the button.
>
> And does anyone know if I can alter the little three-note test sequence 
> that plays if you hit the TEST button in the editor?
>
> If the above isn't possible, I will carry on using the MOUSE button to 
> audition the sound, as this is quite neat (I don't currently have a 
> keyboard, am on a promise of one!).
>
> Mo
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.