So no more limit 1024 file?
1 Like
20 characters of thank you for this.
1 Like
So no more limit 1024 file?
This fixes a crash caused by having too many files on the card. It does not add extra frames to the amount of available memory.
3 Likes
Can you explain what the progressive mode does?
1 Like
It relates to whether we are processing the NTSC/PAL frame (720x486) in the recursive loop or the NTSC/PAL field (720x243, with odd lines processed before even numbered lines.) If you have a naturally interlaced source like a camera, or an LZX system, you want to be processing the fields, otherwise interlacing artifacts end up in the feedback loop. But if your source is progressive (like the image loader), interlacing artifacts are introduced by field rate processing. So it’s nice to have both options.
7 Likes
Image loader is my main workflow, so this is amazing, thank you! Also curious to test if the seams are missing from input now due to the under scan fix, today is the day!
2 Likes
Unfortunately all the interlacing issues remained after installing v2.0.2RC1 found on the above GitHub link @creatorlars
Tests confirmed that the same stairstepping error seen above appears when using Y mirror, and Reflect modes. Both on image loader only source, and from a Vidiot input only source. I have captures from the DVI-D/HDMI output and can upload if needed.
Seams on Vidiot NTSC input also remain, but uncertain if that was an issue covered by under scan fix.
I noticed the boot.bin file was timestamped December 2021, maybe a newer one needs to be uploaded? 
1 Like
Is this issue DVI-D specific, or are you seeing it out of the main outputs as well?
I noticed the boot.bin file was timestamped December 2021, maybe a newer one needs to be uploaded?
No, that’s when the version was released. We needed to test before posting, which we did – but everything’s been so busy we forgot to post it until now!
2 Likes
Yes @creatorlars I just tested this as well. I see the interlacing error in the cvbs 1 and 2, and s-video out as well with image loader and input. Though it’s a little less pronounced in s-video. Darn better luck next version 
I’m trying to update to v2.0.2
But when I try to extract/unzip the files, i get the error
unable to expand “BOOT.bin”. It is in an unsupported format
Any ideas? Have I missed something?
Are you trying to unzip the file, BOOT.bin?
You shouldn’t need to unzip a .bin file. You only need to unzip a .zip file.
1 Like
ah, I was being thick.
Looking at the .pdf guide I expected multiple files - I can see now they’re stills & json folders and the boot.bin!
Cheers!
I’d like an Aux mode that is a post process brightness boost and attenuator.
Sometimes you don’t want a lot of feedback repeats, so you control that by pulling down the contrast. The problem is, that leaves you with a dim image out of the MemPal.
You could bring this back up to desired levels with this Aux boost.
Maybe it would be possible to also use settings below 50% to attenuate the image, so that you could see detail in some of the blown out areas at the expense of some of the areas that are typically visible (they would tend towards black).
5 Likes
@creatorlars Would it be possible to get options for 5v (and -5v/+5v), and maybe even 10v scaling for the VC inputs? I know that was included in earlier firmware versions, but not the recent ones. Since these inputs don’t run at video rate (or audio rate, far as I can tell), I typically find them happiest with relatively slow mod sources (i.e. 5v audio modules).
3 Likes
I think 10 V scaling is impossible due to the limitations of all LZX power.
But 0-5 V and +/- 5 V should be an option for any digital computer like Memory Palace.
1 Like
I love getting feature requests for features already present! 
You can find the +/-5V, 5V, +/-1V and 1V settings in each slider’s detail page. They used to be on a global settings page, but moved to the individual parameter options.
2 Likes
I think it would change the feedback behavior to do this. You could use a gamma or curve processor in your patch to bring up some areas of low contrast. Gamma control in the feedback loop or as post-process in module is something we’ll consider in the future.
3 Likes
just moving from v18 to v202. everything is ok and menu navigation is more intuitive in my feeling and new features & bug fix are great <3 .
but, on v18 I was working with the alternate keying control : keyWhite/keyBlack instead of width/center,
on v202 I can’t find this feature. Did I miss something, did it disappear or am I confuse…?
It is the same, but selected differently in the menu. Choose LUMA as the key mode in the PARAMS menu.
2 Likes
not sure i am fully understood, luma key is ok then width & center sliders act as named, but I preferred the old alternative assignment when “width” become +key (white ‘top window’) and “center” become -key (black ‘bottom window’). Now I’m doubting on my memory, did I dream this feature?
Actual version = 2.0.2RC1