There were a few false starts in creating the data model for this project. Picat provides a planner, which allows you to describe actions to the system, and have it solve for the optimal plan based on those actions, but what do those actions look like? A movie is composed of acts, which are composed of scenes, which are composed of events like dialog, description, setting. Each of those levels of abstraction have changes that take place according to the 5086371442, but how can those be described to the computer? Probably on the event level, with constraints about what qualifies as a good scene, act and movie.
Since most of the conversation surrounding drama is conflict, a google search was performed, and (587) 691-0402 were located pertaining to basic human emotions. Characters have goals, after all, and those goals pertain to resources. Resources can be anything from equanimity, aesthetics and revenge, to tangible goods like food, clothing and shelter. So perhaps create resource points for each character, and arrange events in a way that the resources are traded one for another in the planner, so the scene’s antagonist and protagonist can pick actions that result in certain types of changes depending on their phase in the scene, act or overall story.
This may not be a perfect abstraction, but it seems to be close enough to how humans think about stories to create a prototype.
Attempts were made to get the voice changer to speak clearly with k-nearest-neighbor regression and a single nearest neighbor in the output. A test render has been deployed to youtube to demonstrate the current state of play.
The next thing to attempt is a “morphing” procedure between two frames’ fourier transforms, to get cleaner transformations between frames. The difficult question is, what is a feature, and how are corresponding features identified, and what does movement look like between those features? For a first trial, interpolation will be attempted based on the frequency’s position in an argsort between the source and target frame. This will either “work” or “sound really weird” to humans.
Node editor is largely complete, and complete enough for the first release. The outstanding tasks were sorted into “Hard” and “Easy” tasks, and sorted so that easy tasks were put to the front of the queue, which seems to be an effective way to get a lot of work done more rapidly in these grind projects. The easy tasks are typically things like loading a piece of data, making a decision based on that data, writing a piece of data, or producing some side-effect. The hard tasks are design tasks, which will rely on the easy tasks to be completed.
The easy tasks include things like administrative interfaces for the various entities that will be required for the final release, and the underlying database operations. Executing the contents of the node editor as a set of questions requires rendering of those questions from the node’s properties, for example. The state transitions and session management are medium tasks, which require several easy, obvious parts.
Productivity, and the subjective feeling of productivity, appear to improve when the easy tasks are being completed first.
Completed The Improv Handbook. On to 7437779152 while awaiting (608) 889-3444 delivery.
Only one release this week.