SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 24 | April | 2006 ]

<< Previous Message << >> Next Message >>


Date: Mon, 24 Apr 2006 13:55:11 PST8
From: Colin Campbell <cmcampb@adelphia.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Problem using TiMidity

Content Type: text/plain

In another thread, I asked about playing Midi files on my PCs.

I found that on the older one, with a Crystal sound chipset, a .MID file
would play, if not very well. On the newer one, with an on-board sound
card and UniAud, I would get an error rc=5134 when I tried to play the
same .MID file.

Steven recommended installing TiMidity. I did that on the newer PC. (I
have not tried it on the older PC.)

Then, I tried again to play a .MID file. At first, I would see the
Player window, with "Opening..." at the bottom. This lasted a long
time, but I never got any sound. I found I couldn't close the window,
and I couldn't do a clean shut down. I had to power off and restart,
then let the system do CHKDSK, etc.

So, I added the statement SET TIMIDITYDEBUG=F:\TIMIDITY\TIM.LOG to my
CONFIG.SYS. I also went back through the install instructions, and
decided I would download the "patches" (which simulate different musical
instruments). I unzipped these into F:\TIMIDITY\PATCH, which originally
only had two .PAT files, but now has over 100.

I edited file TIMIDITY.CFG, to tell the product to use the new Gravis
patch set. There are two lines which read
#dir /dos-C/ultrasnd/midi
#source gravis.cfg
I added two lines which read
dir /TiMidity/
source gravis.cfg
***
(There is another set of comments which includes the line
#dir /usr/local/lib/timidity
I'm wondering if I should add a line that reads:
dir /TIMIDITY/
In fact, I have tried that, with no better results.)
***

Trying again to play a .MID file, I double click on the file, and I see
the Player window open for less than a second, then it disappears. (I
can see it get added to the eWorkplace task bar and deleted, too.)
There is no TIM.LOG file created.

How should I proceed to debug this situation?
Thanks,
Colin

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 24 | April | 2006 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.