|Anonymous | Login | Signup for a new account||2017-05-30 00:21 PDT|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007360||ardour||bugs||public||2017-05-15 14:05||2017-05-29 15:14|
|Product Version||5.X git (version in description)|
|Target Version||Fixed in Version|
|Summary||0007360: OSC fader automation not working for touch mode|
|Description||Bug discovered in the new 5.9 version, the first one providing automation through OSC.|
When a track is set to Touch automation mode Ardour doesn't accept any incoming message to control the fader and overwrite the automation curve. The purpose of touch mode should be to override a part of an automation curve as long the fader is touched. The current implementation doesn't allow to modify the fader position.
|Steps To Reproduce||It can be easily reproduced using the oscsend and oscdump commands:|
1. Start a terminal and open a oscdump session: oscdump 8000
2. Start Ardour and configure the OSC surface properly.
3. Start a second terminal and send the osc setup message:
oscsend localhost 3819 /set_surface iiii 0 159 3 1
4. Then test that ardour faders are capturing fader osc messages, for example:
oscsend localhost 3819 /strip/fader if 1 0.5
5. Set a fader to touch mode and play an automation curve.
6. test again to set fader valu to overwrite the automation curve, for example:
oscsend localhost 3819 /strip/fader if 1 0.2
The result, ardour faders don't modify the automation curve
|Tags||No tags attached.|
|/strip/fader/touch has yet to be added. It is coming though.|
|commit f2aac0bca adds /strip/fader/touch, /strip/gain/touch, /select/fader/touch and /select/gain/touch. I can not think of any reason to add feedback for touch.|
Just testing this feature and I'm not able to control the touch mode using the given commands in ardour 5.9.13 (downloaded today from nightly). I've been trying:
/strip/gain/touch i strip_ssid
/strip/gain/touch if strip_ssid 0 or 1 to enable or disable the touch for a given channel
Ardour log response is always "Unhandled OSC message"
Please can you provide more details about the osc touch messages?
Try /strip/gain/touch ii ssid touch
or /strip/gain/touch/<ssid> i touch
where touch is 1 for start touch and 0 for end touch.
Still not working here using the last nightly build (5.9.2)
OSC fader automation is working perfectly in all modes except the touch message. Ardour log reports the following line:
[INFO]: Unhandled OSC message: /strip/gain/touch i:1 i:1
The same tested for fader mode instead of gain mode produces the same results:
[INFO]: Unhandled OSC message: /strip/fader/touch i:1 i:1
I'm missing some configuration or something?
|commit 1e95ccf fixes this. touch was working, but the logger was wrongly showing "Unhandled" even though the message had been handled correctly.|
Tested today using Ardour 5.9-41 from nightly and still having the "unhandled" message for touch osc messages. Moreover, I think that the touch mode is still not working correctly.
When you draw a fader automation curve (for example using write mode) then this curve is reproduced properly under touch mode and an OSC controlled fader. However, when fader is touched (/strip/fader/touch ssid 1 send) to modify the automation curve it only works for a while. In my opinion, the expected behavior should be:
1- A fader automation curve is being played in touch mode.
2- The sound engineer realizes that the fader must be changed for a passage, so he touches the fader.
3- The /strip/fader/touch message is send to alert Ardour that a fader is being touched.
4- The sound engineer moves the fader in order to overwrite a part of automation curve while the fader is being touched. Here many /strip/fader messages are send to Ardour with new fader position values.
5- The sound engineer released the fader and the /strip/fader/touch ssid 0 message is send, so Ardour keeps playing the previously recorded automation curve.
What is actually happening: Steps 1 to 4 are working fine, but after a few seconds Ardour starts to play back the previous automation curve long time before than receiving the /strip/fader/touch ssid 0 message. I'm missing something? Should I send a "/strip/fader/touch ssid 1" message before every "/strip/fader ssid value"? This make no sense to me because, when a fader is touch, it is touched for a while, a song passage, the chorus part or whatever.
Please, can this be checked? Or in case I'm wrong, can you explain me how the touch mode is supposed to works? Thank you so much.
|2017-05-15 14:05||sapista||New Issue|
|2017-05-15 15:29||ovenwerks||Note Added: 0019700|
|2017-05-16 07:07||ovenwerks||Note Added: 0019703|
|2017-05-16 07:07||ovenwerks||Status||new => resolved|
|2017-05-16 07:07||ovenwerks||Resolution||open => fixed|
|2017-05-16 07:07||ovenwerks||Assigned To||=> ovenwerks|
|2017-05-22 13:52||sapista||Note Added: 0019730|
|2017-05-22 14:21||ovenwerks||Note Added: 0019732|
|2017-05-24 13:34||sapista||Note Added: 0019738|
|2017-05-24 14:03||ovenwerks||Note Added: 0019739|
|2017-05-29 15:14||sapista||Note Added: 0019758|
|Copyright © 2000 - 2017 MantisBT Team|