On 04/21/2015 08:42 AM, Ted Felix wrote:
> Fixed in r13911. Again, a rebuild from make distclean required.
I'm glad you sorted something out for that, Ted. I'm half expecting
this will also address one of those annoying Ubuntu build glitches I've
been having to work around.
I'll test tha
On 04/21/2015 08:29 AM, Ted Felix wrote:
> Actually, it looks like I didn't quite do everything that needed to
> be done. I forgot to update the HAVES variable.
Fixed in r13911. Again, a rebuild from make distclean required.
Ted.
-
On 04/21/2015 08:09 AM, Michael Gerdau wrote:
> Worked like a charm :)
Actually, it looks like I didn't quite do everything that needed to
be done. I forgot to update the HAVES variable. Working on this now.
Should have a fix shortly. If you're not using the audio features
(audio segments
>Let me know how it goes.
Worked like a charm :)
Thanks,
Michael
--
Michael Gerdau email: [email protected]
GPG-keys available on request or at public keyserver
signature.asc
Description: This is a digitally signed message part.
---
On 04/21/2015 05:03 AM, Michael Gerdau wrote:
> However that in turn creates the warning:
> configure: WARNING: Required JACK library not found, building with no audio!
Heh. I just fixed this a few hours ago in r13910. Do an svn update
and that should go away. You will need to do a complete
> > could somebody provide
> > me with a very brief sketch as to which part of the code I would have
> > to look at if I intended to add what I think it lacks ?
>
> src/document/io/LilyPondExporter.cpp is the heart and soul of the thing.
> There is also src/gui/dialogs/LilyPondOptionsDialog.cpp
On 04/20/2015 12:02 PM, Michael Gerdau wrote:
> file from scratch I had the impression it could use some improvements
> though.
It can always use improvements, but it's notoriously fiddly code. The
more test cases you can throw at new work, the better. You'll end up
with something that works
Dear developers,
I recently had used rosegarden as a "midi to lilypond" converter.
While the resulting output was way better than starting a lilypond
file from scratch I had the impression it could use some improvements
though.
It also occured to me that the highest supported lilypond version is
On 10/26/2012 08:20 AM, Ted Felix wrote:
> We would need a RosegardenAbstractScrollArea. Probably not worth the effort
> as the
> improvement is not guaranteed, and it's just a band-aid on a much bigger
> problem. Could be an interesting experiment, however.
If a band-aid can avoid major surger
On 26 October 2012 13:20, Ted Felix wrote:
>The RefreshStatus stuff appears to be an attempt to mitigate this CPU
> usage problem. However, it is not complete. The Segment::notify*()
> functions are still there and still in use.
Historical note: the RefreshStatus mechanism actually predates
> Something like that would be fairly quick to try and see if there is any
> measurable positive impact on anything. There might not be, because
> asking the transport its status 488 times a second might be just as
> expensive as what we're trying to avoid doing, or even more so.
If it just check
On 10/26/2012 08:20 AM, Ted Felix wrote:
> needs attention first. But it derives from QAbstractScollArea. So I
> guess it can't derive from RosegardenWidget instead. We would need a
> RosegardenAbstractScrollArea.
It's negligible effort. I'll try to slap something together after work,
and se
On 10/26/2012 08:20 AM, Ted Felix wrote:
> I don't think SegmentRefresh is the best solution, however...
Correction: By SegmentRefresh, I mean either RefreshStatus or
SegmentRefreshStatus.
Ted.
--
Everyone hates
On 10/26/2012 05:52 AM, D. Michael McIntyre wrote:
> On 10/25/2012 07:58 AM, Ted Felix wrote:
>> updateRefreshStatuses() is getting called about 388 times per second.
>
> Holy crap, Batman!
Indeed. We're looking at almost 900 calls per second to Segment
notification related functions while re
On 10/26/2012 05:52 AM, D. Michael McIntyre wrote:
>> Regardless, it would probably be a good idea
>> to redesign the Segment notification stuff so that the GUI can force
>> notifications for every user edit, and the MIDI recording feature can
>> just send notifications periodically, like ten time
On 10/25/2012 07:58 AM, Ted Felix wrote:
> updateRefreshStatuses() is getting called about 388 times per second.
Holy crap, Batman!
> Regardless, it would probably be a good idea
> to redesign the Segment notification stuff so that the GUI can force
> notifications for every user edit, and the M
Chris:
Interesting. Thanks for the historical perspective.
One piece of information that I can add, is that I'm pretty sure I
originally tried to record the Beethoven piece Ted is using for testing,
using the version of Rosegarden that came out with Ubuntu 8.04.
That attempt at recording on
On 10/25/2012 04:16 AM, Chris Cannam wrote:
> (I don't have the program in front of me atm either, and I can't
> actually remember offhand whether we don't show them at all or update
> them in batches -- either way we shouldn't be having a callback
> per-note and no edit commands should be firing)
On 10/25/2012 12:28 AM, Aere Greenway wrote:
> Given the difficulty of fixing this, along with the fact that it has
> never worked before in Rosegarden, I (the submitter of the bug report)
> consider it to be not worth fixing.
We can always add it to the pile of "Live With It" bugs that are
perf
On 25 October 2012 02:38, Ted Felix wrote:
>The executive overview goes something like this Rosegarden was
> designed to be a MIDI editor. Then someone decided to add MIDI
> sequencing to it. But what's ok for a MIDI editor (very CPU intensive
> updates in response to infrequent edit ev
On 25 October 2012 09:13, Chris Cannam wrote:
> don't even try to update the actual notes on canvas.
(I don't have the program in front of me atm either, and I can't
actually remember offhand whether we don't show them at all or update
them in batches -- either way we shouldn't be having a callba
Ted:
Given the difficulty of fixing this, along with the fact that it has
never worked before in Rosegarden, I (the submitter of the bug report)
consider it to be not worth fixing.
I do have a work-around, if I need to record such things, namely to use
MusE (which is how I recorded the version
Well, this is becoming quite the little nightmare.
The executive overview goes something like this Rosegarden was
designed to be a MIDI editor. Then someone decided to add MIDI
sequencing to it. But what's ok for a MIDI editor (very CPU intensive
updates in response to infrequent e
On 09/11/2012 09:15 PM, Ted Felix wrote:
> 3. Ubuntu happens to pick up our release in time for your delivery.
I expect it's much too late to get a new version of Rosegarden into the
October release of Ubuntu, even if I released it today.
--
D. Michael McIntyre
Ted:
The "non-virtuouso case" is fine. That would just fix what was already
there, and should work. The "virtuooso case" is something that hasn't
yet worked in Rosegarden - possibly from the very beginning, and
certainly hasn't worked since Ubuntu 8.04.
Being able to hear what is being record
On 09/11/2012 09:34 PM, Aere Greenway wrote:
> The case where input events get missed when recording is (of the
> problems not yet fixed) the highest priority, which I think the
> Beethoven piece is a part of.
Ok, there were two test cases where notes were dropped. One was very
serious in tha
Ted:
The case where input events get missed when recording is (of the
problems not yet fixed) the highest priority, which I think the
Beethoven piece is a part of.
The next highest priority (from my point of view) is the ability to hear
the multiple instruments being recorded by way of the reco
On 09/11/2012 08:53 PM, Aere Greenway wrote:
> I'm still working on course-ware, so nothing is going to ship in the
> near future.
>
> That means fixing the problems is a higher priority.
Ok, then I'll take a look at Beethoven (and hopefully a whole host of
recording issues) next.
> Since Lub
Ted:
I'm still working on course-ware, so nothing is going to ship in the
near future.
That means fixing the problems is a higher priority.
Since Lubuntu is not a long-term-support release system, will the fixes
now ready, possibly be available in any of the Ubuntu 12.10 releases
(repository
Well, it looks like I fixed bug 3546135 in r13005. Tom, can you take
a look at what I did and verify that it makes sense in the grand scheme
as you're the most knowledgeable in this area?
Where to now? Well, at this point, there is still the matter of
3555441 in which the sequencer has
On 3/23/11, D. Michael McIntyre wrote:
> I still intend to pursue teacher licensure in the long run, but I have just
> gone back to work as a truck driver. I've been at the new job for a little
> over a week now, and I'm writing this now because today was the day when
> everything finally clicked,
From: D. Michael McIntyre [[email protected]]
Sent: Wednesday, March 23, 2011 8:16 AM
To: [email protected]
Cc: [email protected]
Subject: [Rosegarden-devel] Status update for Michael...
I still intend to pursue teacher
I still intend to pursue teacher licensure in the long run, but I have just
gone back to work as a truck driver. I've been at the new job for a little
over a week now, and I'm writing this now because today was the day when
everything finally clicked, and I was sure it was all going to work out
Hello All,
I just found a nasty bug using Adjust->Collapse Equal Pitched Notes
In Main window:
* Create a 2 measures of 4/4
* Open in Notation Editor
In Notation Editor
* add 8 quarter notes (Middle C is good)
* Tie them together
* Select Adjust->Collapse Equal Pitched Notes
Segmentation fault.
he the progress dialog box and post "real"
recommendations. Hopefully, we can decide quickly and implement the solution.
I'd expect I can have some real proposals by 5pm EST.
Sincerely,
Julie S.
--- On Wed, 2/2/11, D. Michael McIntyre
wrote:
> From: D. Michael McInt
On Wednesday, February 02, 2011, Julie S wrote:
> So, I'll update trunk with the bug fix, if that is ok.
Yeah, we should grab that, and we should figure something out right quick with
that progress dialog parenting behavior issue.
Anything else? What kind of shape is my automatic tie selecting
just threw away the prior selection set and
failed to highlight the new segments notation.
So, I'll update trunk with the bug fix, if that is ok.
Sincerely,
Julie S.
--- On Wed, 2/2/11, D. Michael McIntyre
wrote:
> From: D. Michael McIntyre
> Subject: Re: [Rosegarden-devel] Stat
On Wednesday, February 02, 2011, Dave Plater wrote:
> It's just an update so still might make it into gm release or if it's
> 99% ready I'll package svn and if a bug pops up there's the update
> system, I've never had a chance to use it yet.
Now that I've thought about it again, I guess I could j
On 02/02/2011 05:12 PM, D. Michael McIntyre wrote:
> On Wednesday, February 02, 2011, Dave Plater wrote:
>
>
>> The last release was 10.10 that I used, is there a newer one in the
>> pipeline?
>>
> We're working on a new release, but the pipeline is pretty clogged up right
> now. It's loo
On Wednesday, February 02, 2011, Dave Plater wrote:
> The last release was 10.10 that I used, is there a newer one in the
> pipeline?
We're working on a new release, but the pipeline is pretty clogged up right
now. It's looking like March or April, so you're going to have to go with
10.10 to m
On Wed, Feb 2, 2011 at 7:44 AM, Dave Plater wrote:
> Hi, I'm busy franticly updating all and sundry in openSUSE multimedia
> for the 11.4 rc1 deadline at the end of the week. I've been neglecting
> rosegarden. The last release was 10.10 that I used, is there a newer one
> in the pipeline?
Yep, 1
Hi, I'm busy franticly updating all and sundry in openSUSE multimedia
for the 11.4 rc1 deadline at the end of the week. I've been neglecting
rosegarden. The last release was 10.10 that I used, is there a newer one
in the pipeline?
Thanks
Dave Plater
Le mercredi 09 décembre 2009 22:24:48, Alexandre Prokoudine a écrit :
> Let's see :) If you add more translations, anyone can run lupdate
> later and translate what you added. If you remove tr(), noone will be
> able to do it and part of user visible message will be in English till
> next release a
On Wednesday 09 December 2009, Yves Guillemot wrote:
> May I do this commit now or should I remove the translations first until
> the next release after Thorn ?
Go ahead and commit them, Yves.
--
D. Michael McIntyre
--
On 12/10/09, Yves Guillemot wrote:
> I'm on the point of committing some stuff to display inconsistencies in
> overlapping segments.
> But some translations are in it.
>
> May I do this commit now or should I remove the translations first until the
> next release after Thorn ?
Let's see :) If you
I'm on the point of committing some stuff to display inconsistencies in
overlapping segments.
But some translations are in it.
May I do this commit now or should I remove the translations first until the
next release after Thorn ?
Yves
-
Ok,
I'm back on the air and was planning to get stuck into this taskover
the school holidays. However I've had a hiccup as my husband broke his
foot while reroofing our house, yesterday.
Can you believe it! Months without significant rain and now my husband
is out of action and only 1/4 of the
> * gui/editors/segment/segmentcanvas/CompositionView.cpp
> All sorts, mostly related to change from QScrollView to QScrollArea as
> base class
Chris,
I still can't build but have been looking at the change from QScrollView to
QScrollArea.
QScrollArea uses a child widget, set with setWidget. It
So, I've waded through a few crash fixes. It still crashes before a
window appears, but now we appear to be in the realms of "actual
bugs", i.e. real mistakes in the conversion to Qt4 (probably).
I'm off home now, and hope to resist spending any significant time on
this in the next day or so.
Cu
On Tue, Jan 6, 2009 at 9:19 PM, Chris Cannam
wrote:
> [...] device definition files, which Immanuel stubbed
I mean Emanuel -- sorry. I had been doing quite well at getting
everyone's name right, but it's clearly getting to me as well now.
Chris
On Wednesday 07 January 2009, D. Michael McIntyre wrote:
> One down. Read the commit comment. I have no clue if I accomplished
> anything, but at least it compiles now.
Hah. Read the commit comment myself. Funny how putting it all in diff format
finally helped me figure out what it used to do
> > Mysterious error I haven't looked into ('paint' is not a member of
> > 'QTableWidgetItem')
>
> This looks fixable. I'm piddling with it.
One down. Read the commit comment. I have no clue if I accomplished
anything, but at least it compiles now.
One for me, 114 for Chris, and I get to crow
On Tuesday 06 January 2009, Chris Cannam wrote:
> * gui/widgets/ColourTableItem.cpp
>
> Mysterious error I haven't looked into ('paint' is not a member of
> 'QTableWidgetItem')
This looks fixable. I'm piddling with it.
--
D. Michael McIntyre
---
grep error make.log | wc
3287 31388 317107
3287 errors, but now I get it. This is that stuff Chris broke in the makefile
after he switched to some too new distro with libs in different places, isn't
it?
OK. 115 errors now. 582 .cpp files, 575 .o files. Wow!
OK, so let's get back to m
On Tuesday 06 January 2009, CJN Fryer wrote:
> Sorry if I'm being dumb - I get the feeling I'm doing a bit of that at the
> moment but
> The newline after the parent class colon looks a little unorthodox - is it
> maybe one compiler doesn't mind and one does?
Nah. We have this idiom everywhere
Sorry if I'm being dumb - I get the feeling I'm doing a bit of that at the
moment but
> src/gui/rulers/TempoRuler.cpp:98: error: no matching function for call
> to ‘QWidget::QWidget(QWidget*&, const char*&)’
I think that's the constructor which contains:
TempoRuler::TempoRuler(RulerScale *rulerS
On Tuesday 06 January 2009, Chris Cannam wrote:
> My figures for the number of files building differ slightly from
> Heikki's just posted -- I have one fewer. Perhaps a file that used to
> build no longer does, and you need to make clean?
Mine differ too. I come up with 561 building out of 583.
I've committed a fairly big tranche of action-related changes, as well
as a few other updates.
I must say that it's been great to feel confident that I could just go
ahead and rewrite all the actions to the new short form, and that the
.rc files will have all the right data already. Julie, while
Translation status report for Rosegarden project
rosegarden.pot has 2316 messages
Lang Total DoneFuzzy Pending Status
- - --- --
cs 231623160 0[+]
fi 231623160 0[+]
it 23162205
On Saturday 29 Jul 2006 19:19, Guillaume Laurent wrote:
> On Saturday 29 July 2006 19:05, Stephen Torri wrote:
> > I am working with a PhD student out of italy on this. [...]
>
> That's Michelle, right ?
International person of mystery! I think Michelle has certainly
indicated in the past that
On Sun, 2006-07-30 at 03:35 +0200, Pedro Lopez-Cabanillas wrote:
> On Saturday, 29 July 2006 21:01, I wrote:
> > The problem must be at the rendering part, I guess.
>
> I've committed a patch trying to fix this issue. First, the Event constructor
> at Fingering::getAsEvent() was wrong (it needs
On Saturday, 29 July 2006 21:01, I wrote:
> The problem must be at the rendering part, I guess.
I've committed a patch trying to fix this issue. First, the Event constructor
at Fingering::getAsEvent() was wrong (it needs four arguments). It now sets
the sub-ordering property to -60 as you want
On Saturday 29 July 2006 2:19 pm, Guillaume Laurent wrote:
> That's Michelle, right ? I wish she had replied to my request to provide a
> patch using standard tools :-).
Me too.
--
D. Michael 'Silvan' McIntyre Silvan <[EMAIL PROTECTED]>
Linux fanatic, and certified Geek; registered Lin
On Sat, 2006-07-29 at 20:19 +0200, Guillaume Laurent wrote:
> On Saturday 29 July 2006 19:05, Stephen Torri wrote:
> >
> > I am working on the next generation of the guitar chord. What you see at
> > present is a prototype which is going to be radically changed. The
> > present prototype allows the
On Saturday 29 July 2006 3:01 pm, Pedro Lopez-Cabanillas wrote:
> I think that there is nothing wrong in this code fragment. You are
> calculating the insertionTime correctly, and you can see in the event list
> editor that your fingering events have the right times. The problem must be
> at the r
On Saturday 29 July 2006 2:09 pm, Pedro Lopez-Cabanillas wrote:
> I don't have a "show fretboard" command. I think that you need to set the
> fretboard mode, pressing the button without a real icon (next to the "text"
No real icon? I committed an icon for this some time back, and it shows up
he
On Saturday, 29 July 2006 20:25, Stephen Torri wrote:
> On Sat, 2006-07-29 at 20:09 +0200, Pedro Lopez-Cabanillas wrote:
> > I think that there is a bug: the chord diagrams aren't drawn over the
> > notehead you clicked, but one or two beats after it.
>
> How you suggest I get the position of where
On Sat, 2006-07-29 at 20:09 +0200, Pedro Lopez-Cabanillas wrote:
> I think that there is a bug: the chord diagrams aren't drawn over the
> notehead
> you clicked, but one or two beats after it.
How you suggest I get the position of where to play the diagram? At
present I try to calculate the cl
On Saturday 29 July 2006 19:05, Stephen Torri wrote:
>
> I am working on the next generation of the guitar chord. What you see at
> present is a prototype which is going to be radically changed. The
> present prototype allows the user to create, modify or select chords.
> The new version is going t
On Saturday, 29 July 2006 12:26, Guillaume Laurent wrote:
> I can't find a way to invoke it ('show fretboard' fails).
>
> So what's up ?
I don't have a "show fretboard" command. I think that you need to set the
fretboard mode, pressing the button without a real icon (next to the "text"
mode one)
On Sat, 2006-07-29 at 12:26 +0200, Guillaume Laurent wrote:
> Can anyone bring me up to date on the current status of the guitar-related
> code ? I'm looking into it right now and it seems to be missing some bits (it
> refers to some rc files, guitar.rc fretboardinserter.rc, some classes aren't
Can anyone bring me up to date on the current status of the guitar-related
code ? I'm looking into it right now and it seems to be missing some bits (it
refers to some rc files, guitar.rc fretboardinserter.rc, some classes aren't
used anywhere - GuitarTabEditorWindow), and I can't find a way to
The last commit message pretty well tells it. 1-4 are all but finalized. 5
needs more work, which I will get done soon. 6 needs a little more work at
the end.
7 is coming next for real. I just need to write and ksnapshot for a few hours
to knock it out, really. I almost started it today, b
73 matches
Mail list logo
