Comments (12)
from image-sequencer.
So is it memory vs runtime?
from image-sequencer.
from image-sequencer.
Maybe we should do so.
Yeah I guess storing the images won't be a problem after all.
I think we should create another method apart from run().
But anyways, All the steps will have to rerun when a step is removed. (I'm almost dome implementing the removeStep() function)
from image-sequencer.
from image-sequencer.
Can't we have a lower precision version for working and process the complete image only when a full-fledged render is required. This way we would be spending less memory and it would be feasible to have the output of each node stored with it.
from image-sequencer.
Could you please explain that?
from image-sequencer.
We'll, you can see this method used in majority of memory heavy software. They work on a lower resolution version during the crafting and complete all the actions on the full resolution image only when the work is final. It does not make sense to process the entire image spanning 4MPs or something when your display window is barely 500px in width or so
from image-sequencer.
This can still be thought upon!
from image-sequencer.
from image-sequencer.
Yes I totally agree. I think this can be implemented at a later stage though!
from image-sequencer.
I'm going to close this since we now only re-run the critical modules! If someone wants to open a new issue for "preview versions" that'd be cool too!
from image-sequencer.
Related Issues (20)
- Adding an image sharpening module
- Removing scroll-to-top on mobile devices HOT 5
- Focus stacking module implementation HOT 1
- Halftone angle (in radians) needs to be a decimal instead of an integer HOT 3
- Dependencies Requiring Manual Upgrades HOT 1
- Remove Unused Dependencies HOT 1
- Supported NodeJS Versions HOT 3
- New module idea: ocr text recognition
- Use Modern JS HOT 2
- Can add units to the dimension of the image HOT 10
- How do I specify "executablePath" when calling Puppeteer HOT 5
- yarn.lock vs. package-lock.json HOT 1
- Checklist and coordination for v3.7.2 patch release and v3.7.3 follow-up patch release HOT 8
- Ideas for next release HOT 2
- Yarn complains about [email protected] expecting node 0.8.x HOT 13
- New module idea: descreen/dehalftone/inverse halftone
- Checklist and coordination for v3.8.0 minor release
- Incorrect local path for manipulation.wasm when using as an embedded library in MapKnitter.org
- eslint-error : Expected linebreaks to be 'LF' but found 'CLRF' HOT 1
- all thumbnails are not visible in the add step box HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from image-sequencer.