Old 04-27-2012, 01:33 AM   #521
Anton9
Human being with feelings
 
Anton9's Avatar
 
Join Date: Jun 2009
Location: Earth
Posts: 1,334
Default

Quote:
Originally Posted by Banned View Post
some scheme to automatically generate a name based on date and time (e.g. 20120412_175645) would be awesome. Perhaps also something to include track/slot numbers (e.g. t12_s3_20120412_175645).
Nice idea.., I would take this a little further and suggest the ability to save using wildcards similar to what we currently have with render wildcards and perhaps a dialog or config file where users could create custom wildcards.., maybe like 16 of them. Then a set of actions labeled something like "Save preset using wildcard 1" through 16.
Anton9 is offline   Reply With Quote
Old 04-27-2012, 01:38 AM   #522
Anton9
Human being with feelings
 
Anton9's Avatar
 
Join Date: Jun 2009
Location: Earth
Posts: 1,334
Default OSC Request

Schwa,

Could you please add OSC control for all of the Parameter Modulation dialog's parameters?



Thank you,

Anton9
Anton9 is offline   Reply With Quote
Old 04-29-2012, 10:14 AM   #523
zydeholic
Human being with feelings
 
Join Date: Oct 2011
Posts: 14
Default Here's a request: make MIDI work for non-rocket scientists

I've been using Mixcraft, and it is easy as hell to get a midi recording up and working. And I can select actual instruments, not synths.

Instead of having to go through 6 or more steps (which are not working anyway for me), just do a drag and drop midi track and select in instrument, arm and record.

Your current interface, which I have yet to get working, is thus so difficult that I can't use it.

I have a Roland FR-18 digital triple row accordion. I have an Alesis io2 audio interface. I can record midi in probably two steps in Mixcraft. In Reaper, I can't even get started.

I don't have to time to become a rocket scientist while trying to compose music.
zydeholic is offline   Reply With Quote
Old 04-30-2012, 06:49 AM   #524
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by zydeholic View Post
[...] midi [...] midi [...].
Sorry, but this thread is not about MIDI, it's about OSC.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 05-06-2012, 06:15 AM   #525
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Can we please have OSC support for the pre-FX volume and pan track parameters? As discussed in this thread, currently there seems to be no way to control these parameters remotely.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 05-06-2012, 08:38 AM   #526
wolfgerb
Human being with feelings
 
Join Date: Dec 2011
Location: austria
Posts: 257
Default OSC Region Name

Since we have a " Go to region 01 after...." action now, would`t it be great
to have a the possibility of Reaper transmitting the region names (and marker names)
like it does with the track names?

Thanx Wolfger
wolfgerb is offline   Reply With Quote
Old 05-10-2012, 01:59 PM   #527
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default [FR] + triggering non-native actions using their unique command ID string

[FR] Can we please have the ability to trigger non-native actions using their unique command ID strings? As also discussed here (also see posts # 10 and #11 in the same thread), this would make sense, since action IDs are not reliable for non-native actions, and workarounds such as using toolbar buttons containing such actions have their own issues, and should not be needed in the first place.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 05-11-2012, 03:53 PM   #528
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default [bug] REAPER sends string for *previous* fxparam value when receiving new one

There seems to be a bug in the message patterns for plugin (instrument) parameter values: when sending feedback on receiving an update from the control surface, the string representing the 'scaled' value sends the string for the *previous* value instead of the current one.

See this example (project with only 1 track, 1 plugin in first slot: ReaDelay; default OSC config):

Code:
OSC to REAPER: /fxparam/4/value 0
OSC from REAPER: /fxparam/4/value/str 10000.0
OSC from REAPER: /track/1/fx/1/fxparam/4/value 0

OSC to REAPER: /fxparam/4/value 1
OSC from REAPER: /fxparam/4/value/str 0.0
OSC from REAPER: /track/1/fx/1/fxparam/4/value 1

OSC to REAPER: /fxparam/4/value 0
OSC from REAPER: /fxparam/4/value/str 10000.0
OSC from REAPER: /track/1/fx/1/fxparam/4/value 0

OSC to REAPER: /fxparam/4/value 0.25
OSC from REAPER: /fxparam/4/value/str 0.0
OSC from REAPER: /track/1/fx/1/fxparam/4/value 0.25

OSC to REAPER: /fxparam/4/value 0
OSC from REAPER: /fxparam/4/value/str 2500.0
OSC from REAPER: /track/1/fx/1/fxparam/4/value 0
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 05-12-2012, 05:50 AM   #529
musicbynumbers
Human being with feelings
 
musicbynumbers's Avatar
 
Join Date: Jun 2009
Location: brighton, uk
Posts: 12,745
Default

Hi all I came across this app the other day https://www.youtube.com/watch?v=VuQ0K...e_gdata_player and wasn't sure if it has been mentioned before or even a decent thread to put it in (since searching the forum thread titles for "OSC" comes up with nothing for some reason)

Hope someone can put it in the right place
musicbynumbers is online now   Reply With Quote
Old 05-12-2012, 09:54 AM   #530
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by musicbynumbers View Post
Hi all I came across this app the other day https://www.youtube.com/watch?v=VuQ0K...e_gdata_player and wasn't sure if it has been mentioned before or even a decent thread to put it in (since searching the forum thread titles for "OSC" comes up with nothing for some reason) [...]
I think that's johnrule's stuff, which can also be found using the links on his sig.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 05-12-2012, 01:17 PM   #531
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default [FR] + start/stop touch parameter (for "touch" automation mode)

I'd like to request an OSC message pattern that can tell REAPER when the user starts/stops touching any parameter, in order to be able to use REAPER's "touch" automation mode with OSC control surfaces.

Ideally we would be able to get the same information sent from REAPER to the control surface as well when the user starts/stops touching a parameter in REAPER.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 05-12-2012, 01:28 PM   #532
musicbynumbers
Human being with feelings
 
musicbynumbers's Avatar
 
Join Date: Jun 2009
Location: brighton, uk
Posts: 12,745
Default

thanks for that info plus your above idea is a very very good one!

Quote:
Originally Posted by Banned View Post
I'd like to request an OSC message pattern that can tell REAPER when the user starts/stops touching any parameter, in order to be able to use REAPER's "touch" automation mode with OSC control surfaces.

Ideally we would be able to get the same information sent from REAPER to the control surface as well when the user starts/stops touching a parameter in REAPER.
musicbynumbers is online now   Reply With Quote
Old 05-12-2012, 01:33 PM   #533
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by musicbynumbers View Post
thanks for that info plus your above idea is a very very good one!
Thanks.

I still don't think I have a good idea of how I'd like such messages to look like exactly though. Adding separate patterns with "/touch" suffixes everywhere seems overkill... but sending strings like "start" and "stop" to addresses that otherwise expect float or integer numbers may be confusing as well.

Any suggestions welcome, of course!
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 05-13-2012, 11:24 AM   #534
mim
Human being with feelings
 
Join Date: Mar 2009
Posts: 346
Default

Quote:
Originally Posted by Banned View Post
Thanks.

I still don't think I have a good idea of how I'd like such messages to look like exactly though. Adding separate patterns with "/touch" suffixes everywhere seems overkill... but sending strings like "start" and "stop" to addresses that otherwise expect float or integer numbers may be confusing as well.

Any suggestions welcome, of course!
It took me 2 months to realize it is not possible to use the touch mode with an OSC controller. I was sure it was my usine patch that was wrong.

The Idea to send
touch/track/volume 1
when I'm hitting the track OSC fader then
touch/track/volume 0
when I'm not touching it anymore
is ok for me...

Using touch automation mode with an OSC control surface is an absolute need. It is very strange it hasn't been considered ( I was thinking Reaper would stay on touch mode if it receive regulary enough data, but it doesn't seem to be the case).
mim is offline   Reply With Quote
Old 05-18-2012, 02:03 PM   #535
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by Default.ReaperOSC
# DEVICE_EQ determines whether sending any FX_EQ message will automatically insert
# ReaEQ on the target track if it does not exist, or the message will only affect
# an existing instance of ReaEQ.
# Allowed values: INSERT, EXISTING
The default setting for this is "INSERT":
Code:
DEVICE_EQ INSERT
However, changing this setting to "EXISTING" like below does not work, REAPER reports an error:
Code:
DEVICE_EQ EXISTING
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 06-03-2012, 05:44 AM   #536
gardsted
Human being with feelings
 
Join Date: Jul 2007
Posts: 8
Default Pylotech.py: Dump all OSC messages from Reaper to text file in pretty format

I don't know if any did similar - but I wanted to see 'what I could get', so I made this python script to help me out - maybe somebody else likes it:

Usage:

Start this script in a terminal (python pylotech.py)
Fool around in reaper, adding tracks, play, record or whatever
type /play 1 in terminal to make reaper play
type /stop in terminal to make reaper stop
type quit to dump all received data to 'reaper_osc.txt'

This file will look like below but nicely indented which is not shown here:

{ 'autorecarm': { '#d': [0.0], '#m': None, '#t': 'f'},
'beat': { '#m': None, 'str': { '#d': ['1.1.00'], '#m': None, '#t': 's'}},
'bymarker': { '#d': [0.0], '#m': None, '#t': 'f'},
'device': { '#m': None,
'fx': { '#m': None,
'select': { '#m': None,
'1': { '#d': [0.0], '#m': None, '#t': 'f'},
'2': { '#d': [0.0], '#m': None, '#t': 'f'},
'3': { '#d': [0.0], '#m': None, '#t': 'f'},
'4': { '#d': [0.0], '#m': None, '#t': 'f'},
'5': { '#d': [0.0], '#m': None, '#t': 'f'},
'6': { '#d': [0.0], '#m': None, '#t': 'f'},
'7': { '#d': [0.0], '#m': None, '#t': 'f'},
'8': { '#d': [0.0], '#m': None, '#t': 'f'}}},

...

'time': { '#d': [0.0],
'#m': None,
'#t': 'f',
'str': { '#d': ['0:00.000'], '#m': None, '#t': 's'}},
'track': { '#m': None,
'1': { '#m': None,
'autolatch': { '#d': [0.0], '#m': None, '#t': 'f'},
'autoread': { '#d': [0.0], '#m': None, '#t': 'f'},
'autotouch': { '#d': [0.0], '#m': None, '#t': 'f'},
'autotrim': { '#d': [1.0], '#m': None, '#t': 'f'},
'autowrite': { '#d': [0.0], '#m': None, '#t': 'f'},
...

'master': { '#m': None,
'send': { '#m': None,
'1': { '#m': None,
'name': { '#d': ['Left Output'],
'#m': None,
'#t': 's'}}},
'vu': { '#d': [0.0], '#m': None, '#t': 'f'}},
'play': { '#d': [0.0], '#m': None, '#t': 'f'},
'playrate': { '#d': [0.20000000298023224],
'#m': None,
'#t': 'f',
'raw': { '#d': [1.0], '#m': None, '#t': 'f'}},
'record': { '#d': [0.0], '#m': None, '#t': 'f'},
'samples': { '#d': [0.0],
'#m': None,
'#t': 'f',
'str': { '#d': ['0'], '#m': None, '#t': 's'}},


...

and it is pretty long
Attached Images
File Type: jpg pylotech.jpg (26.9 KB, 128 views)
Attached Files
File Type: zip pylotech.zip (1.5 KB, 102 views)

Last edited by gardsted; 06-03-2012 at 05:51 AM. Reason: indent not shown
gardsted is offline   Reply With Quote
Old 06-05-2012, 08:15 AM   #537
keys
Human being with feelings
 
keys's Avatar
 
Join Date: Jul 2008
Location: South Coast, England
Posts: 695
Default

Quote:
Originally Posted by schwa View Post
The latest prereleases of REAPER have preliminary support for using OSC devices as control surfaces. Please use this thread to report bugs or request features.

For example, what would be the best way for us to support messages to implement an XY or XYZ pad? Here is one possibility, which could support multiple XY or XYZ pads:

FX_ASSIGN_X /x/@/track/@/fx/@/fxparam/@
FX_ASSIGN_Y /y/@/track/@/fx/@/fxparam/@
FX_ASSIGN_Z z/@/track/@/fx/@/fxparam/@
FX_XY_VALUES /xy/@/value (+2 arguments)
FX_XYZ_VALUES /xyz/@/value (+3 arguments)
Hi Schwa,
Has something like this been implemented for XY pads please?
I've tried to get an XY pad to work in TouchOSC but can only get one axis to be seen using the FX_PARAM_VALUE pattern.
Many thanks,
keys.

edit: now working just fine - see http://forum.cockos.com/showthread.php?t=108269 post #8

Last edited by keys; 08-17-2012 at 11:03 AM. Reason: Now working XY pad!
keys is offline   Reply With Quote
Old 06-30-2012, 05:58 AM   #538
daxliniere
Human being with feelings
 
daxliniere's Avatar
 
Join Date: Nov 2008
Location: London, UK
Posts: 1,933
Default

Hey guys,
Today I discovered a bug.

I'm using the LogicPad layout on an iPad and I noticed that on the "Channel Strip" tab, the inserts are displayed incorrectly.

The best way to recreate this is to insert 2 plugins on a track, then go to the Channel Strip tab and select the track you just added plugins to.

You will notice a problem with the "INSERT ON" and "EDIT" widgets.
The names of the 2 plugins you inserted are correctly displayed at the top, but the horizontal bars that form the enable/disable buttons are reversed (insert #1 is at the bottom, insert #2 is above that).
This bug is also present in the "EDIT" column, which allows you to select which plugins' parameters you will edit with the 16 rotary controls on the right of the screen.

I'm using TouchOSC 1.8.1


Please ask if you need more info to hunt down this bug.

Cheers,
Dax.
__________________
Dax Liniere
London's newest premium studio complex! (Facebook)
[i7-4790K, 12Gb RAM, Win8.1x64, NVidia GT710, UAD2-OCTO, FireFaceUFX, REAPER x64]
daxliniere is offline   Reply With Quote
Old 06-30-2012, 08:57 AM   #539
Coachz
Human being with feelings
 
Coachz's Avatar
 
Join Date: Oct 2010
Location: Charleston, SC USA
Posts: 7,305
Unhappy

I'm stunned that touch doesn't work. This is 100% useless to me without touch automation. So disappointed.

Can this be added IMMEDIATELY ?? I don't want to buy some hardware just for this please .

Quote:
Originally Posted by mim View Post
It took me 2 months to realize it is not possible to use the touch mode with an OSC controller. I was sure it was my usine patch that was wrong.

The Idea to send
touch/track/volume 1
when I'm hitting the track OSC fader then
touch/track/volume 0
when I'm not touching it anymore
is ok for me...

Using touch automation mode with an OSC control surface is an absolute need. It is very strange it hasn't been considered ( I was thinking Reaper would stay on touch mode if it receive regulary enough data, but it doesn't seem to be the case).
Coachz is online now   Reply With Quote
Old 07-01-2012, 07:36 AM   #540
daxliniere
Human being with feelings
 
daxliniere's Avatar
 
Join Date: Nov 2008
Location: London, UK
Posts: 1,933
Default

Quote:
Originally Posted by Coachz View Post
I'm stunned that touch doesn't work. This is 100% useless to me without touch automation. So disappointed.
Yeah, it's quite a shame, really. There is a lot of potential in OSC.
__________________
Dax Liniere
London's newest premium studio complex! (Facebook)
[i7-4790K, 12Gb RAM, Win8.1x64, NVidia GT710, UAD2-OCTO, FireFaceUFX, REAPER x64]
daxliniere is offline   Reply With Quote
Old 07-11-2012, 12:10 PM   #541
Viente
Human being with feelings
 
Viente's Avatar
 
Join Date: Feb 2012
Posts: 1,972
Default

So i was try to set my custom layout for selecting samples via OSC control surface using Media Explorer, but looks like there are no actions for moving up and down inside shortcuts area and to move to the files tab, so all the actions for moving up and down inside folder tab are useless if you're using OSC only, beucase when you open Media Explorer you can't do nothing.

So at least 3 new actions are needed

- Move up/down inside shorcuts area
- Switch active tab

And each time i open a folder in ME it lost focus so i cant use OSC again
Viente is offline   Reply With Quote
Old 07-11-2012, 09:13 PM   #542
pianogineer
Human being with feelings
 
Join Date: Nov 2011
Posts: 105
Default

Is there a way to force Reaper to dump "all" OSC values specified in the configuration file? I'm struggling with getting my OSC template filled out upon connecting. The only way I've been able to reliably do it so far is to "Edit" the OSC connection within REAPER (even without changing anything) and hit OK, at which point all the parameters are sent.

Opening/closing the mixer sends "some", but things like names/labels don't always seem to be sent.

Would be great if there were just an action to dump everything.
pianogineer is offline   Reply With Quote
Old 07-11-2012, 11:38 PM   #543
wolfgerb
Human being with feelings
 
Join Date: Dec 2011
Location: austria
Posts: 257
Default

Quote:
Originally Posted by pianogineer View Post
Is there a way to force Reaper to dump "all" OSC values specified in the configuration file? I'm struggling with getting my OSC template filled out upon connecting. The only way I've been able to reliably do it so far is to "Edit" the OSC connection within REAPER (even without changing anything) and hit OK, at which point all the parameters are sent.

Opening/closing the mixer sends "some", but things like names/labels don't always seem to be sent.

Would be great if there were just an action to dump everything.
I'm not at my omputer now, but there shold be a "refresh all control surfaces" action or something like that.

wolfger
wolfgerb is offline   Reply With Quote
Old 07-12-2012, 09:23 AM   #544
pianogineer
Human being with feelings
 
Join Date: Nov 2011
Posts: 105
Default

Quote:
Originally Posted by wolfgerb View Post
I'm not at my omputer now, but there shold be a "refresh all control surfaces" action or something like that.

wolfger
Ah thanks! Looks like it's called "Control surface: refresh all surfaces". Will have to give it a shot tonight
pianogineer is offline   Reply With Quote
Old 07-13-2012, 09:45 AM   #545
pianogineer
Human being with feelings
 
Join Date: Nov 2011
Posts: 105
Default

Tried out the new FX_EQ OSC messages with version 4.25. Things seem to be working generally well. I wasn't getting any feedback from REAPER for either the /fxeq/gain or /fxeq/gain/str messages. Other parameters seemed to be feeding back ok, so don't believe it's my setup, but I could have been screwing something up. Can anyone else confirm?

Also, a FR... it seems like it would be VERY useful to be able to enable/disable specific bands with OSC messages. The way it is now, once you put in a hi-pass or lo-pass, there's no way to completely get rid of it, as the gain doesn't really do anything for HP/LP filters, and you can't quite get rid of the effects by adjusting the Q. But, I noticed the enable/disable band is not even available as a normal parameter, so seems it would require a ReaEQ change as opposed to just adding OSC support for those functions.
pianogineer is offline   Reply With Quote
Old 07-22-2012, 05:44 PM   #546
pbk
Human being with feelings
 
pbk's Avatar
 
Join Date: Jul 2009
Location: Afford Slaughterhouse, FL
Posts: 622
Default

Quote:
Originally Posted by wolfgerb View Post
Since we have a " Go to region 01 after...." action now, would`t it be great
to have a the possibility of Reaper transmitting the region names (and marker names)
like it does with the track names?

Thanx Wolfger
Bumping this. Is there currently any way to retrieve the region and marker names using OSC?
__________________
It takes an ordered complex system to recognize another ordered complex system.
pbk is offline   Reply With Quote
Old 08-19-2012, 09:19 AM   #547
diversgens
Human being with feelings
 
Join Date: Oct 2010
Location: France
Posts: 125
Default

Quote:
Originally Posted by Banned View Post
The default setting for this is "INSERT":
Code:
DEVICE_EQ INSERT
However, changing this setting to "EXISTING" like below does not work, REAPER reports an error:
Code:
DEVICE_EQ EXISTING
I confirm this.
And i can't get the FX_EQ_BAND gain,freq and q working, no move on the slider or point in the relative band.
diversgens is offline   Reply With Quote
Old 08-20-2012, 01:31 PM   #548
diversgens
Human being with feelings
 
Join Date: Oct 2010
Location: France
Posts: 125
Default

Quote:
Originally Posted by diversgens View Post
I confirm this.
And i can't get the FX_EQ_BAND gain,freq and q working, no move on the slider or point in the relative band.
my bad the FX_EQ_BAND are working, it's just a little bit tricky to use it with Lemur, i have to use double @ for the band number ...
diversgens is offline   Reply With Quote
Old 08-21-2012, 08:45 AM   #549
diversgens
Human being with feelings
 
Join Date: Oct 2010
Location: France
Posts: 125
Default

Quote:
Originally Posted by diversgens View Post
my bad the FX_EQ_BAND are working, it's just a little bit tricky to use it with Lemur, i have to use double @ for the band number ...
And it's not working as expect using the double @@ just work with the eq on Master track, as soon as i select another channel the band aren't working anymore. The syntax for the band is the same as send but using the same pattern structure doesn't work with bands, LowPass and HighPass works as expected on selected channel.
Other bug Reaper doesn't send the string for EQ master gain and eq wet/dry nor the value.

Has someone try the eq over OSC to confirm or deny this eventually bugs.
diversgens is offline   Reply With Quote
Old 08-21-2012, 11:32 AM   #550
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by diversgens View Post
[...] Has someone try the eq over OSC to confirm or deny this eventually bugs.
I had a look at the OSC specs for (Rea)EQ, but didn't like much about it. I had a quick test, was able to create and send stuff to ReaEQ, but was not able to receive anything back. Why are there even separate message patterns for different band types? And can we not change a band's type via OSC, like we can on the GUI? To me, it feels like a hack to work around missing *regular* 'band type' parameters. And why can't we add or remove bands either? And why does it not make a distinction between inserting a new instance or targeting an existing one, is it unable to remove an instance, target more than a single instance on a track?

Oh, and can you imagine the horror of adding hundreds of different OSC message patterns to support a handful of Cockos in-house effects? The OSC namespace is becoming a huge mess this way. :/

As far as I'm concerned, I vote to just start fixing ReaEQ's many issues before giving it any special treatment here. For example, fix the sloppy curve for its 'Log-scaled automated frequencies'. And *please* stop linking its gain parameters to the setting in Preferences > Appearance > VU Meters/Faders > Volume fader range, it doesn't make any sense. That setting is misleading at best, as it is doing things that are completely different from what it says, and it is *not* a matter of 'appearance' at all.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 08-21-2012, 01:50 PM   #551
diversgens
Human being with feelings
 
Join Date: Oct 2010
Location: France
Posts: 125
Default

Thanks Banned for your answer, i'm agree with you on some points regarding the way ReaEQ osc support has been developed but this is better than nothing.

In an other way i'm disappointed by the lack of further developments in osc since the two last release, for me for me it was fun (and painful) to work on it with Lemur and my major complain is that it has been essentially implement in Touchosc in mind and a lot of Lemur possibilities can't be use at the moment. I really hope that Schaw will come back here with good news regarding new features in the next release (and bugs solving ...)
diversgens is offline   Reply With Quote
Old 08-21-2012, 02:18 PM   #552
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by diversgens View Post
Thanks Banned for your answer, i'm agree with you on some points regarding the way ReaEQ osc support has been developed but this is better than nothing.

In an other way i'm disappointed by the lack of further developments in osc since the two last release, for me for me it was fun (and painful) to work on it with Lemur and my major complain is that it has been essentially implement in Touchosc in mind and a lot of Lemur possibilities can't be use at the moment. I really hope that Schaw will come back here with good news regarding new features in the next release (and bugs solving ...)
Yeah, I was hoping for a bit more as well. Perhaps it is a good idea to consolidate our outstanding FRs into the tracker? This is becoming quite a long thread already, isn't it.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 08-21-2012, 02:32 PM   #553
diversgens
Human being with feelings
 
Join Date: Oct 2010
Location: France
Posts: 125
Default

Quote:
Originally Posted by Banned View Post
Yeah, I was hoping for a bit more as well. Perhaps it is a good idea to consolidate our outstanding FRs into the tracker? This is becoming quite a long thread already, isn't it.
For sure, and a very helpfully one ... without it i'm sure i wouldn't have find enough energy to do the Lemur template
diversgens is offline   Reply With Quote
Old 08-23-2012, 09:18 AM   #554
diversgens
Human being with feelings
 
Join Date: Oct 2010
Location: France
Posts: 125
Red face By bad ...

Quote:
Originally Posted by diversgens View Post
And it's not working as expect using the double @@ just work with the eq on Master track, as soon as i select another channel the band aren't working anymore. The syntax for the band is the same as send but using the same pattern structure doesn't work with bands, LowPass and HighPass works as expected on selected channel.
Other bug Reaper doesn't send the string for EQ master gain and eq wet/dry nor the value.

Has someone try the eq over OSC to confirm or deny this eventually bugs.
It works, no bug in band control .... sorry for the false informations!!
diversgens is offline   Reply With Quote
Old 08-25-2012, 07:16 PM   #555
Kadmium
Human being with feelings
 
Join Date: Aug 2012
Posts: 11
Default

Reaper seems to have stopped sending automated FX Param updates for me in 4.261. Is that a side effect of the new touch automation support? Is there a way to change this behavior?
Kadmium is offline   Reply With Quote
Old 09-06-2012, 11:47 PM   #556
pianogineer
Human being with feelings
 
Join Date: Nov 2011
Posts: 105
Default

Quote:
Originally Posted by Kadmium View Post
Reaper seems to have stopped sending automated FX Param updates for me in 4.261. Is that a side effect of the new touch automation support? Is there a way to change this behavior?
This! I'm just delving in and didn't realize it was tied to 4.261 specifically. I'll try downgrading...

EDIT: Went all the way back to 4.22, and still can't get REAPER to send:

"FX_PARAM_VALUE n/track/@/fx/@/fxparam/@/value"

I simply get nothing...

EDIT 2: The only thing I can get to work is using the "FX_PARAM_VALUE n/fxparam/@/value" message. As soon as I add a second (or third) wildcard, I get nothing fed back. I can, however, set parameters via messages with 2 or 3 wildcards.

Last edited by pianogineer; 09-07-2012 at 12:17 AM.
pianogineer is offline   Reply With Quote
Old 09-07-2012, 07:41 AM   #557
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by pianogineer View Post
This! I'm just delving in and didn't realize it was tied to 4.261 specifically. I'll try downgrading...

EDIT: Went all the way back to 4.22, and still can't get REAPER to send:

"FX_PARAM_VALUE n/track/@/fx/@/fxparam/@/value"

I simply get nothing...

EDIT 2: The only thing I can get to work is using the "FX_PARAM_VALUE n/fxparam/@/value" message. As soon as I add a second (or third) wildcard, I get nothing fed back. I can, however, set parameters via messages with 2 or 3 wildcards.
I can confirm it is broken.

However, I have different results when trying to determine where it exactly broke. I just tried the 32-bit OS X installers, and "FX_PARAM_VALUE n/track/@/fx/@/fxparam/@/value" still worked as expected on version 4.22 for me. It still worked on 4.25 as well as the first three 4.26 pre-releases. Then it stopped working on 4.26pre4.

So it indeed seems to be related to the addition of touch-sensitive automation:

Quote:
v4.26pre4 - July 25 2012
+ ASIO: improved samplerate changing behavior
# ASIO: hopefully fixed samplerate changing related crash introduced in pre3 with some drivers
+ ReaControlMIDI: improved automation of snap-to-scale root and scale type
+ API: added functions to count, get, and set tempo/time signature markers
+ API: added function to get or insert FX by name
+ OSC: added explicit volume/pan automation touch messages
+ Video: Added menu item to get the current video file properties
+ Video/FFMPEG: Added FFMPEG DLL path info in video file properties dialog
+ Video/FFMPEG: Added button in render dialog to grab the current video file's width/height/framerate
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 09-07-2012, 07:59 AM   #558
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 10,255
Default

We'll fix the FX parameter feedback problem for the next build. EQ API improvements are also on the way, but probably not for the very next release.
schwa is offline   Reply With Quote
Old 09-07-2012, 08:59 AM   #559
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Thanks!

Good to hear you're taking the time to improve the API for EQ. Please also give a bit of thought to improving/expanding the touch sensitive automation API when you get around to it. I'm really looking forward to being able to use it more generally, and with plugin parameters in particular.

May I also suggest giving a bit of thought to WALTER? It would be pretty awesome, especially in the context of the in-house EQ and dynamics plugins, if there would be some way to link different WALTER layouts/layout types to different 'standard', console type of effects (perhaps by expanding support for different Track FX parameters?). That is, when (programatically) adding an instance of ReaEQ to a track, automatically make dedicated EQ controls appear on the TCP/MCP (for themes that support it). And I'd bet that White Tie would love to add some very pretty EQ and dynamics knobs and switches to Imperial as well.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 09-07-2012, 09:01 AM   #560
pianogineer
Human being with feelings
 
Join Date: Nov 2011
Posts: 105
Default

Quote:
Originally Posted by schwa View Post
EQ API improvements are also on the way, but probably not for the very next release.
Awesome!
pianogineer is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 03:33 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.