Sun Mar 21, 2010 12:52 pm
bug in automation-allocation
i have found that (at least) the dials on LB203 interface does not 'connect' correctly to an automation track. The full span of the dial is not emulated by the automation track. For the 'CUT' dial only barely half of the full movement can be automated.
If the automation-track interface is manually magnified (eg not 'auto'), then it is possible to drag the curve out 'over' its limitation. However, that is not graphically 'shown' -eg the span can be expanded to full, but it is not drawn in the automation-track. It is ofcause not possible to use the sh+click method for smooth curves either.
Please confirm that the automation-track-envelope is one of the highest prioryties for the development team. That part of lmms really brings tears (of anger:) forward.
Automation-envelope and the poor quality of the high/lowpass plugin-filters is the most severe problem in lmms.
BR
i have found that (at least) the dials on LB203 interface does not 'connect' correctly to an automation track. The full span of the dial is not emulated by the automation track. For the 'CUT' dial only barely half of the full movement can be automated.
If the automation-track interface is manually magnified (eg not 'auto'), then it is possible to drag the curve out 'over' its limitation. However, that is not graphically 'shown' -eg the span can be expanded to full, but it is not drawn in the automation-track. It is ofcause not possible to use the sh+click method for smooth curves either.
Please confirm that the automation-track-envelope is one of the highest prioryties for the development team. That part of lmms really brings tears (of anger:) forward.
Automation-envelope and the poor quality of the high/lowpass plugin-filters is the most severe problem in lmms.
BR