FM9 - Pitch/ Capo sound since V8.01

[vangrieg]

NDSP does it much better than Digitech, without newer hardware designs. So it is possible.

the new reverbs and comps are taxing on the unit,

Don’t remember anyone complaining about quality of reverbs in Fractal units.

Not sure why we get reverbs instead of pitch shifting.

 

[FractalAudio]

The newest Pitch algorithm is better than the old one. It has lower latency and less tremolo effect.

The problem, however, is that on the FM-9 and FM-3, in general, presets use more CPU than before which starves the pitch detector thread. This manifests as tremolo mostly and occasionally added latency because the pitch is slow to update.

For these products we recommend reducing CPU usage as much as possible if pitch shifting performance is paramount.

 

[vangrieg]

Can we have the old non-improved reverbs and compressors back? They were fine.

Or are there any specific recommendations at which effects to look at? Like, these run on the same core with pitch detectors.

 

[mr_fender]

You can revert back to the previous FW anytime you want. You can't have your cake and eat it too.

 

[vangrieg]

You can revert back to the previous FW anytime you want. You can't have your cake and eat it too.

If the new pitch algorithm is better but is held back by new reverbs and stuff then reverting doesn’t get the better pitch shifting.

 

[mr_fender]

Then you might need to reduce the CPU level in your presets.

 

[BROCKSTAR]

If the new pitch algorithm is better but is held back by new reverbs and stuff then reverting doesn’t get the better pitch shifting.

Basically just use economy models in your reverb and compressor and other blocks if you rely on pitch stuff heavily so that it tracks and sounds better!

 

[Sergius9]

The newest Pitch algorithm is better than the old one. It has lower latency and less tremolo effect.

The problem, however, is that on the FM-9 and FM-3, in general, presets use more CPU than before which starves the pitch detector thread. This manifests as tremolo mostly and occasionally added latency because the pitch is slow to update.

For these products we recommend reducing CPU usage as much as possible if pitch shifting performance is paramount.

Thanks for chiming in!! This is great info.

 

[ocaptainjr2]

If the new pitch algorithm is better but is held back by new reverbs and stuff then reverting doesn’t get the better pitch shifting.

Neither does complaining about something for which you have been provided two options to achieve better pitch shifting, e.g. revert firmware or reduce CPU. You are clearly happy with the Transpose in Neural DSP and should use that product. As @mr_fender said, you can't have your cake and eat it too.

 

[Sergius9]

The newest Pitch algorithm is better than the old one. It has lower latency and less tremolo effect.

The problem, however, is that on the FM-9 and FM-3, in general, presets use more CPU than before which starves the pitch detector thread. This manifests as tremolo mostly and occasionally added latency because the pitch is slow to update.

For these products we recommend reducing CPU usage as much as possible if pitch shifting performance is paramount.

Is it safe to say that Delays and Reverbs do not affect CPU load for the Pitch detector thread?

 

[Chiguete]

Can someone make a simple preset only using Pitch - Amp - Cab and compare the results?

 

[Soldani]

Pitch shifting will always have latency. Newer hardware designs may speed it up. The trick is the quality vs latency ratio. Digitech seems to have figured out a quality vs latency ratio.

You are right, BUT it works much better before the optimization! Really much better, that's the "funny" part.

 

[Soldani]

The newest Pitch algorithm is better than the old one. It has lower latency and less tremolo effect.

The problem, however, is that on the FM-9 and FM-3, in general, presets use more CPU than before which starves the pitch detector thread. This manifests as tremolo mostly and occasionally added latency because the pitch is slow to update.

For these products we recommend reducing CPU usage as much as possible if pitch shifting performance is paramount.

Thanks, for the Information.... I will check this out / maybe with a video

 

[JoKeR III]

I don't believe it matters if certain effects run on different cores. In the FM9, it seems to spread the load across the cores resulting in more efficiency in the system. I believe the CPU percentage reflects the total processing power being used.

There are ways to reduce CPU, especially in the Reverb block. On the Axe III, reducing the Reverb Quality from 'High' to 'Economy' saves @ 5%, reducing the 'Echo Density' from 8 to 4 saves @ 4%. If these result in a 'weaker' sounding reverb, reduce the Size to get some of the 'lushness' back.

 

[ocaptainjr2]

Can someone make a simple preset only using Pitch - Amp - Cab and compare the results?

You are better served doing the test yourself. If I do the test and say the results are 'better' or 'worse' that means nothing to you or anyone else because it is relative to my experience and expectations. Then the thread continues as an echo chamber for the three or four people saying 'the virtual capo sucks' repeating their opinions ad nauseam

 

[vangrieg]

Then the thread continues as an echo chamber

You don’t have to read it

 

[vangrieg]

There are ways to reduce CPU, especially in the Reverb block

I don’t even use reverbs most of the time.

 

[vangrieg]

Then you might need to reduce the CPU level in your presets.

So my question is how specifically do I do that

You are clearly happy with the Transpose in Neural DSP and should use that product

That’s about the only feature I like in that product. The reason why I brought it up was that it’s an example of a pitch shifting implementation that doesn’t require crazy powerful hardware, so it’s possible to do.

 

[ocaptainjr2]

The guy will all the answers doesn't know how to reduce CPU usage

 

[vangrieg]

The guy will all the answers doesn't know how to reduce CPU usage

Not sure why you think it’s a good idea to be a jerk.

Since different effects use different cores, the overall number that you see doesn’t necessarily reflect how specific effects may influence pitch detection.