Main Menu

Recent posts

#1
@Exhale
no this is what i was talking about:
https://www.youtube.com/watch?v=6IxSL1zrLDo

it's Vectif and he said he did some unreleased demos with ompt and as you can see video is not that old
#2
Technical Documents / Re: Why there won't be more ef...
Last post by Exhale - Today at 02:51:12
Quote from: Saga Musix on Yesterday at 16:53:02For the MPTM format, I'd rather try to start fresh at some point and try to avoid this problem from existing in the first place. If it's physically impossible to enter a conflicting effect combination, e.g. because different effects must go into different columns (like in Renoise), this helps both the users and maintainers of playback code because the question of how conflicting effects should be dealt with doesn't even arise.
I like that option immensely... the way I picture it being handled is the first column is a master column and works exactly like the effect column we already have, but anything put into the second column is a slave to the first and if it conflicts with the first column people can put it in - it will be highlighted in a bright red background with black text and will not save if you save the file. That way you only have to check the second column for conflicts with the first if someone puts anything in it and it basically flat out refuses to even process conflicting commands put into it.
And with things that dont conflict but are similar to the way we have things in the volume column as it is right now, you can keep your multiplication system (I didnt even know it did that, I thought it added/subtracted, learn something new every day :D)
And this could be another way of adding to the functionality of the volume column, make all the new additions a slave to both effect columns... which could actually be something we do instead of adding the new column right away, add more functionality to the volume column, as many effects as you can in a similar way to the way we have been doing it, but make the new effects slaves to the effects column, and any conflict would show up as an obvious error and not save when the file is saved.
#3
General Chatter / Re: OpenMPT is **** (not user-...
Last post by Exhale - Today at 02:25:53
I loved the colourful shitting on the table analogy saga XD got me lolling big time, and you are dead on, criticism doesnt have to be toxic.
And a wholeheartedly agree that there was nothing resembling constructive actionable criticism in the post, it was all down to taste and personal perspective- what our op here was expecting from a tracker was not met by ompt and then they decided to rant on the forums.
What I personally can sympathize with is the frustration of learning something weird and from your perspective, counter intuitive. That has been my problem with daws and why I have never managed to make the leap.
And that is why I think it would actually not be a bad idea to think of a "welcome to OMPT" option at the first opening of a new install (something ppl can opt out of) "This is the main tab, this is the pattern tab - this is the note column, instrument column, etc, this is the sample tab, you can draw samples here by pressing this button..." that kind of thing for super beginners and maybe a more advanced thing that tells you a little bit about every part of each tab for people who have tracked before but want a quick crash course in how ompt itself works like our OP here. And as I said, obviously something like this would be a massive undertaking, but I think it is something we could think about.

I am also wondering if the overview you found Vojvodinosaurus might have been mine... I did one "universal art's introduction to Modplug" on my youtube channel, and I have been meaning to make more and maybe even redoing the one I have done to make it more idiot proof. I did make it 6 years ago at this stage, so yeah my editing skills and general ability as a video host has improved. https://www.youtube.com/watch?v=CfOJdFNuC_w (that's the link) It is in fact one of the first videos I made for my youtube channel.
#4
Help and Questions / Re: .IT format "Fine" Tone Por...
Last post by Saga Musix - Yesterday at 21:30:47
For the record, the tempo clamping fix can be found in the libopenmpt updated released today.
#5
Technical Documents / Re: Why there won't be more ef...
Last post by Saga Musix - Yesterday at 21:06:50
No, those volumes are by design multiplied with each other, that is not a conflict.
#6
Technical Documents / Re: Why there won't be more ef...
Last post by n0cturn - Yesterday at 20:44:42
Doesn't OMPT already deal with similar conflicts, like note volume opposed to channel and global volume? I'm guessing that works on which has the highest priority
#7
Technical Documents / Re: Why there won't be more ef...
Last post by Saga Musix - Yesterday at 16:53:02
Working backwards from what currently exists and projecting how the future should look isn't a very constructive approach, it's filled with trouble in fact. If we just take the existing set of commands (of which there are about 50), we'd have to evaluate for every combination of two such effects if they are in conflict with each other. It's not just putting the same effect into two different columns which can cause such a conflict, but also just two different effects belonging to the same category (e.g. portamento up and down) that may or may not be troublesome. If this matrix of incompatible effects isn't 100% correct when the feature is introduced, people will be able to use quirky effect combinations and suddenly those quirks must be supported forever, because someone might have already used them (like combining volume column and effect column vibrato in XM files, of course it's a terrible idea to do that and yet there are some modules using this quirk, so it has to be emulated correctly).

For the MPTM format, I'd rather try to start fresh at some point and try to avoid this problem from existing in the first place. If it's physically impossible to enter a conflicting effect combination, e.g. because different effects must go into different columns (like in Renoise), this helps both the users and maintainers of playback code because the question of how conflicting effects should be dealt with doesn't even arise.
#8
Help and Questions / Re: Export as MIDI - Octaves f...
Last post by Saga Musix - Yesterday at 16:39:53
Great to hear :)
#9
General Chatter / Re: OpenMPT is **** (not user-...
Last post by Saga Musix - Yesterday at 16:38:14
Quote from: PRAYTHEPO on January 24, 2023, 17:58:02Yes, differencies make things unique, but unique is not equal to good. Why am I so toxic and drop this words here? Cuz everyone can and must criticize things to influence their development, no matter what it is: software, hardware, music, movies etc.
Criticism absolutely doesn't need to be toxic. The equivalent of your initial post here is being invited to someone's house for dinner, and shitting on the table because there was too much salt in the food, instead of politely telling them the fact that there was too much salt (which may in fact just be a matter of taste). Don't expect to be invited to that person's house again.

There is a lot of valid criticism that can be applied to OpenMPT or any other software, but doing so with cuss words and ranting only guarantees one thing: That I am not interested in listening to you. So if you want to see change - please be constructive.

Quote from: PRAYTHEPO on January 24, 2023, 17:58:02Yes, not every tracker needs to please everyone's taste, but there is
Also, as you didnt say anything about UI and overall instrument/sample operations, that means that i am right.
LOL. As if.

No, just as said above, I see no point in answering to a generic rant that doesn't even address any concrete issues. If you say OpenMPT's logic is "crappy". What does that even mean. How am I supposed to act on that. Rewrite every piece of logic in OpenMPT to do exactly the opposite? I hope you realize that you provided zero valuable feedback to make OpenMPT better. Same about "poor UI" - The Windows UI has always been the most controversial part of OpenMPT, no doubt, but it's also its main distinguishing feature. To put it in a single sentence: If you want OpenMPT to become a tracker that looks like FastTracker 2 - it's never going to happen.

Quote from: PRAYTHEPO on January 24, 2023, 17:58:02This post was the only reason to register here. I know how much effort and how much hours are spent to develop this software, but sometimes we need to accept our mistakes.
I'll stand by the fact that everyonething you mentioned so far is entirely up to taste and not a mistake. If you are incapable of presenting your arguments without throwing curse words around, the indeed there is no point in having this discussion, and I will kindly ask you to leave. If, on the other hand, you have concrete changes you want to see, and you are able to present them in a concise manner without vitriol, you are welcome to put them on our issue tracker.
#10
General Chatter / Re: OpenMPT is **** (not user-...
Last post by Vojvodinosaurus - Yesterday at 15:22:11
tbh i found only 1 short tutorial on yt and it's basically just an overview, i believe you have to (re)learn every new tracker from the ground up, similar to many traditional daws
you basically learn everything new thru experience and tinkering, it may not be easy but it's worth the time and effort believe me
it also depends what kind of music you want compose, some daws and trackers are better suite for specific type of music, genre etc