Topic: New WAVE Version, New Optimization Feature!

[James]

Check this out!

http://laserboy.org/code/LaserBoy_2010_06_29.zip  

There is a totally new feature in this release.

I call it scan wagging.

Lets say you have a frame with  a single line in it. In the past, if you wanted LB to scan that single frame many times over, then it would scan the line. Blank the laser. Return the scanners to the start of the line, turn on the laser and repeat. This means that half of the time the line is being scanned, the laser is blank!

Scan wagging says, let's not do it like that. Instead of blanking and finding the way back to the beginning of the scan, let's just scan this frame backwards!

There is now a new setting in the [Tab] system value settings called

9 max time in seconds for wagging

The default setting is 1/20th of a second. This is the longest a frame can be and still be wagged. If a frame's playing time is any longer than this, it would flicker too much if it was wagged back and forth, so it would just scan those frames from start to end in the forward motion only.

Wow. I think this concept is way more difficult to explain that it was to implement in code!

If you don't want any of this nonsense, you should be able to defeat it by setting the value of (9 max time in seconds for wagging) to 0.00.

This release also fixes an issue that goes all the way back to the very beginning. The information that gets added to the header of a wave file used to be stuck at the end of the "fmt " chunk. The size of the chunk was then adjusted to accommodate for the additional data. Since I added another parameter to the optimization stuff and since that needed to be included in the wave header information, I figured now would be a good time to finally separate the LaserBoy wave header information into its own legitimate subchunk. So now LaserBoy waves have a perfectly normal "fmt " chunk and a whole new chunk called "LBoy", followed by a 32-bit integer indicating the size in bytes of the rest of the LaserBoy chunk that follows. This is then followed by the ASCII tag "LaserBoy06282010" and everything that follows that is the same as it was before.

James. 

[meandean]

 Well, at least you retained wave read compatibility with previous LBoy versions.
 
 The most hilarious part is that the present ver of LWave (as it has been for
months) reads your new wave stuff just as well as before by freak accident...
Maybe I just know you too well, as I know to expect the unexpected.
 
 I don't know what your trying to accomplish, but I expect no one else on this
planet will bother to read or write LB formatted waves because the whole thing
is worse than the IRS tax laws, which are supremely complicated and subject to
change on a dime.
 
 And you have the nerve to complain about ILDA...

[James]

It's not really that complicated.

You don't need to use every feature of the LaserBoy WAVE file format extension to get something good out of it.

If you know how to read code, all the documentation you need is right there in LaserBoy_wave.cpp!

Screw ILDA. This is wave!


James. 

[meandean]

If you know how to read code, all the documentation you need is right there in LaserBoy_wave.cpp

James. 

 That's fine and dandy if you're a C++ guru, but not everyone is.
 
 Real standards are written in generic terms that are language independent.  

[James]

Yes. Dean.

Gawd! What a buzz killer.

I have written it up in the past, but like I've said about so many other aspects of LaserBoy, as soon as I spend time writing documentation about how it works right now, I am inspired to add something or change it around!

It's pretty hard to write a document on a moving target!

Besides that, everyone knows......... No one cares about any of this stuff!

James.