• Welcome to ADA Depot - A Forum To Support Users of ADA Amplification Gear.
 

ADA MP-1 Digital Modification

Started by GuitarBuilder, December 30, 2013, 11:09:57 AM

Previous topic - Next topic

Griphook

I reached the 1000 rows of code :banana-rock:

Only a little bit of Layouting and Designing and the Editor is ready to go  :)

Implemented are the MP-1 and the MP-1 Classic. Did not manage to test with the Classic, but the file structure is correct(Maybe I have to adjust the Commands)

Here is a little Sneak-Peak of the Layout.

MarshallJMP

Looks great, I have a classic,so if you want me to test it out for you, just let me know.

vansinn

Quote from: Griphook on July 25, 2016, 03:36:31 PM
I reached the 1000 rows of code :banana-rock:

So, another 9000 lines to go, and it you find only one error in those 10.000 lines, your code may be classified as man-rated - meaning that a astronaut's life may depend on it.
With all the bugs normally found in software, ADA users must require rigid programming!

Cool work, guyz!

Griphook

As far as I tested(normally after each completed Method ::) ) I removed all Bugs and I hope there will be none, when I give it to you.

At least on the weekend I will release the first Version. Then I'm not available for a week (Wacken  :metal: )

Griphook

Soe Here it is.. Finally! :wave: :banana:

The first (I hope so) stable version of the ADA-Editor.
Currently Implemented Devices are the MP-1 and MP-1 Classic, because those were the only Devices we managed to figure out completely. Others will definetely follow.

It is a Windows-Application
.Net Framework 4.5.2 is required
x64 or x86 should work both

So just unzip the .exe and try it out.

You will be able to save and open SysEx-Files. The saved SysEx Files can be transferred via some other MIDI-program like "Bome SendSX" or "MIDI-OX"

Tell me, what you think :thumb-up: :)

MarshallJMP

How do you select your midi device?

Griphook

I deactivated that, because it produces a Fatal Error on Close, which I cant fix atm...
So i just deactivated the MIDI-relevant Controls

MarshallJMP

Nothing seems to happen here,so normally if you change let's the od1 ,the mp-1 should react correct,or do you first have to make a setting and send it?

Griphook

#143
You first make your setting, then save it as sysEx-File.
Send this SysEx-File with Bome SendSX or similar.

But now it seems, that the Checksum is not calculated properly, if it is higher than 80h

rnolan

Hey Griphook, great work my friend  :thumb-up: , you are getting there and is very much appreciated  :wave: . Hopefully MikeB can try it out and see how it goes as he has MP1.  I'll have to wait for the MP2 and MB1 versions.
Studio Rig: Stuff; Live Rig: More Stuff; Guitars: A few

MarshallJMP

So there's no midi connection, it just makes a sysex file correct?

Griphook

Thank you R :)

Yeah, thats correct, MJ

The MIDI-Connection throws fatalErrors. And I did not write the classes and libraries of that MIDI-DLL, so it is very difficult for me to troubleshoot that :/

I also found the Issue with the non-correct loading. The Parameters are just set to the wrong position... I have not tried it that far  :facepalm: ::)

Griphook

#147
Here is another Try

I now totally disabled the MIDI-Controls(not visible anymore).

The Data should now be in the correct order and therefore working :)


Don't mind the Value written into the TextBox on the left after each open/save Process. This was just a test for the calculated checksum.

Next things will be:

       
  • Correct Display Value for Presence-Control
  • Default Value for the Tone-Controls set to 0db



Until this point, are there anything that bothers you? Have I forgotten something?

vansinn

#148
I get an exception every time I try to select any of the Devices.

Unhandled exception has occurred in you application.
...
InvalidArgument=Value of '0' is not valid for 'SelecedIndex
Parameter neme: SelectedIndex.


There's of course the usual details box with lots more info; haven't checked where this might be written to a text file on disk - if it does,
and screen shots of such aren't too helpful as the Details scroll box cannot be enlarged.

System is Windows 7 Pro, English, SP1, with all updates and .NET updated to 4.5.2.
The only thing I forgot was to reboot, hwich I only realized now that I've written all of this ;)
System or [manual off-line] install process didn't suggest reboot, but hey, it's windblows, so guess I should've done that.. :facepalm: :lol:

EDIT: After dismissing the exception, I can set any of the other parameters.
However, when saving as a SysEx, I get:

Error: Could not save to disk. Original reference not set to an instance of an object.


Aaaaannnd.. I'll now go do the reboot...

EDIT2: Rebooted, no change..

MarshallJMP

Will try the new version tomorrow.