White lines in Software Grid mode on Windows Laptop

I upgraded to 2.8 a few days ago without any problem. Since yesterday I got this wierd problem with white lines showing up in the grid mode. The lines only show on the software, not on the screen of my Touch itself.

Is it a known bug or some crazy option I activated by accident? (not a pro)



I'm running on Windows 10. 8GB, 64 bit Intel i-7-6500 CPU

Any help would be appreciated.

Hi,

Not sure if you solved this issue?

It happened to me too and after tweaking here and there I've found it was caused by having the windows text size at a value different from 100%.
In my case, windows says 125% is recommended but after I set it to 100% the MPC (white lines) issue was fixed.
I hope it helps because it was annoying.

The old 'lines on display' issue is back

It's a retro feature for authentic feeling
peace

peterpiper wrote::shock:
The old 'lines on display' issue is back

It's a retro feature for authentic feeling
peace

Damn you!!!

Sonico wrote:In my case, windows says 125% is recommended but after I set it to 100% the MPC (white lines) issue was fixed.I hope it helps because it was annoying.

Yes, that "fixes" it but nevertheless it's a bug that Akai has to fix, the same like blurry pad names on piano roll when using Drum Program. MPC Software simply doesn't support high-DPI screens properly.

i'm only here because i read ''white lines''

and i don't even do drugs

I get these white lines in the grid too; in an already ugly piece of software.
Just another issue among so many more.



My day job is as a software engineer; I know a screwed project when I see one. New bugs are introduced at every update; and it's been this way for a long time. These people don't know what they're doing anymore; and the code is likely a steaming pile of spaghetti. This is one of the oldest "gotchas" of software development projects. It's well documented and known about. Everyone sees this from time to time, it's just the way it goes - the nature of many different people coming together over long periods of time to write programs in computer code.

Maybe AKAI's dev team should book Uncle Bob for an emergency seminar or something, and start doing TDD properly, because this is unacceptable.

biomaskin wrote:I get these white lines in the grid too; in an already ugly piece of software.
Just another issue among so many more.



My day job is as a software engineer; I know a screwed project when I see one. New bugs are introduced at every update; and it's been this way for a long time. These people don't know what they're doing anymore; and the code is likely a steaming pile of spaghetti. This is one of the oldest "gotchas" of software development projects. It's well documented and known about. Everyone sees this from time to time, it's just the way it goes - the nature of many different people coming together over long periods of time to write programs in computer code.

Maybe AKAI's dev team should book Uncle Bob for an emergency seminar or something, and start doing TDD properly, because this is unacceptable.

Maybe you should take your moaning to a quality prostitute and get some proper sucky sucky. It will calm you down, hopefully.

bees80 wrote:Maybe you should take your moaning to a quality prostitute and get some proper sucky sucky. It will calm you down, hopefully.

You're truly not getting any of this.

biomaskin wrote:

bees80 wrote:Maybe you should take your moaning to a quality prostitute and get some proper sucky sucky. It will calm you down, hopefully.

You're truly not getting any of this.

That's what she said

biomaskin wrote:I get these white lines in the grid too; in an already ugly piece of software.
Just another issue among so many more.



My day job is as a software engineer; I know a screwed project when I see one. New bugs are introduced at every update; and it's been this way for a long time. These people don't know what they're doing anymore; and the code is likely a steaming pile of spaghetti. This is one of the oldest "gotchas" of software development projects. It's well documented and known about. Everyone sees this from time to time, it's just the way it goes - the nature of many different people coming together over long periods of time to write programs in computer code.

Maybe AKAI's dev team should book Uncle Bob for an emergency seminar or something, and start doing TDD properly, because this is unacceptable.

Although I think there are some incompetent programmers at AKAI (just like in most companies) I think (probably wrong cause I'm not into programming) that issues like that are also caused by the infinite number of different systems the software run on. On an Atari ST there are not multiple other devices connected, no USB, no drivers for this and that, no user configurations of this and that, no antivirus and other shit in the background. And Cubase runs stable as hell (if you have the dongle. If not you might get some bombs here and there ). I can't remember having any problems with this software on Atari.

I mean USB alone is so horrorfying. So isn't it more a thing of all the different systems users have and the architechture of the computer system itself?

peace

peterpiper wrote:So isn't it more a thing of all the different systems users have and the architechture of the computer system itself?

Yes, that's a huge challenge! I guess (hope) they got separate teams for Mac OS and Windows development, though. Wouldn't assume this is is the programmers fault, usually the issue is with middle management (demanding too much too fast), old code that isn't properly written and/or documented, or lack of proper testing.