0003360: cannot add MIDI track after removing a MIDI track w/ device attached

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0003360

[ardour] bugs

major

always

2010-07-25 07:35

2010-08-14 03:02

Reporter

danboid

View Status

public

Assigned To

cth103

Priority

normal

Resolution

duplicate

Status

resolved

Product Version

SVN 3.0

Summary

0003360: cannot add MIDI track after removing a MIDI track w/ device attached

Description

Create a MIDI track, attach it to a physical MIDI device and record from it. Now delete the MIDI track and try creating a new MIDI track. Under 7490 you get an error like:

[ERROR]: Can not feed IO AUDIO=0:MIDI=0 with diskstream AUDIO=0:MIDI=1
Can not feed IO AUDIO=0:MIDI=0 with diskstream AUDIO=0:MIDI=1
Can not feed IO AUDIO=0:MIDI=0 with diskstream AUDIO=0:MIDI=1
Can not feed IO AUDIO=0:MIDI=0 with diskstream AUDIO=0:MIDI=1
JACK: cannot deliver port registration request
[ERROR]: No more JACK ports are available. You will need to stop Ardour and restart JACK with ports if you need this many tracks.
[ERROR]: could not create a new midi track

Additional Information

Tags

No tags attached.

cost

0.00

Attached Files

Relationships

duplicate of

0003395

resolved

cth103

cannot create new MIDI track after removing one connected to softsynth

Notes
(0008649) cth103 (administrator) 2010-07-25 19:12	I can't reproduce this. Can you give a precise recipe starting from a new session? And perhaps attach the session file just before you remove the track? Thanks.

(0008651) danboid (reporter) 2010-07-26 00:34	He he! OK, so it turns out this was me doing something totally non-sensical, so nothing new there but it has exposed a novel way to mess up Ardour at least :) Under MIDI connection manager -> Track Tab (under Sources) I connected the output of a track to System Tab (under Destinations) a target I obviously didn't realise was called alsa_pcm:USB-Oxygen-49/midi_playback_1 but that keyboard is strictly a MIDI controller. Sorry 'bout that!

(0008834) danboid (reporter) 2010-08-14 01:27	Ooops! This is dupe of 3395 (or rather the other way round) just that now I know users can get this error by deleting a track that was correctly set up whereas here I thought it was just me doing something stupid.

Issue History
Date Modified	Username	Field	Change
2010-07-25 07:35	danboid	New Issue
2010-07-25 11:11	cth103	cost	=> 0.00
2010-07-25 11:11	cth103	Target Version	=> 3.0-beta1
2010-07-25 19:12	cth103	Note Added: 0008649
2010-07-25 19:12	cth103	Status	new => feedback
2010-07-26 00:34	danboid	Note Added: 0008651
2010-08-14 01:27	danboid	Note Added: 0008834
2010-08-14 03:02	cth103	Relationship added	duplicate of 0003395
2010-08-14 03:02	cth103	Status	feedback => resolved
2010-08-14 03:02	cth103	Resolution	open => duplicate
2010-08-14 03:02	cth103	Assigned To	=> cth103