When sending ramps from Diver to either Memory Palace or Structure, there is a hiccup/flicker every few seconds. Memory Palace is the master clock, and power is supplied by a Monorocket M9C. I tried replacing sync cables, moving the modules to different power rails with no luck. What might be causing this?
If I unplug the sync cable and let it drift the flicker goes away.
Some Divers seem to have inconsistencies processing sync signal. Users have quelled the issue by placing Diver first in the chain after the sync source, but this isn’t working for everybody. The LZX team is in the midst of researching the issue. I will post the solution here once I have a definitive answer. Sorry for the trouble!
Thanks, looking forward to it. I hope it’s not a hardware issue - it’s assuring that the Orion modules can be fixed/improved/augmented with firmware updates!
Do you happen to have a Visual Cortex or another sync source? If so, could you try syncing to something other than Memory Palace? We have a hunch that using Memory Palace as a sync source might be the issue.
Oh no. Unfortunately I don’t presently have another way to generate sync besides Memory Palace. I have a TBC2 on order but I’m assuming that will be a while.
I’m not sure why Structure can’t generate the sync. The is an RCA connector on the back labeled “GEN” but I’ve had no luck with it. Erogenous tones mentioned to me once “To use ramps from LZX with STRUCTURE you need to run a SYNC signal into STRUCTURE from something like Visual Cortex, so the input will be synced.”
I use Cadet 1 for the master sync of my system. That works well with the other modules of Cadet/ Castle series. But Diver doesn’t make steady images even if placed just next to Cadet 1. Images drift, or hiccups like Spacenoodle has shown. When I put the signals from Cadet 2 RGB encoder into Cadet 1, the speed of drifting and the frequency of hiccups seems to be lessened. How can I think of that? Is there effect of signal feedback of sync pulses?
Hi everyone. We’ve been doing some thorough lab testing with Diver, and are in the midst of confirming some fixes. So far, we track the compatibility issues down to Memory Palace and Cadet I when either are used as the master sync sources.
Once we find a fix, it will either be firmware upgrade (ideal!) or we’ll ask to recall your Memory Palace for a warranty fix that involves some hardware changes. Or there will be a small adapter PCB that solves the issue that we can ship you.
For now I would recommend you try a chain with an external video source as your sync master. For example:
External Video -> Diver Loop In
Diver Loop Thru -> Memory Palace Loop In (Memory Palace in External Sync mode.)
External Video -> Diver Loop In
Diver Loop Thru -> Cadet I Sync/Video In
If you can try this, please let us know how it goes. In the meantime, we’ll be working on a more permanent fix. We’re just drowned in work getting TBC2 ready at the moment. Most of the rest of the year is attention on the Orion modules after that job is done.
I tried ’ External Video -> Diver Loop In
Diver Loop Thru -> Cadet I Sync/Video In '. H+V ramp was used.
I found that drifting was lessened but frequent flickering appeared (there was some frame offset from before). I will be glad if it helps you to resolve the problems. thank you.
I am having similar experience with the Diver and MP sync. With MP as generator, I will get flicker, scrolling and unable to send ramps into Structure 1v RGB in’s.
Currently running Vidiot as sync generator and getting better results but still a little quirkiness in the Diver. My Diver does have the first firmware update. Able to get Diver ramps into Structure’s 1v RGB in’s.
Sync chain is:
Vidiot sync out (loop switch down) > Diver> Fortress> MP> Structure (terminated)
Here is a quick video of H+V ramp on bank3:
In all of the banks & outputs there is a step on the right side of output on vertical ramp. There is also a bit of wobble and jitter on horizontal ramp, it is more noticeable on just the H ramp out. I unfortunately don’t have a capture device and it is tricky to get a decent example of these finer details that are more noticeable in person.
Also getting some strange behavior that does not seem normal when MP is externally synced. The MP will not send a color image from either composite outs when connected directly to my CRT. Color works as expected over DVI/HDMI or if I send the composite outs to the Strucutre(?!). Dont have the a cable to test MP’s S-Video output. (I’ll edit this part out and make a new thread if too off topic)
Was starting to go a little crazy trouble shooting today until I came across that others are still having some issues. Hope this info is at least a little helpful
Thanks for the report. That’s super helpful.
Are you using Vidiot’s LUMA output for sync?
Could you try removing Memory Palace from the setup to see if that eliminates the issues?
I have isolated the Vidiot and Diver and am still getting same jitter and stepping. I used Vidiot’s luma, chroma and sync outs terminated at Diver for sync testing. The luma and sync out’s get same results, but the chroma glitches out with flickering and image scrolling. The glitching can be affected by changing Vidiot’s various controls.
Just to note, in all my testing on this post and previous the Diver has nothing patched in and the attenuators are fully CCW. The ramps are going to 1v video input on back of Vidiot
Here are some examples:
Diver - CHROMA sync
Diver - Mirrored H+V
Diver - H Ramp Jitter
I’m still kinda new at all this, apologies if this is expected behavior! From my experience having started with the Vidiot, I know images are going to have at least a little bit of wobble and or fuzz.
mine often freezes after powerup (döpfer low cost case, sync from diver to vidiot) sometimes i have to unplug the döpfer case to unfreeze, sometimes i have to unplug the vidiot. and sometimes it freezes in the middle of patching. i will continue to observe this
That is odd. Are you sending Vidiot Luma out to the Diver sync input?
yep, luma out to diver, got that wrong in the first post. could it be that, if diver is patched, the incoming signals/modulation is responsible for the freezing? not quiet shure, but i think it never froze unpatched, have to test this theory