View Issue Details

IDProjectCategoryView StatusLast Update
0002118ardourfeaturespublic2009-07-05 07:12
ReporterAlex Stone Assigned To 
PrioritynormalSeverityminorReproducibilityN/A
Status resolvedResolutionfixed 
Summary0002118: 1) A midi panic button and 2) means of recording audio without having to record midi at the same time.
Description1) This is a feature request for a midi panic/all notes off button (shortcutable) for either each midi track, or globally. It's a really useful feature in other programmes, and i think Ardour would benefit from this too.

2)In testing, i have been unable to use midi to drive a sound source without arming the track for record. That's ok, but if i only want to record the audio, using the midi track as the data driver, then i'd be a bit stuck. I ask you consider a means of getting around this, (Possibly a record arm midi track pause button?) as there are occasions when audio only, driven from midi is desirable.
TagsNo tags attached.

Activities

hansfbaier

2008-04-04 23:23

reporter   ~0004838

2) Why not connect MIDI directly to the softsynth, and the softsynths output to ardour? (Or isnt that what you mean?)

drobilla

2008-12-27 19:51

developer   ~0005548

One issue per ticket please.

1) Panic button added a while ago.
2) This is obviously a bug. "Record arm midi track pause button"? Wow. ;) Fixed now.

seablade

2009-01-28 02:20

manager   ~0005657

Could the OP please check a new version of Ardour 3.0 SVN and see if either of these are still issues? If they are post back up, otherwise I will be resolving this issue in a couple of weeks as they are believed to be fixed. Thanks.

        Seablade

Alex Stone

2009-01-28 05:10

reporter   ~0005662

1) Fixed.

2) Poor explanation on my part.
example:

1 midi track.
1 audio track.

Ardour does monitoring.


engage record arm for both midi and audio. Sound can be heard. Disable either track record arm. no sound. (no midi signal, or no audio signal.)

re-engage both record arms.

Decide what you want to record (monitoring sound as you record), either midi or audio.

Press record/play.

Both tracks get recorded, whether you want this or not. (As both tracks are record armed.)

If we have one midi keyboard inputting to more than one midi track, then auto input is out of the question, as the signal will input to all tracks simultaneously. (auto input must be disengaged to 'isolate' input to a selected, record armed, track)

Suggestion: Creation of a record-arm 'monitor only' state for each track (midi and audio). That way we can engage record arm for the tracks we want, including midi and audio at the same time, but only record either midi or audio if we wish, at the same time retaining the ability to monitor what we're recording, when we're recording.

At revision 4425, this is still a challenge.

drobilla

2009-01-28 05:25

developer   ~0005663

If playback doesn't happen when record isn't armed, that's obviously a bug.

This "workaround" idea of making some kind of weird new record-but-actually-playback state that exists only to allow using record arm to mean playback (which doesn't make sense and is a bug regardless) is beyond insane... I don't think it's the explanation :)

Alex Stone

2009-01-28 05:28

reporter   ~0005664

Dave, I didn't know if this was a bug or simply a feature waiting to happen, hence the beyond insane suggestion. :)

drobilla

2009-01-29 02:10

developer   ~0005677

Convenient as painting bugs as features may be, I don't think we can get away with that one here ;)

seablade

2009-07-05 04:51

manager   ~0006319

So at least the first part of this is no longer an issue, what about the second part? It seems to be what was described is exactly what I would expect, if you record arm a track and hit the transport record it should record every track that is record armed. So I am wondering if this bug is ready to be resolved out or not?

Alex Stone

2009-07-05 06:54

reporter   ~0006334

The issue was (2) being able to record audio driven from a previously recorded midi track, but this is no longer relavent.

So this report is now dead in the water.

Alex.

seablade

2009-07-05 07:12

manager   ~0006335

Resolving out issue then. Thanks.

Issue History

Date Modified Username Field Change
2008-03-10 02:14 Alex Stone New Issue
2008-04-04 23:23 hansfbaier Note Added: 0004838
2008-12-27 19:51 drobilla Note Added: 0005548
2009-01-28 02:20 seablade Note Added: 0005657
2009-01-28 02:20 seablade Status new => feedback
2009-01-28 05:10 Alex Stone Note Added: 0005662
2009-01-28 05:25 drobilla Note Added: 0005663
2009-01-28 05:28 Alex Stone Note Added: 0005664
2009-01-29 02:10 drobilla Note Added: 0005677
2009-07-05 04:51 seablade Note Added: 0006319
2009-07-05 04:51 seablade Description Updated
2009-07-05 06:54 Alex Stone Note Added: 0006334
2009-07-05 07:12 seablade Note Added: 0006335
2009-07-05 07:12 seablade Status feedback => resolved
2009-07-05 07:12 seablade Resolution open => fixed