The Memory Palace Experience (Unf#$&ing la Memory Palacio)

memorypalace
#25

graphic patch bay? that’s sound great! I hope for delay able to put before argb, I mean delayed the dry signal, for camera feedback purpose… (and just from dreaming, triple delay on each R/G/B channel for time glicht experience : https://vimeo.com/59434848 )

2 Likes

#26

Thanks for this list. I have had **Problem #5 happen. Also had the whole module freeze up and be unresponsive a few times. Cycling the power seems to resolve it but not sure the cause.

2 Likes

#27

This may have been mentioned elsewhere, but when running into a crash bug, resetting the MP firmware also reboots the unit (if you’d rather not reboot your whole euorack case).

2 Likes

#28

In the case of the #5 bug listed above. The whole interface freezes up and the buttons no longer work. Is there a way to reset the firmware without needing to interface at all with the modules buttons or menus?

1 Like

#29

@creatorlars I spent a little more time with the MP while trying to use Cortex’s input decoder and MP continues to freeze up. This is even with out patching the external source into MP just attempting to use the still. I guess I am wondering if this is something I should open a ticket for, something that will be addressed in the next firmware update, or what I should do to get a more permanent solution than cycling the power off and on? I realize there is still a lot being developed and worked out with MP, but, just trying to get an idea of the best way to proceed. I guess at this point for me it is just not using external sources into Cortex? Thanks!

0 Likes

#30

@DesertMuseum Cycle the power after connecting a new source to Visual Cortex is always a good idea.
External sources into Visual Cortex are meant to be coming from a stable and consistent timebase, and Memory Palace is expecting to boot up to an already stabilized sync source. When you patch a new source into Cortex, it changes its timing to Genlock. I’m sure I can make Memory Palace more capable of reinitializing itself on a sync change later on, but this shouldn’t be considered a functional issue for now. TBC2 won’t exhibit the same behavior, as it’s a TBC/synchronizer (what you want if you’re going to be live swapping input sources anyway.)

1 Like

#31

Good to know. That being said, I was hoping to run the output of a switcher into Cortex’s input decoder, I am guessing this will not be possible while keeping stable sync through the system, if I was to be switching between sources via switcher? I am guessing only TBC2 would handle this type of external input with stability? I was hoping to make use of Cortex’s input decoder but will it only hold stable sync with a continuous playback? I have not really had a problem in the past, only after Memory Palace was put in the sync chain

0 Likes

#32

Good to know. That being said, I was hoping to run the output of a switcher into Cortex’s input decoder, I am guessing this will not be possible while keeping stable sync through the system, if I was to be switching between sources via switcher?

Using a switcher/mixer with TBCs like the Roland V8EX, etc should not be a problem. Switching between asynchronous sources (like with an Extron matrix switcher or video selection punch box) for your system master sync will reset the timing of the entire system every time you select a new source.

I was hoping to make use of Cortex’s input decoder but will it only hold stable sync with a continuous playback?

The timing of Cortex locks to whatever is fed into the genlock input (either frontpanel Y/Luma jack or rear sync input.) If you change the source to a source with different (asynchronous) timing, the timing of the entire system will change as a result to match the new source. This is causing Memory Palace to lock up because it’s not expecting the system master sync to change timing after it boots up and locks on.

Using a switcher with TBC/frame synchronizer on Visual Cortex inputs so that you’re always feeding your system a stable sync source will solve your issue, as would the TBC2 module.

I’ll see if we can make Memory Palace more resistant to dropouts/abrupt changes in sync in a future update.

2 Likes

#33

Thanks for this insight, super helpful. I will remain on the edge of my seat to receive TBC2.

0 Likes

#34

@creatorlars
Not sure if this has come up yet but the dvi output from my MP is not outputting a signal but if I patch the rgb outs into cortex the image shows up through cortex via the patch cables. Also, the s video out works fine. Not sure what is going on? I tried cycling the power…? Also tried multiple dvi/hdmi cables.

0 Likes

#35

What are you displaying/capturing on? Does it support 525p60/480p60?

0 Likes

#36

Hmm. Just got it to work but had to cycle the power again after it did not work the first time. No external sources plugged in at all. I will mess around with it somemore over the weekend and see if it happens again and under what circumstances. The monitor i am using does support those formats. Thanks for the reply.

0 Likes

#37

I was going to post this about the reset… but you beat me to it…

0 Likes

#38

Just want to add some insight here. My MP definitely would freeze after being left on for a while. Buttons would not respond. Would not pass signal. I’m running the same system of VC providing sync to the MP and changing source feeding the VC often.

For me the issue ended up being power related.
I tried it in a couple of rack configurations that were conforming to the 10Ma per HP standard with a Tip Top Zeus studio bus. Lars recommended this: https://smile.amazon.com/gp/product/B01MTYCRHV/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1

Since installing it I’ve had my MP on for three days straight and no freezing. For $13 it is definitely worth getting if you are troubleshooting the MP. (Now I just need to find a right-angle adaptor for it.)

1 Like

#39

Has anyone been able to capture from Memory Palace’s DVI/HDMI output into a Blackmagic Intensity Shuttle’s HDMI input? I’m able to capture the MemPal’s S-Video out, but not the HDMI output for some reason. Tried every input setting on the Shuttle with no luck.

2 Likes

#40

I captured some MP footage wIth my Blackmagic USB so should work for you.

1 Like

#41

If you haven’t already, I would just double check your shuttle is set to capture at 480p 59.94 (which is what MPs DVI is outputting). Sometimes those shuttles can be finicky if not exactly matching.

2 Likes

#42

Thanks for the tips, guys — still no luck. @DesertMuseum The Shuttle actually only gives me 525i/p options, no 480 — wondering if this has something to do with it.

Also, a very strange bug: I get a black-and-white image out of MP for like 5 minutes, before it eventually transitions to color.

0 Likes

#43

@giantmecha
I don’t use a shuttle but do have another blackmagic device and the 480p out of the MP DVI works fine when the Blackmagic is set to 525p… is this shuttle newly installed on your computer or has it worked in the past with other devices (just not MP)?

Very strange bug (B/W>Color)… I have not had this happen… is this with a HDMI cable running straight from MP into your monitor?

0 Likes

#44

525 is 480. 480 is visual space and the remaining ‘45’ is essentially NTSC Timecode.

0 Likes