Author |
Topic: Sysex Window Problem .... (Read 2965 times) |
|
drpietrzak
New Member
MIDI-OX Rules!
Posts: 8
|
 |
Sysex Window Problem ....
« on: Jan 16th, 2003, 2:33am » |
 Quote  Modify
|
I am trying to use Midi Ox to do an update on my Line 6 PODXT and back up the system. Line 6 posted specific instructions on how to use Midi Ox for this operation but one step seems to fail.
The step where I am requested to use "view" -> "sysex" is supposted to open a new windo for me to work with in the Midi Ox (as I understand it) so it can recieve a manual dump. Hoever, I can't get the windo to come open. It appears to me there is a flash of a window (or an error message) but it does not stay open.
What am I doing wrong?
Dale
|
|
 IP Logged |
|
|
|
Jamie OConnell
Administrator
 
Gender: 
Posts: 2027
|
|
Re: Sysex Window Problem ....
« Reply #1 on: Jan 16th, 2003, 9:48am » |
Quote Modify
|
View | SysEx... should open the SysEx view. If it doesn't then there may be a problem with a component in your system. What OS are you running? The most likely failure would be the RichEdit control, although that's not guaranteed.
In Options | MIDI Devices..., what MIDI devices do you have selected and opened?
|
| « Last Edit: Jan 16th, 2003, 9:50am by Jamie OConnell » |
IP Logged |
--Jamie
Music is its own reward.
|
|
|
drpietrzak
New Member
MIDI-OX Rules!
Posts: 8
|
|
Re: Sysex Window Problem ....
« Reply #2 on: Jan 16th, 2003, 10:12am » |
Quote Modify
|
on Jan 16th, 2003, 9:48am, Jamie OConnell wrote:View | SysEx... should open the SysEx view. If it doesn't then there may be a problem with a component in your system. What OS are you running? The most likely failure would be the RichEdit control, although that's not guaranteed.
In Options | MIDI Devices..., what MIDI devices do you have selected and opened?
|
|
This is installed on a Pent II 366 running Win 98SE. What can I do correct the issue?
Dale
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
Gender:
Posts: 2027
|
|
Re: Sysex Window Problem ....
« Reply #3 on: Jan 16th, 2003, 11:05am » |
Quote Modify
|
The problem can also be an errant MIDI driver or an incorrect number of SysEx buffer specified.
Again, in Options | MIDI Devices..., what MIDI devices do you have selected and opened? Make sure you have both an input and output device selected.
In Options | Configure Buffers..., what are your settings? Recommended initial settings: 256 byte buffers, 16 buffers. For both input and output.
Make sure that Options | PassSysEx is checked (select it, if it is not checked, and then look again).
|
|
IP Logged |
--Jamie
Music is its own reward.
|
|
|
drpietrzak
New Member
MIDI-OX Rules!
Posts: 8
|
|
Re: Sysex Window Problem ....
« Reply #4 on: Jan 16th, 2003, 2:49pm » |
Quote Modify
|
on Jan 16th, 2003, 9:48am, Jamie OConnell wrote:View | SysEx... should open the SysEx view. If it doesn't then there may be a problem with a component in your system. What OS are you running? The most likely failure would be the RichEdit control, although that's not guaranteed.
In Options | MIDI Devices..., what MIDI devices do you have selected and opened?
|
|
TBS Montego MPU-401 for both inputs and output (both are highlighted) The same appears in Port Mapping. This appears again in POrt Map Objects, along with channels, system, midi-ox events, and _moxsysmap1.oxm.
I don't know what a Rich Edit Contol is, any help?
Dale
|
|
IP Logged |
|
|
|
drpietrzak
New Member
MIDI-OX Rules!
Posts: 8
|
|
Re: Sysex Window Problem ....
« Reply #5 on: Jan 16th, 2003, 2:54pm » |
Quote Modify
|
on Jan 16th, 2003, 11:05am, Jamie OConnell wrote:The problem can also be an errant MIDI driver or an incorrect number of SysEx buffer specified.
Again, in Options | MIDI Devices..., what MIDI devices do you have selected and opened? Make sure you have both an input and output device selected.
In Options | Configure Buffers..., what are your settings? Recommended initial settings: 256 byte buffers, 16 buffers. For both input and output.
Make sure that Options | PassSysEx is checked (select it, if it is not checked, and then look again).
|
|
How would I know I have an errant midi driver? The buffer settings are 1024, 2048, 1024 and 1024 as indicated by Line 6 (and this works at the office). The Passsysex is also checked in the Options window.
I tried uninstall and reinstall. It did not work. It does not appear to be a full uninstall however (control panel remove program) as the settings were the same when I reinstalled it as before (not the default buffers).
What is puzzeling is that it worked fine at the office. my Other midid devices appear to be working fine as well.
Dale
Dale
|
|
IP Logged |
|
|
|
drpietrzak
New Member
MIDI-OX Rules!
Posts: 8
|
|
Re: Sysex Window Problem ....
« Reply #6 on: Jan 16th, 2003, 3:10pm » |
Quote Modify
|
OK ... I just received a RichEdit error in another program. This suggests it is a Richedit problem. What is it and where do I find it?
Dale
|
| « Last Edit: Jan 16th, 2003, 3:36pm by drpietrzak » |
IP Logged |
|
|
|
Jamie OConnell
Administrator
Gender:
Posts: 2027
|
|
Re: Sysex Window Problem ....
« Reply #7 on: Jan 16th, 2003, 5:45pm » |
Quote Modify
|
Quote:The buffer settings are 1024, 2048, 1024 and 1024 as indicated by Line 6 (and this works at the office). The Passsysex is also checked in the Options window.
I tried uninstall and reinstall. It did not work. It does not appear to be a full uninstall however (control panel remove program) as the settings were the same when I reinstalled it as before (not the default buffers).
|
|
If I understood you correctly, 1024 buffers is way too many! The total amount of buffer memory supplied to ALL open MIDI drivers must fit within a 64K page locked segment (Win98 still uses 16 bit MME). Again, I recommend no more than 32 buffers of 512 bytes in size, or 64 buffers of 256 bytes in size. If you want to use 1024 byte buffers, allocate only about 16 of them.
The reason why uninstalling does not remove this information is intentional: we never remove appliaction settings upon an uninstall. This is in accordance with Microsoft recommendations for the HKEY_CURRENT_USER portion of the registry. If you ever wanted to manually remove all your settings, you would need to delete the HKEY_CURRENT_USER\Software\MIDI-OX tree from the registry.
The Richedit control is a Microsoft component of Windows. There are several DLL's that implement it, and I'm not sure of all the names on Windows 98 SE. You might try searching their website for information about it.
|
| « Last Edit: Jan 16th, 2003, 5:46pm by Jamie OConnell » |
IP Logged |
--Jamie
Music is its own reward.
|
|
|
drpietrzak
New Member
MIDI-OX Rules!
Posts: 8
|
|
Re: Sysex Window Problem ....
« Reply #8 on: Jan 16th, 2003, 5:57pm » |
Quote Modify
|
I don't know about too many. It has worked for almost everyone including me at the office. The exact Line 6 instructions read ...
"1. Once you have your hands on a PC with Internet access and a MIDI interface (or PC soundcard) properly connected and configured, go here to download the “MIDI-Ox” System Exclusive Utility software to your computer - take note of where you save it.
2. Once you’ve downloaded the application, double-click the “midioxse.exe” icon to extract and run the installer.
3. After it is installed, launch the application. You’ll find the MIDI-Ox program icon (which looks like a Swiss Army knife) in your Start menu under Start>Programs>MIDI-OX.
4. To configure the software, go to the MIDI-Ox “Options” menu and select “Configure Buffers…”
5. In the “Configure Sysex Buffers” dialog that appears, you’ll see four numeric fields with different numeric values already assigned to them.
- Change the value in the top two fields (Low Level Input Buffers “Size” and “Num”) to “1024”.
- Change the value in the 3rd field (Low Level Output Buffers “Size”) to “2048”.
- Change the value in the last field (Low Level Output Buffers “Num”) to “1024”.
- Click “OK” to save your changes and exit the dialog.
6. At this point, you’ll need to confirm that the correct MIDI device (the MIDI interface or PC soundcard you connected and configured in step 1 above) is selected for MIDI communication to and from your computer.
To confirm that the correct MIDI device is selected:
- Go to the MIDI-Ox “Options” menu and select “MIDI devices…”
In the dialog that appears, you’ll see two large fields. One labeled “MIDI Inputs” and one-labeled “MIDI Outputs”.
- Under “MIDI Inputs:” highlight your MIDI interface in the list of options (e.g.: SB Live! MIDI In).
- Under “MIDI Outputs:” highlight your MIDI interface in the list of options (e.g.: SB Live! MIDI UART or SB Live! MIDI Out)
- Make sure the “Automatically attach Inputs to Outputs during selection.” checkbox is unchecked.
- The Options: Pass Sysex menu item should be checked by default, but must be checked to use the Sysex window.
- Click “OK” to save your changes and exit the dialog.
By default, the “Monitor – Output” window should now be opened and updated to show “Opened MIDI Input” and “Opened MIDI Output”. "
In any case, how can I fix a RichEdit problem? There are a million hits on the micorsoft site for it. None seem to be reinstalls.
Dale
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
Gender:
Posts: 2027
|
|
Re: Sysex Window Problem ....
« Reply #9 on: Jan 16th, 2003, 6:04pm » |
Quote Modify
|
It may indeed work. It would work on Windows 2000 and XP anyway, but their suggestions are a vast waste of resources IMO. I would say they are asking for trouble recommending that under Windows 9x, and it is always myself who has to deal with those having trouble. 
Anyway, here is an article from the Microsoft site about the Richedit control: http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b308310
|
| « Last Edit: Jan 16th, 2003, 6:05pm by Jamie OConnell » |
IP Logged |
--Jamie
Music is its own reward.
|
|
|
drpietrzak
New Member
MIDI-OX Rules!
Posts: 8
|
|
Re: Sysex Window Problem ....
« Reply #10 on: Jan 16th, 2003, 10:13pm » |
Quote Modify
|
OK. I tried the microsoft update and setting the buffer to 256 and restarted the system. Sadly, no change. I checked files and I have the following:
RichTx32.ocx
Riched20.dll
Riched32.dll
Riched.dll
Some are in windows\options\cabs.
Some are in windoows\system.
Any other ideas on things I can try?
Dale
PS:
I really appreciate your williness to help with this.
|
| « Last Edit: Jan 16th, 2003, 10:15pm by drpietrzak » |
IP Logged |
|
|
|
Jamie OConnell
Administrator
Gender:
Posts: 2027
|
|
Re: Sysex Window Problem ....
« Reply #11 on: Jan 16th, 2003, 10:47pm » |
Quote Modify
|
I think I wasn't clear: the buffer size is not the problem, but the number of buffers might be. How many buffers did you set?
Quote:
RichTx32.ocx
Riched20.dll
Riched32.dll
Riched.dll
|
|
That sounds like the right set. They are only used in windows\system
The ones in windows\options\cabs are likely the original installer files. I don't know if you've installed service packs, etc. that modified any of the ones in cabs, but you could try backing up all the richedxxx.dll files in \windows\system (to some other directory) and then updating them with the versions from windows\options\cabs. Be aware, that the versions in the cabs may be compressed, so you might want to check with some other sources before doing this. I am not running Windows 98, or I could be more helpful.
One thing I keep thinking about is that I thought that riched32.dll was a wrapper for the original version 1.0 riched (riched.dll?). If that's the case, you might first just try moving riched.dll to another sub-directory and see if that fixes things.
|
| « Last Edit: Jan 16th, 2003, 10:50pm by Jamie OConnell » |
IP Logged |
--Jamie
Music is its own reward.
|
|
|
drpietrzak
New Member
MIDI-OX Rules!
Posts: 8
|
|
Re: Sysex Window Problem ....
« Reply #12 on: Jan 16th, 2003, 11:27pm » |
Quote Modify
|
That was it. The Riched32.dll was not in the windows/system directory. A copy of it to that directory and all is well. I bet when I did an auto uninstall of some audio program it took it with it without my realizing it. Very cool. All is well with the world again.
Thank you very much!
Dale
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print