View Issue Details

IDProjectCategoryView StatusLast Update
0000628OpenMPTFeature Requestpublic2015-01-04 20:26
ReporterAmaroq_Dricaldari Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionwon't fix 
Platformx86OSWindowsOS Version7
Product VersionOpenMPT 1.24.01.00 / libopenmpt 0.2-beta8 (upgrade first) 
Summary0000628: Small little requests
Description
  • Panning Slide effect:
    Being able to put this in a pattern would be useful, even if you are using panning envelopes for instruments. Normally, you would require duplicates of the same instrument with different envelopes if you wanted to give it a different panning effect, but by implementing this you could drastically reduce the number of instruments that a song could potentially require.

  • Channel Panning Slide:
    Same as above, but effecting the channel pan.

  • "Set Relative Panning" option for samples and instruments:
    Being able to choose whether you want to set the "absolute" panning for an instrument (the current system, which overrides channel panning and most panning commands), or the "relative" panning (for instance, +2 or -2)

  • "Surround" checkbox on a sample-by-sample basis:
    I am certain that this will come in handy, especially when you are working with only a small handful of channels that are filled with notes.

  • Allow panning when surround is enabled:
    Sometimes you still want something to move left and right, even if the right-channel is inverted and the left channel isn't. To prevent cancellation, all you have to do is just make the left channel quieter when panning right and make the right channel quieter when panning left.

  • Have the lines in the sample editor change color to indicate clipping (like in Audacity):
    A simple change. A visual indicator that a sample is too loud (before you actually playing it) would be a very handy thing to have.

  • When saving a module that was previously an MO3, have an option to leave the samples compressed (assuming the waveform hasn't been modified)

  • When importing an MP3 sample, have an option to leave it as an MP3:
    You don't magically get an increase in quality by converting it back to a FLAC or WAV, so why waste the extra space?

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

Activities

Saga Musix

Saga Musix

2015-01-04 20:26

administrator   ~0001903

Panning Slide effect

Already exists (Pxy).

Channel Panning Slide:

There is no differentiation between sample/instrument/channel panning, hence how should this be possible?

Allow panning when surround is enabled

Use MPT panning mode / quad surround (S9B). For compatibility's sake IT panning mode is enabled by default, which doesn't support this.

Have the lines in the sample editor change color to indicate clipping (like in Audacity)

Technically impossible, since OpenMPT does not even have support for floating-point samples or samples which can exceed 0dB in general. A sample by itself never clips, since its maximum volume can be 0dB. If your samples clip, it's the fault of the overall mix, not of a single sample.

When saving a module that was previously an MO3, have an option to leave the samples compressed (assuming the waveform hasn't been modified)

Technically impossible, because unmo3 just gives us the uncompressed file. MO3 is supposed to be a "final" format, i.e. you are not supposed to edit files that are already saved as MO3. ALWAYS edit the uncompressed file!

- When importing an MP3 sample, have an option to leave it as an MP3:
You don't magically get an increase in quality by converting it back to a FLAC or WAV, so why waste the extra space?

Recompressing an edited sample will actually degrade its quality, hence re-saving a modified MP3 sample as lossless is always a good idea. If you want to keep your MP3 samples as-is, you can use MPTM's "external samples" features and simply keep a reference to the original MP3 sample instead of embedding it in the file.

So, since all requests but one (per-sample surround setting) are either already possible or technically infeasible, I'm going to close this report. Feel free to create a new one for the one feature that is actually possible and is not already implemented. And in the future, please do not create multiple requests in one issue, this just makes everything confusing and untidy, thank you.

Issue History

Date Modified Username Field Change
2015-01-04 19:30 Amaroq_Dricaldari New Issue
2015-01-04 20:26 Saga Musix Note Added: 0001903
2015-01-04 20:26 Saga Musix Status new => closed
2015-01-04 20:26 Saga Musix Resolution open => won't fix