+ OSC: support bidirectional communication by setting send and/or receive port to 0 + ReaComp: support TrackFX_GetNamedConfigParm(GainReduction_dB) + Regions: improve handling of tempo envelope when moving or copying regions + VST: support TrackFX_GetNamedConfigParm() with GainReduction_dB to retrieve the current GR from plug-ins that support the Presonus GR API # Notation editor: leave a bit more room for accidentals in proportional spacing mode
__________________ subproject FRs click here note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
Agreed, a way this can be integrated in the mixer would be nice.
Here's a slightly better one:
Anyway... that's enough for now. It would need to have a better scale and labels, and work for gating values properly (I just did a super naive version in like 2 minutes).
__________________ subproject FRs click here note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
+ OSC: support bidirectional communication by setting send and/or receive port to 0
doesn't work for me (using touch osc). Port 0 seems to disable everything. On other ports, one way remote works as is usual (device -> reaper).
Besides: It would be so nice to have the bidirectional osc feature working with every port. Some guys are using a Behringer x32 together with REAPER. The x32 doesn't allow changing ports.
GainReduction_dB implemented in Track Inspector. cool!
for GR display in mixer... if you are having more than one ReaComp in the FX Chain.. which one to display? The latest one in the chain? a control to choose which one? how?
Also this is not easy. Where do you put the gain reduction in the theme? it could break v5 themes. Things that need new theme elements, are for version 6 I suppose.
doesn't work for me (using touch osc). Port 0 seems to disable everything. On other ports, one way remote works as is usual (device -> reaper).
Besides: It would be so nice to have the bidirectional osc feature working with every port. Some guys are using a Behringer x32 together with REAPER. The x32 doesn't allow changing ports.
You would only set one to 0, the other would need to be valid. So for example if you send OSC to the remote at 192.168.1.99:8000, you could set your receive to enabled, but port 0, and if the other end replies, it will use the reply.
Alternatively if you want you can listen on :9000, and set send to enabled, but port 0, and then if anybody sends to you, they will get any OSC messages that you end up sending.
I've read this multiple times and am having trouble understanding what the 0 achieves. Does it just mean that with the 0 designation that reaper doesn't need to be configured for a specific port ahead of time for the direction of the 0 port?
Very excited for more OSC development as I use reaper live with tablet control!
Quote:
Originally Posted by Justin
You would only set one to 0, the other would need to be valid. So for example if you send OSC to the remote at 192.168.1.99:8000, you could set your receive to enabled, but port 0, and if the other end replies, it will use the reply.
Alternatively if you want you can listen on :9000, and set send to enabled, but port 0, and then if anybody sends to you, they will get any OSC messages that you end up sending.
I've read this multiple times and am having trouble understanding what the 0 achieves. Does it just mean that with the 0 designation that reaper doesn't need to be configured for a specific port ahead of time for the direction of the 0 port?
Very excited for more OSC development as I use reaper live with tablet control!
Using 0 for the send port means that instead of sending to a specific host/port, it will send to whatever host/port was sending to REAPER (on the port specified by the receive section).
Using 0 for the receive port means that instead of listening on a particular port, just listen for replies from the host being sent-TO (that host/port specified in the send section).
You should only use 0 for one of those ports, if you did both then you'd have no way of communicating with anything.
Perhaps we should update the UI for this. Here are the 6 use cases and their current equivalents:
Mode: disabled
current equivalent: unchecked send, unchecked receive boxes
Mode: separate send/receive
configurable options: receive port, send host/port
current equivalent: checked send, host/port specified, checked receive, receive port specified
Mode: send to remote
configurable options: send host/port
current equivalent: checked send, host/port specified, checked receive, receive port=0
Mode: send to remote (ignore responses)
configurable options: send host/port
current equivalent: checked send, host/port specified, unchecked receive
Mode: receive from remote
configurable options: receive port
current equivalent: checked send, send port=0, checked receive, receive port specified
Mode: receive-only from remote (do not send)
configurable options: receive port
current equivalent: unchecked send, checked receive, receive port specified
Maybe that is a new feature ovnis? I didn't notice it in pre 11, but I think someone was asking for that before. In 5.62 the arrow won't enter another region...
edit. Well, maybe it's complicated. I didn't test that much. Except seems like moving region with it's own time sig there is not working right...
edit2. Re-read the older threads. I guess it's been around for several phases now. Well, I will leave the first edit uncovered because the time signature part seems wrong too.
One more insert point vs time signature pic. I will stop that now.
For some reason the first point to be inserted doesn't cause it, but the second point to be inserted does. If I undo the point inserted on right of peak and just put in the point on the left of the peak, it still causes the damage.
edit. I see from watching the gif that the points by the tool tip get messed up with the point on the right of the peak...
+ ReaComp: support TrackFX_GetNamedConfigParm(GainReduction_dB) + VST: support TrackFX_GetNamedConfigParm() with GainReduction_dB to retrieve the current GR from plug-ins that support the Presonus GR API
This is fantastic!
Looking forward to see how this will be implemented on the GUI-side.
Is there a list of vendors that supports this Gain reduction reporting?
I am delighted about these improvements in Region vs tempo envelope!
When there are two tempo markers at the same position, their order should carefully be preserved. At present, if I try to edit the value of one tempo marker in such a doublet via the "Edit Tempo/Time Signature" dialog box, the order of the tempo markers is changed:
Before editing:
After editing in timebase = Time, the order of the edited marker is changed:
(The 80bpm marker gets placed before the edited 180bpm marker.)
After editing in timebase = Beats, the order of earlier markers is also changed:
(The 149.091 tempo gets placed before the 236.364 tempo.)
+ OSC: support bidirectional communication by setting send and/or receive port to 0
I have no idea about the technical background within the program but can we hope that midi feedback maybe also implemented once you are on it or is this something different internally?
In case something is unclear - I am talking about that FR. In the end it's just the same just for midi protocol.
+ Regions: improve handling of tempo envelope when moving or copying regions
I'm always happy to see improvements here.
Last project I needed to take out 8 bars in the middle of a 50 track project, with tempo env. etc.
It's a very delicate thing
Using 0 for the send port means that instead of sending to a specific host/port, it will send to whatever host/port was sending to REAPER (on the port specified by the receive section).
Using 0 for the receive port means that instead of listening on a particular port, just listen for replies from the host being sent-TO (that host/port specified in the send section).
You should only use 0 for one of those ports, if you did both then you'd have no way of communicating with anything.
...
I'm sorry but I still don't get it work: I learnt a parameter with my touchOSC capable android device. Remote controlling that parameter from android->reaper direction does work as always. I now expect touchOSC to react as soon as I move that parameter in reaper using my mouse. That does not happen.
In touchOSC I use port 9000 for incoming and port 8000 for outgoing signals. Changes here don't bring any improvement.
I even tried it using port 0 (receive) and port 9000 (send) in reaper which means the one way direction breaks.
Bug :
The region shouldn't go below the other region...
The problem is probably that in your project, region 57 starts just before the bar 28 gridline. Could you post the project that contains these regions? You can delete all of the FX and media.
Just dreaming a bit about the GR display feature...
If / When we're there that this can be integrated in Reaper's GUI / mixer, my hope would be that we could also use this not only for displaying GR but also custom meters (e.g. have a JS / VST that calculates RMS / Loudness and display its levels in the mixer).
I'm sorry but I still don't get it work: I learnt a parameter with my touchOSC capable android device. Remote controlling that parameter from android->reaper direction does work as always. I now expect touchOSC to react as soon as I move that parameter in reaper using my mouse. That does not happen.
In touchOSC I use port 9000 for incoming and port 8000 for outgoing signals. Changes here don't bring any improvement.
I even tried it using port 0 (receive) and port 9000 (send) in reaper which means the one way direction breaks.
Your screenshot looks correct -- as to why touchOSC doesn't react, that is unclear (does touchOSC listen for replies?). Might help to use WireShark to see if the network packets are being sent (if they are, then it's touchOSC's issue, probably)
I can't import settings of a configuration. The problem has appeared from version 5.62. In portable version 5.62 there is no problem - everything is ok. Version of x64 RUS Windows 7 OS. In a name of the account there is Cyrillics - the Russian word "Administrator"
I can't import settings of a configuration. The problem has appeared from version 5.62. In portable version 5.62 there is no problem - everything is ok. Version of x64 RUS Windows 7 OS. In a name of the account there is Cyrillics - the Russian word "Administrator"
Ah yes, it looks like import of configuration that has non-latin characters in the path does not work on Windows. Fixing!
I am delighted about these improvements in Region vs tempo envelope!
When there are two tempo markers at the same position, their order should carefully be preserved. At present, if I try to edit the value of one tempo marker in such a doublet via the "Edit Tempo/Time Signature" dialog box, the order of the tempo markers is changed:
If two tempo markers at same time positions, editing the first one (the one that is connected to earlier points) via the dialog box will make a later tempo marker disappear:
* It doesn't matter whether the points are linear or square, or whether timebase is beats or time.
* Editing by dragging the tempo envelope point or segment works fine.