Repro-1 (out now)

[Gadget Fiend]

Here's a version without the Mod Envelope which is apparently too radical for some folks:

[e@rs]

Yo, the LCD screen still shows 'Repro-1'.

[Gadget Fiend]

Yo, the LCD screen still shows 'Repro-1'.

Beta "software." LOL.

[fluffy_little_something]

Regarding velocity and aftertouch modulation, I think it would be better to list the menu items in the GUI order.
Basically, why are there even those menus when one can assign the modulation target by dragging?
The menus would make sense if one could modulate effects parameters as the effect GUI's can't be displayed at the same time as the velocity and aftertouch fields.

[Viktor [TUC]]

The menus would make sense if one could modulate effects parameters as the effect GUI's can't be displayed at the same time as the velocity and aftertouch fields.

That's exactly what you can do, turn on the FX and you can modulate FX parameters.

Viktor

[fluffy_little_something]

The menus would make sense if one could modulate effects parameters as the effect GUI's can't be displayed at the same time as the velocity and aftertouch fields.

That's exactly what you can do, turn on the FX and you can modulate FX parameters.

Viktor

Ah, one has to turn them on first

[Urs]

Oh Ye of Little Imagination (and any capacity for advanced thought).

Well, here's the problem.

You can quickly photoshop anything into a nice UI and stuff, with all features you find fit your purpose. However, our software is actually built around formulas derived from circuit schematics and something called Kirchhoff's Current Law. That is, we have variables for all those little resistors, waveshapers and integrators wherever there are the parts that suggest doing so. We've had our oscilloscope hooked up into the board to verify that our signals look just like the signals our model predicted. If not, we adjusted the model.

I'm not gonna throw that away and start over with something I can't even measure.

[david.beholder]

Great, and by omitting the audio rate modulations we could even save CPU!

And by adding generic filter, reducing internal audio rate it's gonna spare even more CPU. Then use spare cpu for 4 LFOs and 4 ENVs

[wagtunes]

Damn, I ran out of popcorn from last night's election. lol

[fluffy_little_something]

Did the original (which I don't know at all) have velocity sensitivity as well? Would be cool if one could assign it to more than just one target, like to cutoff, env attack and some effect parameter(s)

And those options from the Tweaks panel? For instance the note priority selector? (By the way, I find it odd that there is no normal mode, i.e. neither legato, nor retriggering of the first key when releasing the second key).

[EvilDragon]

Pro-One did not have all those options for note priority, nor velocity, AFAIK.

[AnX]

Im gonna pass on this. Filter is not to my taste. I also dont like the FX much (feels like they have been added to compensate for something...) Would prefer some polyphony over those. GUI is also way too brown....why? The Pro One was black wasnt it? (Long time since ive seen one in person tho...) CPU is huge for a mono synth. I doubt it will be reduced enough by final release to warrant spending cash on a mono.

[koalaboy]

I'm just pointing out that the approach you have adopted is no longer favored in most software shops. Product and UX (who speak on behalf of customers) have finally taken over. LOL.

No they haven't. By a long shot. And they won't for anything that isn't a social media app or some other flashy web-like app.

Apple may like to sell this premise, but that's not how most of the world's software works - it may explain why so much of it is becoming 'style' above 'substance'.

There's always been customer focus - it's just that UX (User eXperience) has become a trendy buzzword, and designers/web developers like to talk about it as being the initial (and most important) part of an 'app'.

Luckily for people that need to actually get things done, most 'software shops' of any quality still work on the fundamentals as well and don't need to conform to the current design-favourite of the month. They're also aware that every customer is different and as such, unless there's a large outcry / consensus on something being 'wrong', there's little point changing anything as it's just opinion.

It's great to have feedback, but I would suggest that telling successful (and respected) developers how they should do their job doesn't achieve anything other than make you look stupid and make people ignore you and/or the thread.

[Urs]

I wouldn't say engineering-driven, I'd say nostalgia-driven.

A week in since the initial beta release, Repro-1 has topped Hive's first week by 100% (i.e. it sold twice as often), Bazille's by 150%. Those were our most successful product launches ever, prior to this one. In fact Repro-1 has sold twice as many copies as Bazille in all of 2016. It's quite remarkable by our standards.

[Gadget Fiend]

I'm just pointing out that the approach you have adopted is no longer favored in most software shops. Product and UX (who speak on behalf of customers) have finally taken over. LOL.

Luckily for people that need to actually get things done, most 'software shops' of any quality still work on the fundamentals as well and don't need to conform to the current design-favourite of the month. They're also aware that every customer is different and as such, unless there's a large outcry / consensus on something being 'wrong', there's little point changing anything as it's just opinion.

Yes, IBM and Intel are clearly trendy, "flavor of the month" companies creating silly social media apps:

http://www.nytimes.com/2015/11/15/busin ... uares.html

https://software.intel.com/en-us/articl ... anguage=es

Here's a suggestion: Try educating yourself before making uninformed statements like the one above that just serve to make you appear utterly clueless.