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

2017-01-10 Thread Ted Felix
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 shoul

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

2016-11-06 Thread Ted Felix
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 la

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

2016-11-06 Thread D. Michael McIntyre
On 11/06/2016 03:05 PM, Marko Randjelovic wrote: > I would prefer keeping what user has chosen, including if program is The problem when importing a MIDI file is that the user hasn't chosen anything yet. These settings are stored on a per file basis, and there is no global default setup for th

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

2016-11-06 Thread Marko Randjelovic
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 would prefer keeping w

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

2016-11-06 Thread Marko Randjelovic
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. On 6 November 2016 at 18:01, Ted Felix wrote: > On 11/05/2016 06:15

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

2016-11-06 Thread Ted Felix
On 11/05/2016 06:15 PM, Marko Randjelovic wrote: > 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'm actually looking at this right now in conjunction with

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

2016-11-05 Thread David Jones
Rosegarden is up to 16.06. IIRC I have RG 16.02 or .04 via Debian Testing. I haven't had the same problem with MIDI files. David W. Jones gn...@hawaii.rr.com authenticity, honesty, community http://dancingtreefrog.comOn Nov 5, 2016 12:15, Marko Randjelovic wrote: > > When current project is bla

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

2016-11-05 Thread Marko Randjelovic
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: > > > There are MIDI files that will always set to "no

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

2016-11-05 Thread Abrolag
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 --

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

2016-11-05 Thread Marko Randjelovic
There are MIDI files that will always set to "no port". On 5 November 2016 at 23:45, Marko Randjelovic wrote: > I have to correct myself. No matter what MIDI file I open nor whether > current project is blank or not, sometimes ports are set to "no port" (last > on list) and sometimes settings ar

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

2016-11-05 Thread Marko Randjelovic
I have to correct myself. No matter what MIDI file I open nor whether current project is blank or not, sometimes ports are set to "no port" (last on list) and sometimes settings are set to first on list. If current setting is neither first nor last it is not preserved. On 5 November 2016 at 23:15,

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

2016-11-05 Thread Marko Randjelovic
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. -