Kontrol 2024 outlook: what was, what now, what next?
Comments
-
There's another issue you're having then, because the pixelated thumbnails is not a thing.
Yes it is, worse if you have a larger monitor and due to the fact they now increase the image size displayed on-screen but use a much smaller image to draw from. It's barely an issue tho, this is for making music, not displaying works of art.
0 -
Well, that screen specifically is 90% pixelated works of art 😄
I would rather see the plugin as other people said… but if we are going to have the thumbnails I’d like them to at least look good.
I’m pretty sure that’s already on the list of things to fix but not super pressing of course.
1 -
This is because the image being used by KK is 134x66. The software is capable of displaying higher resolution.
Take a look at Native access to see what's possible.
Or, You can do what I've done, and replace all the files with higher resolution artwork.
2 -
I didn't mention the buttons.
Made a mock-up of possibilities with using the buttons with my modular screen idea.
The knobs not having push buttons to reset parameters really bugs me. If they did have them you could free up a bunch of global buttons for recording options or whatever you want. But having reset buttons somewhere is really important.
The browser info to the right would probably be in the browser screen instead, but if the browser isn't running, it's good info to have at a glance.
The dedicated browser screen could have a Kontakt mode and an Effects mode. It would have little buttons to choose the mode. Or push the off button and the screen would turn off when you don't need it. The Kontakt mode would have the condensed Kontakt instrument rack on its screen, however that would work.
The Effects mode would handle the effects stack for the current plugin, replacing the system we have now. All the usual suspects for effect management would be present, but I didn't bother putting any ideas on this pic because there wouldn't be any knobs or buttons to work with it, except the ticky encoder to choose the plugin from the list, or add a new one. Choosing a plugin would show it on the main screen for editing. Effects would be modular as the generators would be.
Or there could be little buttons for the browser screen that is used for every of its modes. A button in Browser mode could handle the favorites; the same button in Kontakt and Effect modes would toggle mute/solo for that selection, etc. The point is having a dedicated browser screen opens a world of possibilities. A lot less moving between screens and menu diving.
0 -
Yes, if people check out the NKS2 plugin folders many of them have higher res versions of the image assets, it's not just hardware banner images - these include:
NKS2_software_tile.webp - 264 x 198
NKS2_hardware_banner.webp - 1280 x 212
VB_cardview.png - 384 x 188
VB_cardview@2x.png - 768 x 376
OSO_logo@2x.png - 834 x 130
VB_artwork@2x.png - 192 x 94
LibBrowser.png - 587 x 98
It's just most libraries are not yet updated to include them
2 -
is that the case still? Why is that? Are they not Nks compatible?
0 -
Good to know it's an easy fix! I can totally wait until they get there and fix it.
I don't have a single library that shows up in higher resolution though. Even Hypha and Diva that were the first to support NKS2 appear pixelated, so it's not only weird libraries that don't support NKS2.Maybe they are waiting to have all the images to change it and avoid a resolution cacophony hehe
0 -
OK but I got those specs by checking what was in the updated Diva NKS2 image asset folder. Still I guess on a large HDPI screen even a double res thumbnail may still pixellate but it looks OK on the keyboard screen to me.
0 -
Oh yeah, on the keyboard they look fine!
I'm not sure what's going on in the computer, it might be a mac thing… but my screen isn't HDPI (32" 1440p) and it's pretty apparent.0 -
They were, and are, but KK's database scanning/management for 3.x works differently, I think, so it just doesn't show all spitfire libraries when you select the vendor.
It's definiately KK3.x up, because it works fine on 2.9.4 and on Maschine, which use the same database structure, in the old location.
KK3.x moves the database into a new folder (on windows at least), but it's parsing of that database doesn't produce the same results as previous iterations.0 -
@Matthew_NI Matthew, with all due respect for you, as you have been very helpful, what is holding up this update on MIDI templates, Play Assist, etc.? I mean frankly it feels like there is one programmer working in a basement for NI. It's been 8 months and we haven't seen a single thing promised for the MK3 released. NI dropped a whole bunch of planned features for MIDI templates and really this is a feature that even a $100 controller comes with. This is not rocket science. I mean this should not take 8 months right? I've consulted several friends that are programmers and they find the situation laughable and rather troubling. Some of us invested so much in NI and it really feels odd to have such failures in deliverables. Is there a problem that should be reported to management? I think many of us are scratching our heads here.
8 -
As a programmer myself I can say we have a tendency to grossly underestimate the time it takes to do things, especially if it's other people that are doing the thing :D
7 -
@Oscar Morante understood and we have, as a group, graciously allowed for some underestimate 'buffer'; however, this delay feels more like gross mismanagement or understaffing. Two timelines have been missed, features dropped and still we have nothing. Not even Beta. By the sounds of what @Matthew_NI was relating a week or two ago, it doesn't even seem that there is an Alpha version of MIDI Templates, not to mention Play Assist on-board functionality which at this point seems lost in the discussion. People are excited and asking for new features, but the backlog seems, at this point at least, unmanageable. My question again would be should some action be taken at the management level? Has @Matthew_NI related our concerns to management? Perhaps there is a formal process.
2 -
They are on an older version of the NKS SDK and need to update
0 -
It's pretty simple.
The work began in earnest in Q1, after a Q4 spent resolving the most critical issues.
Out of eagerness, we spread too thin across too many topics, and so we progressed everything somewhat, but nothing far enough.
In Q2, we have instead focussed on two areas near-exclusively. One is Maschine related and outside the scope of this thread, but something we've hinted at here and there. The other is MIDI Templates.
As a result, MIDI Templates are really close now to landing on beta, which is ongoing, but usually results in a shippable increment within a couple weeks after.
The above has been said by me several times in several threads, and is still true. The next major update from me is going to be associated with a big public firmware release, as I've nothing more substantive to add until then.
7
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 735 Tech Talks
- 3.9K Native Access
- 15.9K Komplete
- 1.9K Komplete General
- 4.1K Komplete Kontrol
- 5.5K Kontakt
- 1.5K Reaktor
- 364 Battery 4
- 817 Guitar Rig & FX
- 416 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.5K Maschine
- 7K Traktor
- 7K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators