5 Commits

Include renames

Author	SHA1	Message	Date
itsmattkc	5227e10f39	render one frame per thread for increased parallelism ... If the nodes are now stateless, there's nothing stopping the renderer from rendering multiple frames at once. Earlier since the nodes held some of their input/output data (and that data could change per frame), it was not possible to render multiple frames at once without conflicts. Now that the node state is held in render threads, they can do whatever they want at any time.	2019-12-06 15:37:31 +11:00
itsmattkc	8e6c23ffc1	fixed bug that caused some frames to never render indefinitely ... Frames should no longer get stuck unrendered.	2019-11-17 17:14:08 +09:00
itsmattkc	40b3879440	overhauled render classes to support video AND audio ... Major refactoring work to try sharing as much code as possible between the video renderers and audio renderers, as well as make them as platform-independent as possible.	2019-11-15 13:50:58 +09:00
itsmattkc	7a6dd02e5b	furthered development of audio renderers ... Mostly reimplementing functions from other workers to produce audio samples	2019-11-11 11:35:01 +09:00
itsmattkc	1206eb73b9	moved frame cache to external class that's easier to pass around	2019-11-06 23:46:44 +11:00