Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

External Clock no longer works in the Hemisphere Suite in v1.8.2. #109

Closed
TFModular opened this issue Nov 24, 2024 · 5 comments
Closed

External Clock no longer works in the Hemisphere Suite in v1.8.2. #109

TFModular opened this issue Nov 24, 2024 · 5 comments

Comments

@TFModular
Copy link

Seems to affect all apps in Hemisphere. The original apps like Sequins work, only Hemisphere does not. Am I missing something?

@djphazer
Copy link
Owner

None of the trigger inputs work in Hemisphere? Can you provide some more details? Perhaps a screenshot of your Clock Setup screen settings?
Did this work fine in an older release of Phazerville? Are you running a Custom Build for T3.2? Or is it T4.0?

@TFModular
Copy link
Author

It is T4.0. v1.8.1 works without any problems. The firmware is freshly installed. The settings in the clock setup have not been changed.

@djphazer
Copy link
Owner

Very strange... not much changed between v1.8.1 and v1.8.2. I just reflashed my T4.0 unit back to the release build (085b225) and could not reproduce - applets respond to all 4 trigger inputs, and I can see them visually on the Meters screensaver. I even did a Reset to clear the EEPROM settings... of course, calibration is still retained - I'll admit, it's hard for me to test for bugs that may happen with a completely fresh Teensy, uncalibrated.

Another thought: all the internal clock multipliers are OFF by default now, which may give the impression that the internal clock doesn't work. This wouldn't affect the trigger inputs, though.

@TFModular
Copy link
Author

Yes, really strange, I can no longer reproduce the error either ... I may have triggered a bug without knowing how. I will continue to monitor this and report back if there are any findings. Thanks for the quick response.

@djphazer
Copy link
Owner

Another theory: This could also be related to the new Tuner code not shutting down properly somewhere... which I think would disable TR1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants