Fantom outputs

Each of the 16 zones in a scene can be assigned to the various outputs.

ZT Audio has done a very useful video about Sub Outputs:

https://www.youtube.com/watch?v=06N-3gTXGYU

One more question please.
If I connect some signal to input fantom channels I guess that this input signal will be sent to fantom main out. Now if that's true, what happen if I change a main fantom output level by fantom main out knob? Does the signal that is connected to fantom input change with changing of fantom main output or not?

Devnor wrote:

Each of the 16 zones in a scene can be assigned to the various outputs.

OK, it is for the zones, but is possible the sample-pads to assign to different sub-outs?

I wish there were output routing options for each zone when connected to a computer. They seem to be auto locked to zones 1-16 and cannot by cross routed.

Yes, it would be nice! But I still don’t know whether is possible to play the pads through different outputs than the synth-zones...

Vitus wrote:

Devnor wrote:

Each of the 16 zones in a scene can be assigned to the various outputs.

OK, it is for the zones, but is possible the sample-pads to assign to different sub-outs?

I and new to Fantom (7) and I just tried routing a pad zone to sub 1 with no luck. I thought this was supposed to work for backing tracks etc.?

Elara wrote:

I and new to Fantom (7) and I just tried routing a pad zone to sub 1 with no luck. I thought this was supposed to work for backing tracks etc.?

The output routing for sample pads can be changed in EFFECTS EDIT - PAD. All sample pads use the same routing. It is not possible to configure it per pad. You can route pads through MAIN, SUB1 and SUB2. You can also pick INPUT1, INPUT2 and INPUT1/2, which will use the audio paths that are configured for the audio inputs.

Elara wrote:

Vitus wrote:

Devnor wrote:

Each of the 16 zones in a scene can be assigned to the various outputs.

OK, it is for the zones, but is possible the sample-pads to assign to different sub-outs?

I and new to Fantom (7) and I just tried routing a pad zone to sub 1 with no luck. I thought this was supposed to work for backing tracks etc.?

If I remember well, the pad can be placed on a track, via Scene settings, including the mode it will be working on.

Each square in the pad is assigned to a key for it to sound, when in Sample mode, starting from C2 if my memory does not deceive me.

Then that zone can be assigned to different outputs...

But may be that setting works only when using the internal engine, not when the pad is assigned to the zone.

Have a try and see...

I barely remember it because at first I thought I could go programming the pad for each scene, but since it was surprisingly not so, I decided I wouldn't use it much anymore until such aberration became fixed.

Still waiting: such update (fix should I say) would be COOOL.

😀😀😀😀
🎹🎹🎹🎹

Vitus wrote:

I’m thinking of buying a Fantom, have no one at home therefore I would need to know some details.
1) Is possible to the different routing (to subout1, subout2) a scene’s zone and sequencer track?
2) Is possible to the different routing different sampler-pads? For ex. all zones to mainout, sample-pad1 to subout1, sample-pad2 to subout2.
Thanks!

To address your concerns and attempt to keep MagicSpam after the upgrade, you can try the following steps:

Contact the MagicSpam support team: Reach out to the MagicSpam support team directly and inquire about the compatibility of MagicSpam with Debian 11 and Plesk 18.0.48. They will have the most accurate and up-to-date information regarding their software's compatibility.

Verify the MagicSpam version: Check which version of MagicSpam you currently have installed. If it is an outdated version, upgrading to the latest version might resolve any compatibility issues.

Consult with server experts: Discuss the compatibility concerns with the server experts who will be performing the upgrade. Request more specific information about the compatibility issues they have encountered and ask if there are any workarounds or alternative solutions available.

Test the upgrade in a staging environment: If possible, set up a staging environment that replicates your server configuration and perform a test upgrade to Debian 11 and Plesk 18.0.48. Install MagicSpam in the staging environment and assess if it functions properly. This will help you verify the compatibility firsthand and mitigate any risks.