3 months since the release of Heavier7Strings and being recommanded by Jordan Rudess of Dream Theater and Neil Zaza, Heavier7Strings DEMO VERSION is avaiable now! Download at 
 
Three-Body Technology proudly presents Heavier7Strings, a real-time playable sample-based virtual instrument thats brings back Heavy Metal to your productions. Equiped with a complete effect rack and a patterns library, this metal-style guitar library has everything you need!
The love for music, and a desire to create innovative studio technology was the mainspring that made Heavier7Strings possible. With total of 4 years in the making, using only top quality equipment, more than 10.000 samples were painstakingly recorded in 24-bit and 48 kHz. To top it all off Heavier7Strings comes with a self-developed sampler with no compromise on sound quality.

The following funtions have been disabled in demo version:
-An instructive sound for every 20 seconds.
-Modules in effect rack can be dragged into, but cannot be removed.
-Global bypass cannot be used.
-Presets cannot be saved, including guitar controlling presets and effect rack presets.
-The state of Heavier7Strings is not saved when host DAW saves project.
-The default assignment of MIDI CC cannot be changed. Cannot be used in non-realtime mode.
-DEMO mark on GUI.
 
Enjoy!

Cool, definitely going to check out the demo!

One correction in the list of disabled features:
Shouldn't it be "An INTRUSIVE sound for every 20 seconds"?  Instead of "instructive"?
That would mean the sound every 20 seconds would provide knowledge or information. 

Oh, and there's no download link. But I'm guessing the automated functions of this forum blocked the link.
(Which isn't very instructive either)

I'm downloading the demo right now. 

But I'm wondering if anyone else has had a chance to try the demo version.
One person in the Three-Body Technology forums claimed the INTRUSIVE sound at every 20 seconds was so annoying that he just uninstalled the demo. Because he was unable to enjoy or accurately test out the software.

My suggestion to Three-Body Technology would be to make the intrusive sound every 60 seconds (at least) allowing the user to more accurately and enjoyably check out the software.  Every 20 seconds is a bit too close together.

I just assumed "instructive sound" was a case of creative doublespeak. It instructs you that they're still waiting for your money.
 
I have uninstalled many a demo because of intrusive and annoying beeps, noise bursts or dropouts. Limiting functionality such as saving presets is reasonable, but how the heck are you supposed to evaluate a product that only works for 20 seconds at a time?

Link didn't post because your post count is too low. Here ya go: http://forums.threebodyte...opic.php?f=12&t=60

bitflipper
I just assumed "instructive sound" was a case of creative doublespeak. It instructs you that they're still waiting for your money.
 
I have uninstalled many a demo because of intrusive and annoying beeps, noise bursts or dropouts. Limiting functionality such as saving presets is reasonable, but how the heck are you supposed to evaluate a product that only works for 20 seconds at a time?

Exactly.  Are they so afraid someone is going to "steal" a minutes worth of their sampled software?  You'd have to be pretty hard up to try and edit and splice 20 seconds or a minute's worth of audio.  
Three-Body Technology if you're reading this, please consider changing the "instructive sound" to at least one minute.
Your potential customers want to check out your software, but it's very difficult and frustrating at intrusive sounds every 20 seconds.  It's just not worth downloading with those kind of limitations!

Or at least make the dropouts/beeps very short, like half a second. That's enough to keep someone from using the instrument in a real project, but not so intrusive as to put them off to the point where they refuse to give it a chance.

The sound is a vocal clip, "Thanks for trying our demo!" with a drum fill at the end, so is roughly 5 seconds long. Since there is a substantial amount of configuration required to fully use this, disabling presets alone would be sufficient for a demo. Half second dropouts/beeps would be more accepted without a time limitation on the demo itself (i.e., a 10-day trial limit on fully functional is probably the best practice out there, since it would span two weekends for people trying it out... then could either disable it or shift to the 25% downtime).

SONAR (Manchester) will not even receive audio from this demo, so I was forced to use another DAW as soon as I started testing it as a plugin.

Leee

bitflipper
I just assumed "instructive sound" was a case of creative doublespeak. It instructs you that they're still waiting for your money.
 
I have uninstalled many a demo because of intrusive and annoying beeps, noise bursts or dropouts. Limiting functionality such as saving presets is reasonable, but how the heck are you supposed to evaluate a product that only works for 20 seconds at a time?

Exactly.  Are they so afraid someone is going to "steal" a minutes worth of their sampled software?  You'd have to be pretty hard up to try and edit and splice 20 seconds or a minute's worth of audio.  
Three-Body Technology if you're reading this, please consider changing the "instructive sound" to at least one minute.
Your potential customers want to check out your software, but it's very difficult and frustrating at intrusive sounds every 20 seconds.  It's just not worth downloading with those kind of limitations!

Hi,
Thanks for the advice! The thing is, within one hour we released the demo, somebody made a 3 minutes song using the demo to let us kone it's not "demo" enough. That's why we have to make it 20 seconds.

mettelus
The sound is a vocal clip, "Thanks for trying our demo!" with a drum fill at the end, so is roughly 5 seconds long. Since there is a substantial amount of configuration required to fully use this, disabling presets alone would be sufficient for a demo. Half second dropouts/beeps would be more accepted without a time limitation on the demo itself (i.e., a 10-day trial limit on fully functional is probably the best practice out there, since it would span two weekends for people trying it out... then could either disable it or shift to the 25% downtime).

SONAR (Manchester) will not even receive audio from this demo, so I was forced to use another DAW as soon as I started testing it as a plugin.

Regarding the no sound problem in 64bit SONAR, the demo verison will mute the sound once it detacted the status of host is non-realtime, so user can’t export audio. But somehow for 64 bit SONAR, the demo will detact it as non-realtime although it is not, that’s why there’s no sound in the DEMO if you are using 64 bit SONAR. This problem will only occur in demo, not commerical version. We are working hard to solve it by updating the demo.
Thank you for pointing out the problem!