Re: [Rosegarden-user] Questions about audio playback and MIDI connections

2020-06-30 Thread Ted Felix

On 6/30/20 1:11 PM, Malhaire Christophe wrote:
AlsaDriver::setPlausibleConnection: connection like "24:0 Unitor8 MIDI 1 
(duplex)" requested for device 2
AlsaDriver::setPlausibleConnection: fuzzy match 24:0 XV-5050 MIDI 1 
(duplex) available with fitness 1


  Interesting.  So it looks like we need to more heavily weight the 
name portion and downplay the device/port numbers.  Especially, it 
seems, the device numbers (24 in this case) which can maybe be 
completely ignored since they are completely unpredictable.


  This looks like it might be really easy to fix.  I will have a closer 
look.  Hopefully you can hang around for a couple of weeks and help me 
with the testing.  I should be back to working on rg this weekend.


Ted.


___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] Questions about audio playback and MIDI connections

2020-06-30 Thread Malhaire Christophe

Ted,

Thanks a lot for your answer, here is the content of the Details window. 
In the Manage MIDI Devices window, the connections are not good. For 
example, the Roland XV-5050 device is connected to the 32:5 Motif-R MIDI 
6 (write) output instead of the 24:0 XV-5050 MIDI 1 (duplex) output. And 
the MOTIF RACK device is connected to the 28:0 Unitor8 MIDI 1 (duplex) 
output instead of the 32:0 Motif-R MIDI 1 (duplex) output


Regards.

Rosegarden 20.06 - AlsaDriver [ALSA library version 1.2.2, module 
version 5.4.0-39-lowlatency, kernel version 5.4.0-39-lowlatency]


===

JackDriver::initialise() begin...

JACK server not running

Attempt to start JACK server was made per user config

ALSA Client information:

14,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype 2, ptype 
655362, cap 99]


24,0 - (XV-5050, XV-5050 MIDI 1) (DUPLEX) [ctype 2, ptype 589826, cap 127]

28,0 - (Unitor8, Unitor8 MIDI 1) (DUPLEX) [ctype 2, ptype 589826, cap 127]

28,1 - (Unitor8, Unitor8 MIDI 2) (DUPLEX) [ctype 2, ptype 589826, cap 127]

28,2 - (Unitor8, Unitor8 MIDI 3) (DUPLEX) [ctype 2, ptype 589826, cap 127]

28,3 - (Unitor8, Unitor8 MIDI 4) (DUPLEX) [ctype 2, ptype 589826, cap 127]

28,4 - (Unitor8, Unitor8 MIDI 5) (DUPLEX) [ctype 2, ptype 589826, cap 127]

28,5 - (Unitor8, Unitor8 MIDI 6) (DUPLEX) [ctype 2, ptype 589826, cap 127]

28,6 - (Unitor8, Unitor8 MIDI 7) (DUPLEX) [ctype 2, ptype 589826, cap 127]

28,7 - (Unitor8, Unitor8 MIDI 8) (DUPLEX) [ctype 2, ptype 589826, cap 127]

28,8 - (Unitor8, Unitor8 Broadcast) (DUPLEX) [ctype 2, ptype 589826, cap 
127]


32,0 - (MOTIF-R, MOTIF-R MIDI 1) (DUPLEX) [ctype 2, ptype 589826, cap 127]

32,1 - (MOTIF-R, MOTIF-R MIDI 2) (WRITE ONLY) [ctype 2, ptype 589826, 
cap 74]


32,2 - (MOTIF-R, MOTIF-R MIDI 3) (WRITE ONLY) [ctype 2, ptype 589826, 
cap 74]


32,3 - (MOTIF-R, MOTIF-R MIDI 4) (WRITE ONLY) [ctype 2, ptype 589826, 
cap 74]


32,4 - (MOTIF-R, MOTIF-R MIDI 5) (WRITE ONLY) [ctype 2, ptype 589826, 
cap 74]


32,5 - (MOTIF-R, MOTIF-R MIDI 6) (WRITE ONLY) [ctype 2, ptype 589826, 
cap 74]


32,6 - (MOTIF-R, MOTIF-R MIDI 7) (WRITE ONLY) [ctype 2, ptype 589826, 
cap 74]


32,7 - (MOTIF-R, MOTIF-R MIDI 8) (WRITE ONLY) [ctype 2, ptype 589826, 
cap 74]


Current timer set to "system timer"

AlsaDriver::initialiseMidi - initialised MIDI subsystem

Current timer set to "system timer"

AlsaDriver::setPlausibleConnection: connection like "28:2 MOTIF-R MIDI 3 
(write)" requested for device 0


AlsaDriver::setPlausibleConnection: fuzzy match 32:2 MOTIF-R MIDI 3 
(write) available with fitness 1


AlsaDriver::setRecordDevice - 32:7 failed to subscribe device 1 as 
record port


AlsaDriver::setPlausibleConnection: connection like "28:7 MOTIF-R MIDI 8 
(write)" requested for device 1


AlsaDriver::setPlausibleConnection: fuzzy match 32:7 MOTIF-R MIDI 8 
(write) available with fitness 1


AlsaDriver::setPlausibleConnection: connection like "24:0 Unitor8 MIDI 1 
(duplex)" requested for device 2


AlsaDriver::setPlausibleConnection: fuzzy match 24:0 XV-5050 MIDI 1 
(duplex) available with fitness 1


AlsaDriver::setPlausibleConnection: connection like "28:3 MOTIF-R MIDI 4 
(write)" requested for device 3


AlsaDriver::setPlausibleConnection: fuzzy match 32:3 MOTIF-R MIDI 4 
(write) available with fitness 1


AlsaDriver::setPlausibleConnection: connection like "28:1 MOTIF-R MIDI 2 
(write)" requested for device 4


AlsaDriver::setPlausibleConnection: fuzzy match 32:1 MOTIF-R MIDI 2 
(write) available with fitness 1


AlsaDriver::setPlausibleConnection: connection like "28:4 MOTIF-R MIDI 5 
(write)" requested for device 5


AlsaDriver::setPlausibleConnection: fuzzy match 32:4 MOTIF-R MIDI 5 
(write) available with fitness 1


AlsaDriver::setPlausibleConnection: connection like "32:0 XV-5050 MIDI 1 
(duplex)" requested for device 6


AlsaDriver::setPlausibleConnection: fuzzy match 32:5 MOTIF-R MIDI 6 
(write) available with fitness 1


AlsaDriver::setPlausibleConnection: connection like "28:0 MOTIF-R MIDI 1 
(duplex)" requested for device 7


AlsaDriver::setPlausibleConnection: fuzzy match 28:0 Unitor8 MIDI 1 
(duplex) available with fitness 1


AlsaDriver::setPlausibleConnection: connection like "28:6 MOTIF-R MIDI 7 
(write)" requested for device 8


AlsaDriver::setPlausibleConnection: fuzzy match 32:6 MOTIF-R MIDI 7 
(write) available with fitness 1


AlsaDriver::setPlausibleConnection: connection like "28:1 MOTIF-R MIDI 2 
(write)" requested for device 9


AlsaDriver::setPlausibleConnection: fuzzy match 28:1 Unitor8 MIDI 2 
(duplex) available with fitness 1


AlsaDriver::setPlausibleConnection: connection like "24:1 Unitor8 MIDI 2 
(duplex)" requested for device 10


AlsaDriver::setPlausibleConnection: fuzzy match 28:2 Unitor8 MIDI 3 
(duplex) available with fitness 1


AlsaDriver::setPlausibleConnection: connection like "24:3 Unitor8 MIDI 4 
(duplex)" requested for device 11


AlsaDriver::setPlausibleConnection: fuzzy match 28:3 

Re: [Rosegarden-user] (no subject)

2020-06-30 Thread rhkramer
On Tuesday, June 30, 2020 11:32:34 AM Dan Ritter wrote:
> Does that help?

It sounds like it should help, but not being my problem, I won't be following 
up on it -- I hope it will help the OP and maybe others on the Rosegarden 
list.

If more questions come up, I might (again) forward them to the debian-users 
list.

Thank you very much!


___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


[Rosegarden-user] OT (for the debian-list): Re: Questions about audio playback and MIDI connections

2020-06-30 Thread rhkramer
(Intentionally cross posted)

The following quotes are from an email to a rosegarden mail list -- Rosegarden 
is a music notation (mcow) program.

A user is describing a problem in which it appears the MIDI ports (connected 
via USB ports) change on each boot (or maybe even each start of the Rosegarden 
program).

I just wondered if this is similar to the current Linux behavior related to 
disks wherein, in the old days, disks came up in a consistent order, but 
nowadays (maybe because of systemd?) they (or some of them) can start in 
parallel and thus their device numbers are not consistent.

If a similar problem does exist with USB ports, is there a way to force them 
to be identified in a consistent way on each boot (i.e., something like using 
UUIDs or labels for disks)?

Thanks!

On Tuesday, June 30, 2020 10:46:30 AM Ted Felix wrote:
> On 6/30/20 5:20 AM, Malhaire Christophe wrote:
> > 1) While using Rosegarden, I cannot play a video on Youtube, or play a
> > piece of music using Parole Media Player.
> 
>Off the top of my head, it sounds like those programs likely use
> ALSA, but you have JACK running.  When JACK is running, it takes over
> ALSA and anything trying to use ALSA will be "broken".
> 
>There may be a way to get ALSA and JACK apps to cooperate.  I seem to
> remember an article on the JACK website.  This is a common complaint.
> 
> > 2) Each time the PC and Rosegarden are restarted, I have to check and
> > change my MIDI connections because the MIDI ports of my external USB
> > sound modules are systematically inconsistent (MIDI Playback devices
> > related to MIDI Outputs).
> 
>This is interesting as we've had this complaint before.  I really
> would like to work on fixing this, if possible, but the other user
> reported that the problem went away.
> 
>To get a closer look at what rg is doing to make those connections,
> load a composition, then go to Edit > Preferences... and press the
> "Details..." button next to "Sequencer Status".  This should show you
> the connections it is trying to make.  If you can post what's in there,
> that might help with figuring out what we might be able to do to fix this.
> 
> > I believe Rosegarden has an internal function
> > for "smartly" attaching a MIDI device, according to its name, but it
> > doesn't work for me. Surely I must miss something but what?
> 
>It's all automated, so not really anything you can do.  We need to
> have a closer look and see if anything can be done at all.
> 
> > Is there anything to add to the .rgd file?
> 
>.rgd files are only relevant when you create a new device.  It is the
> .rg file that is driving things from that point on.  It's the exact same
> info, though.
> 
> > But since the port number can change at each boot, or depending on the
> > order in which the devices are turned on, maybe this is not a good
> > method?
> 
>I suspect that is what is really happening.  There's a limit to what
> we can obtain from the drivers.  Therefore there is a limit as to how
> good of a job we can do matching things up.
> 
> > 3) And by the way, where can we find a complete manual about the xml
> > format of .rgd files?
> 
>You'll have to read the code.  We've barely got time to write code
> let alone documentation.  Feel free to create some, though.  We'd be
> happy to post it to the wiki.
> 
> Ted.
> 
> 
> ___
> Rosegarden-user mailing list
> Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user


___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] Questions about audio playback and MIDI connections

2020-06-30 Thread Ted Felix

On 6/30/20 5:20 AM, Malhaire Christophe wrote:
1) While using Rosegarden, I cannot play a video on Youtube, or play a 
piece of music using Parole Media Player.


  Off the top of my head, it sounds like those programs likely use 
ALSA, but you have JACK running.  When JACK is running, it takes over 
ALSA and anything trying to use ALSA will be "broken".


  There may be a way to get ALSA and JACK apps to cooperate.  I seem to 
remember an article on the JACK website.  This is a common complaint.


2) Each time the PC and Rosegarden are restarted, I have to check and 
change my MIDI connections because the MIDI ports of my external USB 
sound modules are systematically inconsistent (MIDI Playback devices 
related to MIDI Outputs).


  This is interesting as we've had this complaint before.  I really 
would like to work on fixing this, if possible, but the other user 
reported that the problem went away.


  To get a closer look at what rg is doing to make those connections, 
load a composition, then go to Edit > Preferences... and press the 
"Details..." button next to "Sequencer Status".  This should show you 
the connections it is trying to make.  If you can post what's in there, 
that might help with figuring out what we might be able to do to fix this.


I believe Rosegarden has an internal function 
for "smartly" attaching a MIDI device, according to its name, but it 
doesn't work for me. Surely I must miss something but what?


  It's all automated, so not really anything you can do.  We need to 
have a closer look and see if anything can be done at all.



Is there anything to add to the .rgd file?


  .rgd files are only relevant when you create a new device.  It is the 
.rg file that is driving things from that point on.  It's the exact same 
info, though.


But since the port number can change at each boot, or depending on the 
order in which the devices are turned on, maybe this is not a good method?


  I suspect that is what is really happening.  There's a limit to what 
we can obtain from the drivers.  Therefore there is a limit as to how 
good of a job we can do matching things up.


3) And by the way, where can we find a complete manual about the xml 
format of .rgd files?


  You'll have to read the code.  We've barely got time to write code 
let alone documentation.  Feel free to create some, though.  We'd be 
happy to post it to the wiki.


Ted.


___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] Add Control Ruler not working as expected in Matrix Editor and a few other questions

2020-06-30 Thread Ted Felix

On 6/29/20 4:41 AM, Hugo van Galen wrote:
I have been using Rosegarden for about a decade now and have been able 
to figure it out using search engines. Lately I ran into an issue that I 
don't remember having before: I noticed that, when in the Matrix Editor, 
the option "View / Rulers / Add Control Ruler / Volume Controller" 
doesn't do anything; yet when in the "Notation Editor" this works fine.


  I can't reproduce this.  But the code does look like it needs some 
review.  The issue will likely become apparent upon cleaning up and 
syncing the relevant routines.


It seems that any other controller except Velocity and Pitch bend only 
work in the Notation Editor.


  Those are handled separately, so it isn't surprising they are not 
affected.


Is there an underlying logical reason for 
this to behave this way -- or is this a bug?


  Sounds like you've found a legitimate bug.  The key routines in 
question are:


MatrixWidget::addControlRuler()
NotationWidget::slotAddControlRuler()

  There are differences that need to be resolved between those two and 
that might clear up the issue.  I don't have time at the moment, but 
should be back to Rosegarden this weekend.  I will have a look then.


- I also wonder whether it is already possible to "remember" the zoom 
options for any given segment as I always find myself tweaking 
these, the default zoom doesn't work for me here. Or am I overlooking 
something obvious in the settings? (Ideally, it would be great if all 
"view" options could be memorised, so when opening the same segment 
later, all zoom options, and controller rulers could be restored.)


  This is very likely an oversight.  I recommend opening a feature 
request on sourceforge:


https://sourceforge.net/p/rosegarden/feature-requests/


- I wonder how the Figuration functionality actually works


  Not my area of expertise.  Somebody here can probably fill in the 
blanks, though.  Then we really should update the documentation based on 
what was found.


Ted.


___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


[Rosegarden-user] Questions about audio playback and MIDI connections

2020-06-30 Thread Malhaire Christophe

Hi,
I now use Rosegarden 20.06 on Ubuntu Studio 20.04 (xfce desktop 
environment) without major problem but I still have some questions about 
things that have worried me for a long time:


1) While using Rosegarden, I cannot play a video on Youtube, or play a 
piece of music using Parole Media Player. The only way I know to work 
around this is to change the settings of QjackCtl:

Execute script after Startup: a2jmidid -e &
Execute script on Shutdown: killall jackd

It works, but I'm not very sure what it does, and above all I wonder if 
there is not an easier way?


2) Each time the PC and Rosegarden are restarted, I have to check and 
change my MIDI connections because the MIDI ports of my external USB 
sound modules are systematically inconsistent (MIDI Playback devices 
related to MIDI Outputs). I believe Rosegarden has an internal function 
for "smartly" attaching a MIDI device, according to its name, but it 
doesn't work for me. Surely I must miss something but what?


Is there anything to add to the .rgd file? For example I have already 
seen something like this, which uses the keyword "connection":


connection="72:0 XV-2020 MIDI 1 (duplex)" type="midi">


But since the port number can change at each boot, or depending on the 
order in which the devices are turned on, maybe this is not a good method?


3) And by the way, where can we find a complete manual about the xml 
format of .rgd files?


Best Regards.

--
Christophe MALHAIRE



___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user