Re: Add key change [WAS] Re: Testing Appreciated for 24.06
Ted Felix <ted-Ll1PANez7xxWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.audio.rosegarden.user |
|---|---|
| Message-ID | <[email protected]> |
Here's my procedure: - New Composition - Draw a four bar segment on track 1 at bar 1. - Switch to arrow (select and edit) tool. - Ctrl+Drag to Track 2, 3, 4, etc... until I have a segment on all 16 tracks. - Select all and launch notation. - First staff is selected, position pointer is at bar 1. - Repeat until all segments have key changes. - Alt+G+K, pick Bb, Ok. - Key change appears. - Hover over the segment selector wheel and mouse wheel down to the next segment. No problems at all. Does the above process work for you? Ted. On 6/5/24 1:55 AM, Lorenzo Sutton wrote: > On 04/06/2024 22:04, Ted Felix wrote: >> I have a feeling those messages in the output are not related to >> the issue. I tried adding some key changes to a new document, and it >> worked fine. >> >> How often does the problem happen? > > I think I found a possible culprit / criteria to trigger this: > > - Create an empty segment in track 1 > - Now *duplicate* that segment dragging it to track 2 > - OR create another segment on another track > > - All these segments are at measure 1 > > After this trying to add a key change on those segments seems to fail. > > moving them around seems to 'unlock' this but randomly, as sometimes it > doesn't. > > TIn all cases where adding a key change fails the relevant message on > the terminal seems to be: > > Internal error in NotationTypes, Pitch::transpose() > > Hope this helps > Lorenzo > > > > > > >> >> Ted. >> >> On 6/4/24 11:19 AM, Lorenzo Sutton wrote: >>> Hi Ted, >>> >>> Very quick answer... >>> >>> Actually this was on empty segments. The idea is like by default you >>> are in C major and already know you want to change key kind of >>> scenario, so no notes involved. >>> >>> Two segments on two different tracks was the only common denominator. >>> >>> Sorry if this isn't too helpful. >>> >>> Lorenzo >>> >>> On Tue, 4 Jun 2024 at 17:04, Ted Felix <[email protected]> wrote: >>>> >>>> I edited two segments and made a key change at every bar, but no >>>> luck >>>> reproducing. Probably because transposition might be involved and I >>>> had >>>> no notes. >>>> >>>> The "internal error" message, if it is relevant, seems to indicate >>>> that the transposition resulted in notes that were outside (below) the >>>> MIDI note range. Are you working with some really low notes? >>>> >>>> I think you might be able to insert the key change without >>>> transposition then transpose separately? That's probably really >>>> inconvenient, but it might help determine whether it is the key change >>>> or the transposition that is the problem. >>>> >>>> I'll keep trying to reproduce the message with some low notes and >>>> some wild key changes. >>>> >>>> As for the other messages, those may have been caused by some >>>> baseclass rearranging I did in response to warnings in the translation >>>> stuff. I sure hope not. I'll take a closer look. >>>> >>>> Ted. >>>> >>>> On 6/3/24 5:56 AM, Lorenzo Sutton wrote: >>>>> Sorry for using the mailing list for this but it's on a bit of a >>>>> deadline project. >>>>> >>>>> When trying to add a key change in notation editor nothing happens and >>>>> in the terminal I get this: >>>>> >>>>> [NotationTool] NotationTool::findActionInParentView: Can't find >>>>> ActionFileClient in parent widget hierarchy >>>>> [NotationTool] NotationTool::invokeInParentView: No action " >>>>> "no_accidental" " found in parent view >>>>> Internal error in NotationTypes, Pitch::transpose() >>>>> >>>>> It seems to happen randomly... I managed to "trigger" this by editing >>>>> two segments in the same notation editor window >>>>> >>>>> >>>>> On 08/05/2024 18:01, Ted Felix wrote: >>>>>> Rosegarden 24.06 will be released on June 5. Please test the latest >>>>>> version in git as much as possible. See the release notes for areas >>>>>> that need testing: >>>>>> >>>>>> https://www.rosegardenmusic.com/wiki/dev:24.06 >>>>>> >>>>>> Let me know if you have any questions about the release notes >>>>>> and I >>>>>> will elaborate. >>>>>> >>>>>> If you've not built Rosegarden before, give it a shot and let us >>>>>> know if you run into trouble. We'll walk you through it. I've >>>>>> written up instructions on the wiki that should help you through the >>>>>> build process: >>>>>> >>>>>> https://www.rosegardenmusic.com/wiki/dev:building_rosegarden_from_source >>>>>> >>>>>> To help out with 24.06 you can either download a source >>>>>> snapshot, or >>>>>> use git to stay up to date with the latest. >>>>>> >>>>>> Thanks. >>>>>> Ted. >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Rosegarden-user mailing list >>>>>> [email protected] - use the link below to >>>>>> unsubscribe >>>>>> https://lists.sourceforge.net/lists/listinfo/rosegarden-user >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Rosegarden-user mailing list >>>>> [email protected] - use the link below to >>>>> unsubscribe >>>>> https://lists.sourceforge.net/lists/listinfo/rosegarden-user >>>> >>>> >>>> _______________________________________________ >>>> Rosegarden-user mailing list >>>> [email protected] - use the link below to >>>> unsubscribe >>>> https://lists.sourceforge.net/lists/listinfo/rosegarden-user >>> >>> >>> _______________________________________________ >>> Rosegarden-user mailing list >>> [email protected] - use the link below to >>> unsubscribe >>> https://lists.sourceforge.net/lists/listinfo/rosegarden-user >> >> >> _______________________________________________ >> Rosegarden-user mailing list >> [email protected] - use the link below to unsubscribe >> https://lists.sourceforge.net/lists/listinfo/rosegarden-user > > > > _______________________________________________ > Rosegarden-user mailing list > [email protected] - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-user _______________________________________________ Rosegarden-user mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user