Giter VIP home page Giter VIP logo

cpms's Introduction

Camera Printed Music Staves Dataset

The CPMS dataset is a camera-based printed music score dataset under realistic scenarios created by us, which is set up by taking photos with mobile devices under different angles and light conditions. The test set is originate from the public repertoire of the 2020 sight-singing exam at the Wuhan Conservatory of Music in China(http://www.hbea.edu.cn/html/2019-09/12349.html), and we take pictures and label the printed msuic scores.

Annotation schema

Directory Structure

Our project adopts the following directory structure

CPMS_Dataset/
├── data/
|		├── IMG_1609.jpeg
|		├── IMG_1610.jpeg
|		└── ...
├── label/
|		├── IMG_1609.json
|		├── IMG_1610.json
|		└── ...

The data folder stores the pictures of the photographed music scores, and the label folder stores the annotation data. Each music score image corresponds to a json format label.

Annotation File format Example

{
		"0": [
				{
            "x": 125,
            "y": 167,
            "pitch": "G4",
            "duration": 1
        },
        ...
		],
		"1": [
        {
            "x": 111,
            "y": 291,
            "pitch": "C5",
            "duration": 4
        },
        ...
    ],
    ...
}

Notes:

  • The annotation file is in JSON format, each music score image corresponds to a json format file.

  • The top level field 01indicates the row index of the staff, usually a staff has 10 lines.

  • The fieldxyindicate the coordinates of the upper left corner of the notehead bounding box.

  • The field pitchindicates the pitch of the note in scientific pitch notation.

  • The fielddurationindicates the index of duration classification of the note,and the corresponding relationship is as follows:

    index 0 1 2 3 4
    duration whole half half_dot quarter quarter_dot
    index 5 6 7 8 9
    duration eighth eighth_dot sixteenth sixteenth_dot thirty_second

cpms's People

Contributors

ramy-wu avatar xk-wang avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar

cpms's Issues

Encoding of accidentals

Hello,

Thanks for this dataset! The semantic files seem to encode accidentals differently so that I fear that one can't parse them correctly, and perhaps you can help me to understand the convention you used by creating them?

My understanding of the encoding so far was that it is inspired by the PrIMuS semantic definition, but that CPMS decided to encode accidentals in what PrIMuS calls agnostic. With this in mind, this example makes sense to me:

https://github.com/itec-hust/CPMS/tree/main/semantic/training/6826807-5

D#4 is the only note with an accidental symbol, and thus the only note with an accidental in the semantic file. In particular, the F-notes don't get an accidental (which the semantic format of PrIMus would suggest), as the sharp comes from the key but not from an accidental symbol.

My issue arises with https://github.com/itec-hust/CPMS/blob/main/semantic/training/6546825-4/
The F4 note has a courtesy accidental which doesn't show up in the semantic file. But the true issue is that the B-Natural has no indication of that the natural symbol cancelled the key for this note.

When reading the semantic file of the first example, then the sharp of the key must be added to the F note to get the correct pitch. But in the second example the flat must not be added to the B note, and there is no indication in the file encoding which rule to apply then parsing the semantic files.

I just found this example, and it might make the issue much clearer: https://github.com/itec-hust/CPMS/tree/main/semantic/training/91103002-5 : The semantic file has four B-notes

note-Bb4_eighth note-B4_eighth note-B4_eighth note-B4_eighth

The first B-note received a courtesy accidental. The next two are Bb notes due to the key. However, the last B-note has a natural and therefore is a B-Natural. How would one tell the B-natural apart from the B-flats?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.