@Big_Goomba
I`m very sorry but that is not possible. The MIDI Channel is reported by the DEQ2496 itself while answering a Broadcast SysEx Command.
Kind regards
I`m very sorry but that is not possible. The MIDI Channel is reported by the DEQ2496 itself while answering a Broadcast SysEx Command.
Kind regards
Hello BigD,
First I wanted to thank you for creating such a great tool for the DEQ2496.
However, I am experiencing an issue I'm havin and wanted to report to you.
When the program is first opened, and after DEQ2496 Lookup...
When the buttons (listed below) are pressed:
DEQ-Modules:
GEQ, PEQ, DEQ, WIDTH, FBD, DYN/LIMIT, DELAY, MEMORY, RTA, METER, IO/Settings
Tools:
Screen Loader, REW/Import, Quick Change
I am prompted with a Windows Installer (see attached photos).
The Windows Installer is looking for something that doesn't exist:
C:\Users\david\Desktop\InstallShield 12 Premier Edition SP1\tmp\
Then when I Click OK:
See attached photos
After cancelling several times to close the Windows Installer the program then works fine.
Hope you find this information helpful...
Best,
David
First I wanted to thank you for creating such a great tool for the DEQ2496.
However, I am experiencing an issue I'm havin and wanted to report to you.
When the program is first opened, and after DEQ2496 Lookup...
When the buttons (listed below) are pressed:
DEQ-Modules:
GEQ, PEQ, DEQ, WIDTH, FBD, DYN/LIMIT, DELAY, MEMORY, RTA, METER, IO/Settings
Tools:
Screen Loader, REW/Import, Quick Change
I am prompted with a Windows Installer (see attached photos).
The Windows Installer is looking for something that doesn't exist:
C:\Users\david\Desktop\InstallShield 12 Premier Edition SP1\tmp\
Then when I Click OK:
See attached photos
After cancelling several times to close the Windows Installer the program then works fine.
Hope you find this information helpful...
Best,
David
Attachments
Dear David,
which Windows version do you use? I've never seen this on a Win7 to Win10 system.
It my be a rights conflict with Midi-OX.
1. Disable all THIRD-party Virusscanners and friends
2. Load down MIDI-OX from its homepage
3. Reinstall MIDI-OK with Administrator rights
4. Report what's happend
Kind rergards
which Windows version do you use? I've never seen this on a Win7 to Win10 system.
It my be a rights conflict with Midi-OX.
1. Disable all THIRD-party Virusscanners and friends
2. Load down MIDI-OX from its homepage
3. Reinstall MIDI-OK with Administrator rights
4. Report what's happend
Kind rergards
Hi BigD,
This may sound (and is) weird, but after I reinstalled the "InstallShield 2010" software everything is working fine.
I uninstalled "InstallShield 2010" to confirm this and the issue returned. This is indeed very strange.
So, I ended up installing "InstallShield 2010" so I can avoid this issue altogether...
I have no idea why the DEQ2496Control program would cause the Windows Installer to open.
I just hope you might find the information helpful in some way.
Best,
David
This may sound (and is) weird, but after I reinstalled the "InstallShield 2010" software everything is working fine.
I uninstalled "InstallShield 2010" to confirm this and the issue returned. This is indeed very strange.
So, I ended up installing "InstallShield 2010" so I can avoid this issue altogether...
I have no idea why the DEQ2496Control program would cause the Windows Installer to open.
I just hope you might find the information helpful in some way.
Best,
David
Hi BigD,
Ok, so I found the culprit in the windows the registry...
I removed this key [HKEY_CLASSES_ROOT\Installer\Products\5B523C89ED7855F4D8992C22BD8B0CE2] and all is well.
Sorry for bothering you with this mess. I didn't mean to waste any of your time.
Best Regards,
David
Ok, so I found the culprit in the windows the registry...
I removed this key [HKEY_CLASSES_ROOT\Installer\Products\5B523C89ED7855F4D8992C22BD8B0CE2] and all is well.
Sorry for bothering you with this mess. I didn't mean to waste any of your time.
Best Regards,
David
Hi BigD, greetings from Italy!
Thank you very much for your work. I've downloaded all the pieces and the drivers, but I am encountering a problem with your tool, and I think that the problem's origin is in the communication between your tool and MIDI-OX (remote procedure call failed).
I've included some pictures that should be enough to understand the sequence of events. Basically, a few seconds after the DEQ9624 is connected, both the control tool and MIDI-OX crash, with the message shown in the last picture.
I am running Windows 11 Pro, version 10.0.26100. The DEQ firmware is v3.0.
If you have an idea of how to address this, thank you - I have the DEQ tucked away and your tool would do wonders. Alternatively, if you like, you could share the code. I am no stranger to coding, so I might be able to troubleshoot the issue on my own and help you.
Thank you very much for your work. I've downloaded all the pieces and the drivers, but I am encountering a problem with your tool, and I think that the problem's origin is in the communication between your tool and MIDI-OX (remote procedure call failed).
I've included some pictures that should be enough to understand the sequence of events. Basically, a few seconds after the DEQ9624 is connected, both the control tool and MIDI-OX crash, with the message shown in the last picture.
I am running Windows 11 Pro, version 10.0.26100. The DEQ firmware is v3.0.
If you have an idea of how to address this, thank you - I have the DEQ tucked away and your tool would do wonders. Alternatively, if you like, you could share the code. I am no stranger to coding, so I might be able to troubleshoot the issue on my own and help you.
Attachments
Hi Gemina,
If you run just the MIDI-OX program, does it work properly with the WIDI device?
If not, then try using a different MIDI interface.
If you run just the MIDI-OX program, does it work properly with the WIDI device?
If not, then try using a different MIDI interface.
Hello Gemin,
your problem seems to be the Windows DriverStack. If small SysEx Messages are transfered, everything is working. You can see that your DEQ will be recognized. So the general communication pipe is working DEQ Control > MIDI-OX > MidiInterface.
As Big_Goomba already wrote, for my opinion the Midi-Interface struggles to handle long SysEx Messages.
After recognizing the DEQ (if it's there) I am asking the DEQ2494 to send the complete Editbuffer. This are 378 bytes. The USB-Driver of your MIDI-Interface crashes.
Try this with a Roland Midi-Interface. Some users reported, that this Interface works well with Windows 11.
Kind Regards
BigD
your problem seems to be the Windows DriverStack. If small SysEx Messages are transfered, everything is working. You can see that your DEQ will be recognized. So the general communication pipe is working DEQ Control > MIDI-OX > MidiInterface.
As Big_Goomba already wrote, for my opinion the Midi-Interface struggles to handle long SysEx Messages.
After recognizing the DEQ (if it's there) I am asking the DEQ2494 to send the complete Editbuffer. This are 378 bytes. The USB-Driver of your MIDI-Interface crashes.
Try this with a Roland Midi-Interface. Some users reported, that this Interface works well with Windows 11.
Kind Regards
BigD
That's entirely possible - thank you for your response! Let me try with different interfaces - I might need a cable :/ (WIDI is wireless)
OK, thank you to @Big_Goomba (no, it wasn't the problem, WIDI with MIDI-OX works just fine for short SysEx messages) and @BIgD71 (yes, that was the problem).
It looks like when I use a different interface the tool is able to recognize the DEQ and load the configuration just fine. The crash is quite likely due to the inability of the WIDI interface to handle long SysEx messages.
This is a great step forward, but it's a bit disappointing, because I was hoping to have the DEQ tucked away in the stack while I could control it from my laptop using wireless MIDI, but I suppose one cannot ask for everything 🙂
It looks like when I use a different interface the tool is able to recognize the DEQ and load the configuration just fine. The crash is quite likely due to the inability of the WIDI interface to handle long SysEx messages.
This is a great step forward, but it's a bit disappointing, because I was hoping to have the DEQ tucked away in the stack while I could control it from my laptop using wireless MIDI, but I suppose one cannot ask for everything 🙂
Here is an actual download link:
https://drive.google.com/file/d/14G68GfEAcZielNJEh5bJVxPjtFpJwHZH/view?usp=drive_link
https://drive.google.com/file/d/14G68GfEAcZielNJEh5bJVxPjtFpJwHZH/view?usp=drive_link
Hello maxspl,
please see posts starting from Gemina. He tried to use a WIDI-Interface. His interface was not able to handle long Sys-Ex-Messages.
So it depends on the capability to handle LONG messages (>300 bytes) correctly. A normal Midi-Command has only three bytes.
Kind Regards
please see posts starting from Gemina. He tried to use a WIDI-Interface. His interface was not able to handle long Sys-Ex-Messages.
So it depends on the capability to handle LONG messages (>300 bytes) correctly. A normal Midi-Command has only three bytes.
Kind Regards