v4.16pre20 - February 24 2012

rob.manderson · 02-24-2012, 09:53 AM

v4.16pre20 - February 24 2012
# Take envelope strings can now be customized in menus
# JS: fixed possible deadlock when loading default presets
# JS: fixed completely broken saving of presets that have pin mappings set
# OSC: listen window does not eat messages
# OSC: anti-flood setting can be enabled per-device
# OSC: config file setting for active track (in the device) to follow last touched track (in REAPER)
# OSC: config file setting for active FX (in the device) to follow last touched or focused FX (in REAPER)
# OSC: support for previous/next FX preset
# OSC: various fixes and improvements
# OSC: please see many new comments in Default.ReaperOSC
+ OSX: potential fixes for Mountain Lion beta
+ WALTER: added new theme images master_mcp_io and master_tcp_io for master track

Coachz · 02-24-2012, 10:02 AM

cool ! What's a "take envelope string" ?

Banned · 02-24-2012, 11:24 AM

Awesome!

Off to more OSC hacking and testing...

musicbynumbers · 02-24-2012, 12:05 PM

# Take envelope strings can now be customized in menus

I'd so like to believe this means envelopes for take FX

But even if it doesn't, still intrigued

EvilDragon · 02-24-2012, 12:52 PM

Quote:

Originally Posted by musicbynumbers

# Take envelope strings can now be customized in menus

I'd so like to believe this means envelopes for take FX

But even if it doesn't, still intrigued

That's related to this thread, I believe.

vidalsh · 02-24-2012, 01:16 PM

Quote:

Originally Posted by rob.manderson

v4.16pre20 - February 24 2012
+ WALTER: added new theme images master_mcp_io and master_tcp_io for master track

???...what´s that?

EvilDragon · 02-24-2012, 01:19 PM

Separate image for I/O button for master tracks in TCP and MCP, obviously.

musicbynumbers · 02-24-2012, 01:57 PM

Quote:

Originally Posted by EvilDragon

That's related to this thread, I believe.

oh well.. just another dream laying dead then!

vidalsh · 02-24-2012, 02:04 PM

Quote:

Originally Posted by EvilDragon

Separate image for I/O button for master tracks in TCP and MCP, obviously.

yes I know...LOL..

but what´s the meaning of that?

are there some changes in master i/o? or is this only one image more for that?

EvilDragon · 02-24-2012, 02:13 PM

Just one more image for that.

vidalsh · 02-24-2012, 02:16 PM

Quote:

Originally Posted by EvilDragon

Just one more image for that.

ok thanks...

Win Conway · 02-25-2012, 02:34 PM

It is because the current system allows you to have a kind of send/receive display, but because a send receive display is rather pointless on the master, the new images allow you to have a much tidier look

daxliniere · 02-26-2012, 05:03 AM

Drag'n'drop effect doesn't copy pin routing correctly.

To reproduce (in MCP):
Insert an effect,
Change I/O pin configuration from 2 pins to 4 pins,
Change routing from 1+2 to 3+4,
Drag'n'drop effect to a new track,
Open duplicated effect and you will see:

1) Only 2 pins are shown (none of the checkboxes are filled)
2) When you press the [+] button to reveal pins 3+4, they are correctly filled.

This is also the perfect time to mention this:

Please change plugin drag'n'drop behaviour to observe the position where the plugin is dropped.
Currently, when you drag'n'drop a plugin, it's always placed at the bottom of the chain, not in order of where you dropped it. This is REALLY annoying if you are duplicating something like Slate VCC across 90+ tracks.

White Tie · 02-26-2012, 05:09 AM

Quote:

Originally Posted by vidalsh

???...what´s that?

The track 'IO' button launches a window called 'routing'. The master 'io' button launches a window called 'outputs'. So they're not precisely the same button, therefore it makes sense to not necessarily have the same image.

musicbynumbers · 02-26-2012, 06:11 AM

Plus one to these!

Quote:

Originally Posted by daxliniere

Drag'n'drop effect doesn't copy pin routing correctly.

To reproduce (in MCP):
Insert an effect,
Change I/O pin configuration from 2 pins to 4 pins,
Change routing from 1+2 to 3+4,
Drag'n'drop effect to a new track,
Open duplicated effect and you will see:

1) Only 2 pins are shown (none of the checkboxes are filled)
2) When you press the [+] button to reveal pins 3+4, they are correctly filled.

This is also the perfect time to mention this:

Please change plugin drag'n'drop behaviour to observe the position where the plugin is dropped.
Currently, when you drag'n'drop a plugin, it's always placed at the bottom of the chain, not in order of where you dropped it. This is REALLY annoying if you are duplicating something like Slate VCC across 90+ tracks.