Why Are All Multiprocessing Options The Same Across Programs?

[abcoin]

I got a pair of the new stereo headphones this week. While I haven't gotten out with them yet, I noticed something weird.

In the expert menu for each multiprocessing option, the settings on channel 1 don't reflect the specific program you're in. For example, my favorite program is Sensitive Full Tones, but none of the multiprocessing options under that program include full tones (Morph 1's default is two tones, Morph 2 has three, etc). The same is true in Fast and all the other programs that have the multiprocessing options.

It seems that XP should've either:

1) Customized the settings on channel 1 to mirror those of each program that offers multiprocessing, or

2) Added the four multiprocessing options to the Deus 2 as four new programs 

Has anyone else encountered this? I've already seen videos where, for example, people seem to think that they are testing Morph 1 in the "Fast" program when they're just testing Morph 1 (the program doesn't matter, Morph 1 is Morph 1 regardless).

I've already saved a custom program with the settings from Sensitive Full Tones on channel 1 and all metal mode on channel 2. Just odd that XP didn't include that to start.

[Chase Goldman]

3 hours ago, abcoin said:

I got a pair of the new stereo headphones this week. While I haven't gotten out with them yet, I noticed something weird.

In the expert menu for each multiprocessing option, the settings on channel 1 don't reflect the specific program you're in. For example, my favorite program is Sensitive Full Tones, but none of the multiprocessing options under that program include full tones (Morph 1's default is two tones, Morph 2 has three, etc). The same is true in Fast and all the other programs that have the multiprocessing options.

It seems that XP should've either:

1) Customized the settings on channel 1 to mirror those of each program that offers multiprocessing, or

2) Added the four multiprocessing options to the Deus 2 as four new programs 

Has anyone else encountered this? I've already seen videos where, for example, people seem to think that they are testing Morph 1 in the "Fast" program when they're just testing Morph 1 (the program doesn't matter, Morph 1 is Morph 1 regardless).

I've already saved a custom program with the settings from Sensitive Full Tones on channel 1 and all metal mode on channel 2. Just odd that XP didn't include that to start.

I understand your point.  I think XP could have approached the Multiprocessing presets the way you described (i.e., tailored to emulate the base program presets) but I think they opted for "simplicity" by making the presets for the four Multiprocessing default programs (Morph1, Morph2, Dual Rx, and Dual Axis) the same across the board.  Probably easier to implement from a software standpoint and also from a Manual description standpoint.  You would probably end up having to save a custom program anyway  if you futz with either the main or the Multiprocessing defaults.  I rarely ever use a Factory Program as-is, so I am saving a custom program regardless.  I agree with you that people should not be fooling themselves into thinking they are still running the base program if they apply any of the  Multiprocessing presets.

I just think of the Multiprocessing preset as a more sophisticated user mod to the base program, like other user selectable changes (disc, tones, sensitivity, reactivity, etc.) but on steroids depending which of the four processes you want to apply (Morph 1, 2, Dual Rx, Dual Axis).  Yes there are some underlying parameters that give each program it's unique DNA that are modified by the Multiprocessing presets, but there are also underlying processes unique to the base program in terms of FMF processing (that XP refers to as platforms) that are unaffected by Multiprocessing.  In other words even without Multiprocessing you can set up any Program based on the Sensitive Program 2 platform (i.e., Programs 3, and 4 and possibly even Programs 5 and 6) to be identical by cloning the identical user selectable parameters such as Disc, Sens, Reactivity, etc.) across those programs.  But base programs that are not built on the same platform will be behave differently (i.e., Programs 1 and 2 because they handle ground feedback differently) even if set up with the identical user parameter settings.  This also goes for the Beach/Dive programs which behave differently than the "terrestrial" programs because they also manage salt sensitivity, etc.  Bottom line if you set up Morph1 on the General Program and Morph1 on the Sensitive Program then they will behave differently.  But if you set up Morph1 on the Sensitive Program and on the Morph1 on the Fast Program, they may behave the same based on the way Morph1 sets up the Ch 1 parameters identically between the two programs.  Hope this makes sense.  Another way to look at it is that there may be more than one way to get to the same place with Multiprocessing even if you start with different base programs.  That is why is more important than ever to fully understand what the individual program parameters (i.e., Disc, Sens, Reactivity, etc) actually do rather than just blindly taking someone else's program (e.g., Tekkna or Jethro) and applying it.  The "custom" programs that are going to be posted out there with the Multiprocessing sub programs (i.e., Morph, Dual Rx, Dual Axis, etc) are going to really confuse those that don't understand the reason for the settings within custom programs like Tekkna.

[abcoin]

2 hours ago, Chase Goldman said:

Probably easier to implement from a software standpoint and also from a Manual description standpoint.

True. I wonder if they meant to tailor the multiprocessing options to each program but decided not to. Could be a great thing for a future update (hint hint, XP).

2 hours ago, Chase Goldman said:

I rarely ever use a Factory Program as-is, so I am saving a custom program regardless.

Me neither, but I do know that I like Sensitive Full Tones as a base program and would've loved to have all of those settings ready to go in dual axis or dual reactivity.

2 hours ago, Chase Goldman said:

That is why is more important than ever to fully understand what the individual program parameters (i.e., Disc, Sens, Reactivity, etc) actually do rather than just blindly taking someone else's program

Man, you are right about that. I hate to think about all the custom multiprocessing setups that some people are going to be throwing around.

I'm starting slow with dual axis and dual reactivity since those seem to be the easiest use cases to imagine for me. I put together Sensitive FT and one of the all metal options in a custom program for audio definition on shallow/mid-depth targets while simultaneously hitting on deeper stuff with AM. 

Still trying to just wrap my head around what sort of conditions the Morph options are best for.

[broadfield]

3 hours ago, Chase Goldman said:

I understand your point.  I think XP could have approached the Multiprocessing presets the way you described (i.e., tailored to emulate the base program presets) but I think they opted for "simplicity" by making the presets for the four Multiprocessing default programs (Morph1, Morph2, Dual Rx, and Dual Axis) the same across the board.  Probably easier to implement from a software standpoint and also from a Manual description standpoint.  You would probably end up having to save a custom program anyway  if you futz with either the main or the Multiprocessing defaults.  I rarely ever use a Factory Program as-is, so I am saving a custom program regardless.  I agree with you that people should not be fooling themselves into thinking they are still running the base program if they apply any of the  Multiprocessing presets.

I just think of the Multiprocessing preset as a more sophisticated user mod to the base program, like other user selectable changes (disc, tones, sensitivity, reactivity, etc.) but on steroids depending which of the four processes you want to apply (Morph 1, 2, Dual Rx, Dual Axis).  Yes there are some underlying parameters that give each program it's unique DNA that are modified by the Multiprocessing presets, but there are also underlying processes unique to the base program in terms of FMF processing (that XP refers to as platforms) that are unaffected by Multiprocessing.  In other words even without Multiprocessing you can set up any Program based on the Sensitive Program 2 platform (i.e., Programs 3, and 4 and possibly even Programs 5 and 6) to be identical by cloning the identical user selectable parameters such as Disc, Sens, Reactivity, etc.) across those programs.  But base programs that are not built on the same platform will be behave differently (i.e., Programs 1 and 2 because they handle ground feedback differently) even if set up with the identical user parameter settings.  This also goes for the Beach/Dive programs which behave differently than the "terrestrial" programs because they also manage salt sensitivity, etc.  Bottom line if you set up Morph1 on the General Program and Morph1 on the Sensitive Program then they will behave differently.  But if you set up Morph1 on the Sensitive Program and on the Morph1 on the Fast Program, they may behave the same based on the way Morph1 sets up the Ch 1 parameters identically between the two programs.  Hope this makes sense.  Another way to look at it is that there may be more than one way to get to the same place with Multiprocessing even if you start with different base programs.  That is why is more important than ever to fully understand what the individual program parameters (i.e., Disc, Sens, Reactivity, etc) actually do rather than just blindly taking someone else's program (e.g., Tekkna or Jethro) and applying it.  The "custom" programs that are going to be posted out there with the Multiprocessing sub programs (i.e., Morph, Dual Rx, Dual Axis, etc) are going to really confuse those that don't understand the reason for the settings within custom programs like Tekkna.

Bear in mind that program 3 uses a different silencer to any other land program, so when the manual says it's based off program 2 that's not 100% correct.

[broadfield]

7 hours ago, abcoin said:

I got a pair of the new stereo headphones this week. While I haven't gotten out with them yet, I noticed something weird.

In the expert menu for each multiprocessing option, the settings on channel 1 don't reflect the specific program you're in. For example, my favorite program is Sensitive Full Tones, but none of the multiprocessing options under that program include full tones (Morph 1's default is two tones, Morph 2 has three, etc). The same is true in Fast and all the other programs that have the multiprocessing options.

It seems that XP should've either:

1) Customized the settings on channel 1 to mirror those of each program that offers multiprocessing, or

2) Added the four multiprocessing options to the Deus 2 as four new programs 

Has anyone else encountered this? I've already seen videos where, for example, people seem to think that they are testing Morph 1 in the "Fast" program when they're just testing Morph 1 (the program doesn't matter, Morph 1 is Morph 1 regardless).

I've already saved a custom program with the settings from Sensitive Full Tones on channel 1 and all metal mode on channel 2. Just odd that XP didn't include that to start.

 

The preset morphing options are like preset programs within preset programs.

Save your desired factory base program as a custom and a user morph will appear with channel 1 having all the settings

[Chase Goldman]

23 minutes ago, broadfield said:

Bear in mind that program 3 uses a different silencer to any other land program, so when the manual says it's based off program 2 that's not 100% correct.

Yep.  I know about that gotcha, was trying to keep it simple conceptually.  But thanks for the reminder.

[abcoin]

26 minutes ago, broadfield said:

The preset morphing options are like preset programs within preset programs.

Save your desired factory base program as a custom and a user morph will appear with channel 1 having all the settings

Right, that's what I ended up doing. My point was just that it's sort of a clunky way to do things as opposed to XP simply carrying over each batch of preset program settings to channel 1 on each of the multiprocessing options.