Re: [Rosegarden-user] Opening MIDI file sets MIDI devices to "no port"

On 11/06/2016 03:05 PM, Marko Randjelovic wrote: > I would prefer keeping what user has chosen, including if program is > terminated and started again. If user didn't yet choose anything or if > chosen device is currently unavailable, then I would prefer assign to > first port found. This

Re: [Rosegarden-user] Opening MIDI file sets MIDI devices to "no port"

On 11/06/2016 07:03 PM, D. Michael McIntyre wrote: > The way it was supposed to work, when you imported MIDI it would try to > fuzzy match you with "General MIDI Device" and try to assign that to a > playable port. That sounds simple. I'll keep it in mind when I get there. > I remember the

Re: [Rosegarden-user] Opening MIDI file sets MIDI devices to "no port"

Of course, since Rosegarden can save its project files, settings should be saved to .rg and restored when file is loaded. But since midi files are not project files, nothing should be changed on loading such files. On 6 November 2016 at 21:05, Marko Randjelovic wrote: > I

Re: [Rosegarden-user] Opening MIDI file sets MIDI devices to "no port"

Because besides such behavior doesn't make any sense, I have many MIDI files and saving all of them as rg files would be impractical. On 6 November 2016 at 00:18, Abrolag wrote: > On Sun, 6 Nov 2016 00:04:33 +0100 > Marko Randjelovic wrote: >

Re: [Rosegarden-user] Opening MIDI file sets MIDI devices to "no port"

On Sun, 6 Nov 2016 00:04:33 +0100 Marko Randjelovic wrote: > There are MIDI files that will always set to "no port". Why not just change the ports to the ones you want then re-save as a Rosegarden file. They will then be remembered. -- W J G

[Rosegarden-user] Opening MIDI file sets MIDI devices to "no port"

When current project is blank, if I open or import any MIDI file, both input and output MIDI devices are set to "no port". At start, Rosegarden sets devices to other then "no port". I use Rosegarden 14.02-2 on Devuan Jessie.