v4.33pre23 - March 24 2013

... As soon as I realize that I may have forgotten to install the latest pre, I always check to see if there's a newer one. There almost always is :P

+ Batch converter: support for rendering media items that have take-fx, including tail [issueid=4689] + Batch converter: setting for FX tail size when applying FX That's a big one for game sound designers! thanks a lot! :) + Freeze: basic support for position change in frozen items propagating back to frozen state That's interesting too! :) does this mean then that we can move positions of items around and the item's won't go back to there original state on unfeeze? If so, does this have a dialogue box to ask this (if it detects you have moved items) because I can see situations where both options are useful. :) EDIT: tested and it does mean this! :) although the dialogue that comes up is a little unhelpful. ;)

Also, thinking of things like batch converter. Is there a reason why we can use "control + alt" to move multiple items from project bay to a folder but not from the Arrange? Was that ever explained? ;) be so useful!

In regards to the batch convertor, can this behavior be looked at? I understand there may be valid reason for thiese options as default, but all I ask is that Reaper remember the setting when I change it. 100% of the time I use the batch convertor to convert song exports to mp3s for my iPhone so having Reaper default to adding "--" the start of each file name every time the window is opened is in no way helpful. 4.26 Batch Convertor Wildcard Bug Also: Batch Convertor does not check for disk space. Continues indefinitely with 0 bytes thanks. P.S. "+ Freeze: basic support for position change in frozen items propagating back to frozen state" is awesome! And stretch markers totally kick ass!! :D

Maybe just me who would like this, but I wish the batch converter could copy tags from an mp3 being converted to mp3 (downsampling Amazon mp3s in my case). I actually don't have a program that will easily do this.

While on topic of freeze - one handy feature would be to have special layout option for frozen tracks under Screensets

Just noticed a bug: I see the video preview change when I draw a time selection or when I extend an item but not when I draw a new MIDI item... No big deal but if it's fixed it will save me some time. (And please, add a option for frame-based grid, I'm working on some videos and it's really a very important, and missing feature!)

This is probably an absurd and useless late night thought, but I thought I'd post it anyway just in case: What if you could move backwards and forwards through the freeze history, sort of like the undo history, such that moving backward wouldn't discard more recent states? Maybe via mouse-wheeling on top of the proposed "snowflake with number" icon ... The track would fully take on its state directory prior to each freeze. Freezing over top of a past state would discard (or branch from) future freeze states, again like the undo history. That way unfreezing (moving backward through the freeze history) could be differentiated from "+ Freeze: basic support for position change in frozen items propagating back to frozen state", which is actually more like "merge modified frozen state into prior unfrozen state". The new track state produced by this merge operation could actually be added at the current freeze history HEAD, so the prior modified freeze state, and the once-unfrozen state before that, would all still be available by moving backward through the history.

I want a frozen fish sticks symbol or a polar bear pup. :) Please don't get your expectations too high, the change to freeze was only to address an "insert empty space" (a.k.a. position change) issue outside of (frozen) items, editing frozen items is something else and you should still avoid that.

While we're having some batch love... Can I just bring the dev's attention to this related FR: Essentially, it allows you to normalize after rendering. It would be very useful for people creating libraries of sound FX. Most of my sound FX are at different levels, I would love a way to batch normalize them all. (If you are rendering to a lossy format like MP3, it would first render to wav, normalize, then re-render to mp3 to avoid terrible losses).