denemo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Denemo-devel] MIDI Import (Was Re: Release 2.0.6)


From: Richard Shann
Subject: [Denemo-devel] MIDI Import (Was Re: Release 2.0.6)
Date: Mon, 28 Mar 2016 17:40:18 +0100

On Mon, 2016-03-28 at 11:14 -0500, Jeremiah Benham wrote:
> Here is an example of a midi file that is four whole notes.
This imports (using automatic import) as four whole notes each in a
separate bar. It does this both with current master and 2.0.4
Do you get something different?

>  I was thinking this midi import may be better if it was written in
> scheme instead of c. I have been meaning to get around to trying to
> create one when I find time. I would need a way to find out if there
> is a note sounding on a staff at time x on each staff. Then I would
> have to write some thing to quantize it before placing the notes in. I
> would just need to find out if there is a note sounding on staff x at
> time x. If there is I would need to create a new staff to avoid the
> collision. 
> 
Do you have some example file which is typical of what you would like to
import? Your current algorithm for automatic import already has some
quantization procedure in it IIRC.

Richard

> 
> Jeremiah  
> 
> 
> On Sat, Mar 26, 2016 at 12:50 PM, Richard Shann
> <address@hidden> wrote:
>         On Sat, 2016-03-26 at 12:45 -0500, Jeremiah Benham wrote:
>         > I noticed that import midi no longer draws barlines with the
>         automatic
>         > import.
>         
>         Can you give an example? I just created a file with four bars
>         of quarter
>         notes, exported it as MIDI and automatically imported it as
>         MIDI. It got
>         it correctly.
>         Is what you observed a regression? I know MIDI files vary
>         enormously ...
>         
>         Richard
>         
>         >
>         > Jeremiah
>         >
>         > On Mar 26, 2016 10:53 AM, "Richard Shann"
>         <address@hidden>
>         > wrote:
>         >         On Sat, 2016-03-26 at 13:43 +0000, Richard Shann
>         wrote:
>         >         > I've found a regression - Ungroup of Multi-measure
>         rests is
>         >         broken, a
>         >         > call to draw_score (NULL) is being made somewhere.
>         I think
>         >         this should
>         >         > be fixed before we release.
>         >
>         >         I've done this now, it will be available in Mar 27th
>         versions
>         >         at
>         >
>         >         http://denemo.org/~jjbenham/gub/uploads/
>         >
>         >         Richard
>         >
>         >
>         >         >
>         >         > Richard
>         >         >
>         >         >
>         >         > On Tue, 2016-03-22 at 12:58 +0000, Richard Shann
>         wrote:
>         >         > > I think we can start the release cycle for 2.0.6
>         >         > > The new features are:
>         >         > >
>         >         > >     Play Back Controls
>         >         > >         Buttons to play selection or from cursor
>         >         > >             Fix bugs with initial use
>         >         > >         Mute Staffs
>         >         > >             Mute/Un-mute all or groups of staffs
>         >         > >         Whole Score Volume Override
>         >         > >     Denemo Display
>         >         > >         Upbeat bar numbering matches typesetter
>         >         > >     LilyPond Error Reporting
>         >         > >         Separate report for each run
>         >         > >         Only report include filenames when they
>         error
>         >         > >     Playback View
>         >         > >         Shift-Click to Navigate
>         >         > >         Revert to simple MIDI while editing
>         >         > >     Playback from Typeset View
>         >         > >         Unified interface with Playback View
>         >         > >     Translations
>         >         > >         Chinese (Simplified) Translation
>         >         > >
>         >         > > Perhaps more significant are the
>         under-the-bonnet changes,
>         >         with the
>         >         > > introduction of a structure to represent a
>         measure. For
>         >         this reason
>         >         > > please be extra vigilant in testing.
>         >         > >
>         >         > > You can test the candidate release using the
>         binaries in
>         >         > >
>         >         > > http://denemo.org/~jjbenham/gub/uploads/
>         >         > >
>         >         > > e.g. for Windows users test this:
>         >         > >
>         >         > >
>         >
>          http://denemo.org/~jjbenham/gub/uploads/denemo-mingw-0.0.0.zip
>         >         > >
>         >         > >
>         >         > > Richard
>         >         > >
>         >         > >
>         >         > >
>         >         > > _______________________________________________
>         >         > > Denemo-devel mailing list
>         >         > > address@hidden
>         >         > >
>         https://lists.gnu.org/mailman/listinfo/denemo-devel
>         >         >
>         >         >
>         >         >
>         >         > _______________________________________________
>         >         > Denemo-devel mailing list
>         >         > address@hidden
>         >         >
>         https://lists.gnu.org/mailman/listinfo/denemo-devel
>         >
>         >
>         >
>         >         _______________________________________________
>         >         Denemo-devel mailing list
>         >         address@hidden
>         >         https://lists.gnu.org/mailman/listinfo/denemo-devel
>         
>         
>         
> 
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]