View Issue Details
|ID||Category||Date Submitted||Last Update|
|0003320||bugs||2010-07-16 13:47||2012-06-05 02:17|
|Fixed in Version|
|Summary||0003320: wiimote not corectly initialized|
|Description||svn-ongoing rev7424, as well as ardour 2.8.11|
-create new session
-toggle the wiimote control on in option->control surfaces
-initialize wiimote as explained here: http://ardour.org/node/2158 and in the youtube video.
-ardour does not respond to wiimote.
-now save the session, close and reopen the same session
-go again options->control surfaces and switch the wiimote on, as it is not saved with the session
-now initialize the wiimote again
-ardour now works properly controlled by wiimote
|Additional Information||already in the version 2.8.9 i realized that the wiimote status is not saved with the session, but the bug of having to restart the session in order to control ardour with wiimote is new.|
|Tags||No tags attached.|
i have spoke with sampo in irc about this and we did also some debuging by modifying the libs/surfaces/wiimote/interface.cc.
this was sampos conclusion about this problem:
<sampo_v2> nowhiskey: very interesting. that means there's something wrong
with how ardour initializes the control protocol
<sampo_v2> nowhiskey: it's possible if not likely that other control
protocols suffer from this issue
sampo is right here. i just had the chance to try this with a bcf2000 and it behaves the same in a2 like described above.
||its not likely that this issue will be fixed in 2.X.|
|2010-07-16 13:47||nowhiskey||New Issue|
|2011-03-11 19:05||nowhiskey||Note Added: 0010346|
|2012-02-23 16:03||nowhiskey||Note Added: 0012814|
|2012-02-23 16:04||nowhiskey||Note Edited: 0012814|
|2012-02-27 14:51||cth103||cost||=> 0.00|
|2012-02-27 14:51||cth103||Target Version||=> 3.0|
|2012-06-04 22:56||cth103||Target Version||3.0 => 3.X|
|2012-06-05 02:17||paul||Note Added: 0013378|