Re: [Rosegarden-user] New Rosegarden Logo
On 3/15/19 10:24 AM, Lorenzo Sutton wrote: What would it look like inverted (i.e. white / transparent background) and coloured rose (but please remember the yellow/orange... :P ) I was wondering that myself. Don't think I can do it properly, though, the way I'm just fiddling with it in the GIMP. I'll certainly talk to her about this and show her the app icons in GNOME/Ubuntu. 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] New Rosegarden Logo
On 20/03/19 13:45, Ted Felix wrote: On 3/15/19 10:24 AM, Lorenzo Sutton wrote: What would it look like inverted (i.e. white / transparent background) and coloured rose (but please remember the yellow/orange... :P ) I was wondering that myself. Don't think I can do it properly, though, the way I'm just fiddling with it in the GIMP. I'll certainly talk to her about this and show her the app icons in GNOME/Ubuntu. I think you'd need the source, e.g. SVG if done in Inkscape? 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
[Rosegarden-user] Crashes :(
There seems to be a memory allocation problem that is triggered by deleting tracks/sections. This has been there for quite a long time, but it has only been a real problem for me lately because I'm doing a lot of quite heavy editing, and have to resort to doing very frequent saves. I'm not certain, but I get the impression that the very fact of doing these saves seems to reduce the likelihood of the crashes. Currently using build 15419, but as I said, it's been there a long time - years. -- 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] Crashes :(
On 3/20/19 4:53 PM, Will Godfrey wrote: There seems to be a memory allocation problem that is triggered by deleting tracks/sections. This has been there for quite a long time, but it has only been a real problem for me lately because I'm doing a lot of quite heavy editing, and have to resort to doing very frequent saves. I recently saw a crash when deleting segments related to the undo history. Couldn't reproduce it, though. And it only happened on exit. I'm not certain, but I get the impression that the very fact of doing these saves seems to reduce the likelihood of the crashes. Memory issues are always tricky and can easily be exacerbated or mitigated by almost anything. Currently using build 15419, but as I said, it's been there a long time - years. I'm not surprised. Last time I ran valgrind against rg there were too many problems to even begin to track them all down. I gave up because no one was complaining. That appears to have changed. There are a number of ways you can help me track these down. First would be to characterize the editing you are doing. Just a list of the sorts of things, like track deletes that seem to cause the issue. Also, how big are the compositions? Number of segments, tracks. How many minutes? Does it happen even if you never play the composition? Next, if you can analyze the core dumps for me when you crash, that could be a big help. Though sometimes with memory issues, the stack traces are useless. Have you worked with gdb and core dumps before? Ted. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
