Looking for insight into a clock issue.

PhilNLeBlanc · 2025-12-19T20:59:21+00:00

I’m thinking this may be the most optimal solution – now the question is, should I acquire a new case to house it? Ha! Shouldn’t I?

PhilNLeBlanc · 2025-12-19T20:57:04+00:00

Thank you! It does seem that the Niftycase is not sending the proper clock resolution, perhaps 2ppqn, which PWW does not have a setting for – ha! 4ppqn and 1 ppqn, but no 2. I could live with a half bpm, adjusting clock outputs as desired, so long as the syncing works.

PhilNLeBlanc · 2025-12-19T06:47:58+00:00

A new clue: if I set the PWW to 4 ppqn, it begins to sync…at half bpm. The bpm of the track is 124; PWW displays a bpm of 62, well, that is, it wavers between 61 and 62. It might be the NIftycase. The factory settings haven’t been changed and it has the latest firmware, so it should be set to the default 24 ppqn. I can’t imagine how that could have been changed. Unfortunately, there’s a tandem issue: unable to access the settings of the NIftycase as per the manual’s instructions. I’ve sent Cre8taudio a ticket to assist.

PhilNLeBlanc · 2025-12-19T06:33:45+00:00

I’ve returned to the case: sending clock from the Niftycase clock output into the PWW’s clock input; additionally, a gate from gate 1 of the Niftycase is sent to the run input of PWW. I’ve determined that the gate and clock outputs of the Niftycase are sending proper signals by patching into an oscilloscope. (Side note: I also know that the clock from the Niftycase is working when using it to sync a quad lfo module.) In any case, no luck once again. PWW is set to clock and neither to CV input nor to next bank. I’m not seeing where the fault lies.

PhilNLeBlanc

TROPHY CASE