View Issue Details

IDProjectCategoryView StatusLast Update
0005060ardourbugspublic2020-04-19 20:16
Reporterpneuman Assigned Tonaptastic  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Target Version3.0 
Summary0005060: Can't hear what I'm playing while recording MIDI
DescriptionWhile recording MIDI in to a MIDI track, I can't hear what I'm playing. This affects both tracks with synth plugins (in this case, the plugin outputs no audio) and tracks that feed external MIDI equipment (the track outputs no MIDI).

The problem seems to be monitoring-related. I've left the monitoring for the MIDI track in the default "auto" mode. While the transport is stopped, it switches to "In" monitoring, and I can hear whatever MIDI notes I play. However, as soon as the transport starts rolling, it switches to "Disk" monitoring, and I can no longer hear my input. However, regions already in the track do play.

A simple fix would be to prevent switching to "Disk" monitoring when the transport rolls if the track is armed and recording is enabled, but this would be an incomplete fix: because MIDI regions can be stacked, the user may want to hear both their input *and* whatever regions have already been recorded.

Steps to reproduce:
* Open a new session and add a MIDI track
* Add a synth plugin to the track
* Route input in to the track from a MIDI keyboard
* Hit some keys on the keyboard, and ensure that you can hear the output
* Arm the track, enable recording, and roll the transport
* Hit some keys on the keyboard again -- the data is recorded, but no output is heard
Additional InformationArdour 3 SVN r13103
OS: Ubuntu 12.04 AMD64
TagsNo tags attached.

Activities

froh

2012-09-19 22:57

reporter   ~0014026

I can confirm this on KXStudio 12.04.1
Ardour3.0beta5

paul

2012-12-05 16:08

administrator   ~0014318

rev 13602 has a tentative fix for this issue that needs testing. it handles monitoring for MIDI tracks in exactly the same way as audio tracks.

pneuman

2013-01-20 06:57

reporter   ~0014510

I think this bug can be closed!

system

2020-04-19 20:16

developer   ~0023133

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2012-08-02 23:40 pneuman New Issue
2012-08-05 22:43 cth103 cost => 0.00
2012-08-05 22:43 cth103 Target Version => 3.0
2012-09-19 22:57 froh Note Added: 0014026
2012-12-05 16:08 paul Note Added: 0014318
2012-12-05 16:08 paul Status new => feedback
2013-01-20 06:57 pneuman Note Added: 0014510
2013-03-15 05:49 naptastic Status feedback => resolved
2013-03-15 05:49 naptastic Resolution open => fixed
2013-03-15 05:49 naptastic Assigned To => naptastic
2020-04-19 20:16 system Note Added: 0023133
2020-04-19 20:16 system Status resolved => closed