KVR Audio

pj geerlings · Post by **pj geerlings** » Tue Feb 28, 2006 3:23 pm

zeoy wrote:already got it pj. thanx. What's the best way to inform you about impressions, potential bugs or whatever?

Either in this thread or by email - whichever is easiest for you

peace,
pj

zeoy · Post by **zeoy** » Tue Feb 28, 2006 3:53 pm

Since I was curious about it, I gave it a quick spin here at work (note: crappy PC speakers).
Loaded fine in T1.6 (demo mode here) with an old Barton 2400+ AMD PC. Nothing unusual. Horn EQ gives a sweet color to Nubile's higher registers. All controls worked smoothly. Excellent GUI work. One minor thing though you already said that the drive section is at a preliminary stage: is it before or after the horn section? I'm asking this because it sounded like it was after, and the amount of drive was following the horn's pulse. Like distorting the rotated sound instead of rotating the distorted sound if you know what I mean. I'm not a Hammond expert but I thought that drive before horn is the right order. More serious comments after the real test at home.
Thanx again pj.

pj geerlings · Post by **pj geerlings** » Tue Feb 28, 2006 4:43 pm

zeoy wrote:Since I was curious about it, I gave it a quick spin here at work (note: crappy PC speakers).
Loaded fine in T1.6 (demo mode here) with an old Barton 2400+ AMD PC. Nothing unusual. Horn EQ gives a sweet color to Nubile's higher registers. All controls worked smoothly. Excellent GUI work. One minor thing though you already said that the drive section is at a preliminary stage: is it before or after the horn section? I'm asking this because it sounded like it was after, and the amount of drive was following the horn's pulse. Like distorting the rotated sound instead of rotating the distorted sound if you know what I mean. I'm not a Hammond expert but I thought that drive before horn is the right order. More serious comments after the real test at home.
Thanx again pj.

Glad to hear you could try it out a little - the distortion element is the very first process in the chain - it comes before the crossover and the horn EQ. The filter parameters (Fc/Q/Gain) of the Horn EQ are fixed (to cut down on GUI elements) and probably need some tweaking. These parameters (along with every other parameter I could think of) will be available via MIDI CC# (and config file) in the final version. I hope that clears things up a litle ( sorry for all those parenthetic additions

)

peace,
pj

zeoy · Post by **zeoy** » Tue Feb 28, 2006 4:49 pm

That's what I supposed that was the proper chain but somehow it sounded to me like drive was at the end of the chain. Damn PC speakers

More on this tomorrow pj

amoebe · Post by **amoebe** » Tue Feb 28, 2006 8:54 pm

The filter parameters (Fc/Q/Gain) of the Horn EQ are fixed (to cut down on GUI elements)

There's plenty of available space at the right

Here's an unrequested feature I found.
After I automated one of the switches in Tracktion, the GUI only shows the switch in it's ON state. It looks like the switch doesn't get turned off anymore. I know it's a GUI issue, because the parameters still follows it's automated value, the GUI only stops showing the switches' correct state. If a switch isn't automated I can switch it on and off.
Also, this doesn't happen to knobs. I can see them move according to their parameters automated value.

Can someone confirm this? PJ can't reproduce it. It might very well be a Tracktion specific issue.

Meffy · Post by **Meffy** » Tue Feb 28, 2006 8:57 pm

I don't want the goodie but wanted to say two things. 1) That's a luscious GUI! 2) Wouldn't the natural friend for a NubiLE be a ViriLE? ;-) Sorry, couldn't resist.

pj geerlings · Post by **pj geerlings** » Tue Feb 28, 2006 9:27 pm

amoebe wrote:
The filter parameters (Fc/Q/Gain) of the Horn EQ are fixed (to cut down on GUI elements)
There's plenty of available space at the right

Yeah, but then there are twenty or so other parameters that would want a piece of the real estate

amoebe wrote:Here's an unrequested feature I found.
After I automated one of the switches in Tracktion, the GUI only shows the switch in it's ON state. It looks like the switch doesn't get turned off anymore. I know it's a GUI issue, because the parameters still follows it's automated value, the GUI only stops showing the switches' correct state. If a switch isn't automated I can switch it on and off.
Also, this doesn't happen to knobs. I can see them move according to their parameters automated value.

Can someone confirm this? PJ can't reproduce it. It might very well be a Tracktion specific issue.

Just a thought - what actual values are being used in the automation? SpinnerLE expects "OFF" to be a midi data value strictly less than 64 (0x40) and "ON" to be greater than or equal to 64.

peace,
pj

FEV · Post by **FEV** » Tue Feb 28, 2006 9:30 pm

pj geerlings wrote:It's called SpinnerLE (GUI by amoebe)

Hmmm. I don't see any multi paged views

cheers,
Bart

pj geerlings · Post by **pj geerlings** » Tue Feb 28, 2006 9:32 pm

FEV wrote:
pj geerlings wrote:It's called SpinnerLE (GUI by amoebe)
Hmmm. I don't see any multi paged views

cheers,
Bart

I need to talk to you about that ...

soon

amoebe · Post by **amoebe** » Tue Feb 28, 2006 10:39 pm

Just a thought - what actual values are being used in the automation? SpinnerLE expects "OFF" to be a midi data value strictly less than 64 (0x40) and "ON" to be greater than or equal to 64.

As far as I know, automation works with values from 0 to 1. But the parameter values don't seem to be the problem, as Spinner responds to them exactly as it should.

pj geerlings · Post by **pj geerlings** » Tue Feb 28, 2006 10:56 pm

amoebe wrote:
Just a thought - what actual values are being used in the automation? SpinnerLE expects "OFF" to be a midi data value strictly less than 64 (0x40) and "ON" to be greater than or equal to 64.
As far as I know, automation works with values from 0 to 1. But the parameter values don't seem to be the problem, as Spinner responds to them exactly as it should.

good point - i'm currently stumped ...

Funkybot · Post by **Funkybot** » Tue Feb 28, 2006 11:00 pm

Hey PJ I just sent you a similar bug report, the automation works as expected as far as how it's expected to sound (leslie going from slow to fast, on/off, etc) but the GUI is only being updated on the positive automation values not the negative ones (i.e. the lights turn on but not off, or the switch moves from slow to fast but not back again).

MrM · Post by **MrM** » Wed Mar 01, 2006 1:37 am

A quick question about the accelerator and the decelerator; when should they work; when switching the engage button, or when switching between 'fast' and 'slow'? And are those numbers the 'time' in seconds, or is it the 'speed'?

BTW, the sound is way cool!
No bugs founds; very stable, low CPU, good sound, good GUI

Scotty · Post by **Scotty** » Wed Mar 01, 2006 1:46 am

Yes, what a great looking gui. It just invites you to reach out and adjust the knobs and dials. Fantastic look!

pj geerlings · Post by **pj geerlings** » Wed Mar 01, 2006 2:34 am

MrM wrote:A quick question about the accelerator and the decelerator; when should they work; when switching the engage button, or when switching between 'fast' and 'slow'? And are those numbers the 'time' in seconds, or is it the 'speed'?

Acceleration is the time (in seconds) to ramp from slow to fast. Similarly the Decelerate time is to ramp from fast to slow.

MrM wrote:BTW, the sound is way cool!
No bugs founds; very stable, low CPU, good sound, good GUI

Thanks - great to hear!

NuBi LE has a new friend ...