KVR Audio

adamszabo · Post by **adamszabo** » Tue Apr 03, 2018 4:08 pm

I downloaded the UltraNova editor to see what it does, and yup, just as I thought, the tabs are for showing information, you cant control parameters there either.

AnX · Post by **AnX** » Tue Apr 03, 2018 4:24 pm

That doesnt mean its not a good idea.

adamszabo · Post by **adamszabo** » Tue Apr 03, 2018 4:38 pm

I never said its not a good idea, I only said it would cause too many problems and basically its a trivial thing, I have much more important things to work on.

Halonmusic · Post by **Halonmusic** » Tue Apr 03, 2018 7:35 pm

adamtrance wrote:I never said its not a good idea, I only said it would cause too many problems and basically its a trivial thing, I have much more important things to work on.

Like an update to JP6?

v1o · Post by **v1o** » Tue Apr 03, 2018 11:23 pm

Ingonator wrote:
adamtrance wrote:Hmm, I didnt want to post until the 64 bit is finished so that it could be my 604th post, but oh well, ill do it when the 128 bit comes out for my 1208 post

Anyway I appreciate all ideas and comments but you have to look at it from a design/programmers point of view. When I looked at the Virus GUI, I was investigating if there is anything I could do a different way. Look at the Virus control:

There are a lot of tabs at the top, but convey absolutely zero information. Can you tell from this screenshot what filters they use? How many oscillators are enabled? Which effects are turned on? Nope nothing, you have to go to each page to see whats going on. I wanted some easy way to see the most common parameters, and since Viper is a VST you dont need multi outs (since you can load up as many instances as you want, however you can only have ONE Virus control thats why it needs multi outs), I didnt need the left most part, it was just a waste of space. Then I thought it would be the perfect place to put some bigger tabs that show information for free.

Now its a nice idea to make the controls in the tabs changeable, but it will turn into a logistics nightmare. Just think about this, I have to create clickable mouse areas (green squares) for the knobs. But then if I allow knobs to be tweaked people will complain they want to choose filters and all other stuff, so then I have to create more mouse areas (blue squares). I would be forced to do this because it makes zero logical sense to allow only a few parameters to be tweaked, how would I explain that to a user? They would have to understand the whole thing right away. Ok so now that all those parameters are editable how would it work? If you are in the Osc section but want to change the cutoff without going to to filter section, then when you click on the little cutoff, should the tab switch to the filter section or stay? If it says then if you want to go to the filter you have to click around the controls and that would be a pain in the behind. Plus what if someone wants to go to the filter section, but clicked on the cutoff and changed it by accident? then I will get complaints about that. Then people want options for making it behave differently. As you can see it will become a nightmare quickly, plus I can go on and on with all the issues, but I have to get back to the 64 bit. I hope you guys see its too much trouble for something small. The easiest way to solve is to have them as big tabs that convey information and problem solved. I cant make everybody happy.
Actually for me the design of Viper looks closer to the Novation UltraNova VST editor than the Virus TI editor, at least the left part of the Viper GUI:

http://global.novationmusic.com/sites/d ... Editor.png

FWIW i had owned a Virus TI MK1 desktop from 2006 until 2015 and an UltraNova since 2015 so i had used both VST editors.

Why did you sell the Virus and keep the Ultranova? The Ultranova got a lukewarm reception from what I remember when it came out.

v1o · Post by **v1o** » Tue Apr 03, 2018 11:25 pm

Halonmusic wrote:
adamtrance wrote:I never said its not a good idea, I only said it would cause too many problems and basically its a trivial thing, I have much more important things to work on.
Like an update to JP6?

Obviously 64 bit and 128 bit.

Halonmusic · Post by **Halonmusic** » Wed Apr 04, 2018 1:09 am

v1o wrote:
Halonmusic wrote:
adamtrance wrote:I never said its not a good idea, I only said it would cause too many problems and basically its a trivial thing, I have much more important things to work on.
Like an update to JP6?
Obviously 64 bit and 128 bit.

64bit isnt that important. And 128bit? Come on.

v1o · Post by **v1o** » Wed Apr 04, 2018 1:21 am

64 bit is more important than Oxygen from the Amazon. You can’t launch 32 bit plugins in this day and age.

Halonmusic · Post by **Halonmusic** » Wed Apr 04, 2018 3:59 am

v1o wrote:64 bit is more important than Oxygen from the Amazon. You can’t launch 32 bit plugins in this day and age.

Sure you can. I use 32bit plugins everyday.

rasmusklump · Post by **rasmusklump** » Wed Apr 04, 2018 11:43 am

Really ? AGAIN this debate ?

Sorry, but 64 bit should be the most important point.

I don't even download free 32 bit plugins anymore.

wagtunes · Post by **wagtunes** » Wed Apr 04, 2018 11:45 am

Halonmusic wrote:
v1o wrote:64 bit is more important than Oxygen from the Amazon. You can’t launch 32 bit plugins in this day and age.
Sure you can. I use 32bit plugins everyday.

Yeah, true. 5 to 10 years from now, unless you've got spare parts laying around, good luck finding a brand new machine that's 32 bit. So pray your 32 bit machine lasts longer than you do because once that's gone, good luck running your 32 bit plugs "smoothly" without bridging, which is never a 100% perfect solution, which I found out the hard way. Almost none of my 32 bit plugs work without some kind of glitch, even with JBridge.

recursive one · Post by **recursive one** » Wed Apr 04, 2018 11:49 am

According to Adam, 64 bit is in progress and will be released any time soon

AnX · Post by **AnX** » Wed Apr 04, 2018 11:49 am

wagtunes wrote:
Halonmusic wrote:
v1o wrote:64 bit is more important than Oxygen from the Amazon. You can’t launch 32 bit plugins in this day and age.
Sure you can. I use 32bit plugins everyday.
Yeah, true. 5 to 10 years from now, unless you've got spare parts laying around, good luck finding a brand new machine that's 32 bit. So pray your 32 bit machine lasts longer than you do because once that's gone, good luck running your 32 bit plugs "smoothly" without bridging, which is never a 100% perfect solution, which I found out the hard way. Almost none of my 32 bit plugs work without some kind of glitch, even with JBridge.

You can run 32 bit hosts on a 64 bit OS. Works fine on Win7 and 10. No bridge needed.

chk071 · Post by **chk071** » Wed Apr 04, 2018 11:54 am

Except for the hosts which don't even have a 32-bit version anymore (Cubase, Reason, Logic, more to follow for sure).

wagtunes · Post by **wagtunes** » Wed Apr 04, 2018 12:00 pm

AnX wrote:
wagtunes wrote:
Halonmusic wrote:
v1o wrote:64 bit is more important than Oxygen from the Amazon. You can’t launch 32 bit plugins in this day and age.
Sure you can. I use 32bit plugins everyday.
Yeah, true. 5 to 10 years from now, unless you've got spare parts laying around, good luck finding a brand new machine that's 32 bit. So pray your 32 bit machine lasts longer than you do because once that's gone, good luck running your 32 bit plugs "smoothly" without bridging, which is never a 100% perfect solution, which I found out the hard way. Almost none of my 32 bit plugs work without some kind of glitch, even with JBridge.
You can run 32 bit hosts on a 64 bit OS. Works fine on Win7 and 10. No bridge needed.

That's assuming that in 10 years they're still making 32 bit hosts. If not, which is a distinct possibility, have fun running Cubase 7 when the rest of the world is on Cubase 15.

Sure, using that same argument, you can still run Windows 95 apps.

On the plus side, you won't have to worry about depending on any support from anyone because they won't be supporting 20 year old apps and OS.

Viper｜1.2.2 update with bugfixes and new skin