OSC bug reports and feature requests

[lucianoiam]

I created a OSC <-> WebSockets bridge that brings REAPER's OSC API to web applications, it can be grabbed from here https://github.com/lucianoiam/reaper-websockets . Includes a JS client library for easy control of some mixer features. A set of mixer-related widgets is on the way...

[galileon]

Hi,
Do anybody found how to get any message when track is moved to group ( under another track ) ?
Thanx
R.

[Michael200]

Originally Posted by galileon

Hi,
Do anybody found how to get any message when track is moved to group ( under another track ) ?
Thanx
R.

this would also interest me! thanks

[MIDIsince85]

I am looking without much luck so far in these forums for an example, or script, etc that would show me how to translate a MIDI note-on and note-off generated by ReaGate into two corresponding OSC paths and sending that. It must be here somewhere I just haven't found it.

I've found and read the .ReaperOSC file, and THINK I know how, but I'd like to avoid any rabbit hole, dumb approach, or reinventing wheels. Any pointer would be appreciated.

[mschnell]

This can be done by OSCIIBot linked to Reaper by (e.g.) LoopMidi.

Another way might be to move some standard slider or button or so that can be configured to send OSC messages from Reaper (in fact I have no idea which and how to enable the sending of OSC medssages).

To do this you would need to use (e.g.) Midi Conver To CC to create a CC message from the Note, then MidiToReaControlPath to create a Message in the control path and then you can "learn" such a slider/switch/button to it.

-Michael

[MIDIsince85]

Thanks for your quick reply and for these suggestions. I still need to find a solution to the simple problem I described.

[Mr.X]

Originally Posted by schwa

BTW there is an existing protocol for this (though REAPER doesn't support it yet).

http://opensoundcontrol.org/files/osc-query-system.pdf ("current value" being the most interesting part).

Is there a yet a way to poll via OSC for a current value? My thought would be that it would be a simple as not supplying a value for the function.

If a normal command is

/play,f 1

the request/poll command is (without any value)

/play

and reaper would reply

/play,f 1

Being able to poll a track for it's name or a marker for it's name would be amazeballs.

ATM the biggest issue for me is retrieving the current track and marker counts from a project. I can set how many markers and tracks I'd like to receive information from, but no way to determine how many tracks and markers there are in a project.
Maybe if the were changes to the commands like:

DEVICE_TRACK_COUNT *

and

DEVICE_MARKER_COUNT *

Where the * means "how ever many the project has". Also, can these values be changed dynamically?

[Ayejay]

i try to open my project file and it says ( parsing error) and will not open the project please help
. bak file does not load either

[Vin Morgan]

Originally Posted by airon

FR

Smart control resource management.
Nobody can anticipate how many control resources you need for the next mix, which is why consoles have things like focus sections, plugin maps, custom fader groups, group spills(members of group spilled on a set of controls).

In other words, control resources are being reused in different contexts. This is a more general FR, but it applies to OSC as much as it does to midi control sources as well as any natively supported control surface.

The present control resource management is slow to setup because it is buried in submenus and can only be changed one at a time through access to several submenus per parameter.

Default plugin maps can be saved, but you can't use all control resources at your fingertips to do so. If the Mackie control universal is used a control surface, a custom plugin takes over, and the possibility of setting up a default plugin map with that control surface is gone.

I propose to abandon any custom development on your part for control surfaces and instead focus on getting whatever control resources there are available used in a more efficient and useful fashion, and that goes especially for OSC control resources.

The simpler method of accessing plugin parameters is to have a couple of simple methods and controls. You need direct access to these modes plus at least two sets of banking switches in addition to the ones used for track banking(sets) and nudging(single). Each mode access switch toggles in and out of the mode.

• Mode access switches for changing control access of a bunch of control resources to control
  • Sends
    Bank switches A control access to the next/previous set of sends on all tracks. More stuff in regard to access to control parameters like send mute, prefx/postfx/postfader, send type, send source/target,phase,channel count has to be figured out.
    
    
  • Plugins
    Banking switches A control access to the previous and next plugin
    Banking switches B control access to the plugin parameter pages
    Usually this type of parameter access is limited to the knobs of one channel on control surfaces.
    
  • Custom plugin maps
    Banking switches A control access to the previous and next plugin on the channel(not all channels)
    Banking switches B control access to the previous and next pages of plugin parameters.
    
    This kind of plugin control usually takes over a large set of control resources. Most often all controls on sets of four or eight tracks are used.
    
    
  • Group spills
    Spreads all members of group that the currently selected track belongs to on to all track control resources.
    
    Banking switches A control access to the previous and next group.
    
    
  • VCA Masters
    Access all VCA masters and thus give access to
    
  • VCA Master Group Spill(accessed from the VCA Masters mode)
    Access the members of the VCA master. This has proven to be highly usefull in almost any show I've had the chance to use this.
    
    
  • Custom track configurations
    First layer picks the track configuration via any control resources selected to do so. It could be any OSC message, a button or touching a fader.

Ok, so this all looks like hardware control surface stuff, but OSC is actually way more flexible.

With OSC, you can setup commands to go along with the mode switches, to flip to a specific page for TouchOSC for example.

The difficult thing here is presenting this to the user so they can set this stuff up, share it, customize it and back it up.

OSC is just perfect for this, since all the feedback stuff is setup anyway. The hardware control surface folks will require one plugin to present the control resources and the feedback paths correctly to the system.

The editor, that you, Cockos, need to provide for this to work, is a difficult project. I realize that it's asking a lot.

The payoff is that nobody will need to be a programmer any longer to create exceptional control solutions. You will multiplied the number of people that can do this by at least a thousand.

All the MCU folks will be able to share setups for plugins, VCA group spills, custom fader maps. Behringer BCR2000 and BCF2000 can share their most efficient setups, without having to become programmers.

Cockos provides the tools to manage the control resources and control feedback, and the users make the rest happen.

I love the way you think.

[patko]

We don't know if [fx] is enable or disabled through OSC, it would be worth to do it, and be able to enable or disable from OSC interface.

[patko]

The OSC interface send twice all parameters on tab switch. I don't know if it's intentional, it looks like a buggy behavior.

My reaper version is w64 6.14

[patko]

Originally Posted by patko

The OSC interface send twice all parameters on tab switch. I don't know if it's intentional, it looks like a buggy behavior.

My reaper version is w64 6.14

In fact reaper sends all OSC parameters at session closing, that is quite useless. I haven't found an option to prevent this behavior.

So reaper doesn't really send same OSC parameters twice, but send once at session opening and once at session closing, that's why I thought it sent OSC parameters twice at tab switching.

[Burtan]

Hi, is there an api to tell reaper that a new OSC device is in use so that it gets all current values sent? Switching banks results in most needed values being sent, but e.g. pan values are not sent, if they are on the default (0). Not sure if this is a bug.

Also,
TRACK_MONITOR b/track/monitor b/track/@/monitor i/track/monitor i/track/@/monitor
feedback is only given sometimes. This seems to be dependent on the state of the button in Reaper.

One more,
FX_BYPASS b/track/@/fx/bypass
Should bypass the whole fx chain. I don't see an API yet that does that.