Test build of TiMidity++ 2.13.2 (including GUI)
Alex Taylor
release version, 2.13.2, at least to the point where it's suitable for
testing.
Somewhat to my (pleased) surprise, I've also actually succeeded in
merging Darwin O'Connor's old (1997) GUI from TimidPM into the code.
To a point, at least; it seems more or less functional, but I can't
guarantee that everything actually works the way it should. (The
TiMidity internals changed somewhat between 1997 and 2004, in particular
the event callback logic; I think I got most of it converted but I
haven't tested very extensively.)
http://users.socis.ca/~ataylo00/programming/ports/timidity-2.13.2_test_2009-08-
13.zip
http://users.socis.ca/~ataylo00/programming/ports/timidity_source-2.13.2_test_2
009-08-13.zip
The dumb, ncurses, and PM interfaces are compiled in. (So is the
vt100 interface, technically, except that it doesn't actually work.)
To start the PM interface, specify the '-io' switch on the command
line. (Or rename the executable to timidpm.exe, in which case it'll
start the PM GUI automatically.)
There's still quite a bit of work I want to do on this... the GUI is
a bit crude, for one thing; I'd like to prettify it somewhat.
I also want to find a way to start the program in WINDOWAPI mode
and dynamically switch to VIO if a text interface is specified (to
avoid opening a VIO window if started from the desktop). I've played
a bit with that already, but haven't had much success so far.
--
Alex Taylor
Fukushima, Japan
http://www.socis.ca/~ataylo00
Please take off hat when replying.
Ian Manners
> I've succeeded in getting the OS/2 port of TiMidity++ updated to the last
> release version, 2.13.2, at least to the point where it's suitable for
> testing.
Much appreciated, you have given me the kick I need to get Timidity up
and running again on my OS/2 box, which has been on my todo list for,
um, ya, a few years :-)
Cheers
Paul Ratcliffe
> I also want to find a way to start the program in WINDOWAPI mode
> and dynamically switch to VIO if a text interface is specified (to
> avoid opening a VIO window if started from the desktop). I've played
> a bit with that already, but haven't had much success so far.
There is no way to do this in the same process. You would have to start
a separate session to run in VIO and then exit the PM instance.
Alex Taylor
<ab...@orac12.clara34.co56.uk78> wrote:
> > I also want to find a way to start the program in WINDOWAPI mode
> > and dynamically switch to VIO if a text interface is specified (to
> > avoid opening a VIO window if started from the desktop). I've played
> > a bit with that already, but haven't had much success so far.
>
> There is no way to do this in the same process. You would have to start
> a separate session to run in VIO and then exit the PM instance.
Yeah, I've come to the same conclusion after fiddling with it some more.
My main motivation was that if the user tries to specify a text-mode
UI on the command line (e.g. -in) if the exe is WINDOWAPI, it'll hang
PMShell.
Instead what I think I'll do is simply detect if the executable is
running in WINDOWAPI mode, and if so disable all other interfaces. I
think I have this working now.
Alex Taylor
http://users.socis.ca/~ataylo00/programming/ports/timidity-2.13.2_test.zip
http://users.socis.ca/~ataylo00/programming/ports/timidity_source-2.13.2_test.z
ip
(I took the dates out of the zipfiles so I could update the files without
having to post the new links every time.)
Notable changes:
- The current-time display in the GUI should be correct now.
- Properly detects when running as 'TIMIDPM.EXE'.
- Automatically forces the PM GUI if EXE is in WINDOWAPI mode.
- Changed the behaviour of the message window somewhat.
- Various bugfixes.
Still-outstanding bugs:
- In the GUI, if you finish playing a file all the way to the end,
then choose to start playing another (or the same) file, it'll
pause for a few seconds and then show the message "Output Flush
timed out" in the message window before it starts playing.
Haven't gotten around to tracking this down yet.
- The GUI treats any file not ending in ".MID(I)" as not supported
by TiMidity, and tries to play it using MMOS/2 instead. I need
to make the detection more intelligent.
- I have a MIDI file which causes the program to SYS3175 on play,
no idea why.
Best way to install is to have an existing TiMidity installation
(e.g. from my WPI files of v2.10.4) and then simply copy
timidity.exe over the old one (back it up first, of course). If
you have a program object, either add the '-io' switch to the
parameters if you want to use the GUI, or rename the executable
to 'timidpm.exe'.