Hi Guys.... Randall and Cameron,
I was following Cameron some months in his improvements and redesigns of pistomp code. Really incredibly impressive how many nice improvements and features are implemented now! Even some plugins have a graphical interface via the LCD screen!
And..... I love the Tuner!!
And... new to me... the recover utilities and the update possibilities via the LCD UI!!!
And... Also new to me is the NAM capture.... great!
I LOVE IT!
Thanks guys!!
Cheers,
Maarten
PS
An observation: The Q factor for some of the filter plugins in the UI on the LCD screen presents opposite values of what I would expect with regards to the Band Width that is shown in the plot. AFAIK the higher the Q-factor, the smaller the Band Width around the filter frequency. Now it is showing the opposite....
PPS It would be nice (convenient) if in pistomp.conf also the n (amount of buffers) could be defined: so...
JACK_SAMPLE_RATE XXXXX
JACK_PERIOD XXX
_JACK_N_PERIOD XX
Hi Guys.... Randall and Cameron,
I was following Cameron some months in his improvements and redesigns of pistomp code. Really incredibly impressive how many nice improvements and features are implemented now! Even some plugins have a graphical interface via the LCD screen!
And..... I love the Tuner!!
And... new to me... the recover utilities and the update possibilities via the LCD UI!!!
And... Also new to me is the NAM capture.... great!
I LOVE IT!
Thanks guys!!
Cheers,
Maarten
PS
An observation: The Q factor for some of the filter plugins in the UI on the LCD screen presents opposite values of what I would expect with regards to the Band Width that is shown in the plot. AFAIK the higher the Q-factor, the smaller the Band Width around the filter frequency. Now it is showing the opposite....
PPS It would be nice (convenient) if in pistomp.conf also the n (amount of buffers) could be defined: so...
JACK_SAMPLE_RATE XXXXX
JACK_PERIOD XXX
_JACK_N_PERIOD XX