On Wed, 15 May 2019 20:00:37 -0400
Ted Felix wrote:
>On 5/15/19 2:36 PM, Will Godfrey wrote:
>> My understanding is that nullptr is the 'modern' replacement for NULL, so I
>> can't see why it would fail.
>
> It is.
>
> In this case, the older version of QSharedPointer provides no way for
On 5/15/19 2:36 PM, Will Godfrey wrote:
My understanding is that nullptr is the 'modern' replacement for NULL, so I
can't see why it would fail.
It is.
In this case, the older version of QSharedPointer provides no way for
the compiler to convert a nullptr (which is actually a nullptr_t)
On 5/15/19 2:36 PM, Will Godfrey wrote:
Just tried to compile this, and it fails with the report:
error: no match for ‘operator=’ (operand types are
‘QSharedPointer’ and ‘std::nullptr_t’) m_baseStyle =
nullptr;
Should be fixed in [r15493].
Ted.
On 5/15/19 2:36 PM, Will Godfrey wrote:
Just tried to compile this, and it fails with the report:
error: no match for ‘operator=’ (operand types are
‘QSharedPointer’ and ‘std::nullptr_t’) m_baseStyle =
nullptr;
Looks like you may have an older version of the Qt5 development
stuff. 5.7 and
On Sun, 12 May 2019 19:51:54 -0400
Ted Felix wrote:
>On 5/3/19 5:06 AM, Will Godfrey wrote:
>> I haven't forgotten this - I'm still totally bogged down with work on
>> Yoshimi.
>> There is a *lot* going on!
>
> Just pushed r15492 which was a memory access issue related to
>deleting segments
On 5/3/19 5:06 AM, Will Godfrey wrote:
I haven't forgotten this - I'm still totally bogged down with work on Yoshimi.
There is a *lot* going on!
Just pushed r15492 which was a memory access issue related to
deleting segments and the segment parameter box. This may have fixed
the problem.
On Wed, 17 Apr 2019 09:42:42 -0400
Ted Felix wrote:
>On 4/8/19 3:56 AM, Will Godfrey wrote:
>> I'm afraid I've still not had time to do anything with this - not fired up
>> the
>> DAW at all lately - to much other stuff getting in the way :(
>
> I've updated the instructions for getting a
On 4/8/19 3:56 AM, Will Godfrey wrote:
I'm afraid I've still not had time to do anything with this - not fired up the
DAW at all lately - to much other stuff getting in the way :(
I've updated the instructions for getting a stack trace on the wiki.
Yes. Remembering also that even a good power supply running too long on
a below-normal voltage source can be damaged by that over time.
Also keep in mind the mortal enemy of all computers and electronics:
heat. Over time, that bakes the life out of electronic components like
capacitors and
On 4/10/19 3:52 AM, Sami Jumppanen wrote:
For dying computer owners: before upgrading anything, use a known good
PSU.
That's a thought. Just because I put a good PSU in a couple years ago
doesn't mean the PSU isn't the issue now. I don't remember what it is,
but it's a ridiculously high
On 4/10/19 8:54 AM, rhkra...@gmail.com wrote:
I guess you mean a retail desktop without Windows off the shelf?
No, I mean a retail desktop anything off the shelf. Nobody stocks them
anymore. It's all laptops and all-in-ones, peppered with the occasional
ridiculous "gaming PC" that has
On 4/9/19 4:55 AM, Will Godfrey wrote:
Is there nothing like that where you are?
There is, but my father made a scene, and I'm not welcome there anymore.
They wouldn't take back a laptop they ordered for Dad, so he said,
"Can I smash it on the counter then?" They gave the go ahead, and he
On 4/9/19 7:49 AM, Sami Jumppanen wrote:
Out of curiosity, what is the problem?
I have no idea. I'm in the middle of typing, and then the computer is
just frozen rock solid. When I get it back up, there's a good chance
X11 or Weyland or whatever I'm using will be broken to a point where I
On Tuesday, April 09, 2019 04:37:15 AM D. Michael McIntyre wrote:
> I had gotten in the habit of just buying a retail desktop PC off the
> shelf, but you can't buy those anymore.
I guess you mean a retail desktop without Windows off the shelf?
___
On 4/8/19 3:56 AM, Will Godfrey wrote:
My guess is that the delete
operation has left an invalid pointer somewhere.
There are definitely bad pointers left around in the code.
Intentionally. (!?) See the comments in
SequenceManager::segmentDeleted(). If, as I explain there, the memory
For dying computer owners: before upgrading anything, use a known good PSU.
I just lost a week worth of late nights trying to set up a new computer. I
deducted that it was the PSU on the nearly functional computer that had
caused CPU failure, by having something else than DC voltage. On the
On 4/7/19 9:56 PM, Will Godfrey wrote:
On Thu, 28 Mar 2019 22:18:27 -0400
Ted Felix wrote:
On 3/28/19 6:24 PM, Will Godfrey wrote:
Not forgotten this - just busy firefighting yoshimi :(
No problem. I've been working my way through everything valgrind is
showing me to see if I can find
On April 9, 2019 1:49:22 AM HST, Sami Jumppanen
wrote:
> Out of curiosity, what is the problem?
>
>
> > >I had gotten in the habit of just buying a retail desktop PC off
> the
> > >shelf, but you can't buy those anymore. Getting Linux onto a
> retail
> > >Windows PC is a huge pain in the
On 4/8/19 10:37 PM, D. Michael McIntyre wrote:
I haven't tested the timing thing either. My computer keeps freezing.
When I reboot it, I'm stuck at 1024x768, and the only way I have managed
to make progress on that issue is to reinstall Kubuntu. I've been
around that bush three times now,
Out of curiosity, what is the problem?
> >I had gotten in the habit of just buying a retail desktop PC off the
> >shelf, but you can't buy those anymore. Getting Linux onto a retail
> >Windows PC is a huge pain in the ass anyway. I guess I have to go
> >figure out what components to buy and
I haven't tested the timing thing either. My computer keeps freezing.
When I reboot it, I'm stuck at 1024x768, and the only way I have managed
to make progress on that issue is to reinstall Kubuntu. I've been
around that bush three times now, and I have grown tired of the
aggravation. This
On Thu, 28 Mar 2019 22:18:27 -0400
Ted Felix wrote:
>On 3/28/19 6:24 PM, Will Godfrey wrote:
>> Not forgotten this - just busy firefighting yoshimi :(
>
> No problem. I've been working my way through everything valgrind is
>showing me to see if I can find your crashes. Nothing yet. Lots
On 3/28/19 4:18 PM, Ted Felix wrote:
On 3/28/19 6:24 PM, Will Godfrey wrote:
Not forgotten this - just busy firefighting yoshimi :(
No problem. I've been working my way through everything valgrind is
showing me to see if I can find your crashes. Nothing yet. Lots of
memory leaks, but
On 3/28/19 6:24 PM, Will Godfrey wrote:
Not forgotten this - just busy firefighting yoshimi :(
No problem. I've been working my way through everything valgrind is
showing me to see if I can find your crashes. Nothing yet. Lots of
memory leaks, but nothing crashy.
Ted.
On Sun, 24 Mar 2019 21:30:31 -0400
Ted Felix wrote:
>On 3/23/19 5:27 AM, Will Godfrey wrote:
>> Typically 3-4 minutes 8-12 tracks MIDI only.
>>
>> Most commonly happens when splitting a track then deleting part of it. Actual
>> crash usually happens next time I go to 'Play'.
>
> Ok, thanks.
On 3/23/19 5:27 AM, Will Godfrey wrote:
Typically 3-4 minutes 8-12 tracks MIDI only.
Most commonly happens when splitting a track then deleting part of it. Actual
crash usually happens next time I go to 'Play'.
Ok, thanks. I'll see if I can reproduce with these sorts of edits.
Had a look
On 3/23/19 5:27 AM, Will Godfrey wrote:
Yoshimi - gdb was no help at all and we found the problem by simply undoing
commits till we found the one where it changed :(
Some bug has existed in some form since Richard Bown implemented track
deletion, so we'd have to roll back to the commit
On Wed, 20 Mar 2019 18:07:43 -0400
Ted Felix wrote:
>
> 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?
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
On Fri, Jun 24, 2011 at 8:16 AM, Chris Cannam
can...@all-day-breakfast.com wrote:
I had a quick try and couldn't reproduce this. Can you try running
Rosegarden under a debugger and asking for a stack trace?
i.e.
$ gdb /usr/bin/rosegarden (or wherever it lives)
(gdb) run
On Friday, June 24, 2011, Peter Desjardins wrote:
I can arrange segments and play them without problems. However, when I
hold down shift and drag to resize, Rosegarden instantly crashes. I
can repeat this every time.
Is there another configuration problem that might be causing the crashes?
Thank you for your work on Rosegarden, it's a wonderful program. Let
me know if I can help when you do get a chance.
Is there a more stable way to do what I am trying to do? I want to
arrange a sequence of samples, snippets of music and drum sounds.
Would most people use a separate sequencing
32 matches
Mail list logo
