3.11beta2 is up

[rob.manderson]

v3.11beta2 - September 16 2009
+ [removeme] fixed missing API functions (causing midi editor crash, etc) in beta
+ [removeme] info line prefix fix
+ [removeme] other small tweaks

[Tallisman]

and the stuff from the beta 1 for easy reference:

v3.11beta - September 14 2009
+ Action: crossfade any overlapping selected items
+ Action: toggle master track and tempo envelope visibility together
+ Action window: allow removal of multiple key bindings at once
+ ASIO: fixed compatibility with Zoom R16 (and possibly other devices)
+ Automation: freehand envelope drawing (ctrl+drag by default, optionally ctrl+alt+drag)
+ Automation: envelope data reduction during recording is now on by default
+ Automation: add a point anywhere in an envelope lane by clicking
+ Automation: envelope lanes now respect locking
+ Editing: fixed shift+click for multiple selection in arrange view
+ Editing: do not allow track envelopes to move vertically when ripple edit is enabled
+ Fades: option to disable autofades/autocrossfades for MIDI items
+ FX autobuild routing: clearer indication that cancelling autobuild will still load the FX
+ FX chains: loading FX chains will search the path of the .rfxchain for media files (for reasamplomatic/reaverb)
+ FX window: UTF-8 support for preset/program combo boxes
+ Help: useful information (info or context sensitive help) displayed below TCP section
+ License keys: updated text for non-commercial to be more accurate (personal/small business)
+ Loop recording: fixes for rounding errors causing items to be slightly too long
+ MCU: better support for emulated surfaces that do not notify touch state
+ Media explorer: menu options to enable RPP preview, disable tempo sync
+ MIDI editor: velocity lane editing affects only selected notes if there is a selection visible
+ MIDI editor: show MIDI track input on piano keys (preliminary/test, may not remain)
+ MIDI editor: less eager to show empty space to the left of the MIDI item
+ MIDI editor: fixed drawing controller data over existing data on another channel
+ MIDI editor: actions to move to previous/next lyric
+ MIDI editor: fixed blinking cursor reappearing when offscreen
+ MIDI: in-project MIDI preview should now interrupt audio less
+ Mixer: improved extended mixer FX context menu layout
+ Multiproject: support for playing background projects with current, option to sync start times
+ OSX: fixed low latency MIDI output mode
+ OSX: fixed menu key binding labels
+ OSX: fixed MIDI note name editing
+ OSX: AU compatibility improvements
+ OSX: fixed key assigning special keys in actions window
+ OSX: fixed keyboard navigation in file open/save dialogs
+ Pan: allow settings as low as +1/-1% with control+drag
+ Peak building now handles multiple projects nicely
+ Pencil mode: obey loop preference when drawing empty MIDI item
+ Project settings: project media browse dialog better deals with relative paths
+ ReaSamplomatic5000: ability to fully buffer smaller audio samples (better performance)
+ ReaSamplomatic5000: removed pan automation zipper noises
+ ReaSamplomatic5000: volume/rate/etc automation now affects playing samples
+ ReaSamplomatic5000: parameter for MIDI pitch bend amount (default is 2 semitones, can do up to 12)
+ ReaSamplomatic5000: safer thread-source management
+ ReaSamplomatic5000: notify undo state when sample changed
+ ReaVerb: less RAM use during file loading
+ Safer memory management in undo, ReaVerb, and other areas
+ Snap: relative snap support
+ Snap: when grid-snap settings follow visible grid, do not snap if grid is not visible
+ Selection: faster selection of multiple tracks in some cases where other windows are open
+ Take: reverse take, fixes/improvements to loop section
+ TCP: Fixed track VU meter glitch
+ TCP/mixer: mousewheel support on FX knobs and sends
+ Tempo markers: manual edit of position defaults to timeline units (bars.beats, min:sec, etc)
+ Toolbar: arm a custom toolbar button by right-clicking, click an item in the arrange view to run it (super-preliminary)
+ Undo: fixed multiproject undo system bugs
+ Undo window: safer destroy on exit
+ User preference: default track height in new projects, set to medium (was small) by default
+ Virtual MIDI keyboard: arrow keys can be passed through to main window
+ VST: configurable bridging/firewalling on x64 and x86 (prefs/VST)
+ VST: FX browser option for run mode (default, native, separate process, dedicated process)
+ Windows Vista/7: validate ini file path before using (to ensure that it is writeable)

[StepOne]

Bug still exists in MIDI editor zoom - vertical zoom always scrolls to selected/center note, regardless of mouse preference (mine is set to "track under mouse cursor", so MIDI editor should scroll to the note under the mouse cursor.)

This bug has been there for a while.

[musicbynumbers]

Please could we have middle mouse button pan scrolling in the midi editor (without using the top time bar)! pretty please!

[StepOne]

Originally Posted by musicbynumbers

Please could we have middle mouse button pan scrolling in the midi editor (without using the top time bar)! pretty please!

I'm confused...alt-mousewheel does this already?

[gofer]

musicbynumbers means the cool hand grabber cursor you can get with the middle mouse button (depends on Preferences -> Mouse -> Middle button) in the main view. It's xtracool for quick small vertical and horizontal adjustments, I'd love to see that in the MIDI editor as well.

But I'd also love to see 3.11 out in the real world It's amazing enough and I can't wait to see pip again in the next pre-ride

[dub3000]

this new API stuff... does this suggest that the MIDI editor is going to be extensible? (or is that already possible?)

[Xenakios]

Originally Posted by dub3000

this new API stuff... does this suggest that the MIDI editor is going to be extensible? (or is that already possible?)

The current MIDI editor, which is an extension itself, is not exposed to 3rd party extensions. Not sure what the fixed API stuff refers to. Could be some Cockos internal stuff.

[koolkeys]

+ Toolbar: arm a custom toolbar button by right-clicking, click an item in the arrange view to run it (super-preliminary)

Just curious, but what advantage would this provide?

Brent

[j79]

this will (kinda) enable people to make tools like other daws have...arming "split item under mousecursor", would effectively result in a scissor-tool.

[airon]

Brent, make up some macros that perform operations on the item underneath your mouse cursor for example.

Any repetitive task that you may not want to put on to a key.

New toy. We gotta play a while to know what it's good for.

[airon]

-edit- double post at maintenance time

[gregerlindberg]

Is there a way to get a hand on the betareleases?

[Tallisman]

Originally Posted by koolkeys

+ Toolbar: arm a custom toolbar button by right-clicking, click an item in the arrange view to run it (super-preliminary)

Just curious, but what advantage would this provide?

Brent

it would offer sooooooooo very much if it were enhanced a little:




.t

[jamester]

+ Loop recording: fixes for rounding errors causing items to be slightly too long

Does this mean that loop-recorded midi tracks won't have that little nub extending past the loop region anymore? If so, that's fantastic cuz that's been a minor annoyance for some time now...

[koolkeys]

Originally Posted by airon

Brent, make up some macros that perform operations on the item underneath your mouse cursor for example.

Any repetitive task that you may not want to put on to a key.

New toy. We gotta play a while to know what it's good for.

So if I understand correctly, "arming" a toolbar button wouldn't just arm it for a single execution, but you could arm it and then apply that action to, say, ten different items in a row without arming it again?

I think that I was thinking it was a single execution. Arm, apply, arm apply, arm, apply, etc. Which would of course not be as good.

Am I getting it right then?

Brent

[setvice]

I would like to try this beta. Where can I find it??

[Tallisman]

Originally Posted by koolkeys

So if I understand correctly, "arming" a toolbar button wouldn't just arm it for a single execution, but you could arm it and then apply that action to, say, ten different items in a row without arming it again?

I think that I was thinking it was a single execution. Arm, apply, arm apply, arm, apply, etc. Which would of course not be as good.

Am I getting it right then?

Brent

yes brent
arm click away.


then disarm for normal mousing about.

.t

[Tallisman]

Originally Posted by setvice

I would like to try this beta. Where can I find it??

http://landoleet.org

[musicbynumbers]

Love the idea above for toolbars!

if we could get a "preset drop down box" for the toolbar to allow us to have more than one set. This would allow a set for say cutting and trimming and then a set for mixing tools and even a set for take editing. Would be amazing.

Even better would be the ability to have multiple toolbars. Great for multi monitors.

I'm sure this is a feature request i made.. Will find it and post the link!

[gofer]

Haha, no it's a FR I made. It's here: http://forum.cockos.com/project.php?issueid=1100 Needs plenty of votes still

Also, the unarming of a toolbar button is a bit slowing things down, or is there another way than to click on an empty space in the toolbar?

[musicbynumbers]

Escape button i think and maybe right click?

Will check out your thread but i've a feeling i've voted already!

[gofer]

Escape works, but also kills the time selection (plus the loop selection, if you prefer). That's not exactly brilliant.

[BenK-msx]

Originally Posted by gofer

Escape works, but also kills the time selection (plus the loop selection, if you prefer). That's not exactly brilliant.

i agree - mentioned it here, think it got slightly swamped by a tallisman super-idea (and nowt wrong with that btw! is a good one)

http://forum.cockos.com/showpost.php...34&postcount=5