View Issue Details

IDProjectCategoryView StatusLast Update
0001155OpenMPTFeature Requestpublic2018-11-05 21:29
Reporterharbinger Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status newResolutionopen 
Platformx64OSWindowsOS Version7
Product VersionOpenMPT 1.27.10.00 / libopenmpt 0.3.12 (upgrade first) 
Summary0001155: Merge Channels
Description

When transferring to a MIDI file (so i can create a score with MuseScore), there are many times when i want more than one MPTM channel combined into a single MIDI channel. Unfortunately, doing this for a whole track takes forever.
What i could use is a Merge Channels command, where i could combine given channels in one fell swoop. This would be a great tool that would help in MIDI preparation.
Merging of course would offer the option on how to merge — that is, which channels take precedence when there are conflicts, what to do in cases of different instruments, etc. Personally when i merge manually, i use the old IT-style of pasting, where nothing is merged if something already exists in that row...

This could a long way towards MIDI compatibility with MPT. Preparing for MIDI is mostly used for score creation.

TagsNo tags attached.
Has the bug occurred in previous versions?
Tested code revision (in case you know it)

Activities

Saga Musix

Saga Musix

2018-10-15 17:20

administrator   ~0003667

While such a feature would be useful without doubt, I wonder why it would help you with MIDI export. Pattern channels do not correlate to MIDI channels or MIDI tracks in any way. If you want several instruments to share the same MIDI channel, you should assign them to the same exported MIDI channel. OpenMPT 1.28 will also allow them to be aware of each other (and thus cancel each other's note, as would merging them into a channel do), you can try a test build to verify if this helps you achieving what you want.

harbinger

harbinger

2018-10-22 16:51

reporter   ~0003677

Well, here's what i'm working with...

All of my Piano Suites were set up with one PE channel PER NOTE. That is, i would have one channel devoted to say, C-5, and that note was called in that channel only when C-5 needed to be played. This would allow me to simulate the Sustain pedal being pressed, then i could pass a note off '==' in every channel when i was releasing the sustain pedal.

Now i'm using MuseScore to finally create and self-publish the scores to these suites. Instead of re-entering all the notes again, i realized i could just Export the MPTM file into MIDI (now that it's much better supported). Only problem is, to get MuseScore to recognize that all these notes belong on two staves, i have to merge down all the left-hand note-channels to one, and all the right-hand channels to another. Then i can MIDI Export it, and Musescore reads it and notates it perfectly with very little tweaking.

Are you saying there's another way? Or does the FR still need to be implemented to save me time?

Saga Musix

Saga Musix

2018-10-22 16:58

administrator   ~0003678

I'm actually saying that what you are trying to do is not helping at all - because OpenMPT does not expose its pattern channels in the MIDI file it any way (unless you chose to export in "mapped" mode) - it used to export one MIDI track per pattern channel, but that was long while ago - what it does these days is exporting one MIDI track per instrument. What you need to do is to assign the notes to two different instruments (left / right hand). If MuseScore imports its score per MIDI track, then you are done. If it imports its score per MIDI channel, then you need to assign two different MIDI channels to those two instruments during export. But rearranging your pattern structure is not necessary at all.

harbinger

harbinger

2018-10-22 17:11

reporter   ~0003680

Oh Okay! I'll try that! I naturally assumed that each channel would end up with its own staff. (That's right...i didn't actually <i>test</i> it!)

I'll let you know what happens to see if we can discard this FR.

Saga Musix

Saga Musix

2018-10-22 17:46

administrator   ~0003683

As said initially - I think even if this specific use-case is not a use-case at all, there are still other valid reasons to implement this at some point, so there is no need to close this issue.

harbinger

harbinger

2018-11-05 21:29

reporter   ~0003697

OK, now i know why i want the channels to be mergeable.

When exporting to MIDI, all the notes that are still playing in the pattern channels will create notes that stay on thru multiple measures in a score. So you'll end up with notes that are tied over several measures until they're played again.

By combining channels, this will eliminate the notes that are carried over.

Issue History

Date Modified Username Field Change
2018-10-15 15:27 harbinger New Issue
2018-10-15 17:20 Saga Musix Note Added: 0003667
2018-10-22 16:51 harbinger Note Added: 0003677
2018-10-22 16:58 Saga Musix Note Added: 0003678
2018-10-22 17:11 harbinger Note Added: 0003680
2018-10-22 17:46 Saga Musix Note Added: 0003683
2018-11-05 21:29 harbinger Note Added: 0003697