KVR Audio

UncleAge · Post by **UncleAge** » Sun Jun 05, 2016 7:41 pm

resistent wrote:?..The modules need to be a bit bigger...

You can do this in the canvas area using the zoom (magnifying glass) near the top right of the screen.

ThomasHelzle · Post by **ThomasHelzle** » Sun Jun 05, 2016 7:55 pm

WXLF wrote:Also this may be an ignorant question, but why don't the parameters show up on the device panel like other VST's? (in bitwig studio)

If you check the Macro node, there you can set a parameter called "Auto lane" which first had me stumped too, but it's "Auto(mation) lane", so if you set a macro to use Auto lane 1 than that corresponds to automation parameter "1" in your image.
Would be cool if the parameter in Bitwig would pick up the Macro name though...

I think in a modular this kind of approach makes sense since there are no fixed parameters and having all parameters of all components in the automation list would get cluttered very fast...

Cheers,

Tom

mangadrive · Post by **mangadrive** » Sun Jun 05, 2016 7:55 pm

ThomasHelzle wrote:In Bitwig (and in StudioOne) there is a blacklist for plugins that crashed before:

In Bitwig you go to Preferences -> Plug-in management -> Scroll down and click on "Show errors found with plugins" and in the panel shown then you can either look for Tangle and hit the "Rescan" button behind it or "Rescan All" to check all failed plugins again (which makes sense every now and then to do to see if something is fixed that was broken).

In Studio One there is a similar thing, when starting it should show plugins not scanned since they crashed before. Go to Studio One -> Options -> Locations -> VST Plugins and click "Reset Blacklist". That will scan all problematic plugins again and if the Runtimes fixed the problem you should then see the plugin.

Cheers,

Tom

Ok that's embarrassing. One of the reasons I went up to Win10 is because I couldn't get Bitwig to work in 7. I mostly bought it for the keylab and tossed it, but was a bonus with the upgrade haha. I've never had this issue with Studio One 3 so didn't know about it. FL Studio will spoil you on ease of use at least.

So to confirm: 64 bit plugin now working in FL12, Bitwig and Studio One 3 (64 bit versions respectively). 32 bit is still no dice in FL/Bitwig where it should show. Studio One 3 64 understandably won't have it either way. I have no personal care for this but obviously it's not all about me So..

Maybe this error from Bitwig helps though?

C:\Audio\Plugins\64BIT\Tangle32.dll

com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Could not read VST plug-in metadata
64 bit plugin host reported errors: Pluginhost returned non zero exit code -1

32 bit plugin host reported errors: Pluginhost returned non zero exit code -1
-------------------------------------------------------------------

Ignore the fact the folder is called 64BIT. I was just trying to help with a solution so I copied it over to the directory.

deastman · Post by **deastman** » Sun Jun 05, 2016 7:58 pm

thetechnobear wrote:any chance of MPE support (voice per midi channel) ?

minimal support would require, voice to be allocated per midi channel , and capable of receiving pitchbend (+/- 48 semi) , channel pressure, and CC 74 (for timbre).

+1 on this!

Aloysius · Post by **Aloysius** » Sun Jun 05, 2016 8:07 pm

I'd never buy Mangle from you. As a Neighbours fan from the 80s, I can't get past this face:

Nell Mangle. Not vey inspiring.

I like the sound of your new synth though, so I'm gonna check it out.

c_voltage · Post by **c_voltage** » Sun Jun 05, 2016 8:24 pm

widdershins wrote:
c_voltage wrote:Guys, please try make wavetable blending, i.e. transition between waves in osc (especially in manual mode) - it works for you or not ?
Hi there, I think the UI is unclear right now. There is a small button above the wave number (i.e. 1, 2, 3, 4). This must be on (orange) for the wave to be activated for blending.

Oh really then works ! Ty

widdershins · Post by **widdershins** » Sun Jun 05, 2016 9:01 pm

Aloysius wrote:I'd never buy Mangle from you. As a Neighbours fan from the 80s, I can't get past this face:

Nell Mangle. Not vey inspiring.

I like the sound of your new synth though, so I'm gonna check it out.

Bit before my time, I'm afraid: I'm a Neighbours fan from the 90s.

ThomasHelzle · Post by **ThomasHelzle** » Sun Jun 05, 2016 9:04 pm

That modulateable delay is awesome.
Check this preset and just hold very long notes:
http://www.screendream.de/stuff/TheTang ... erator.zip
Instant endless Ambient...

Sometimes the levels get too high - would an optional limiter on the output make sense?

Cheers,

Tom

UncleAge · Post by **UncleAge** » Sun Jun 05, 2016 9:40 pm

I think I've spent 3 hours just playing with the sequencer. What a unique approach to a component. I'm sure this will need a small tutorial all its own.

Also, so far the save/load feature (in the sequencer component) is not working but I'm sure its on its way like a lot of other things.

OSX 10.9.5
Reaper 4.61/64bit

widdershins · Post by **widdershins** » Sun Jun 05, 2016 11:38 pm

Hi all, Thomas Helzle emailed me some terrific feedback and bug reports, and I thought I might reproduce my answer to him here, as it contains some useful info. I will probably be pushing a hotfix tomorrow with some fixes for the more common problems people are having (some are already fixed), and I've indicated those in my answer:

1. You can delete a connection by double clicking the 'arrow' in its centre. This isn't obvious, I know, I need to find a way to hint this to the user.

2. Good point on UI persisting state like preset & voicing bars, plus zoom, I'll implement that soon.

3. Crash when connecting osc out to it own frequency input - oops, that shouldn't be possible! Feedback is not implemented right now, it's coming soon... I thought I disabled this action but maybe not... It's disabled in the hotfix.

4. Outputs: yes, I am planning multi-output, and you will be able to add more outputs for this purpose. Since multi-out's not done yet, I disabled the option to add more outputs - but forgot you may delete the only output! I'll disable deleting the output in the hotfix.

5. Settable default zoom - good idea, added to features todo list

6. Names of components: Yes, it would be a good idea to fit the names of the components someplace. For example, I'm aware the delay component gives no clue that's what it does! I want to keep things uncluttered, so I will find a way to do this somehow...

7. Good point again about the 'x' for connection strength not being obvious... I guess in my mind it was a multiplication symbol, but it does suggest deletion, you're right. I have changed it to a simple dot on the hotfix, but I'll think of something better for it soon.

8. Connection strength dot thingy fading away - yeah I guess I wanted to hide it if it's not gonna be used... Maybe a rethink.

9. Muting connections: very good idea, added to feature list. I think it would also be nice to be able to disable whole components, that will go on there too.

10. Plugin crashes on clicking an output dot - yep, silly regression that got through, it's fixed in the hotfix.

11. Should have done a closed beta - yeah... fair point. Overexcitement after long months of toil....

12. Save and load buttons in the Sequencer and Quantizer do nothing - Yep, not implemented yet, there will be 'sub-presets' for some components like these. Easy to do, I just haven't got around to it yet...

13. Searches in waveform browser should persist - good idea.

14. Component panels being added/replaced/disappearing weirdness - yep, working on this bug.

15. Triggering envelope component with the sequencer - Hmm, good idea, would be nice to have a 'reset' input that takes env back to start (or loop start) when the input crosses 1.

Thanks everyone for a wonderful response, useful bug reports and your patience while I fix these silly bugs. Means the world to me

WXLF · Post by **WXLF** » Mon Jun 06, 2016 1:12 am

ThomasHelzle wrote:
WXLF wrote:Also this may be an ignorant question, but why don't the parameters show up on the device panel like other VST's? (in bitwig studio)

If you check the Macro node, there you can set a parameter called "Auto lane" which first had me stumped too, but it's "Auto(mation) lane", so if you set a macro to use Auto lane 1 than that corresponds to automation parameter "1" in your image.
Would be cool if the parameter in Bitwig would pick up the Macro name though...

I think in a modular this kind of approach makes sense since there are no fixed parameters and having all parameters of all components in the automation list would get cluttered very fast...

Cheers,

Tom

Ah, okay. Makes sense.. Thanks, Tom

Cheers,

Richie

emcee · Post by **emcee** » Mon Jun 06, 2016 1:18 am

widdershins wrote:
Aloysius wrote:I'd never buy Mangle from you. As a Neighbours fan from the 80s, I can't get past this face:

Nell Mangle. Not vey inspiring.

I like the sound of your new synth though, so I'm gonna check it out.
Bit before my time, I'm afraid: I'm a Neighbours fan from the 90s.

Was wondering if the actress who played old Nell was still with us - turns out she's 91 and also this from wikipedia:
Gray left her role of Mrs Mangel after receiving abuse from Neighbours fans who could not distinguish fact from fiction. As such, this was Vivean Gray's last acting role and she retired, leading a very private life ever since.

Another tenuous link from Tangle to Mangel:
She initially wanted to become a jazz pianist, but decided to choose acting

himalaya · Post by **himalaya** » Mon Jun 06, 2016 10:06 am

deastman wrote:
thetechnobear wrote:any chance of MPE support (voice per midi channel) ?

minimal support would require, voice to be allocated per midi channel , and capable of receiving pitchbend (+/- 48 semi) , channel pressure, and CC 74 (for timbre).
+1 on this!

+1000000

Please add to that list note-off-release as well.

Also, please add poly-pressure (if not already implemented).

Jorgeelalto · Post by **Jorgeelalto** » Mon Jun 06, 2016 11:27 am

I'll wait for some updates and that stuff, but this is amazing. My next buy.

Gone soft · Post by **Gone soft** » Mon Jun 06, 2016 12:33 pm

Looks like a bunch of fun, I´ll happily take some tangled virtual wires tank you.

Will wait for feedbackloops to be in place as I agree that's a lot of the fun with modulars. Hopefully we can freely route for instance the output of an oscillator through filters and delays (and perhaps throw a little AM and some other stuff int i the mix as well) before routing them back to the phase input and make a wonderfull virtually tangled up mess of it all.

Have you considered ringmodulation (as in bipolar AM), or is that perhaps somehow allready possible?

Tangle: new modular FM synth