Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
I prefer the brighter version. In general the slightly increased contrast will also make the graphics more accesible to people with bad vision. So I suggest to go with that version (and update the other colors).
22


I made the grey color lighter. Note that if this is the color we go with, we need to change the color on everything else. It's not really a problem though. I made the waveform brighter as well. I personally think it looks better when it's darker but I'll let you be the judge of that.
23
I like it too. I do like how nearly invisible the waveform is though, so to my taste it would not need to be brighter. But on systems that don't have a high contrast ratio, that waveform would probably vanish, and for that reason, and that reason alone, looking to increase its brightness just a little bit might be a good idea. But I would definitely increase the brightness of the letters by the same amount. So probably a brightness/contrast on the entire logo would be what I'd do.
24
Help and Questions / Re: Play Cursor not visible with fast tempos
« Last post by LPChip on April 04, 2018, 15:37:43 »
Ah yeah, I reported the same issue. There already is a bug report in the Issue Tracker and Manx took a look at it.

This mainly happens with high latencies as far as I can tell and doesn't matter if you have samples or vst's. ASIO is far more noticable on my end, but it does happen with WASAPI too on very high latency settings.
25
Yes, now we're really getting somewhere! I think the waveform adds a lot and looks great. I'd also probably increase the brightness of both the waveform and the grey part of the logo just a little bit to see if it's any better.
26
This is really pretty if you ask me n_n
Only thing i could posibly nitpick on is that the brightness of the logotype could be raised a bit to make it a tad more contrasted with the background
27


What do you think about this for the about screen?
28
Help and Questions / Re: Play Cursor not visible with fast tempos
« Last post by Saga Musix on April 03, 2018, 23:29:52 »
I had to lower the latency on my new soundcard's own device menu.
If you're talking about ASIO, the latency that OpenMPT likes to use is just an indication to the driver, it doesn't need to respect it at all - there is a minimum and maximum latency the driver reports, and oftentimes these two numbers are identical - namely the latency that you specify in the driver panel.
29
Help and Questions / Re: Play Cursor not visible with fast tempos
« Last post by oxxi on April 03, 2018, 16:54:33 »
It looks like it's working now but it still flickers a bit and I'm on the classic windows theme, overall though it's tolerable. I had to lower the latency on my new soundcard's own device menu. I was originally reducing the latency on MPT itself but it didn't do anything. Also disabling the window manager didn't improve the issue. Thx for the help.
30
Help and Questions / Re: Play Cursor not visible with fast tempos
« Last post by Saga Musix on April 03, 2018, 14:31:06 »
This mostly happens because OpenMPT does not double-buffer the pattern display, which does not play well with the compositing window manager used by default in Windows 7.
There are several factors that may come into play why it just started happening for you, e.g. because the compositing window manager was not used (on Windows 7, it can be disabled if you are not using Aero, but Aero designs require it) or because you used a different audio configuration with a different period setting, which directly influences how often the display is updated.
Ultimately we need to start double-buffering the pattern editor (just like the instrument and sample editor), not doing it is a relict of old times, but until then, I can only recommend trying to experiment with the period settings in the sound card settings or disable the compositing window manager if you use the "classic" Windows look anyway.
Pages: 1 2 [3] 4 5 ... 10