|
Post by Kyaa on Mar 30, 2022 17:01:07 GMT
There have been a number of recent purchases, I wonder who else is new to the Euclid club?
|
|
|
Post by Kyaa on Apr 28, 2022 18:29:54 GMT
Just a PSA, but I'm onto my last two units of the second batch. I'm also not going to be able to restock for the next few months due to parts availability (read: chip shortage). Thanks for your patience and support so far!
|
|
|
Post by Kyaa on Oct 11, 2022 15:25:50 GMT
Howdy.
Random update, but I'm currently tinkering on a version of Euclid that fixes some of the low output issues.
No promises, but I think it would be alright to assume that I can start restocking by the end of the year.
|
|
|
Post by solipsistnation on Oct 31, 2022 20:42:00 GMT
Is that a firmware update or hardware?
Are existing modules moddable or just new ones?
|
|
|
Post by Kyaa on Oct 31, 2022 22:09:29 GMT
The low output fix in theory is something users could do themselves, but the component size is generally unfriendly to work with... I'll see if I can make a backpack PCB to fix the issue.
There may be some other small additional functionality, but that would also be hinging on some improvements to the button matrix, so those likely wouldn't be possible to port to the old units.
I'll do my best to make sure the old units are supported as possible.
|
|
|
Post by tIB on Mar 17, 2023 9:50:38 GMT
The low output fix in theory is something users could do themselves, but the component size is generally unfriendly to work with... I'll see if I can make a backpack PCB to fix the issue. There may be some other small additional functionality, but that would also be hinging on some improvements to the button matrix, so those likely wouldn't be possible to port to the old units. I'll do my best to make sure the old units are supported as possible. Is a backpack something that you're still thinking on given you're recent tweaks to approach, or will the output issue be fixed on the latest reprint? If love to get this module playing nicely with my logic modules - that's the only issue in my setup as everything else triggers fine.
|
|
|
Post by Kyaa on Mar 19, 2023 17:40:39 GMT
The low output fix in theory is something users could do themselves, but the component size is generally unfriendly to work with... I'll see if I can make a backpack PCB to fix the issue. There may be some other small additional functionality, but that would also be hinging on some improvements to the button matrix, so those likely wouldn't be possible to port to the old units. I'll do my best to make sure the old units are supported as possible. Is a backpack something that you're still thinking on given you're recent tweaks to approach, or will the output issue be fixed on the latest reprint? If love to get this module playing nicely with my logic modules - that's the only issue in my setup as everything else triggers fine. Ah, it's something I legit forgot about. I can totally whip together a prototype for my next pcb order.
|
|
|
Post by tIB on May 13, 2023 21:23:37 GMT
If you ever do a hardware V2 an out for the internal clock would be great.
|
|
|
Post by Kyaa on May 13, 2023 21:51:08 GMT
If you ever do a hardware V2 an out for the internal clock would be great. That's a good idea. I could theoretically do that with a firmware update instead though. The output pins are all driven separately so I could put a clock out on the first or last pin when the internal clock is enabled.
|
|
|
Post by tIB on May 14, 2023 7:00:17 GMT
If you ever do a hardware V2 an out for the internal clock would be great. That's a good idea. I could theoretically do that with a firmware update instead though. The output pins are all driven separately so I could put a clock out on the first or last pin when the internal clock is enabled. Funnily enough I was going to ask if there's a way it could be hacked but assumed it wouldn't be possible. That would be great- last pin makes most sense for me! It's a terrific module this - are you still thinking per track divisions could be crammed into the current iteration or was that a V2 thing?
|
|
|
Post by dizzeesatchel on May 14, 2023 7:20:00 GMT
Clock out would be super awesome. I usually use the clock from RBSS at the moment, but of course itโs harder to set a precise value
|
|
|
Post by leethargo on Feb 17, 2024 16:12:25 GMT
I've had an issue today when using a (fast) external clock to drive Euclid Grid and it appeared to sometimes skip clock signals, ie not advancing the sequence.
In my patch I patched one output of MM-DIV to Euclid Grid's clock input (and another MM-DIV output to TRIG164's clock input). This worked for a while, but then the two sequencers got out of sync, with Euclid Grid falling behind by one step, later another.
I'm aware of the power level issue of Euclid Grid v1.0, failing to trigger some needy modules (eg S&H), but my problem occurs at the other end. Could the trigger from MM-DIV be too low to consistently clock Euclid Grid? Or is there a maximum clock rate that it can handle?
As clock input for MM-DIV itself, I tried both RBSS' clock as well as a square LFO.
I first thought that it might be an issue with MM-DIV (skipping some outputs), but I have two copies of MM-DIV and could recreate the behavior with both. I then also rerouted this signal to trigger a drum module and did not "hear" a skipped beat.
For reference, the clock signal arriving at Euclid Grid was probably around 400 BPM, with MM-DIV running at 1600 BPM. Also, I think have v1.1 of the module.
|
|
|
Post by leethargo on Feb 17, 2024 18:21:14 GMT
The above observations were part of a more involved patch, and I now tried to isolate the problem by reproducing the behavior in a smaller patch using only 3-4 modules. It's become more difficult (ie really rare) to get two sequencers to go out of sync, and I've now also had a case where the other seq was a step behind Euclid Grid. This is to say that maybe it's really an issue with low power levels coming out of MM-DIV (maybe because of power drops with many modules active) and I'll try to amplify the triggers to avoid it.
|
|
|
Post by Kyaa on Feb 21, 2024 6:16:04 GMT
I've had an issue today when using a (fast) external clock to drive Euclid Grid and it appeared to sometimes skip clock signals, ie not advancing the sequence. In my patch I patched one output of MM-DIV to Euclid Grid's clock input (and another MM-DIV output to TRIG164's clock input). This worked for a while, but then the two sequencers got out of sync, with Euclid Grid falling behind by one step, later another. I'm aware of the power level issue of Euclid Grid v1.0, failing to trigger some needy modules (eg S&H), but my problem occurs at the other end. Could the trigger from MM-DIV be too low to consistently clock Euclid Grid? Or is there a maximum clock rate that it can handle? As clock input for MM-DIV itself, I tried both RBSS' clock as well as a square LFO. I first thought that it might be an issue with MM-DIV (skipping some outputs), but I have two copies of MM-DIV and could recreate the behavior with both. I then also rerouted this signal to trigger a drum module and did not "hear" a skipped beat. For reference, the clock signal arriving at Euclid Grid was probably around 400 BPM, with MM-DIV running at 1600 BPM. Also, I think have v1.1 of the module. Hmmm... I've not explicitly tested with MM-DIV (I'm not sure I have one to be honest). 400 is definitely fast but doesn't seem like it would be outside the acceptable range. When I've run into similar issues, I've used the logic module to buffer signals, and it can help. You could try that and see if it positively impacts your situation.
|
|
|
Post by leethargo on Feb 21, 2024 8:05:55 GMT
Thanks for the tip. I'll try buffering (with LOGIC or BUFFER) when the issue arises again.
During my experiments I also turned up the clock way high (rbss clock fully clockwise) for some seconds then turned it back to normal and most of the time the Euclid Grid was still in sync with either TRIG164 or the 2nd MM-DIV. That is, I could recreate the behavior by playing with the clock alone (in my minimal reproducable example) and there must be some other factor.
|
|
|
Post by maydonpoliris on Mar 11, 2024 8:44:21 GMT
Think I've managed to assassinate my Euclid Grid. Noticed it wasn't powering on eg no blinky lights and also I checked the output against the meter module and nothing shows. Also its plugged in correctly too. Not sure how I did this but luckily I did it before trying out the power fix so I can rule that out.
Are there any standard practices to debug modules or do I just start stabbing randomly with a fork? To clarify I have no idea about this sort of thing.
any tips would be really cool, Cheers
|
|
|
Post by Kyaa on Mar 11, 2024 17:35:54 GMT
Think I've managed to assassinate my Euclid Grid. Noticed it wasn't powering on eg no blinky lights and also I checked the output against the meter module and nothing shows. Also its plugged in correctly too. Not sure how I did this but luckily I did it before trying out the power fix so I can rule that out. Are there any standard practices to debug modules or do I just start stabbing randomly with a fork? To clarify I have no idea about this sort of thing. any tips would be really cool, Cheers Can I inquire which version you have?
|
|
|
Post by maydonpoliris on Mar 12, 2024 7:30:58 GMT
it was hot off the press when the original was released so i'm guess version 1. sorry Kyaa
|
|
|
Post by Kyaa on Mar 12, 2024 17:07:57 GMT
it was hot off the press when the original was released so i'm guess version 1. sorry Kyaa That has me less worried actually. I've observed at least one other instance where one of the filtering resistors can burn out. Have you applied the power fix board? That might fix the issue.
|
|
|
Post by maydonpoliris on Mar 12, 2024 19:02:11 GMT
Oh cool, I haven't yet applied the fix as I didn't want to make it worse. I'll give it a crack hopefully this weekend and let you know. Thanks Kyaa
|
|
|
Post by maydonpoliris on Apr 20, 2024 22:50:53 GMT
sorry Kyaa unfortunately the power fix didn't bring my Grid back to life so RIP EG and thanks for the ride
|
|
|
Post by Kyaa on Apr 21, 2024 17:29:24 GMT
sorry Kyaa unfortunately the power fix didn't bring my Grid back to life so RIP EG and thanks for the ride Dang, that's a bummer... ๐ I wonder what the cause is.
|
|
|
Post by maydonpoliris on Apr 22, 2024 9:03:58 GMT
Not sure why it happened, or exactly when. I just noticed the lights were out one day. Only thing I do remember was at one point trying some erratic clocking through a few different sources. My soldering for the fix may be dodgy too. These things happen so all good, I've had it since day 1 of the release so it has done the hard yards
|
|