1. Does anybody know a workaround for the incompatibility issue which
causes the WPS to restart whenever a folder containing midi files is opened?
2. If I try to open a midi file using MMPM, the player starts but closes
instantaneously. Timidity.exe (v2.10.4) works fine. Any thoughts on
this? (I'd like to have midi support in win-os2, which I had on my
previous machine using John Gow's genaud. AFAIK this needs midi working
in MMOS2, hence timidity.exe alone does not suffice.)
Thanks
Pete
Thanks
Pete
Peter Milne wrote:
> Sorry, subject of previous message should have been 'midi'! I do have a
> question about CD players, though: I'm not a great fan of the eCS CD
> player.
I could get to like it - if it actually produced sound that would help.
Sadly the new player is not Digital Transfer capable so is not of any
use here.
For all its sins. I actually like the old CDPM.exe. So far I've
> been unable to locate it on the CP2 disc. Does anyone know where to find
> it, and whether there would be any problem using it with RC6a?
>
> Thanks
> Pete
No problems using cdpm with RC6a here.
Regards
Pete
Peter Milne schrieb:
>
> Sorry, subject of previous message should have been 'midi'! I do have a
> question about CD though: I'm not a great fan of the eCS CD
> player. For all its sins. I actually like the old CDPM.exe. So far I've
> been unable to locate it on the CP2 disc. Does anyone know where to find
> it, and whether there would be any problem using it with RC6a?
>
> Thanks
> Pete
Sorry,
nowhere on the CP2 discs.
You have to look on the Warp 3 discs.
And there it would be \os2image\DISK_14\PACK5
Hendrik
I'll second that.
For all its sins. I actually like the old CDPM.exe. So far I've
>> been unable to locate it on the CP2 disc. Does anyone know where to find
>> it, and whether there would be any problem using it with RC6a?
eCS already has CDPM.EXE installed. It just doesn't create a program object
for it. Just drop a program template on the desktop, set the path and file name to
b:\MMOS2\MMPLAYER\CDPM.EXE
where b is your boot drive, set the parameter field to
CDaudio01
and you're up and running. If you care, you can hunt around in the MMOS2 tree
for a suitable icon.
What version of ecs are you using and was this a fresh install.
I can't find cdpm.exe on the warp4 cd, the cds of the CPs, the ecs 1.1
cd 1 nor ecs 1.2 cd 1 (all German), haven't checked any ecs 1.0 cd.
Hendrik
I am using eCS2.0RC7 (Silver Release). It is a fresh install. On the install
disk, CDPM.EXE is in \CID\SERVER\MMECS\BASE. Also, CDPLAYER.CIO is in the same
directory.
I imagine that on the versions you mention, these files are in a compressed
archive somewhere.
Ok,
I only looked in the os2image tree.
Hendrik
Memory is too fuzzy for me. Check Google because this has been
discussed before. Don't remember if there was a solution, but I don't
remember having this problem myself.
> 2. If I try to open a midi file using MMPM, the player starts but closes
> instantaneously. Timidity.exe (v2.10.4) works fine. Any thoughts on
> this? (I'd like to have midi support in win-os2, which I had on my
> previous machine using John Gow's genaud. AFAIK this needs midi working
> in MMOS2, hence timidity.exe alone does not suffice.)
The GUI player worked for me sometimes, but I found it was unreliable...
especially if you tried to pause or seek around in the MIDI (= FLAMING
DEATH!). I changed my associations to only use PLAY.CMD to play MIDIs,
and this worked well unless you launched more than one at a time (on
purpose or by accident). I patched up PLAY.CMD to make it more tolerant
of bad MIDI files and the sound device being occupied when you try to
play. With these changes, I had it working quite reliably, even with
some bad MIDI files on occasion.
--
[Reverse the parts of the e-mail address to reply.]
The reason MMPM does not play MIDI files is simply that there is no midi
support in the uniaud driver.
Regards
Pete
> The GUI player worked for me sometimes, but I found it was unreliable...
> especially if you tried to pause or seek around in the MIDI (= FLAMING
> DEATH!).
Do you mean the old version on Hobbes (0.2i) or my updated test version
(based on 2.13.2)? Seeking and pausing seem to work OK in my admittedly
limited use...
--
Alex Taylor
Fukushima, Japan
http://www.socis.ca/~ataylo00
Please take off hat when replying.
Sorry for the confusion, Alex. I was talking about using the old MMOS/2
codec with the OS/2 built-in GUI player. Not your new Timidity GUI,
which I'm sure works quite well.
> Sorry for the confusion, Alex. I was talking about using the old MMOS/2
> codec with the OS/2 built-in GUI player. Not your new Timidity GUI,
> which I'm sure works quite well.
Thanks, although I haven't really run it through enough stress to say
if it "works quite well" or not. BTW, it's not really "my new" GUI,
rather Darwin's old GUI dusted off with a few tweaks.
This is a known prob with Timidity MCD. It only allows one instance (one
simulateous call into the DLL) but the MMOS2 players starts twice when you
open it. That leads to a crash.
Found it and created an object! Thanks for all replies.
Pete
But MMPM should be using Timidity MCD, shouldn't it? I do have some
progress here - NormalPlayer will play MIDI files ok using Timidity MCD
via MMOS2, so Timidity is providing MIDI support to MMOS2 as it should.
Apart from the annoyance of being unable to open folders containing MIDI
files, even in eCenter menus, the big problem now is that I still can't
get MIDI or wave support in Win-os2. During boot, genaud reports itself
as loaded and can find wave audio (uniaud) and sequencer (Timidity).
However, in the Win-os2 control panel os2wave and os2midi are not
listed, although the corresponding .drv files have been copied to
\os2\mdos\winos2\system and the appropriate lines added to system.ini.
I'm stuck here as I don't know how Win 3.1 decides what to put in the
list of available drivers.
Pete
Peter Milne wrote:
> Peter Brown wrote:
>> Hi Peter
>>
>> Peter Milne wrote:
>>> I've recently installed RC6a on an oldish computer which has onboard
>>> SI7018/CMI9738 sound chips. Uniaud 1.0.9 gives wave audio but no MIDI
>>> support, which I would like to have. I've therefore installed Timidity
>>> MCI. Two questions:
>>>
>>> 1. Does anybody know a workaround for the incompatibility issue which
>>> causes the WPS to restart whenever a folder containing midi files is
>>> opened?
>>>
>>> 2. If I try to open a midi file using MMPM, the player starts but closes
>>> instantaneously. Timidity.exe (v2.10.4) works fine. Any thoughts on
>>> this? (I'd like to have midi support in win-os2, which I had on my
>>> previous machine using John Gow's genaud. AFAIK this needs midi working
>>> in MMOS2, hence timidity.exe alone does not suffice.)
>>>
>>> Thanks
>>> Pete
>>
>>
>>
>> The reason MMPM does not play MIDI files is simply that there is no
>> midi support in the uniaud driver.
>>
>
> But MMPM should be using Timidity MCD, shouldn't it?
To be honest it is a long time since I bothered with midi due to the
problems involved.
I do have some
> progress here - NormalPlayer will play MIDI files ok using Timidity MCD
> via MMOS2, so Timidity is providing MIDI support to MMOS2 as it should.
>
> Apart from the annoyance of being unable to open folders containing MIDI
> files, even in eCenter menus, the big problem now is that I still can't
> get MIDI or wave support in Win-os2. During boot, genaud reports itself
> as loaded and can find wave audio (uniaud) and sequencer (Timidity).
genaud? - aha! The older version of DTA.
> However, in the Win-os2 control panel os2wave and os2midi are not
> listed, although the corresponding .drv files have been copied to
> \os2\mdos\winos2\system and the appropriate lines added to system.ini.
> I'm stuck here as I don't know how Win 3.1 decides what to put in the
> list of available drivers.
>
> Pete
As I have DTA.zip available here I had a look in the readme and noticed
this:-
- The old version of the generic WIN/OS2 driver which can be found on
http://home.wanadoo.nl/rwklein has the following problem:
Please note that when you have installed the driver and you
don't get any sound in WIN/OS2, check the following:
Click with the right mouse button on the icon of the WIN 16 session
(Folder Local System->Command Prompts).
Select the properties, click on the green tab "session",
click on the button Win 16 Properties. A new window pops up.
Choose "DOS memory settings" and click on OK.
Select the option EMS_MEMORY_LIMIT and put the slider to the left (to 0).
Select EMS_FRAME_LOCATION and choose NONE.
As that would seem to apply to the genaud package I hope it helps.
Regards
Pete
Gives a 404 error.
Hendrik