tubus

3538 Suggestions

Hi all
/usual preamble on
... how happy and thankful i am with the kX drivers since its beginnings ...
/usual preamble off

Since the forthcoming of the 'DSP-made-easy'-objects (thank you LeMury) i am actually beginning to really *use* the DSP-Window. So take this as kind of Usability-report and a suggestion for some actually very minor (as i think) improvements which could greatly enhance the efficiency of DSP-editing (at least for me).

First of all:
- for gods sake pls *display* the current filename anywhere on the window. How many times i have edited a setup, wanted to save and then had to take pains in remembering or locating the setup i was working on.

- preserving filenames in the load/save dialog boxes would also be very handy . C'mon kX-Gods, this can't be difficult.

- while beeing on this matter: a longer MRU-Files list would also be usefull. (May be i'm missing something and this already can be adjusted ). Actually best would be: a display of the current filename beside the device-selector on the DSP-Window, click on it to get the MRU-Files-Selector

- What would also help me: bigger connector-boxes of the DSP objects (or to be more precise: bigger 'sensible' areas for clicking on them). Again: how many times i wanted to make a connection and have shifted the object instead.

May be some of these suggestions can be considered for the next release. I'm looking forward to it, especially since i read on the 'to-do list' something like 'kX scripts support'

thnx

tubus


BTW. May be i'm missing something again, but one thing i never understood:
*Why in a MIDI-Application the the 'kX-Control'-Port is a Input-device??*
Is'nt it suposed to be a [B]Output[B]-device??

NightBreed

Because it controls automation of the kx effects. This is not a synth. Use it if you have a external midi device or program to send midi data to that port to remotely control the effect in the kx auto portion of the mixer.

tubus

AAAA

tubus

asdasdasd ddsa d asd assss asd

tubus

Sorry about above Posts, Operator error

Thnx for your response, but sorry again, I don't get it!!

If the 'kX-Control'-Port is supposed to control the kX-effects, then seen from the controlling Program it should obviously be an output-port .
From a logical point of view it's no difference to controling the kX-Synths.
Or, put another way, how am i supposed to send MIDI-Data to this port, if it is an input -port??

dj_stick

this may not be possible, due to size restriction and window size (the DSP is 800x600, and some people may be running their resolution at that

__________________

HunterZ

I think it might be a smart idea to make the objects and/or the DSP window resizable. It might also be cool if the DSP window were zoomable and/or scrollable, possibly even with a thumbnail map.

I find the fixed size to be limiting, personally.

The ultimate in cool of course would be a 3D DSP window

__________________
Athlon XP 3200+, Gigabyte GA7N-400Pro2 Rev 2.0 (nVidia nForce2 chipset), 1 GB DDR400 (CAS 2.0, dual-channel), ATI Radeon 9800 Pro 256MB AGP 8x, WinXP Pro SP2, DX9.0c., Logitech Z-5500 5.1 speakers

dj_stick

3D DSP window would jus confuse most people lol
but as for scrolling… has its uses, but its actually easier to use if you can see the whole thing

__________________

HunterZ

Yeah, well my DSP window confuses most people too, so being able to make a 3D arrangement can only help

That's why I mentioned the idea of being able to zoom or see a thumbnail/mini picture.

I'm not knocking the current system though - kX kicks some serious ass and I don't think I could ever live with the Creative drivers (I would probably lose patience just trying to get them to install properly at this point, provided I could even think of a compelling reason to). There are also a million other things that probably should be worked on before adding DSP frills too, but it's nice to dream

__________________
Athlon XP 3200+, Gigabyte GA7N-400Pro2 Rev 2.0 (nVidia nForce2 chipset), 1 GB DDR400 (CAS 2.0, dual-channel), ATI Radeon 9800 Pro 256MB AGP 8x, WinXP Pro SP2, DX9.0c., Logitech Z-5500 5.1 speakers

dj_stick

i see your points there… and yes it is nice to dream… (24/192 w/ kX)

__________________

tubus

Re: 3538 Suggestions

quote:

Actually, with 'bigger connector-boxes' I mean just the very tiny boxes to grab the 'wires' between the DSP-objects.
Make them bigger, they are very easily missed, no need to change anything else!
Say, in the left third of the DSP-object you always grab the nearest input, in the middle third you grab the object itself, in the right third you grab the nearest output.
A very minor change indeed, but much less precission-motoric needed then, = more resources left over to actual *thinking*

/tubus

dj_stick

hmm i see ur point, but if u increase the size of the connector "blocks" you may also have to increase the size of the entire module… thats my reasoning for my view

__________________

tubus

not necessarily, well may be the 'cool look' is suffering a bit, but i think we are also supposed to actually *work* withthe DSP-window, not only to look at it.

Well, may be this point is only *my* problem, since i'm more the 50years old
(which may qualify me as a *real* senior member)

dj_stick

ah lol… in that case have you tired using the magnifier aceesibilty tool that comes with windows?

__________________

HunterZ

I think it would be better if the connector pin under the mouse would light up when the mouse cursor is hovering over it so you can see if you're over it or not, and the response area of the pin should be as large as possible (larger than the graphical representation of it). I'm not sure, but being able to create "wires" by double-clicking on and output and then an input might be more user-friendly than the current click-and-drag system (on the other hand, it may be less friendly - it's hard to tell without actually implementing it)

__________________
Athlon XP 3200+, Gigabyte GA7N-400Pro2 Rev 2.0 (nVidia nForce2 chipset), 1 GB DDR400 (CAS 2.0, dual-channel), ATI Radeon 9800 Pro 256MB AGP 8x, WinXP Pro SP2, DX9.0c., Logitech Z-5500 5.1 speakers

Toadly_Ossum

Im still learning the DSP myself.

I agree that the DSP connects and boxes are to small, I generally run resolutions higher than 1024X768, and they get real small at that res. being able to resize, reshape the components and connectors would be helpful.

Color coding of different input,output and bus connecters would be helpfull to me as well.

tubus

... tried or tired, that is here the question ...

/tubus

tubus

quote:

--------------------------------------------------------------------------------
ah lol… in that case have you tired using the magnifier aceesibilty tool that comes with windows?
--------------------------------------------------------------------------------


... tried or tired, that is here the question ...

/tubus

dj_stick

lol sorry… tried

__________________

NightBreed

Would be great if the DSP's in the dsp window could be locked down, so you couldnt accidently drag them when you didnt want to.

Lex Nahumury

Tubus,
>>Why in a MIDI-Application the the 'kX-Control'-Port is a Input-device??*
This depends on the application. i.e. in Cubase SX it apears as both.

>>If the 'kX-Control'-Port is supposed to control the kX-effects, then seen from the controlling Program it >>should obviously be an output-port .
Yep,..and it *is* a midi-Output port, so use it that way.

Bottom line;
No matter what your app. reports; It's a internal midi-out to control (automate) those kX DSP plugins
that are written to respond to midi messages.

/LeMury

BiCho

i would love to see tips showing you which the destination of the cable, take a look at reason, when you put the pointer over a cable, it shows you which cable is that remotely connected to, instead of telling you what are you pointing at

__________________
Audiotecna - Innovación Musical
Distribuidora oficial de Ortofon DJ, Native Instruments and Moog Music para Colombia (1)8073934

tubus

Thnx LeMury
Yes, the 'kX-Control' miraculously appeard on the list, once i opened the 'kX-Control' input port

Actually i was thinking (hoping), that 'kX-Control'-Port if on the input-port list, really *is* an input port too.
That is, if you press any key on the remote-control out of this port would come a (any) MIDI-message.
Say Controller-number 'whatever' with the keynumber as its databyte, this would be very nice indeed.
And again, i think very little coding needed! (Well may be not, since kX up to now does not do any MIDI-ouput at all)

/tubus

BiCho

what about renaming the channels in the tweak windows? the same way you can do it in Reason's mixer.

__________________
Audiotecna - Innovación Musical
Distribuidora oficial de Ortofon DJ, Native Instruments and Moog Music para Colombia (1)8073934

dj_stick

tweak windows? you mean the mixer pages ,Rec, I/O etc… that kinda defeats the purpose…

__________________

BiCho

some modules say channel0, channel1, channel2, etc. but i want them to read out guitar, bass keyboards, etc. is that possible?

__________________
Audiotecna - Innovación Musical
Distribuidora oficial de Ortofon DJ, Native Instruments and Moog Music para Colombia (1)8073934

BiCho

In fact, Reaktor has exactly that function. you can send the movement of the slider to an external MIDI port. in that way you can record the mixer movements with the help of your mouse, or your keyboard, back into the sequencer. it would be a lovely feature


cheers

BiCho

__________________
Audiotecna - Innovación Musical
Distribuidora oficial de Ortofon DJ, Native Instruments and Moog Music para Colombia (1)8073934

dj_stick

when i have the time i will test in logic whether i can use sliders in the environment to control kx devices… if so i will post my results

__________________

BiCho

what about sending windows to front when clicking on them on the DSP?

__________________
Audiotecna - Innovación Musical
Distribuidora oficial de Ortofon DJ, Native Instruments and Moog Music para Colombia (1)8073934

dj_stick

one major suggestion- when double-clicking the fxbus module in the DSP, open up the kX Router Windows

__________________