I find myself constantly topping out the device memory at 100% or more. (I think the most I’ve seen is 104%). It’s hard to edit down the modes, I like a lot of options when performing.
Is it a problem to have the device memory near, at, or over 100%?
Can one put a larger SD card in the ETC? Noting the manual says:
“This slot comes preloaded with a card that serves as the internal microcomputer’s root disk. We do not recommend ejecting or otherwise manipulating this card as nothing good will come of it.”
Obviously, that’s pretty clear. However, updates to the SD were recommended for other problems, in this forum.
Thanks for any help and info anyone can offer.
Where do you get this “device memory” output? Or do you mean the “memory used” line in the OSD?
I mean the memory used line when I toggle on the info button on the ETC. (Sorry, I’m not sure what the OSD is.)
It won’t cause any lasting harm to run the device over 100% memory, you might see performance start to lag, dropped frames, sluggish response, that kind of thing.
100% actually includes about 10% headroom, so 100% is around 90% actual… then it was a little bug not to cap the displayed value at 100% which is why you see it going over 100%
but this memory is RAM memory which is hardwired. so changing SD card size won’t have any effect.
are you using many image files? I assume that is what eats up the memory. You could try reducing size of files, only use big bitmaps if they are necessary. and also if modes use the same image files, you could update the modes to read them from a central location, so modes are loading the same file over and over.
I think we had this topic a year ago and someone from C&G (you?) explained that each mode loades its images again - even if they were loaded by another mode already.
Thanks oweno - this is helpful info. I’m glad to know I’m not damaging the device by running it near 100%
would love to see a tutorial about this useful feature
as written below this, this does not help for the memory issue. (see also ETC memory best practices)
Regarding holding images on a central directory you simply can use a path relative to the modes directory, which is expressed by the variable etc.mode_root. Example
This finds all png-files from /usbdrive/Modes//
for filepath in sorted(glob.glob(etc.mode_root + './*.png')):
Now we create a directory “Images” on the usb-drive and move all images to this directory. So we can access them like this:
for filepath in sorted(glob.glob(etc.mode_root + '../../Images/*.png')):
The first “. ./” shifts down from /usbdrive/Modes/MyMode to /usbdrive/Modes
The second “. ./” shifts down to /usbdrive
and from there we go into /usbdrive/Images
Hope this helps.
I think the only way to save memory, would be for all images to be loaded into a dictionary.
Then the mode would then just reference that dictionary.
( so images are only loaded once)
However, this will only help if a lot of common images are used (across modes).
The alternative is to make it so etc load and unloads images as the mode is activated but that is contrary to the fun of being able to switch between modes without any stutters.
What I’ve tended to do, is only have the modes I’m using in the modes directory , and others elsewhere on the disk - which I can then copy ( or link ;)) in when needed.
Following up on this, since posting I’ve been more careful to compress images used in image modes. (I tend to use a lot of them.) Running images through TinyPNG.com has given me significant file size reduction without any noticeable chage in image quality. This has helped the ETC run much more smoothly.
For another option for reducing size of image files (png & jpg at least) there’s also: https://imageoptim.com/mac
Thanks, I’ll check that one out too.