[Rosegarden-bugs] [ rosegarden-Feature Requests-1881398 ] Export markers in lilypond

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Feature Requests item #1881398, was opened at 2008-01-28 12:25
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=354932&aid=1881398&group_id=4932

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Priority: 9
Private: No
Submitted By: Jaakko H Kyro (jkyro)
Assigned to: Jaakko H Kyro (jkyro)
Summary: Export markers in lilypond

Initial Comment:
A nice feature would be to export the document markers as rehearsal marks, so that they would appear in the same place in each separate sheet. Currently, one needs to specify the markers using text annotations (unless I'm mistaken) and for each staff separately.

Shouldn't be too hard, at least my use case merely requires \mark \default to be inserted into the lilypond output whenever there is a marker. I'll try and make a patch for this.

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2008-02-28 19:20

Message:
Logged In: YES 
user_id=1312539
Originator: NO

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Jaakko H Kyro (jkyro)
Date: 2008-02-05 14:40

Message:
Logged In: YES 
user_id=504191
Originator: YES

Committed in revision 8618.

----------------------------------------------------------------------

Comment By: Jaakko H Kyro (jkyro)
Date: 2008-02-02 14:57

Message:
Logged In: YES 
user_id=504191
Originator: YES

Ok, thanks. I'll do some more testing to see that I don't break anything.

----------------------------------------------------------------------

Comment By: D. Michael McIntyre (dmmcintyr)
Date: 2008-02-02 14:39

Message:
Logged In: YES 
user_id=663564
Originator: NO

This sounds interesting, though I'm not sure I would use it, and
definitely wouldn't know how to use it without some hand holding.  I think
I'd want help making sure I address this topic suitably in some future
tutorial.

Here, I'm reassigning this to you, and adding you to our project.  I
should probably get some kind of committee concensus before taking that
step, but you've already done two patches nobody applied, and seem intent
on pursuing this matter until you come up with something useful.  Your
patches look good, and even if all you ever do is work on this one thing,
it will be more convenient for everybody to let you commit directly.

Well, unless that idea freaks you out, and you'd rather not be bothered to
figure out what to do with your new superhero powers.

----------------------------------------------------------------------

Comment By: Jaakko H Kyro (jkyro)
Date: 2008-02-02 13:42

Message:
Logged In: YES 
user_id=504191
Originator: YES

Taking things a bit further, I've come up with some extensions. First,
allow exporting the marker text instead of the default rehearsal mark. This
would just use the "marker text" instead of \default(plus probably some
positioning as to not interfere with other markup stuff like chord text).
There probably will be some clashes anyway, so why not allow for custom
markup field with a placeholder to tweak the layout?

like, the user can input 
\hspace #0 \raise #2.0 %text%
into a textfield and the result would be placed inside \markup { } in the
resulting lilypond. 

Any thoughts?

----------------------------------------------------------------------

Comment By: Jaakko H Kyro (jkyro)
Date: 2008-01-29 13:29

Message:
Logged In: YES 
user_id=504191
Originator: YES

OK, here's another patch, which should work, at least in the two cases I
tested it. There's still some ugliness but feel free to commit if you see
it fit.

The change was correcting the assumption that the markers would be sorted
by time.
File Added: rg-markers-export2.patch

----------------------------------------------------------------------

Comment By: Jaakko H Kyro (jkyro)
Date: 2008-01-28 21:38

Message:
Logged In: YES 
user_id=504191
Originator: YES

Sometimes the writeSkip seems to return  an empty string, resuting in an
extra marker being written into the output. There's probably a load of
other stuff I'm not taking into account as well.,

----------------------------------------------------------------------

Comment By: D. Michael McIntyre (dmmcintyr)
Date: 2008-01-28 14:39

Message:
Logged In: YES 
user_id=663564
Originator: NO

What doesn't fully work about it?  Should I think about applying it yet,
or let you continue working?

----------------------------------------------------------------------

Comment By: Jaakko H Kyro (jkyro)
Date: 2008-01-28 14:23

Message:
Logged In: YES 
user_id=504191
Originator: YES

Initial patch against revision 8594 attached. Doesn't fully work but the
principle should be obvious. Also seems to apply cleanly to version 1.6.1
at least.
File Added: rg-markers-export.diff

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=354932&aid=1881398&group_id=4932