DSP GPRs: 263/256

WxMan1 · Nov 18, 2008, 08:35 PM

Also, xTramSize is indicated at 122/2048. Any reason NOT to reduce the xTramSize memory to say 128?

This with Kx Project v3541 implemented with CT4780 (10k1)

Russ · Nov 18, 2008, 09:22 PM

This is a known issue, FxBus outputs do not use GPR's, but are counted as GPR's in the resource counter at the top of DSP.

As for xTram, that depends on how often you will use any DSP configs that use more than 128.

Max M. · Nov 18, 2008, 10:10 PM

Quote:

Any reason NOT to reduce the xTramSize memory to say 128?

But there're no reasons to reduce it also.

WxMan1 · Nov 19, 2008, 04:30 AM

Quote:

Originally Posted by Russ

This is a known issue, FxBus outputs do not use GPR's, but are counted as GPR's in the resource counter at the top of DSP.

As for xTram, that depends on how often you will use any DSP configs that use more than 128.

Mxy4x2 apparently was the culprit.

Bad Mxy4x2, bad, bad, baaaaaaad Mxy4x2.

It's all good though; I don't need her anymore.

Nov 18, 2008, 08:35 PM	#1
WxMan1 HardwareHeaven Lover Join Date: Dec 2007 Posts: 221 Rep Power: 40	DSP GPRs: 263/256 Also, xTramSize is indicated at 122/2048. Any reason NOT to reduce the xTramSize memory to say 128? This with Kx Project v3541 implemented with CT4780 (10k1)

Nov 18, 2008, 09:22 PM	#2
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,561 Rep Power: 62	Re: DSP GPRs: 263/256 This is a known issue, FxBus outputs do not use GPR's, but are counted as GPR's in the resource counter at the top of DSP. As for xTram, that depends on how often you will use any DSP configs that use more than 128.