0000986: Map to Successive Samples - OpenMPT Issue Tracker

ID	Project	Category	View Status	Date Submitted	Last Update

0000986	OpenMPT	Feature Request	public	2017-07-12 23:16	2017-07-13 20:42

Reporter	Wodd	Assigned To
Priority	low	Severity	minor	Reproducibility	have not tried
Status	new	Resolution	open
Platform	x64	OS	Windows	OS Version	10
Product Version	OpenMPT 1.27.00.* (old testing)

Summary	0000986: Map to Successive Samples
Description	The ability to map all notes and samples to the same value is neat. But, it would be great if there was a way to map samples successively. For example: If I map note C-0 in instrument 1 to sample 1, I would like to have a function that maps the remaining notes to the next set of samples. That is: C-0 1, C#0 2, D-0 3, … B-9: 120. Having to manually type them is tedious and leaves much room for error. If I had a way to map to successive samples, my time could be cut significantly and the margin for error could be almost eliminated.
Additional Information	I envision it as follows: Instrument 1: C-0: 1 (manual input) [Insert keyboard shortcut here.] C#0: 2 D-0: 3 ⋮ Instrument 2: C-0: 121 (manual input or carryover from previous instrument with keyboard shortcut from above) [keyboard shortcut from above if not carried over from previous instrument] C#0: 122 D-0: 123 ⋮ The first sample in each instrument would need to be typed manually (unless a carryover similar to the pattern view's overflow paste can be programmed in that carries the sample map over from the previous instrument) (example: Pressing a shortcut key or key combination while in instrument 2 carries over from instrument 1, thus mapping the focused note to sample 121 and the notes below it to successive samples.)
Tags	scripting

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

Saga Musix 2017-07-12 23:38 administrator ~0003098	I cannot imagine any practical use for this, but you could write an SFZ instrument (requires OpenMPT 1.27 testing version), or once the scripting API is in place, this could be created almost automatically.

Wodd 2017-07-13 02:06 reporter ~0003100	Thank you for the suggestion, Saga Musix. That is quite a nifty format. I can see that the <region> tags are the samples and that the key is the note on the sample map, in the range 0 to 119. That does exactly what I am looking for. Thank you! Since I see the term "SFZ" mentioned only twice in the manual, I am guessing that it is a recent implementation. I was not familiar with the format until I saw your suggestion of using it now.

Saga Musix 2017-07-13 10:46 administrator ~0003104	It's a recent addition but it's also not going to get any more mentions - it's not an OpenMPT-specific format so I don't see any merit in documenting it in our manual, apart from the fact that it is supported of course. I might document the supported opcodes, but that's about it.

Wodd 2017-07-13 20:42 reporter ~0003105	You do bring up a good paint about the format not being specific to OpenMPT. Adding the supported opcodes to the manual is also y good move.

Date Modified	Username	Field	Change
2017-07-12 23:16	Wodd	New Issue
2017-07-12 23:38	Saga Musix	Note Added: 0003098
2017-07-12 23:38	Saga Musix	Priority	normal => low
2017-07-12 23:38	Saga Musix	Tag Attached: scripting
2017-07-13 02:06	Wodd	Note Added: 0003100
2017-07-13 10:46	Saga Musix	Note Added: 0003104
2017-07-13 20:42	Wodd	Note Added: 0003105