KVR Audio

Boardwalk · Post by **Boardwalk** » Thu Apr 28, 2016 12:15 pm

I'd just like to point out that in the original design the logo is meant for the whole synth (as a proportion of the surface).

http://www.synthtopia.com/content/2009/ ... nthesizer/

So if you look to the proportions of the original design; the logo should be about 37.5% procent smaller (8:5) in the design of sergiofrias than it is now.

By the way, the original design knows a rectangle of 2:1 (40×20 inch).

BlackWinny · Post by **BlackWinny** » Thu Apr 28, 2016 12:21 pm

Going so far in the precision concerning simply the logo... perhaps the best would be that you purchase a unit of the true hardware.

wagtunes · Post by **wagtunes** » Thu Apr 28, 2016 12:30 pm

Boardwalk wrote:I'd just like to point out that in the original design the logo is meant for the whole synth (as a proportion of the surface).

http://www.synthtopia.com/content/2009/ ... nthesizer/

So if you look to the proportions of the original design; the logo should be about 37.5% procent smaller (8:5) in the design of sergiofrias than it is now.

By the way, the original design knows a rectangle of 2:1 (40×20 inch).

Seriously? Is this the level of minutia that this forum has descended to?

Boardwalk · Post by **Boardwalk** » Thu Apr 28, 2016 12:50 pm

@wagtunes

No, I guess we are just having fun here.
Besides, A 37.5% smaller logo is not really a trivial point IMHO

Seriously, my contributions are not born out of disobedience nor ingratitude AFAIK

BlackWinny · Post by **BlackWinny** » Thu Apr 28, 2016 12:57 pm

Don't worry, it's taken as a joke.

chk071 · Post by **chk071** » Thu Apr 28, 2016 1:06 pm

Mutant wrote:Nice skin, but the blurry text needs some more work.

Yeah. Also the font seems a bit misplaced, maybe try another one? And the logo is too big. Apart from that, it's splendid.

jbraner · Post by **jbraner** » Thu Apr 28, 2016 1:19 pm

Here's another idea to throw out - and I have absolutely no ability to do this.

For any coders - how easy do you think it would be to analyse a fxp preset file?
If it was easy - it might not be too hard to write a *librarian* (not an editor) to build up banks (as fxb files). Then we'd need to work out how to "load" these in OBXD - besides the normal loading via a DAW.

I know it would be hard to change OBXD - but even if we had to open a separate (librarian) program, it would be so cool to be able to drag presets to and from a bank loaded in the OBXD.
(I'm thinking like the "cart" idea in dexed)

I don't know if this makes sense, or if it would be easy/difficult/impossible - I'm just thinking out loud to see if anyone says "hmm - that just might work"

Otherwise - let's forget it, and use it like it is

layzer · Post by **layzer** » Thu Apr 28, 2016 5:20 pm

is anything ever really "finished"?

.jon · Post by **.jon** » Thu Apr 28, 2016 6:45 pm

It does look pretty ready to me

fmr · Post by **fmr** » Thu Apr 28, 2016 6:49 pm

layzer wrote:is anything ever really "finished"?

Maybe just lift the "Manual" title a little bit. You introduced a gradient in the background grey, didn't you? And also lightened it.

Boardwalk · Post by **Boardwalk** » Fri Apr 29, 2016 8:56 am

I can live with it. Looks very retro somehow. Could be 1930s.
Anyway, I think the logo is still a tad too large. It would be nice if the rectangle of the logo is somewhat smaller than the 'manual' rectangle. So it fits 'in'. So to speak. As a finishing touch

aciddose · Post by **aciddose** » Fri Apr 29, 2016 11:07 am

jbraner wrote:Here's another idea to throw out - and I have absolutely no ability to do this.

For any coders - how easy do you think it would be to analyse a fxp preset file?
If it was easy - it might not be too hard to write a *librarian* (not an editor) to build up banks (as fxb files). Then we'd need to work out how to "load" these in OBXD - besides the normal loading via a DAW.

Extremely easy. The ability to load/save/read/write fxp and fxb files is provided via the "VST-SDK", so it's included in the same source everyone has access to. This file format is incredibly stupid and it's questionable why anyone would want to use it, the one point it has going for it is interoperability between different hosts. An internal preset format would be far more reliable though and if the plug-in currently supports saving state via host interface (fxp/fxb) it already uses an internal preset format.

Difficulty of finding someone willing to do it: Extremely hard.

fmr · Post by **fmr** » Fri Apr 29, 2016 11:20 am

aciddose wrote: Extremely easy. The ability to load/save/read/write fxp and fxb files is provided via the "VST-SDK", so it's included in the same source everyone has access to. This file format is incredibly stupid and it's questionable why anyone would want to use it, the one point it has going for it is interoperability between different hosts. An internal preset format would be far more reliable though and if the plug-in currently supports saving state via host interface (fxp/fxb) it already uses an internal preset format.

Difficulty of finding someone willing to do it: Extremely hard.

You are a coder, and this is now open source. What would be needed to persuade you to take the task upon your shoulders?

aciddose · Post by **aciddose** » Fri Apr 29, 2016 11:28 am

I'd need to have some motivation to examine the source and determine the difficulty involved in getting the code to compile/work, then I'd need about $1500 to cover my time, then I'd need a license to the VST-SDK 2.4 which I assume the project requires. (Otherwise, while I can work on the source of the project itself I can not provide a binary for distribution built with the source it requires.)

None of those are possible. Stienberg as far as I'm aware no longer provides the VST-SDK 2.4 and has replaced it with 3. The version 3 used to contain a copy of 2.4 along with the license documents although again as far as I'm aware it no longer does.

aciddose · Post by **aciddose** » Fri Apr 29, 2016 11:33 am

What I could do is port the project to use some other plug-in format (not VST) which has an open-source compatible license.

My cost would then increase dramatically, perhaps $4500 might cover the extra effort required. Keep in mind these numbers are only a guess of the number of hours that might be required.

Obxd synthesizer