Version 1.8 Serial Port support questions - Bome Forums Archive 2005

ibanman555

2015-10-07 00:32:35

Hey! Loving the addition of serial support in the new version, this helps me get a lot of my controllers working with direct connection to the PC! I've been experimenting now with just 1 controller, but I'm stumped in a few things.

First, I have an 8 port serial card installed in my PC and it's functional. These are RS232 ports that all my controllers terminate to. I set up COM 10 in MTP with the proper baud rate to match my controller and enabled that COM 10 be used as a midi device. Any activity on my controller shows up in the event window under MIDI IN. Cool!!!

Now I assigned some translations to my music software via "BMT1". Moving faders and pushing buttons translate to my music software! Now, I send the programs midi back out to MTP via "BMT2", translated back, and then back to the controller via COM 10... But there's no activity. I captured midi coming back from my software and it's sending the right messages back to MTP, just not back to the COM 10 port... I can see that MTP isn't showing Midi Out activity in the event window either.

I've used this exact same MTP file/preset before with Hairless MIDI to serial as the converter successfully... But I'm stumped here. Any thoughts?? Thanks!!!

DvlsAdvct

2015-10-07 16:07:41

Hi ibanman555

I'm going to pass this up to Florian, so he can troubleshoot and make sure whether or not this is a bug. You should hear from him soon.

Thanks
Jared

ibanman555

2015-10-07 21:03:30

Thank you. I tested with virtual midi ports from LoopBe30 and getting the same result. I will check again with Hairless as well to make sure I'm not missing something serial related in BMT.

florian

2015-10-07 21:54:33

Hi, not sure what's going on! I doubt it's a problem with the virtual ports. You should use the Log Window and verify that the MIDI data is received from your music software (btw. you can also use BMT 1 for that). Make sure in the MIDI setup that the virtual INPUT port is marked OPEN. You should see MIDI IN activity from the program in the Log Window.
Then next step is to verify that your translators trigger on the received MIDI data. The Log Window will tell you if they do.
Last, but not least, is to verify that MIDI data is sent out the serial port. Make sure that the serial OUT port is marked OPEN.

Makes sense?
Thanks,
Florian

ibanman555

2015-10-08 01:52:15

OK... So my music software is indeed receiving midi data from my controller:

Controller > COM 10 > BMT1> Music Software

In the Translator for the above, the incoming COM 10 port (set up as a midi device) is 'open', Midi In (event monitor) is showing activity, translating, then sending to the music software via outgoing BMT1 virtual port, which is also 'open', Midi Out (event monitor) is showing activity. My music software is responding to my controller movements as it should (Note: the 'Midi In' light is showing activity (event monitor) when I touch my controller, I assume is because I assigned COM 10 as a Midi Device.)

Music Software >BMT2>COM 10>Controller

Now going backwards, there is a separate Translator for that. However BMT2 is receiving the data from the music software because I like to have a dedicated virtual midi port to send data in one direction, instead of using one virtual midi port bidirectional. Now I can see the proper data from BMT2 is coming into MTP, but from there it stops. Both BMT2 and COM 10 are are 'open for incoming and outgoing in this Translator. No Midi Out or Serial Out data in the event monitor.

In your last message you say "Make sure that the serial OUT port is marked OPEN", are you referring to my COM 10 port in the outgoing portion of my second Translator back to the controller, or is there a dedicated section where I do this? I can't seem to get either serial IN or OUT to show any activity in the event monitor. If I do not select COM 10 as "use this port as midi device" in its configuration settings, it shows up as 'pending' in any incoming and outgoing windows of any Translator.

florian

2015-10-08 10:22:02

Hi,
please start using the "Log Window" (from the View menu). It will tell you in a much more detailed way what's going on.

I have a hunch that your incoming action in the translator is not correctly defined, so it will never trigger on MIDI data from your application.

If you mark a serial port as "use as MIDI device", then you'll get virtual MIDI IN and OUT devices inside MIDI Translator Pro. That makes sense if a device is sending MIDI data over a serial port. If not, you don't need to activate this.

There is a global serial port list in the Settings, but the list of serial ports is the same in the incoming/outgoing serial translator sections.

I believe that you're using MIDI incoming and outgoing messages for your serial port. But look again into the translator definitions: instead of type "MIDI" you can select type "serial port" there:

That's the more straight forward way to deal with serial ports. Then, also the "LEDs" in the event monitor should light up on receiving/sending serial port data.

Please copy/paste your preset here: in MT, you can select all presets and use the Copy function, then paste into the forum. It works.
Also, please post the output in the Log Window for data going application -> BMT2 -> COM 10.

Thanks!
Florian

PS: I can assure you, you can use BMT1 for the way from application to MT, too. MT's virtual ports are not loopback ports like LoopBE, but direct connections from MT into the other applications and vice versa. There is a section in the user's manual about that, too...

ibanman555

2015-10-09 01:24:55

This is the Controller to Pro Tools translator for a CH 1 Mute Button Press:

Code: Select all

[x] Translator 1.4: Mute Press Ch1
Incoming: Serial: 0xB0 0x46 0x7F from Mixer 1
Outgoing: MIDI B0 0F 00 B0 2F 42, to port Bome MIDI Translator 1 Virtual Out

Here is the the Pro Tools to Controller translator for a CH 1 Mute Button Press:

Code: Select all

[x] Translator 2.0: Mute Press On Ch 1 (2)
Options: swallow
Incoming: MIDI B0 0C 00 B0 2C 02, on port Bome MIDI Translator 1 Virtual In
Outgoing: Serial: 0xB0 0x46 0x00 to Mixer 1

[x] Translator 2.1: Mute Press On Ch 1 (3)
Options: swallow
Incoming: MIDI B0 0C 00 B0 2C 42, on port Bome MIDI Translator 1 Virtual In
Outgoing: Serial: 0xB0 0x46 0x7F to Mixer 1

Right now, set up like it is, the mute button press on my controller is sending to Pro Tools CH 1 mute button, toggling it on and off as it should. Here is the log of me pressing that button 6 times:

Code: Select all

1: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
2: OUT  2.1  Serial: B0 46 7F to COM10 [Mixer 1]
3: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
4: OUT  2.0  Serial: B0 46 00 to COM10 [Mixer 1]
5: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
6: OUT  2.1  Serial: B0 46 7F to COM10 [Mixer 1]
7: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
8: OUT  2.0  Serial: B0 46 00 to COM10 [Mixer 1]
9: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
10: OUT  2.1  Serial: B0 46 7F to COM10 [Mixer 1]
11: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
12: OUT  2.0  Serial: B0 46 00 to COM10 [Mixer 1]

Here is the log of me pressing the mute button 6 times in the Pro Tools software itself:

Code: Select all

1: OUT  2.1  Serial: B0 46 7F to COM10 [Mixer 1]
2: OUT  2.0  Serial: B0 46 00 to COM10 [Mixer 1]
3: OUT  2.1  Serial: B0 46 7F to COM10 [Mixer 1]
4: OUT  2.0  Serial: B0 46 00 to COM10 [Mixer 1]
5: OUT  2.1  Serial: B0 46 7F to COM10 [Mixer 1]
6: OUT  2.0  Serial: B0 46 00 to COM10 [Mixer 1]

I've set this up stricty as serial in and serial out but have tried with and without 'use this serial port as a midi device' selected. Again, a controller button press is sending the data to Pro Tools, and activating the mute button there, as it should. I am seeing 'Serial In' led active in the event monitor when I press that controller button. I am not getting data back to the controller from Pro Tools even though all the data is being sent properly, based on the log window data. The "Serial Out" led is not blinking in the event monitor, which tells me it's not actually sending back to the COM 10 port. I don't know why....

Attachments

: serial ports; serial ports.PNG (87.59 KiB) Viewed 15307 times

: PT to Controller; Pro Tools to Controller screen shot.PNG (137.03 KiB) Viewed 15307 times

: Controller to PT; Controller to Pro Tools screen shot.PNG (139.63 KiB) Viewed 15307 times

florian

2015-10-09 15:29:44

Hi,
makes sense!

I wasn't aware that your mixer controllers send MIDI over serial port! What kind of device is that? could be interesting for other MIDI Translator users! And it would also make sense to use the "use as MIDI device" function. Then you don't need to deal with hex codes, but can use the "Simple MIDI" options in the MIDI type selector box.

If you enable the "Incoming" checkbox in the Log Window, you'll get a more complete picture of what's happening.

I've noticed that for some reason, pressing the button on your controller will trigger the "MIDI to serial" translator 1.4, but also translator 2.1, feeding serial port data back to the controller. Maybe Pro Tools is echoing all MIDI data?
Also enable MIDI IN and MIDI OUT in the log window to better see that.

I've done a quick test: the Serial Out LED works fine for me. If the port is not properly opened so that only input works, I guess the LED will not light up. But in MT, serial ports are always opened input and output at the same time. Not sure what's going on there. Maybe, after all, the serial port data is sent to the controller, but it could be the wrong message?

Thanks,
Florian

ibanman555

2015-10-09 16:25:11

These are JL Cooper ES 8/400 mixers, the RS232 version. This button press sends B0 46 7F when pressed, and expects the same message back to turn the light on for that button. B0 46 00 is sent to the controller to turn that same light off. So the messages are correct, as I mentioned this entire MTP file was used before (the old version) successfully.

Your correct that it's 'echoing' data. When I push mute on my controller, it sends the data to turn mute on in Pro Tools. Then Pro Tools sends mute on (B0 46 7F) back to the controller to turn the corresponding light on. If I push mute again on my controller, it turns mute off in Pro Tools, and Pro Tools sends mute off (B0 46 00) back to the controller to turn the light off.

I'll do a log of the complete process, in and out as soon as possible and post it here. Worst case I can send you my MTP file to have a look.... I'm stumped why it's not sending serial out as well.

ibanman555

2015-10-09 17:35:32

Here is a log of pressing the mute button twice on my controller. This turns mute on and off in Pro Tools. Still not getting any response (light on or off) on the controller for the corresponding button:

Code: Select all

138095997 - IN   1.4  Serial Port: B0 46 7F from COM10 [Mixer 1]
138095997 - MIDI OUT [Bome MIDI Translator 1 Virtual Out]: B0 0F 00 B0 2F 42
138095997 - OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
138095997 - MIDI IN [COM10]: B0 46 7F
138096000 - MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 0C 00
138096000 - MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 2C 42
138096000 - IN   2.1  MIDI 6 bytes B0 0C 00 B0 2C 42
138096006 - OUT  2.1  Serial: B0 46 7F to COM10 [Mixer 1]

138098123 - IN   1.4  Serial Port: B0 46 7F from COM10 [Mixer 1]
138098123 - MIDI OUT [Bome MIDI Translator 1 Virtual Out]: B0 0F 00 B0 2F 42
138098123 - OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
138098123 - MIDI IN [COM10]: B0 46 7F
138098130 - MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 0C 00
138098130 - MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 2C 02
138098130 - IN   2.0  MIDI 6 bytes B0 0C 00 B0 2C 02
138098137 - OUT  2.0  Serial: B0 46 00 to COM10 [Mixer 1]

I've also sent you my MTP file for your review.

ibanman555

2015-10-09 22:12:55

Update: I just wanted to eliminate error... I am using the RealTerm serial program to send data commands to my controllers, and the controller is responding to my commands sent to it. I wanted to make sure there wasn't a problem with the controllers or Serial ports.

ibanman555

2015-10-09 23:15:21

It's working now and I have no idea why. I tried to back track my steps, and I think this occurred because I assigned global incoming and outgoing for the specific "preset". I didn't even need to assign each specific Translator. I'm also back to strictly using Midi and not serial... I will try to figure out what happened......

ibanman555

2015-10-10 00:15:03

OK sorry for blowing up this topic. I've got another question regarding this project, even tho I've got communication working.

I've gone into the settings window and selected "Serial Ports". In here I select COM 10 and assign it's proper baud rate and select "use this serial port as a midi device" I click OK then double click COM 10 to an "open" state. Then, I create an alias in this window for COM 10. Click OK.

This alias I created does not show up as an option under incoming or outgoing in the Preset Default Midi Ports windows. So I created aliases for incoming and outgoing COM 10s where needed in the incoming and outgoing windows respectively. I save the whole preset/session/program file, and close MTP.

When I reopen MTP the COM 10 settings and alias I created under the settings window (serial ports window) all default or aren't there anymore. The aliases I created under incoming and outgoing are still there, but they, and COM 10 ports are showing "pending". I need to go back and reset everything in the settings window for Serial everytime I restart the program.

Code: Select all

Error(015): MIDI output "COM10" does not exist. It is set to 'pending' so that it is used automatically when you plug it in.
Error(015): MIDI input "COM10" does not exist. It is set to 'pending' so that it is used automatically when you plug it in.

Is this supposed to happen? Are the ports disconnected once you close MTP and need to manually reopen everything serial related?? I'm hoping to be able to start my computer, have MTP launch during startup with my Presets and not have to adjust anything to use my controllers. Thanks very much!

EDIT: I seem to have gone back to the problem at hand... double and triple checked my I/O and ports, all serial ports are "open" and active yet the log is showing me that the port is closed. There is no MIDI or SERIAL out activity in the Event Monitor. Mute button pressed on the controller CH 1 4 times:

Code: Select all

1: MIDI OUT [Bome MIDI Translator 1 Virtual Out]: B0 0F 00 B0 2F 42
2: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
3: MIDI OUT [COM10]: B0 46 7F
4: OUT  5.1  MIDI B0 46 7F [port closed]
5: MIDI OUT [Bome MIDI Translator 1 Virtual Out]: B0 0F 00 B0 2F 42
6: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
7: MIDI OUT [COM10]: B0 46 00
8: OUT  5.0  MIDI B0 46 00 [port closed]
9: MIDI OUT [Bome MIDI Translator 1 Virtual Out]: B0 0F 00 B0 2F 42
10: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
11: MIDI OUT [COM10]: B0 46 7F
12: OUT  5.1  MIDI B0 46 7F [port closed]
13: MIDI OUT [Bome MIDI Translator 1 Virtual Out]: B0 0F 00 B0 2F 42
14: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
15: MIDI OUT [COM10]: B0 46 00
16: OUT  5.0  MIDI B0 46 00 [port closed]

I really don't understand what I'm doing wrong here... it starting working, and quit again...

Attachments

: wtf.PNG (71.3 KiB) Viewed 14566 times

: portclosedwtf.PNG (198.06 KiB) Viewed 14566 times

florian

2015-10-10 10:37:53

hmmm, this setup looks good to me. Strange that it works sometimes, and sometimes it doesn't? Please make sure that no other program is using the serial port when opening it in MT Pro.

You can only create MIDI devices from actual serial ports -- not from serial port aliases. But then you can and should (as you did) create a MIDI alias for the COM10 MIDI port.

I understand that this can be confusing. Once a serial port appears in a MIDI list, it's a mapped MIDI port. So then it's sufficient to deal with this mapped MIDI port: open that MIDI port, and the associated serial port will be opened. Sending, receiving and closing the MIDI port will all be delegated to the associated serial port, too.

Aliases for serial ports, and aliases for MIDI ports, are usually removed on restart, until they re-appear in a project file. The project file also stores which serial port is mapped as a MIDI device. So upon opening your project file, MT Pro should do this:

Map COM10 as MIDI device "COM10" (IN+OUT)
Recreate MIDI IN Alias "Mixer 1"
lookup stored association of MIDI IN "Mixer 1": it is assigned to "COM 10" MIDI IN
open this used MIDI Alias "Mixer 1": it opens MIDI IN "COM 10", which, in turn, opens serial port "COM 10"
do steps 2-4 for the MIDI OUT alias "Mixer 1", too.

This logic should always recreate a working environment when loading your project file. And because MT Pro reloads the last project file, simply starting MT Pro should get you ready to roll!

Please try out what's happening... the Log Window will also list which ports get opened/closed.

Thanks,
Florian

ibanman555

2015-10-11 05:13:34

I've gotten as far as I can right now without dropping dead. I really feel like something is wrong and I'm not sure where the problem lies. I've gotten 1 of my controllers working properly. You will see in the reluctantly attached file that Preset 1 and 3 are for sending and receiving for Mixer #1. The session will now open with my Serial Ports settings still intact, as well as the alias I made for COM 10 in that settings window.

: sp.PNG (102.87 KiB) Viewed 14193 times

***Here is something important that others using serial devices should know***

You Will Not be able to reopen MTP and expect your Serial Port settings seen above to remain with the settings you place for them, or the aliases you make for them without having at least 1 actual serial translation in your Project, as you can see on 1.4
This is the only serial port translation in my whole preset for Mixer 1. All other I/O is set with Preset Default MIDI Ports.

Here is just a look at the log of me pressing Mute Ch 1 two times on Mixer 1. All works well:

Code: Select all

7: MIDI IN [COM10]: B0 46 7F
8: IN   1.4  Serial Port: B0 46 7F from COM10 [Mixer 1]
9: MIDI OUT [Bome MIDI Translator 1 Virtual Out]: B0 0F 00 B0 2F 42
10: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
11: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 0C 00
12: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 2C 42
13: IN   3.1  MIDI 6 bytes B0 0C 00 B0 2C 42
14: MIDI OUT [COM10]: B0 46 7F
15: OUT  3.1  MIDI B0 46 7F

17: MIDI IN [COM10]: B0 46 7F
18: IN   1.4  Serial Port: B0 46 7F from COM10 [Mixer 1]
19: MIDI OUT [Bome MIDI Translator 1 Virtual Out]: B0 0F 00 B0 2F 42
20: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
21: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 0C 00
22: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 2C 02
23: IN   3.0  MIDI 6 bytes B0 0C 00 B0 2C 02
24: MIDI OUT [COM10]: B0 46 00
25: OUT  3.0  MIDI B0 46 00

So now I move on to the next mixer. All I am doing is duplicating each send and receive preset for the second mixer, and changing all of the I/O to BMT2 and COM 8, where my next mixer is connected to. Again, as seen below, both COM 10 and 8 are open each time I restart the program, and all my assignments for the second mixer, presets 2 and 4 are correct and open:

Code: Select all

1: Loaded Project file: C:\Users\Small Dog Production\Desktop\Controller 2015.bmtp
2: Activated preset: Controller - to PT Mixer 1
3: Activated preset: Controller - to PT Mixer 2
4: Activated preset: PT to Controller - Mixer 1
5: Activated preset: PT to Controller - Mixer 2
6: Opened MIDI OUT: Bome MIDI Translator 1 Virtual Out
7: Opened MIDI IN: COM10
8: Opened MIDI OUT: COM10
9: Opened MIDI IN: Bome MIDI Translator 1 Virtual In
10: Opened MIDI OUT: Bome MIDI Translator 2 Virtual Out
11: Opened MIDI IN: COM8
12: Opened MIDI IN: Bome MIDI Translator 2 Virtual In
13: Opened MIDI OUT: COM8

: pc2.PNG (32.54 KiB) Viewed 14193 times

: cp2.PNG (32.09 KiB) Viewed 14193 times

Mixer 1 is still working, but I am having the same problem as before with Mixer 2... all movements on Mixer 2 send to Pro Tools, but I don't get the data back thru the OPEN COM 8 (mute CH 1, mixer 2, pushed twice):

Code: Select all

5: IN   2.4  Serial Port: B0 46 7F from COM8 [Mixer 2]
6: MIDI OUT [Bome MIDI Translator 2 Virtual Out]: B0 0F 00 B0 2F 42
7: OUT  2.4  MIDI 6 bytes B0 0F 00 B0 2F 42
8: IN   4.1  MIDI 6 bytes B0 0C 00 B0 2C 42
9: MIDI OUT [COM8]: B0 46 7F
10: OUT  4.1  MIDI B0 46 7F [port closed]
11: IN   2.4  Serial Port: B0 46 7F from COM8 [Mixer 2]
12: MIDI OUT [Bome MIDI Translator 2 Virtual Out]: B0 0F 00 B0 2F 42
13: OUT  2.4  MIDI 6 bytes B0 0F 00 B0 2F 42
14: IN   4.0  MIDI 6 bytes B0 0C 00 B0 2C 02
15: MIDI OUT [COM8]: B0 46 00
16: OUT  4.0  MIDI B0 46 00 [port closed]

Why in the world am I able to send out of COM 10 but COM 8 reads "port closed"?? It is not being used by any other device or program other than MTP, just like COM 10. I have copied and triple checked all connections and followed the same method of setting everything up. Even during startup says both serial ports are opened!!! Very confused, not sure what to do. Kind of discouraging at this point... I'm sorry

ibanman555

2015-10-11 05:15:10

Here's the file and another photo of COM 8 settings looking ok, that I couldn't attach to the last post:

: com8t.PNG (88.35 KiB) Viewed 14193 times

One button push mixer 1, one button push mixer 2:

Code: Select all

1: IN   1.4  Serial Port: B0 46 7F from COM10 [Mixer 1]
2: MIDI OUT [Bome MIDI Translator 1 Virtual Out]: B0 0F 00 B0 2F 42
3: OUT  1.4  MIDI 6 bytes B0 0F 00 B0 2F 42
4: IN   3.1  MIDI 6 bytes B0 0C 00 B0 2C 42
5: MIDI OUT [COM10]: B0 46 7F
6: OUT  3.1  MIDI B0 46 7F

7: IN   2.4  Serial Port: B0 46 7F from COM8 [Mixer 2]
8: MIDI OUT [Bome MIDI Translator 2 Virtual Out]: B0 0F 00 B0 2F 42
9: OUT  2.4  MIDI 6 bytes B0 0F 00 B0 2F 42
10: IN   4.1  MIDI 6 bytes B0 0C 00 B0 2C 42
11: MIDI OUT [COM8]: B0 46 7F
12: OUT  4.1  MIDI B0 46 7F [port closed]

florian

2015-10-11 15:01:16

Hi ibanman,
thanks for the detailed information. I understand your frustration.

It might be, of course, that MT 1.8.0 has hidden bugs in the serial port support. We have tested thoroughly with many different serial port interfaces, and we have had a few beta testers who mainly tested serial ports for their regular setup. But you never know!

Most intriguing is that it took you a while for you to get COM10 to work, but now COM8 has the same problem? This is definitely not how it is supposed to work!

Also, COM8 is shown being open, but the outgoing action reports [port closed] in the Log Window. Have you tried closing and re-opening COM8? You do that by double-clicking the entry in the port list. Please try that in the MIDI IN and MIDI OUT lists, and also in the serial port setup in the settings screen. Also, please try if restarting MT Pro helps at all.

You also write that you needed to set up a dummy serial port action in the preset for getting COM10 to be correctly set up. This seems like a bug which we will fix. Have you set up the same for COM8?

The more you find out why the ports did not work or how to fix it, the more likely it is for us to be able to fix it.

We'll do everything to get it to work! Thanks for hanging in there!
Florian

ibanman555

2015-10-11 16:00:51

florian wrote: Most intriguing is that it took you a while for you to get COM10 to work, but now COM8 has the same problem? This is definitely not how it is supposed to work! You also write that you needed to set up a dummy serial port action in the preset for getting COM10 to be correctly set up. This seems like a bug which we will fix. Have you set up the same for COM 8?

This dummy serial Translator was the original hang up. Since the serial port setup gave me the option to make it a midi device, I ignored the fact that I would need to do this. So, desperate to at least figure something out, I made 1.4 a true serial Translator and learned that all my settings and aliases remained upon closing and restarting MTP. Because the of this dummy serial Translator, it allowed data to transmit "Serial Out", as far as I can tell, completing the circuit. I copied everything verbatim for Mixer 2, using COM 8 and BMT2 as my I/O. Same setup otherwise, including a dummy serial Translator (2.4) for Mixer 2.

I will go around and 'open' and 'close' all serial ports and aliases again, I've tried that but I'll do all of them. I've also closed and restarted MTP many times trying to debug issues. I am 100% for testing and helping find any bugs or solutions for you, but I really appreciate your responses and help/support during this. Couldn't do it without you! This might end up being a really long thread, and I apologize for talking so much!

EDIT: Just as a side note... I tried to eliminate midi and serial together. By unselecting "use serial as midi device" in setup I am unable to use serial at all. All ports and aliases show 'pending' or 'unplugged'. I wanted to use serial strictly for the controllers, and midi to and from Pro Tools only. Unfortunately as you can see in my project is the faders have pp and qq variables, which can't be used with serial as it can be with midi. Each fader produces a total of 1,024 messages which would be an impossible amount of programming. If I could, I would probably have more luck. Is this possibly a feature that can be added for serial?

florian

2015-10-12 00:55:43

Hi, I'll see if I can reproduce any of your problems somehow.
Meanwhile: you can use variables in the serial actions, too! click on the help text under the serial data field for an example.
Florian

ibanman555

2015-10-12 02:07:10

Thanks, I'll look into the variables for serial... But not that it matters much now.

Fortunately everything is working as it should. I have restarted my computer numerous times during this process, but the last restart relieved me of the [port closed] problem. I can only assume there was some miscommunication between MTP and my serial PCI-E card. All my settings were correct originally and once restarted, everything was doing what it was supposed to. I connected and routed the additional 3 controllers without a problem.

So I apologize for any additional talk that was unnecessary. The problem is obviously on my end. I still believe the bug exists regarding serial setup and having an actual serial action present in a project. I will put my PC, my controllers, MTP and Pro Tools through its paces however, this project is still on probation, meaning I can expect weird issues in the future, but not from MTP. Well done, and thanks for the support.

I will hopefully make a little tutorial on my experience with the new version and my controllers for anyone looking for information and may be attempting a similar project.

EDIT Oct. 14, 2015 - Changing the 'data bits' to 9 or higher in serial port settings on any available COM port causes that port to automatically close, and won't reopen upon double clicking it, even after changing the data bits back to a lower number

florian

2015-10-12 11:39:27

Hi ibanman,
great to hear it's working now! Though, of course, for us you should never need to restart MT, or restart the computer, or insert dummy translator entries, to get it to work! So we'll have a deep look into it nonetheless.

And, of course, a tutorial would be greatly appreciated!
Florian

ibanman555

2015-11-04 23:24:23

Update: MTP has been working relatively well with serial COM Ports at this point with the exception of a few issues we have already discussed. There are a few more issues I wanted to list here in addition to the known issues previously discussed, just to keep track. These are in regards to my serial devices and may not be an issue for others.

-MTP will open up on starting the PC, but I'll not minimize to the task bar afterwards, even after setting the executable file up in the start menu and choosing minimize within it's preferences.

-At least one serial translation (incoming or outgoing) is required in a project preset in order for it's configured serial port and alias to remain after restarting MTP in settings, even after saving.

-Setting a serial ports "data bits" to anything other than 8 causes improper operation. Any value above 8 automatically closes the serial port, and won't reopen until restart. A value of "7" will work and provide different useful data output from the serial device, but once closed and restarted, that port no longer sends data unless "data bits" is changed back to 8, saved, and changed back to 7. I've also gotten different/random serial messages after doing this, which is very bazaar. I've tried matching the settings in Device Manager for the COM Ports, but it appears MTP overrides these settings regardless.

-Massive amounts of data being sent to MTP translates, but will become very slow (latency), taking many seconds to complete in relation to what is being sent to MTP.

-Reading serial data using an external monitor yields different serial data than MTP does. This is specific to one of my serial devices, however.