dmoore
Senior elf
This is a re-post from: http://www.lightshowpro.com//showthread.php?1595-Lsp-2-0&p=8791
LightShow Pro Development Update
Thank you for your patience in getting an update!
I would like to start by saying thank you for your continued support, your support makes the LSP development possible.
Through our effort to deliver an exceptional feature set and provide solutions to massive channel growth and emerging lighting capabilities, lets be honest, we took some design and architecture risks. some paid off while and others bit us through compatibility and functional customer issues. Although many customers designed and rand incredible displays using the new LSP features and functionality, we learned some hard lessons.
For that reason, the focus of LSP development this year has been on improving the stability, efficiency, functionality and design of the current LSP feature set. Delivering on the promise, we have refactored all core areas of LSP, those including: file format, memory utilization, grid functionality, undo/redo behavior, effect optimization, copy/paste logic and behaviors, timing management, output plugin architecture and output plugins.
As you can imagine this undertaking was a massive redesign in many regards and required a lot of attention (under the hood) whick hopefully explains the lack of my presence in the forums while building the next solution.
Although we are not prepared to discuss delivery, pricing and upgrade options, we are planning a deployment in late spring pending successful testing cycles and team acceptance.
in addition to backward compatibility and core rewrites, including an open file format and exponetial performance increases in many areas of functionality, you will find multi-core / threaded behavior and reduced memory and disk utilization...
although these numbers are very subjective, for what it is worth, these are the types of performance gains that I am currently seeing through development efforts.
Example:
a 3000 channel sequence in v1.8
v1.8
-load time:1:45*
-file size: 100mb*
-in memory size:800mb*
-effect optimization: 10-20 minutes
v1.x
-load time:0:15
-file size: 25mb
-in memory size:400mb
-effect optimization: 2-10 minutes
**these values are subjective to hardware and sequence complexity
Please look forward to more information as development procedes.
LightShow Pro Development Update
Thank you for your patience in getting an update!
I would like to start by saying thank you for your continued support, your support makes the LSP development possible.
Through our effort to deliver an exceptional feature set and provide solutions to massive channel growth and emerging lighting capabilities, lets be honest, we took some design and architecture risks. some paid off while and others bit us through compatibility and functional customer issues. Although many customers designed and rand incredible displays using the new LSP features and functionality, we learned some hard lessons.
For that reason, the focus of LSP development this year has been on improving the stability, efficiency, functionality and design of the current LSP feature set. Delivering on the promise, we have refactored all core areas of LSP, those including: file format, memory utilization, grid functionality, undo/redo behavior, effect optimization, copy/paste logic and behaviors, timing management, output plugin architecture and output plugins.
As you can imagine this undertaking was a massive redesign in many regards and required a lot of attention (under the hood) whick hopefully explains the lack of my presence in the forums while building the next solution.
Although we are not prepared to discuss delivery, pricing and upgrade options, we are planning a deployment in late spring pending successful testing cycles and team acceptance.
in addition to backward compatibility and core rewrites, including an open file format and exponetial performance increases in many areas of functionality, you will find multi-core / threaded behavior and reduced memory and disk utilization...
although these numbers are very subjective, for what it is worth, these are the types of performance gains that I am currently seeing through development efforts.
Example:
a 3000 channel sequence in v1.8
v1.8
-load time:1:45*
-file size: 100mb*
-in memory size:800mb*
-effect optimization: 10-20 minutes
v1.x
-load time:0:15
-file size: 25mb
-in memory size:400mb
-effect optimization: 2-10 minutes
**these values are subjective to hardware and sequence complexity
Please look forward to more information as development procedes.