Re: [Rosegarden-user] Testing Appreciated for 20.12
On Tue, 10 Nov 2020 10:57:05 +
Will Godfrey wrote:
>Ah! I always keep the setting as 'fixed' so it should be a problem then.
>
should NOT {senior moment!}
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
___
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] Testing Appreciated for 20.12
On Mon, 9 Nov 2020 09:50:09 -0500 Ted Felix wrote: >On 11/8/20 9:39 AM, chuck elliot via Rosegarden-user wrote: >> I presume that this is just the difference between working with a standard, >> gm-based midi device setup VS a custom midi device setup where you have drum >> patches/programs mapped to midi channels other than 10? > > Exactly. Although in a non-GM case, channel 10 is fair game as well. > >> So in the latter case, a channel setting of 'auto' would not work for you as >> it is currently implemented? > > Auto should work in this case (but don't expect much as "auto" has >not been tested in years). It will assign channels and select the >proper patches as needed. > > "Auto" will not work in this situation if you check the "percussion" >checkbox for a track (any track). I believe that checkbox is what sends >the events to channel 10 and that would break Will's setup. > >Ted. Ah! I always keep the setting as 'fixed' so it should be a problem then. -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. ___ 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] Testing Appreciated for 20.12
On 11/8/20 9:39 AM, chuck elliot via Rosegarden-user wrote: I presume that this is just the difference between working with a standard, gm-based midi device setup VS a custom midi device setup where you have drum patches/programs mapped to midi channels other than 10? Exactly. Although in a non-GM case, channel 10 is fair game as well. So in the latter case, a channel setting of 'auto' would not work for you as it is currently implemented? Auto should work in this case (but don't expect much as "auto" has not been tested in years). It will assign channels and select the proper patches as needed. "Auto" will not work in this situation if you check the "percussion" checkbox for a track (any track). I believe that checkbox is what sends the events to channel 10 and that would break Will's setup. 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] Testing Appreciated for 20.12
I presume that this is just the difference between working with a standard, gm-based midi device setup VS a custom midi device setup where you have drum patches/programs mapped to midi channels other than 10? So in the latter case, a channel setting of 'auto' would not work for you as it is currently implemented? CE. On 07/11/2020 9:48 pm, Will Godfrey wrote: On Sat, 7 Nov 2020 16:32:45 -0500 "D. Michael McIntyre" wrote: On 11/7/20 7:27 AM, Ted Felix wrote: Just a follow-up in case someone has a similar issue. Turns out that "auto" mode recognizes "percussion" tracks and sends them to channel 10 no matter what channel they are configured for. That isn't even always correct behavior. I don't have time to get myself back up to speed on all that right now, but I think I can play percussion on channels other than 10 at least two different ways with my current setup, and I don't have anything exotic. I'll try to have a go with some of that before you release. I've been working six days a week most of the year, so no promises. Just jumping in here. I very frequently put percussion in multiple channels. In Yoshimi I have one patch that does very nice snare drums, another that does a range of Cymbals, another that's good for kick drum, shakers etc. Not only can they not all fit in the same channel, but I give them different weights and stereo positions. ___ 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] Testing Appreciated for 20.12
On Sat, 7 Nov 2020 16:32:45 -0500 "D. Michael McIntyre" wrote: >On 11/7/20 7:27 AM, Ted Felix wrote: >> Just a follow-up in case someone has a similar issue. Turns out that >> "auto" mode recognizes "percussion" tracks and sends them to channel 10 >> no matter what channel they are configured for. > >That isn't even always correct behavior. I don't have time to get myself >back up to speed on all that right now, but I think I can play >percussion on channels other than 10 at least two different ways with my >current setup, and I don't have anything exotic. > >I'll try to have a go with some of that before you release. I've been >working six days a week most of the year, so no promises. > Just jumping in here. I very frequently put percussion in multiple channels. In Yoshimi I have one patch that does very nice snare drums, another that does a range of Cymbals, another that's good for kick drum, shakers etc. Not only can they not all fit in the same channel, but I give them different weights and stereo positions. -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. ___ 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] Testing Appreciated for 20.12
On 11/7/20 7:27 AM, Ted Felix wrote: Just a follow-up in case someone has a similar issue. Turns out that "auto" mode recognizes "percussion" tracks and sends them to channel 10 no matter what channel they are configured for. That isn't even always correct behavior. I don't have time to get myself back up to speed on all that right now, but I think I can play percussion on channels other than 10 at least two different ways with my current setup, and I don't have anything exotic. I'll try to have a go with some of that before you release. I've been working six days a week most of the year, so no promises. -- D. Michael McIntyre ___ 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] Testing Appreciated for 20.12
On 11/6/20 7:53 PM, Ted Felix wrote: On 11/6/20 4:16 PM, chuck elliot via Rosegarden-user wrote: One thing that I have noticed in this and previous versions is that my channel setting of 'auto' on a drum track does not appear to be saved in the .rg file and keeps reverting to 'fixed' on reload. This gives me incorrect patch sounds and has to be reset every time. Just a follow-up in case someone has a similar issue. Turns out that "auto" mode recognizes "percussion" tracks and sends them to channel 10 no matter what channel they are configured for. The issue here was that the drum track was being sent to channel 11. In auto mode that is redirected to channel 10 where it belongs. In fixed mode, that plays drums on the piano on channel 11. Switching the track to channel 10 fixes the problem. I still need to fix the save/restore of channel mode regardless of whether auto channel mode is currently supported. 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] Testing Appreciated for 20.12
On 11/6/20 4:16 PM, chuck elliot via Rosegarden-user wrote: One thing that I have noticed in this and previous versions is that my channel setting of 'auto' on a drum track does not appear to be saved in the .rg file and keeps reverting to 'fixed' on reload. This gives me incorrect patch sounds and has to be reset every time. That's odd. I would think the opposite would be true. The "auto" stuff has been abandoned by me in the code and "fixed" is really the only thing that should work. Can you provide a small example file that illustrates the problem? Not the switching from one to the other issue, that's probably obvious and easy to fix, and I will have a look. I'm more interested in the "incorrect patch sounds" issue which sounds new and legit. Can you make this happen in "fixed" mode and send me a small example of that? I'm guessing that patch selects aren't getting sent out when they should in "fixed" mode. "auto" tends to force patch selects out all the time, so it probably inadvertently "fixes" your issue. Thanks. 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] Testing Appreciated for 20.12
'have been using 20.12 for a couple of days and all seems good. Most of the updates don't affect me but I did try out the new marker stuff and that seems to work fine. One thing that I have noticed in this and previous versions is that my channel setting of 'auto' on a drum track does not appear to be saved in the .rg file and keeps reverting to 'fixed' on reload. This gives me incorrect patch sounds and has to be reset every time. cheers, CE On 02/11/2020 2:03 pm, Ted Felix wrote: 20.12 will be released on December 9. Right now, what you see in svn is the release candidate. Please test the latest svn as much as you can. If you've not built from svn, give it a shot and let us know if you run into trouble. We'll walk you through it. The steps I follow for building from svn are here: https://www.rosegardenmusic.com/wiki/dev:eclipse Suggested areas to test: - Restoration of connections to external MIDI hardware and software on .rg file load. - We should be doing a better job with this now. - New marker menu items in the composition menu. - Composition > Add Marker at Playback Position - Composition > Jump to Previous Marker - Composition > Jump to Next Marker - Better support for not sending out CCs for controllers that are not visible on the UI. E.g. if you make Volume not visible via the device manager, no volume CCs will be generated by RG. Only volume CCs in the Segments will be sent out. - External Controller port for control surfaces. - This was broken in 20.06. Should work now. - Enable/Disable via preferences. - Type of control surface configurable via preferences. - Korg nanoKONTROL2 control surface is now supported automatically. - This should be auto detected and auto connected at rg startup. - All buttons, knobs, and sliders should work. - The LEDs are partially supported. If you configure the nanoKONTROL2 for external LED control, the LEDs will work except when recording. So the record LED will appear to not work. If you would like to test this, let me know if you need the sysex files to configure the nanoKONTROL2 for external control of the LEDs. - Transport buttons on MIDI controllers. - If you have a MIDI controller with play, stop, record, FF, Rew, etc... buttons, chances are good those will work now. At least if they are configured for Pro Tools. - Preferences cleanup. - Some regression testing of the preferences dialogs is needed. - Event editor - General editing. - SysEx. SysEx handling and editing has been improved. - Toolbar Icon - Code cleanup. Make sure they look the same. - Percussion Matrix editor. - Some changes here related to note duration. Most importantly, do what you usually do. That will hit the areas that I missed. Thanks. 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] Testing Appreciated for 20.12
On 11/4/20 6:23 AM, Ted Felix wrote: On 11/3/20 11:34 PM, david wrote: Some of those features look great. I have a development snapshot of 20.06, came from SVN. How do I update that? Just do an svn update from your rg-svn directory: $ svn update Updating '.': At revision 16022. Then build. $ cd build $ make Should be that easy. Sometimes if there have been a lot of changes, I will delete my entire build directory and go through the steps in the README again to recreate it and run cmake. Ted. There didn't seem to be a lot of updates. It compiled fine and seemed to the the basics without problems. And it still looks great on my 4K HDR display. :) I wish other programs did that. -- David W. Jones gn...@hawaii.rr.com authenticity, honesty, community http://dancingtreefrog.com "My password is the last 8 digits of π." ___ 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] Testing Appreciated for 20.12
On 11/3/20 11:34 PM, david wrote: Some of those features look great. I have a development snapshot of 20.06, came from SVN. How do I update that? Just do an svn update from your rg-svn directory: $ svn update Updating '.': At revision 16022. Then build. $ cd build $ make Should be that easy. Sometimes if there have been a lot of changes, I will delete my entire build directory and go through the steps in the README again to recreate it and run cmake. 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] Testing Appreciated for 20.12
On 11/2/20 4:03 AM, Ted Felix wrote: 20.12 will be released on December 9. Right now, what you see in svn is the release candidate. Please test the latest svn as much as you can. If you've not built from svn, give it a shot and let us know if you run into trouble. We'll walk you through it. The steps I follow for building from svn are here: https://www.rosegardenmusic.com/wiki/dev:eclipse Suggested areas to test: - Restoration of connections to external MIDI hardware and software on .rg file load. - We should be doing a better job with this now. - New marker menu items in the composition menu. - Composition > Add Marker at Playback Position - Composition > Jump to Previous Marker - Composition > Jump to Next Marker - Better support for not sending out CCs for controllers that are not visible on the UI. E.g. if you make Volume not visible via the device manager, no volume CCs will be generated by RG. Only volume CCs in the Segments will be sent out. - External Controller port for control surfaces. - This was broken in 20.06. Should work now. - Enable/Disable via preferences. - Type of control surface configurable via preferences. - Korg nanoKONTROL2 control surface is now supported automatically. - This should be auto detected and auto connected at rg startup. - All buttons, knobs, and sliders should work. - The LEDs are partially supported. If you configure the nanoKONTROL2 for external LED control, the LEDs will work except when recording. So the record LED will appear to not work. If you would like to test this, let me know if you need the sysex files to configure the nanoKONTROL2 for external control of the LEDs. - Transport buttons on MIDI controllers. - If you have a MIDI controller with play, stop, record, FF, Rew, etc... buttons, chances are good those will work now. At least if they are configured for Pro Tools. - Preferences cleanup. - Some regression testing of the preferences dialogs is needed. - Event editor - General editing. - SysEx. SysEx handling and editing has been improved. - Toolbar Icon - Code cleanup. Make sure they look the same. - Percussion Matrix editor. - Some changes here related to note duration. Most importantly, do what you usually do. That will hit the areas that I missed. Thanks. Some of those features look great. I have a development snapshot of 20.06, came from SVN. How do I update that? -- David W. Jones gn...@hawaii.rr.com authenticity, honesty, community http://dancingtreefrog.com "My password is the last 8 digits of π." ___ 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] Testing Appreciated for 20.12
20.12 will be released on December 9. Right now, what you see in svn is the release candidate. Please test the latest svn as much as you can. If you've not built from svn, give it a shot and let us know if you run into trouble. We'll walk you through it. The steps I follow for building from svn are here: https://www.rosegardenmusic.com/wiki/dev:eclipse Suggested areas to test: - Restoration of connections to external MIDI hardware and software on .rg file load. - We should be doing a better job with this now. - New marker menu items in the composition menu. - Composition > Add Marker at Playback Position - Composition > Jump to Previous Marker - Composition > Jump to Next Marker - Better support for not sending out CCs for controllers that are not visible on the UI. E.g. if you make Volume not visible via the device manager, no volume CCs will be generated by RG. Only volume CCs in the Segments will be sent out. - External Controller port for control surfaces. - This was broken in 20.06. Should work now. - Enable/Disable via preferences. - Type of control surface configurable via preferences. - Korg nanoKONTROL2 control surface is now supported automatically. - This should be auto detected and auto connected at rg startup. - All buttons, knobs, and sliders should work. - The LEDs are partially supported. If you configure the nanoKONTROL2 for external LED control, the LEDs will work except when recording. So the record LED will appear to not work. If you would like to test this, let me know if you need the sysex files to configure the nanoKONTROL2 for external control of the LEDs. - Transport buttons on MIDI controllers. - If you have a MIDI controller with play, stop, record, FF, Rew, etc... buttons, chances are good those will work now. At least if they are configured for Pro Tools. - Preferences cleanup. - Some regression testing of the preferences dialogs is needed. - Event editor - General editing. - SysEx. SysEx handling and editing has been improved. - Toolbar Icon - Code cleanup. Make sure they look the same. - Percussion Matrix editor. - Some changes here related to note duration. Most importantly, do what you usually do. That will hit the areas that I missed. Thanks. Ted. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
