Recent Posts

Pages: [1] 2 3 ... 10
1
Help and Questions / Re: Quality in comparison to other trackers
« Last post by Saga Musix on July 18, 2017, 12:08:02 »
We're talking about 3MB of GUI code that is spread over almost 200 files, and of course recreating every single dialog and tab in Qt's dialog editor. It may be "easy" for some weird definition of easy ("diligent routine work" would probably be a more suitable description - nothing about a code base that has been growing for 20 years is ever "easy"), but this is not something that can be done over night by replacing 100 lines of code. What you linked to is a very high-level view of the things that need to be done. If it was that simple, it would have already been done.

Anyway, back on topic - you still have not provided any examples that could show how OpenMPT sounds "lighter" than Schism. Without such an example there is no way I could advise what you need to change.
2
Help and Questions / Re: Quality in comparison to other trackers
« Last post by weyoun_9th on July 18, 2017, 12:02:48 »
Ah, ok. I hope it will be sooner then later :-)

Did you see this article: https://sites.google.com/site/nttrungmtwiki/home/it/programming/gui-programming/mfc-to-qt-migration---walkthrough

Sounds easy ;-)
3
Help and Questions / Re: Quality in comparison to other trackers
« Last post by manx on July 18, 2017, 10:53:30 »
Adding theme support would be equivalent to rewriting the complete GUI. There exist a long-term plan to replace the MFC code with QT (some day, this is YEARS away).
QT will automatically give theme support. Adding theme support before that is done would be an insane waste of time.
4
Help and Questions / Re: Quality in comparison to other trackers
« Last post by weyoun_9th on July 18, 2017, 10:51:25 »
So Microsoft does not like its own OS when letting you change the appearance of Office or Visual Studio? Not to mention all Adobe programs or Unity...

I think there is a reason why it has been ask a few times over the years ;-)

Thanks
Weyoun 9th
5
Help and Questions / Re: Quality in comparison to other trackers
« Last post by Saga Musix on July 18, 2017, 10:30:54 »
Quote
Have you ever thought about Themes instead of just colours to make it look like oldschool trackers?
Naturally this question has been asked more than once in (Open)MPT's 20 years of lifetime and the answer is no, there will not be any theming support. If you don't like the look of your operating system, then theme your operating system and not single applications.
6
Help and Questions / Re: Quality in comparison to other trackers
« Last post by weyoun_9th on July 18, 2017, 09:15:36 »
Yeah, than I think the difference lies in the paula emulation :-)

With Protracker 2.3D clone it sounds more bassy...

I'm looking forward to OpenMPT 1.27 :-) Have you ever thought about Themes instead of just colours to make it look like oldschool trackers?

Thanks
Weyoun 9th
7
Development Corner / Re: Values Greater than 255
« Last post by Saga Musix on July 17, 2017, 13:47:04 »
You can't. It's simple as that. I lost count how many times I told you this before but we do not offer support for increasing any quantity limits in the OpenMPT code. You will have to figure it out on your own and I can tell you it's not a trivial task that could be accomplished with a single line of code. It requires changes over the entire code base, including file format changes. None of the file formats supported by OpenMPT can technically support more than 255 instruments (or effect values greater than 255, etc.).
8
Development Corner / Values Greater than 255
« Last post by Wodd on July 17, 2017, 13:27:14 »
I was trying to make the pattern view accept instrument values greater than 255, but was unsuccessful. How do I do that? I tried changing the instrument max lines in mod_specifications.cpp and snd_defs.h. But, that does not affect the patterns tab.
9
Bug Reports / Re: 1.18.00.00 .scl support is buggy
« Last post by uncloned on July 16, 2017, 20:00:15 »
Thank you !!

It looks like I have to give this a test drive!
10
Bug Reports / Re: 1.18.00.00 .scl support is buggy
« Last post by manx on July 16, 2017, 17:00:14 »
I spent today mostly working on the Tuning code, in particular implementing .scl export. While doing so, I noticed that .scl import was severely broken, and I implemented the following fixes in https://source.openmpt.org/browse/openmpt/?op=revision&rev=8536:
  • Fix: Tuning: scl: .scl files that contain n frequencies are meant to describe scales with n notes per repeating group. OpenMPT imported them as scales with n+1 notes per repeating group.
  • Fix: Tuning: scl: Setting GroupRatio=1 is completely wrong. Scale files only describe a single octave and should be repeated properly.
  • Fix: Tuning: scl: Looking at various scale files from the official Scala archive, it is pretty obvious that scale files support non-octave repeating scales. In scale files, the first ratio is an implicit 1/1. As a consequence, the last value is redundant for octave-repeating scales (and stored as 2/1 in almost all cases). The last ratio is meant to be interpreted as the repeating ratio.

Saga Musix pointed me to this ancient 7 years old bug report, which I apparently just fixed, without knowing it even existed.

Additionally, I implemented importing note names from .scl in https://source.openmpt.org/browse/openmpt/?op=revision&rev=8537

.scl export is available as of r8539 in 1.27 test builds (available as usual at https://builds.openmpt.org/).
Pages: [1] 2 3 ... 10