Main Menu

Recent posts

#11
General Chatter / Re: Winamp Source code opened ...
Last post by Saga Musix - September 30, 2024, 13:11:50
QuoteThey don't even allow forking
That was under an earlier version of the license, which isn't even compatible with GitHub's terms of service. But the whole situation is still a big mess. I wouldn't go as far as saying that they are asking for free labour, there is clearly not much intent from their part to keep the app alive. It's very obvious that someone that doesn't know anything about the Winamp codebase or licenses (or even Git, for that matter) was tasked with taking care of this, given how unprofessionally this release was done and how they're trying to undo the damage. Someone even pointed out that the license smells AI-generated.
#12
Help and Questions / Re: Question about Offset, Hig...
Last post by Saga Musix - September 30, 2024, 13:08:32
QuoteIt seems like older software like Impulse Tracker didn't have this problem? Or maybe it did and I misundertood the whole thing.
Impulse Tracker is the tracker that "invented" the High Offset command, so it's responsible for all the headaches around it. :) But back then people of course tended to use lower-quality and thus smaller samples, so the High Offset was rarely needed.

Note that there is a more recent alternative to using High Offset in the MPTM format in addition to the #xx command that Harbinger mentioned: You can combine cue points with regular offset commands. This way you can either address the whole sample by a percentage (o00 + OFF always points to the end of the sample no matter how long it is), or parts of the sample relative to cue points, which takes both effect columns but doesn't require the tedious SAx command setup. Read more about this command combination here: https://wiki.openmpt.org/Manual:_Effect_Reference#Combined_Commands
#13
Help and Questions / Re: Question about Offset, Hig...
Last post by Harbinger - September 30, 2024, 12:59:56
Quote from: blast_thickneck on September 30, 2024, 08:01:34My main doubt or problem about it is the need of using High Offset to reach futher into the sample. It seems kind of a hassle or even unintuitive having to set it up but then immediately having to return to normal offset so I can use earlier parts of the sample. I imagine to avoid this I'd probably have to prepare the sample to make it have a lower freq. in like Audacity beforehand but the sample ends up sounding super tinny if i do this. It seems like older software like Impulse Tracker didn't have this problem? Or maybe it did and I misundertood the whole thing.

To anyone who has experience with this is there any way of using stuff like breaks or such without having the need to use High Offset?

Ive done a lot DnB including breakbeats and i was using openMPT before the devs put in the High Offset command into the MPTM format. When #xx came along, it was a gamechanger for all my EDM.

The High Offset command does take some getting used to, but the only other reasonable workaround is to slice up the sample (that youre offsetting into) into smaller sounds, and giving them their own sample or instrument slots. I highly recommend saving the good ones that you think youll be using again.
#14
Help and Questions / Question about Offset, High Of...
Last post by blast_thickneck - September 30, 2024, 08:01:34
Just marked an older thread as solved but decided to open a new thread since this is a completely different question.

I'm interested in doing stuff like jungle, dnb and breakcore and investigating I learned that trackers are maybe the best option for finetuning drums in that genre. That, plus it feels like OpenMPT's sampler is so much better than even some commercial options in my opinion (the Reaper sampler is archaic in comparison)

My main doubt or problem about it is the need of using High Offset to reach futher into the sample. It seems kind of a hassle or even unintuitive having to set it up but then immediately having to return to normal offset so I can use earlier parts of the sample. I imagine to avoid this I'd probably have to prepare the sample to make it have a lower freq. in like Audacity beforehand but the sample ends up sounding super tinny if i do this. It seems like older software like Impulse Tracker didn't have this problem? Or maybe it did and I misundertood the whole thing.

To anyone who has experience with this is there any way of using stuff like breaks or such without having the need to use High Offset? I don't even know if I'm asking in the correct place for this. I see there is sample cues but those seem pretty limited as well.

Anyway, sorry for troubling you and if this is the wrong place to ask please ignore but I'm getting pretty frustrated with this.... Everything else about OpenMPT seems much more straightforward than this.

#15
General Chatter / Re: Winamp Source code opened ...
Last post by Alice (Midori) - September 30, 2024, 07:42:53
The terms under which they relased the code are a joke. They don't even allow forking, and you're only allowed to contribute to the original repository, owned by a very dubious company. It's basically them asking for free labour with no real benefits to the community.

No wonder everyone keeps jesting about this whole situation and trolling the repo with new issues.
#16
Help and Questions / Re: Question about Samples and...
Last post by blast_thickneck - September 30, 2024, 07:40:32
Alright some stuff happened so I couldn't say thanks but I read all your posts. I guess I'll move to using instruments then. I have another doubt but I think I should open another thread I guess?
#17
Free Music Downloads / Sometime, Somehow, Someway [mp...
Last post by n0cturn - September 29, 2024, 03:51:09
These tunes are a good example of how easily distracted I can be, it is just one tune, or at least it started that way, then I got distracted as usual and ended up with 3 different tunes. Not sure I like any of them and I think thats why I kept changing things.

Sometime - https://drive.google.com/file/d/1SxkOf2aeVIg5C5KeODE83wSm5gxbzKC3/view?usp=sharing
Somehow - https://drive.google.com/file/d/1VDi1wCv83Nhwb01CeDcGzYKkspzd5m2D/view?usp=sharing
Someway - https://drive.google.com/file/d/1I4oUF5UYY3IiSRT0l74LVc2ZodisnjlF/view?usp=sharing
#18
Development Corner / Key handling changes in OpenMP...
Last post by Saga Musix - September 27, 2024, 10:33:18
This is a quick description of a few things related to key handling that will change in the upcoming OpenMPT 1.32; if you are using current OpenMPT testing versions you are encouraged to check if shortcuts, navigation, etc. still work as expected for you or if something unexpected changed.

What happened? Well, for the last 18+ years, OpenMPT has used a global keyboard hook to intercept key presses. This hook handled all the global shortcuts, as well listening to the status of modifier keys (Shift, Ctrl, Alt). There were various issues with this approach: The global hook caused some general keyboard input issues on some Wine systems, and modifier keys could get "stuck" on all OpenMPT installations, sometimes causing key presses to not be recognized anymore until the "stuck" modifier was pressed again. This change is also a tiny puzzle piece on the long road to a platform-independent OpenMPT.

In general, the intent was to keep existing behaviour mostly the same as before. Here are some things we know that changed:

  • Global shortcuts now have a lower priority than context-specific shortcuts. This matches the expectations from other context relationships (e.g. Note Column shortcuts have a higher priority than - and thus can override - general Pattern Editor shortcuts). This means that if you had a global shortcut and assigned the same keys to, say, a pattern editor shortcut, the pattern editor shortcut now takes priority if the pattern editor is active.
  • Behaviour change with "special keys": It is possible to use the Windows key as an additional modifier key in OpenMPT, and there is some code that prevents the start menu from opening if this key is pressed while OpenMPT is focussed. Similarly, when using the Caps Lock, Num Lock and Scroll Lock keys, OpenMPT would return the respective indicator lights on the keyboard to their previous state (i.e. Caps Lock would not turn on ALL-CAPS WRITING). These features are still present, but are no longer active when file dialogs, message boxes, or any other context in which OpenMPT does not accept keyboard shortcuts is active. So if you set the Windows key to, say, stop playback, the start menu will no longer be suppressed while you are browsing for a module in a file picker. Previously the start menu would have been suppressed in this situation even though playback would not have been stopped anyway.
  • Like in other applications, global shortcuts no longer work while a menu (either main menu or context menu) is open. This never worked for context-specific shortcuts anyway.

If you notice any changes beyond the ones described above, please let us know (here or on the issue tracker). As you can probably imagine, keyboard handling is an accumulated mess of over 18 years of bugfixes and special cases, and I already had to fix several special cases. If there are any more bugs left, I would hope to find and fix them before an official OpenMPT 1.32 release.
#19
Help and Questions / Re: Need Some Help with Import...
Last post by Saga Musix - September 26, 2024, 11:13:29
OpenMPT can handle pretty much any sample rates and bit depths, and in general the higher the quality of the samples is, the better of course. However, as with any sampler (no matter if hardware or software), there are some limitations to sample playback that may cause samples to sound strange. As your description is a bit vague on what the actual problem is, I will assume in the following description that this is your problem, because it is what confuses most beginners about sample playback.

If you play a single sample across the whole note range, it will typically start sounding strange the further away you move from the root note at which it was recorded and is meant to be played back at. For example, if you play a middle-C on a real piano and then move up one octave, the higher C will have different characteristics in its timbre than the middle-C one. If you simply take a single piano sample and play it one octave up, it will keep the same timbre but play it at double the speed and twice the frequency, and as a result sound very tinny.
You can either embrace this type of sound distortion as the typical sound of samplers, or you can do what all other sampling software and hardware is doing as well, assuming that you have suitable sample material available: Use multiple samples per instrument, spread over the entire note range. OpenMPT's instrument editor lets you assign samples freely over the entire note range of an instrument.

QuoteWhat is the ideal sample rate or bit depth for OpenMPT: ??
Are there any specific settings I should adjust to maintain the original sound quality: ??
As mentioned above, the higher-quality, the better, but going above the mix rate (typically 48 kHz) won't help. Lots of samples are available in 16 bit or 24 bit resolution (the latter will be reduced to 16 bit by OpenMPT upon import), often at 44 kHz or 48 kHz sample rate, which are both fine for OpenMPT, but due to its heritage from oldskool home computer trackers, it has no problem with lower quality samples (there is a FAQ entry why such samples may sound strange with the default playback settings though)

QuoteAny tips for organizing or optimizing sample usage in larger projects: ??
Do you mean your sample library or the samples within a song?
#20
Help and Questions / Need Some Help with Importing ...
Last post by derekkktheler - September 26, 2024, 09:00:27
Hey everyone,

I am fairly new to OpenMPT and loving the flexibility it offers for creating music: However, I have hit a bit of a roadblock when it comes to importing custom samples into my tracks. I have tried loading .WAV and .FLAC files into the sample slots but I am not sure I am doing it correctly because sometimes they don't seem to play right or the sound quality changes:

Can anyone share some best practices for importing and managing custom samples in OpenMPT: ?? For example:

What is the ideal sample rate or bit depth for OpenMPT: ??
Are there any specific settings I should adjust to maintain the original sound quality: ??
Any tips for organizing or optimizing sample usage in larger projects: ??

I am eager to learn and improve my workflow so any advice from more experienced users would be greatly appreciated. Thanks in advance for your help !!

With Regards
Derek Theler