KVR Audio

trimph1 · Post by **trimph1** » Tue Dec 21, 2010 2:24 am

AgiKvr wrote:
Nielzie wrote:
AgiKvr wrote:
Nielzie wrote:Does v3 differ much from v2 sound-wise?
TOP SECRET!!!

the answer is secretely kept in an ancient crypt in vatican...
a 33 degree of freemasonry only knows.....

Right, I'll take that as a "none of your non-betatester's business" then
I'm not beta tester too (unfortunately!)

aaahhhhhhhh---bugger off with the beta-testing already!!!

No public beta...

core · Post by **core** » Tue Dec 21, 2010 11:51 am

Nice, nice... NICE!

trimph1 · Post by **trimph1** » Tue Dec 21, 2010 11:55 am

core wrote:Nice, nice... NICE!

robogone · Post by **robogone** » Tue Dec 21, 2010 2:43 pm

trimph1 wrote:No public beta...

Which allows Sonic Charge to apply some quality control to the beta testers. They ensure that the testers already know the product, and that they can vet beta testing experience first.

xerxes[no] · Post by **xerxes[no]** » Tue Dec 21, 2010 4:40 pm

Great news! Free upgrade is awesome! One of the drums machines I use most by far..

Bronto Scorpio · Post by **Bronto Scorpio** » Fri Dec 24, 2010 4:52 pm

They just revealed one of the new features: Morphing

It seems to be really nice! I can't wait to try it anymore

http://www.soniccharge.com/

Cheers
Dennis

AgiKvr · Post by **AgiKvr** » Fri Dec 24, 2010 9:23 pm

Woooooo!!!
AWESOME

Have you heard the sound cloud v3 demo?
In my opinion MT3 sounds better now (don't know if external fx were used)

And Synplant "semi-random" philosophy for me is very inspiring.

Big Thanx Lidstrom brothers!!! And,naturally,Merry XMas!!!

wetdentist · Post by **wetdentist** » Wed Dec 29, 2010 1:33 pm

the morphing feature sounds pretty cool, but i am much more interested in version 3.0 being x64 so that it will run seamlessly inside Maschine 1.6 when that is released

malström · Post by **malström** » Wed Dec 29, 2010 2:23 pm

wetdentist wrote:the morphing feature sounds pretty cool, but i am much more interested in version 3.0 being x64 so that it will run seamlessly inside Maschine 1.6 when that is released

Let me take this opportunity to disappoint you right away. MicroTonic 3.0 will be 32-bit only.

I know that support for 64-bit is inevitable, but we are still a tiny company with limited resources and support for a new platform (which after all 64-bit is) is something that has to be considered carefully. I am 100% dedicated to making software that runs flawlessly (which is a hell of a task for a plug-in developer, as any other developer can confirm). On Mac especially, going 64-bit will mean a lot of new code that has to be iterated and tested since Apple so kindly removed support for "Carbon", the API that everyone (including me) used up until a few years ago. Add to this the fact that over 50% of our user base (judging from the survey we did when applying for beta-testers) still use hosts that have no 64-bit support, and the ones that have 64-bit basically all run their hosts in 32-bit mode.

Again, we will naturally support 64-bit eventually, but what we have focused on here is adding new features instead, making MicroTonic 3.0 the best possible 32-bit version ever. We are making sure that all existing users can upgrade without problems, even the ones on OS X 10.4 PPC Macs. We will also do our best to officially support the 64<->32-bit bridges during the transition phase.

Finally, this has probably been said many times before, but I still want to remind you that 64-bit only improves one single thing. It extends the addressable process memory space to over 4GB. In practice, this will allow you to load more than 2GB of samples into *memory* for your projects. Notice that "heavier" sample-based products usually stream from disk, which is better anyhow for quicker startup times etc, and you will gain much more from adding SSD drives to your system than going 64-bit.

Any talk of improved performance apart from this is a hit-and-miss question. It is just irrelevant. You lose some performance on the increased amount of data that has to be shuffled to/from the processor and you gain some by the new processor registers Intel so kindly added. Which I guess they did to compensate for the performance loss of 64-bit in the first place.

wetdentist · Post by **wetdentist** » Wed Dec 29, 2010 2:45 pm

i understand that there is only improved performance regarding access to memory, in theory, and that it doesn't matter for all those who use 32 bit DAWs. however from my point of view, bridgers do not do your software any justice. for example, with Synplant in Sonar 8.53 x64 with jBridge, when i open up a saved project, i have to reload my Synplant preset before every time i want to hit "play"

Teksonik · Post by **Teksonik** » Wed Dec 29, 2010 2:49 pm

malström wrote: Finally, this has probably been said many times before, but I still want to remind you that 64-bit only improves one single thing. It extends the addressable process memory space to over 4GB. In practice, this will allow you to load more than 2GB of samples into *memory* for your projects. Notice that "heavier" sample-based products usually stream from disk, which is better anyhow for quicker startup times etc, and you will gain much more from adding SSD drives to your system than going 64-bit.

Any talk of improved performance apart from this is a hit-and-miss question. It is just irrelevant. You lose some performance on the increased amount of data that has to be shuffled to/from the processor and you gain some by the new processor registers Intel so kindly added. Which I guess they did to compensate for the performance loss of 64-bit in the first place.

Thanks so much for addressing this subject. I get the feeling that many people think that 64 bit is "twice as good as" 32 bit when begging for 64 bit versions of plugins. Other than not having to use a Bit Bridge I see no practical reason for a plugin like Microtonic to have a 64 bit version.

wetdentist · Post by **wetdentist** » Wed Dec 29, 2010 2:59 pm

Teksonik wrote: Thanks so much for addressing this subject. I get the feeling that many people think that 64 bit is "twice as good as" 32 bit when begging for 64 bit versions of plugins. Other than not having to use a Bit Bridge I see no practical reason for a plugin like Microtonic to have a 64 bit version.

it's much more than twice as good if the plugin and the bridging technology don't work together as they should

Teksonik · Post by **Teksonik** » Wed Dec 29, 2010 3:08 pm

wetdentist wrote:
Teksonik wrote: Thanks so much for addressing this subject. I get the feeling that many people think that 64 bit is "twice as good as" 32 bit when begging for 64 bit versions of plugins. Other than not having to use a Bit Bridge I see no practical reason for a plugin like Microtonic to have a 64 bit version.
it's much more than twice as good if the plugin and the bridging technology don't work together as they should

Are you being held back by the memory limits of 32 bit? If not then there is no real reason to go 64 bit..............

wetdentist · Post by **wetdentist** » Wed Dec 29, 2010 8:06 pm

thanks, teksonik, i will just go back in my time machine now

LeVzi · Post by **LeVzi** » Wed Dec 29, 2010 8:20 pm

As much as I can see people wanting native 64bit plugins, surely if they are that limited, jbridge is the best option.

Use it as a bridge for a 32bit plugin in a 32bit host, it basically takes the plugin "out" of the total RAM use for the DAW's executable and gives the plugin it's own RAM space, I doubt a single plugin is going to go over 2gig of space. I don't think there is any limit on the number of jbridged plugins you can run at a time.

This stops the need for the DAW to be 64bit (in theory) unless you really do use a lot of audio etc that take up the RAM.

That's how I understand it, I might be wrong, maybe umd (Jbridge's creator) could explain it better, or does in the jbridge thread.

I currently use jbridge to bridge in a 64bit plugin to a 32bit host, which allows the plugin (Kontakt) to use as much RAM as it wants outside of Cubase's .exe, all RAM issues disappeared after that

Just something to think about regards the 64bit vs 32bit issue, and a possible workaround.

Back on topic, I am looking forward to this version of MicroTonic

And seeing how much eardrum damage I can cause with it

The MicroTonic 3 Thread