1 hour ago, pty1973cm said:

sharing the templates X-Touch mini templates for the app

I don't think that this will work. The MIDI devices are bound to have different numerical IDs on the different computers. The app will be unable to match the template to your actual hardware.

Best regards

22 hours ago, Lorby_SI said:

I don't think that this will work. The MIDI devices are bound to have different numerical IDs on the different computers. The app will be unable to match the template to your actual hardware.

Best regards

Thanks, could you elaborate on this?

Even if a MIDI device would show with a different Device ID on each computer, there must be a commonality between the MIDI events themselves ?

 

 

 

 

 

I have altered my X-Touch Mini values in the X-Touch Editor. So if even if the device ID is the same, the button assignments, channels etc are not. You will need to import those first on your device using the X-Touch editor for them to be the same. And even then, any additional joystick assignments in a profile (all stored in the same config xml file) have unique ID's as well and could be a potential problem if used on another computer.

 

Perhaps it's possible to just export/import the Events and then assign them on your own controller?

Edited October 21, 20205 yr by pulstar
question added.

1 hour ago, pty1973cm said:

there must be a commonality between the MIDI events themselves

Not really. Using the driver software of the manufacturer or a MIDI mixer software inbetween, you can assign any MIDI event to any encoder on the device - they aren't fixed. 

To make a setup "portable",

1. the driver software needs some kind of import/export functionality that can work across computers. I don't know if that is the case with Behringer, I think that it might work with Novation Automap though.

2. In P4AO I would have to implement a MIDI template import/export feature too, and that must include an additional step so the user can change the MIDI device ID in the process.

I don't know if step 1. is technologically possible, but if it is, then 2. is relatively simple to make. But it can only work for MIDI devices, it doesn't make much sense for all the other controller options. So it didn't seem worth the effort at the time.

 

 

15 hours ago, pulstar said:

I have altered my X-Touch Mini values in the X-Touch Editor. So if even if the device ID is the same, the button assignments, channels etc are not. You will need to import those first on your device using the X-Touch editor for them to be the same. And even then, any additional joystick assignments in a profile (all stored in the same config xml file) have unique ID's as well and could be a potential problem if used on another computer.

 

Perhaps it's possible to just export/import the Events and then assign them on your own controller?

That's true and I have customized it as well, but that is a different thing - and an easy one to work with because the XTouch utility allows import/export.

 

Quote

MIDI mixer software inbetween, you can assign any MIDI event to any encoder on the device - they aren't fixed. 

Interesting! I know nothing about this so for science, I compared the Xtouch mini MIDI output of the same actions with my laptop and my desktop via Midimonitor.com (results @ end of post) and indeed they came out different. This was suprising to me because the Xtouch utility template appears to be made so that you can standardize the configuration (?).

I cannot imagine being on the music business and buying a controller where every customer needs to reprogram the whole thing... i guess they can get away with that because all musicians are all trying to be unique? : P

But i digress...

Quote

In P4AO I would have to implement a MIDI template import/export feature too, and that must include an additional step so the user can change the MIDI device ID in the process.

if I dare suggesting : D 

One thing that makes a good app great is great defaults, or in this case an easy way to set them up.

The app could have a guided process where you are prompted one by one the entries present in a pre-made template and a new user would just rotate/push his way through it. Like those speech recognition training wizards.

The cherry on top would be a great generic printable template ?

 

------------------------------

 

Timestamp	Device	Type	Data	Channel
09:26 43:586	X-TOUCH MINI	Note On	Note #16 Velocity 127	11
09:26 42:625	X-TOUCH MINI	Note On	Note #8 Velocity 127	11
09:26 40:787	X-TOUCH MINI	Control Change	CC#0 Value 0	11
09:26 40:227	X-TOUCH MINI	Control Change	CC#0 Value 1	11

Timestamp	Device	Type	Data	Channel
09:30 31:561	X-TOUCH MINI	Note Off	Note #16 Velocity 0	11
09:30 30:859	X-TOUCH MINI	Note Off	Note #8 Velocity 0	11
09:30 25:428	X-TOUCH MINI	Control Change	CC#0 Value 1	11
09:30 20:438	X-TOUCH MINI	Control Change	CC#0 Value 2	11

 

20 minutes ago, pty1973cm said:

if I dare suggesting : D 

One thing that makes a good app great is great defaults, or in this case an easy way to set them up.

The app could have a guided process where you are prompted one by one the entries present in a pre-made template and a new user would just rotate/push his way through it. Like those speech recognition training wizards.

The cherry on top would be a great generic printable template ?

I'm sorry, but AxisAndOhs will not be expanded to contain default templates or "guided processes" for hundreds of different controllers, taylored for hundreds of different aircraft in six different simulators. That just isn't possible. 

The example in this thread is just one of the dozens of possible configurations for the X-Touch as a flightsim controller - it hardly represents a "default". And the X-Touch is but one of many controllers. Personally, I don't even have an X-Touch. I only use Native Instruments, Ableton, Roland and Novation hardware.

Best regards

57 minutes ago, Lorby_SI said:

I'm sorry, but AxisAndOhs will not be expanded to contain default templates or "guided processes" for hundreds of different controllers, taylored for hundreds of different aircraft in six different simulators. That just isn't possible. 

I do not agree that a guided setup "just isn't possible" but thanks for the direct response. Mine was just a suggestion, it doesn't even apply to my anymore because I already went through the pain of learning and configuring (until I suppose, I need to move to a new PC).

On 10/22/2020 at 5:25 PM, pty1973cm said:

I do not agree that a guided setup "just isn't possible" but thanks for the direct response. Mine was just a suggestion, it doesn't even apply to my anymore because I already went through the pain of learning and configuring (until I suppose, I need to move to a new PC).

The new version 1.74 has an option now to export and import entire templates. When importing a template, you will be asked to reassign each controller input (Axis, Buttons) to your own hardware. This import also includes the required RPN scripts. Naturally, that will only work if your hardware setup is largely similar (= no point in importing a template that contains an X-Touch controller when you don't have one)

But you still need someone to create the template in the first place - and who is willing to share it. 

Best regards

Edited October 26, 20205 yr by Lorby_SI

5 hours ago, Lorby_SI said:

The new version 1.74 has an option now to export and import entire templates. When importing a template, you will be asked to reassign each controller input (Axis, Buttons) to your own hardware. This import also includes the required RPN scripts. Naturally, that will only work if your hardware setup is largely similar (= no point in importing a template that contains an X-Touch controller when you don't have one)

But you still need someone to create the template in the first place - and who is willing to share it. 

Best regards

Oh, wow, thanks for this!

I just ran through the Import Template "wizard" using this template and respective X-Touch Mini Layer A bin file and these button positions.

1. When "saving" each of the assignment prompts... should they start appearing on the Assigned Buttons column immediately or at the end?

2. I ask #1 above because I finished all assignments and I ended up with an empty list. : / I did it twice with same result.

3. Some UI element (i.e, Key Down Event drop down in particular) don't seem to scale horizontally when resizing the prompt window, the problem with this is that the fixed width of the dropdown crops the full description of the event which makes it more difficult to understand each prompt.

4. The size of the assignment prompt window resets after each prompt : P

Anyway, thanks again for taking care of this!

Edited October 26, 20205 yr by pty1973cm

#1, #2: they don't show up at all in the buttons list. This feature is importing a template, not a profile. After importing it, the template is saved to your database permanently, and you can assign it to any aircraft using the menu.

#3, #4 AAO windows are not supposed to be resizable at all. That you can resize it is the actual bug. It would probably be a good idea on part of the creator of a template to use custom labels for description purposes. How long are those event IDs that they don't fit into the box?

Best regards 

Edited October 27, 20205 yr by Lorby_SI

8 hours ago, Lorby_SI said:

#1, #2: they don't show up at all in the buttons list. This feature is importing a template, not a profile. After importing it, the template is saved to your database permanently, and you can assign it to any aircraft using the menu.

#3, #4 AAO windows are not supposed to be resizable at all. That you can resize it is the actual bug. It would probably be a good idea on part of the creator of a template to use custom labels for description purposes. How long are those event IDs that they don't fit into the box?

Best regards 

Thanks, I figured that the feature imports templates and not actual A/C config after I already shut down my PC. BTW, this is also useful if you want to reorganize buttons and encoders on an existing template.

About the Event Template drop-down horizontal size, I renamed only a few most are default.

I think that even renaming the events will probably result in some truncated descriptions because they are concatenated; many descriptions are verbose (which is a good thing). 

If you're familiar with the events it doesn't matter as much, but a newcomer or when importing somebody else's template this will be significant.

 

Another thing:

When following the template events during import, sometimes the encoders and buttons do not seem to show the MIDI actions for a random short while, sometimes it shows a different event and immediately changes to the right one on subsequent trigger.

I could almost swear this happens more on the template import than when configuring single events.

I know that it is not the controller because this is my second (i returned the first one) and because this doesn't seem to happen when I am actually flying/using; buttons and encoders trigger pretty much flawlessly.

 

 

 

Edited October 27, 20205 yr by pty1973cm

8 minutes ago, pty1973cm said:

If you're familiar with the events it doesn't matter as much, but a newcomer or when importing somebody else's template this will be significant.

I think that especially with the MIDI devices it would be ideal if the creator of the template uses the button name/position as custom labels for the assignments - so you know which one you are supposed to move.

The custom labels are simple textboxes, and you should be able to scroll inside them.

Best regards

On 10/26/2020 at 1:04 PM, Lorby_SI said:

The new version 1.74 has an option now to export and import entire templates. When importing a template, you will be asked to reassign each controller input (Axis, Buttons) to your own hardware. This import also includes the required RPN scripts. Naturally, that will only work if your hardware setup is largely similar (= no point in importing a template that contains an X-Touch controller when you don't have one)

But you still need someone to create the template in the first place - and who is willing to share it. 

Best regards

Many thanks for this, I was able to use the export/import function without issues, this is awesome to move settings between different Sims even on the same PC! (MFSFS -> P3D).

 

Version 1.75 has been uploaded to the shops now. This version brings MIDI Out, so you can access the LEDs on the MIDI controllers too and sync them with the state of simulator variables.

Best regards