KVR Audio

T-CM11 · Post by **T-CM11** » Sun Jan 14, 2018 4:09 pm

fmr wrote: 1920x1080 on a 15.4" display is way too small. Everything will look tiny, it's unavoidable. I'd say for that resolution, 17" is the minimum acceptable.

It's a laptop, you usually sit closer to the screen. Cubase itself looks fine on it. And most plugins I use (bigger or vectorial) too. Windows is no problem, it's scalable.

fmr wrote:2560x1440 on a 27" display. Not so tiny, but still tiny, IMO.

For me, it's a good compromise. Non-scalable software is still usable and everything else looks good because the dpi is relatively high. 1920x1080 on 27" = huge pixels.
If all software I used was scalable, I would've gone for 3840x2160 on 27".

If it weren't for non-scalable software, why would anyone prefer a lower dpi? That doesn't make sense.

aMUSEd · Post by **aMUSEd** » Sun Jan 14, 2018 4:16 pm

aMUSEd wrote:I wanted to be able to control this straight away with my hardware so made a template for playing this in Kore 2:

https://www.dropbox.com/s/8pzsp0qo39spi ... e.ksd?dl=1

And also a less detailed one for use in Komplete Kontrol Series 2 keyboards (bit more complex to setup as it includes thumbnail and database files too so read the info.txt on where to put them)

https://www.dropbox.com/sh/ulf40cicmwzu ... ChOwa?dl=0

Now to 'Komplete' the integration there are Factory patches in NKS format too - a collaborative effort between several of us NI forum members:

https://www.native-instruments.com/foru ... st-1612819

fmr · Post by **fmr** » Sun Jan 14, 2018 4:19 pm

T-CM11 wrote: For me, it's a good compromise. Non-scalable software is still usable and everything else looks good because the dpi is relatively high. 1920x1080 on 27" = huge pixels.
If all software I used was scalable, I would've gone for 3840x2160 on 27".

If it weren't for non-scalable software, why would anyone prefer a lower dpi? That doesn't make sense.

27" with that resolution is a good compromise, I agree (I am thinking of it for myself too). And I agree that 1920x1080 would not look good at that size (21 or 22" are the ideal for that resolution, IMO). But at the current state, the Korg Collection GUIs will look helplessly small. There's no way to avoid it

Anyway, you'd have to agree that the most commonly spread resolution for desktop systems is 1920x1080 on displays between 19 to 22".

T-CM11 · Post by **T-CM11** » Sun Jan 14, 2018 4:23 pm

fmr wrote:But at the current state, the Korg Collection GUIs will look helplessly small. There's no way to avoid it

I know! I'm looking forward to the new GUI updates.

For now, I'm mostly using them via my iPad 2 (except iWavestation, I don't think there's any version of that that ever ran on the iPad 2 (non-64 bit), but maybe I'm wrong).

fmr wrote: Anyway, you'd have to agree that the most commonly spread resolution for desktop systems is 1920x1080 on displays between 19 to 22".

I'd say between 22 to 24". 19" were mostly old 4:3 or 5:4 monitors, I don't think you'll find many 16:9 19" monitors nowadays....

sprnva · Post by **sprnva** » Sun Jan 14, 2018 4:44 pm

The iWavestation is 32-bit and I think I've read about someone running it on an iPad 2.

T-CM11 · Post by **T-CM11** » Sun Jan 14, 2018 4:56 pm

sprnva wrote:The iWavestation is 32-bit and I think I've read about someone running it on an iPad 2.

Cool! But at the moment it's 32,99 €, so I'm going to wait for the updated KLC version.

It's not that expensive, but I just got an RME Fireface UC - so I'm giving music-related spending a rest for the moment.

bill45 · Post by **bill45** » Sun Jan 14, 2018 11:45 pm

I use the Windows magnifying glass 200x the polysix is still hard to read

braj · Post by **braj** » Mon Jan 15, 2018 2:10 am

Korg needs to make resolutions that will be good for 5 years, I would say resizable GUIs with up to 4k resolution 3840x2160 is what they should do, so they can be used in a variety of resolutions and be fairly future proof. My main issue with the new Oddysey is that it isn't resizable. As soon as I get a new monitor, my next definitely will be 4K, it will be too small. So aiming for the common resolution today I think is folley, they should aim at the common standard for good plugin design in 2018, which is to allow the user to adjust it to suit their needs. Korg needs to study U-he etc. to see how to do it right.

Jace-BeOS · Post by **Jace-BeOS** » Mon Jan 15, 2018 3:06 am

DuX wrote:He is probably at 1920x1080 resolution, like 90% of the others, but the 4k and beyond whingers are as loud as they can be... To tell the world they've forked out for a newest fad monitor, to distinct themselves.

It has nothing to do with fads or people wanting to distinguish themselves. It has everything to do with sharp text and bitmaps without seeing pixels. It also is a huge benefit for photographers and video people (working at 100%, instead of zooming or scrolling).

The readability of text on a high-PPI display (with a properly scaling OS) is much better. It's a reduction in strain on people's eyes. If you don't care about sharp text, fine, but your eyes will change some day...

It took me a matter of months for a retina iPhone 4 to leave me accustomed to high density displays with sharp text. i then found looking at my MacBook Pro was ...not preferred. Using an iPad Pro for internet and music all day compounds the effect, since its screen is nearly the same size as my 13" laptop's and it looks much sharper than my 27" iMac.

If hope the internet and desktop software developers catch up before I also have a high-PPI desktop computer. I'm tired of blurry and pixelated bitmaps everywhere.

BONES · Post by **BONES** » Mon Jan 15, 2018 11:22 am

Jace-BeOS wrote:It has everything to do with sharp text and bitmaps without seeing pixels

Absolute, complete and utter bollocks! Until Apple's marketing department came up with the term "Retina Display", I had never in my life heard anyone, ever, even mention that they could see pixels, much less complain about them. The first TFT flat panel monitors I ever saw were 15" screens running at 1024x768 and everyone just "ooh"ed and "ahh"ed at them, nobody said "look at all those giant pixels". And you don't go to the movies and here everyone complaining about the pixels, even though digital projectors are only 2k and they fill half your filed of vision.

When we had CRT monitors, which could be set to any resolution you desired, I never saw anyone setting them beyond about 1600 pixels wide, even on massive 27" monitors (and believe me, a 27" CRT was huge when it was sitting on your desk).

It also is a huge benefit for photographers and video people (working at 100%, instead of zooming or scrolling).

Except that applications like Photoshop and After Effects don't scale your images/vision, so you end having to make the application scale it, which it does a really bad job of.

The readability of text on a high-PPI display (with a properly scaling OS) is much better.

If you are having trouble reading text, run the ClearType utility.

It's a reduction in strain on people's eyes. If you don't care about sharp text, fine, but your eyes will change some day...

More BS. Your OS will render text with the level of anti-aliasing appropriate to the hardware. It has nothing at all to do with DPI. Again, if your text is blurry, run ClearType. That's precisely what it's for.

It took me a matter of months for a retina iPhone 4 to leave me accustomed to high density displays with sharp text.

Emperor's New Clothes, pure and simple. I remember when the first guy at the post house I was working at got an iPhone 4 and we spent a bit of time comparing very high quality, professional images (stock photos) between it and the dinky 480x272 OLED display on my Zune HD. Even the guy who'd just blown $750 on a new iPhone agreed that everything looked better on my Zune.

If hope the internet and desktop software developers catch up before I also have a high-PPI desktop computer. I'm tired of blurry and pixelated bitmaps everywhere.

Then you probbly need some kind of therapy because it's not real, it's just in your head.

EDIT - Reading further, I notice your on a Mac, so you can't run ClearType. Now I understand what your problem is - poor computer choices. PC users don't have the same problems.

T-CM11 · Post by **T-CM11** » Mon Jan 15, 2018 11:50 am

So you've never seen the difference between a high dpi and a low dpi screen?
Cleartype can't add ("sub")pixels smaller than your screen can display. Higher dpi = smaller pixels = sharper text
And it's not comparable to CRT monitors AT ALL. TFT is inherently sharper (less blurry) and only has one (=native) resolution - pixels have a fixed size.

T-CM11 · Post by **T-CM11** » Mon Jan 15, 2018 11:53 am

BONES wrote:I had never in my life heard anyone, ever, even mention that they could see pixels, much less complain about them.

Anecdotal. Why would anyone care about what you've heard from who? Is that supposed to mean anything to us?

braj · Post by **braj** » Mon Jan 15, 2018 11:54 am

So the guy arguing for 32 bit is now arguing for low res screens

that's hilarious.

Aloysius · Post by **Aloysius** » Mon Jan 15, 2018 1:33 pm

This topic is sooooooooo boring

pelle_8 · Post by **pelle_8** » Thu Jan 18, 2018 1:24 am

(Haven't read the whole thread)
BUMP

Korg ARP Odyssey in standalone mode on Win10 seems to have problems switching to ASIO for some users.
It causes the app to crash.

How many here have experienced this?

UAD Apollo FireWire and RME Fireface are among the affected.

Korg updates its Legacy Collection with a new Arp Odyssey emulation