V-Machine

[EvilDragon]

why then use Pianoteq live ? There are close alternatives(unless you are a super classical player who can't live without the perfect piano) which play samples and should be good enough for live playing, let's face it, any vmachine type product at this price point will not comete with a 3 ghz desktop, but that is not what its for, this tiny beast is for live playing and in that situation, IMHO you dont need the power of Pianoteq.

I disagree. I'm not a super classical piano player, but I've been with pianos whole my life, and none of sampled versions of it really cut it for me. Pianoteq changed my life when it showed up, and I want it live. I need it live. Nothing comes near to it, not even Truepianos. Besides, I think that the possibilities pianoteq offers are great and can really be brought up to a larger audience live.

That's why I wish so hard for it to be able to run smoothly on the V-Machine. If that ever happens, I CAN GUARANTEE YOU that there will be a whole lot of buyers interested in this thing. Just drop a topic on Pianoteq forum (or any other forum, for that matter) with a youtube vid that shows how perfectly Pianoteq runs on V-Machine, BAM, in an instant there will be hundreds interested.

If I'm wrong, I'll cut my nutsack


As far as other synths are concerned - I would like to see Arturia CS-80 operating at full poly (10) and current CPU ain't cutting it. Also, I never got the info on how it performs with Minimonsta playing a 4- or 8-voice unison patch with all 3 osc, feedback, and delay and stuff...

[mäxchen]

thanks for the wizard for true pianos. will try that out in the afternoon when i am at home...

max

[omnipoly]

Have you seen the new Roland V-piano? Interesting!

(oops wrong thread. Sorry.)

[JazzSinger]

Recommended CPU for Pianoteq 2 is Intel P4 3 GHz, it ensures smooth operation.

Holy cow! What the heck is it doing to need so much power?

It's not only 4x the performance. It's really different (regarding Pianoteq), if you activate dual-processing. If it's off, the CPU load gets higher 10-35%, which is a lot.

The Pianotec guys specifically designed it around current dual-core architectures? Well, OK. And therein lies a dilemma for SM Pro. Is it worth it to build a V-Machine that specifically supports dual-core optimized VSTs? What about when quad-core becomes the de facto standard?

I doubt it's the firmware issue. Pianoteq simply requires a large amount of differential equations solved in realtime :D

From what you say about Pianoteq, yes. I would agree with you. And my gut feel as a firmware developer myself is the V-Machine and Pianoteq 2 ain't made for each other.

[EvilDragon]

Pianoteq can work on a single core (thus the single core 3 GHz requirement for optimal and smooth performance). Modartt designed Pianoteq to be compatible with both single and multicore systems, except of course it will run better on a multicore system. Thus, if V-Machine got dualcore CPU, I doubt other VSTs will be sitting duck not knowing how to use the second core. If nothing else, one core could go for one VST, and other to another VST, but that's up to VFX software how will it manage available resources.

[mon8169]

The options menu, this was removed before the software was released to the public. The manual was created before the software had been finalised and hence may be slightly different to the released software.

Then, how can I choose the midi/audio ports?

Ramon

[ZioKiller]

You can't, until this will be implemented in a future release.

[MatthewSkinner]

The VFX software will currently use whatever is setup in the sounds and audio devices control panel as the default device. If you change it there then it will also change in the vfx software next time it is started.

[JazzSinger]

Pianoteq can work on a single core (thus the single core 3 GHz requirement for optimal and smooth performance). Modartt designed Pianoteq to be compatible with both single and multicore systems, except of course it will run better on a multicore system.

There is no magic happening in multi core processors. A 2 core 2GHz CPU = a 4GHz single core (less overheads). The move to multi core CPUs was driven by the fact that beyond 3GHz, they were no longer able to get the heat out of the chip quickly enough. Dual cores spread the heat over a wider area.

The downside is that to utilize those two 2GHz cores, you need an application that can be split into independent threads and is specifically (re)written to do so. If not, it will perform pretty much like on a single 2GHz processor.

Thus, if V-Machine got dualcore CPU, I doubt other VSTs will be sitting duck not knowing how to use the second core. If nothing else, one core could go for one VST, and other to another VST, but that's up to VFX software how will it manage available resources.

Yes of course, most normal single-core software works on dual core PCs. Some applications did have problems and needed to be patched. This didn't mean they now were true multicore applications.

My point was that if SM Pro WERE to develop a dual core V-Machine and it came out in a year say, then as soon as quad core PCs become standard (later this year already?), quad core optimized VSTs are sure to come out and will probably perform poorly on V-Machine's dual core CPU. It's neverending. The market for V-Machines is tiny compared to that for laptops, they need to recover development costs somehow.

If Pianoteq really needs 3GHz in a single core to work smoothly, then clearly it's not a VST appropriate for V-Machine's 1GHz CPU. Plain and simple. And here I agree with what you said: firmware optimizing isn't going to fix this.

[EvilDragon]

But a CPU upgrade would fix it

A bit off-topic, but V-Machine is getting some serious and mean competition.

MuseBOX.

Below 1k$ and I think a way faster CPU will be in this one. Bit more expensive than V-Machine, but I think it will run Pianoteq like a charm (knowing that old Receptor did that really well).

Let the games begin!

[ptsound]

can someone test this on their vmachine please and let me know if it works for them?

To get TruePianosTrial to work you need to do 2 things.

1.Launch the plugin in standalone first, and press 'options' in the bottom of the plugins window. Disable the 'sympathatic resonances' box and press 'save current plugin state as default' this creates the default.fxp file the wizard refers to and will mean the polyphony of the plugin is higher. If you dont do this first the wizard will create an unknown error as the file is not yet created by the plugin.
2. You need to replace the word 'Demo' in the files_to_copy section to be the name you login to windows with. If you click on your starbar it will be the name at the top. Demo is my user name so this needs to be edited to your user name. You will get errors if you dont edit this correctly.

dll_name: TruePianosTrial/TruePianos.dll
id: 877024336
name: TruePianosTrial
is_synth: 1
parameter_count: 10
program_count: 1
has_editor: 1
editor_width: 794
editor_height: 360
name_abbreviation: TPNO
dirs_to_copy:
...
/Program Files/TruePianos/Content
...
files_to_copy:
...
/Documents and Settings/Demo/TruePianos Settings/default.fxp
...
registry_keys:
...
REGEDIT4

[HKEY_CURRENT_USER\Software\4Front\TruePianos]
"BankDirTrial"="p:\\TruePianosTrial\\Content"
"TrialUninstall"="p:\\TruePianosTrial\\unins000.exe"

[HKEY_CURRENT_USER\Software\4Front\TruePianos\appDefaults]
"optionsShown"=dword:00000001
"multicore"="false"
...
symlinks:
...
windows/profiles/0/TruePianos Settings/default.fxp:TruePianosTrial/default.fxp
...

Hi,
Spent hours yesterday trying to make truepianos demo work.
I've tried again today going through your 2 step directions(listed above)
I keep getting an error message:
ERROR FUT481
Anyone get this working yet?

[Nitrofunk]

can someone test this on their vmachine please and let me know if it works for them?

To get TruePianosTrial to work you need to do 2 things.

1.Launch the plugin in standalone first, and press 'options' in the bottom of the plugins window. Disable the 'sympathatic resonances' box and press 'save current plugin state as default' this creates the default.fxp file the wizard refers to and will mean the polyphony of the plugin is higher. If you dont do this first the wizard will create an unknown error as the file is not yet created by the plugin.
2. You need to replace the word 'Demo' in the files_to_copy section to be the name you login to windows with. If you click on your starbar it will be the name at the top. Demo is my user name so this needs to be edited to your user name. You will get errors if you dont edit this correctly.

dll_name: TruePianosTrial/TruePianos.dll
id: 877024336
name: TruePianosTrial
is_synth: 1
parameter_count: 10
program_count: 1
has_editor: 1
editor_width: 794
editor_height: 360
name_abbreviation: TPNO
dirs_to_copy:
...
/Program Files/TruePianos/Content
...
files_to_copy:
...
/Documents and Settings/Demo/TruePianos Settings/default.fxp
...
registry_keys:
...
REGEDIT4

[HKEY_CURRENT_USER\Software\4Front\TruePianos]
"BankDirTrial"="p:\\TruePianosTrial\\Content"
"TrialUninstall"="p:\\TruePianosTrial\\unins000.exe"

[HKEY_CURRENT_USER\Software\4Front\TruePianos\appDefaults]
"optionsShown"=dword:00000001
"multicore"="false"
...
symlinks:
...
windows/profiles/0/TruePianos Settings/default.fxp:TruePianosTrial/default.fxp
...

Thanks for that!
But how does it perform on the V-Machine? Is it playable?
Peter

[Nitrofunk]

can someone test this on their vmachine please and let me know if it works for them?

To get TruePianosTrial to work you need to do 2 things.

1.Launch the plugin in standalone first, and press 'options' in the bottom of the plugins window. Disable the 'sympathatic resonances' box and press 'save current plugin state as default' this creates the default.fxp file the wizard refers to and will mean the polyphony of the plugin is higher. If you dont do this first the wizard will create an unknown error as the file is not yet created by the plugin.
2. You need to replace the word 'Demo' in the files_to_copy section to be the name you login to windows with. If you click on your starbar it will be the name at the top. Demo is my user name so this needs to be edited to your user name. You will get errors if you dont edit this correctly.

dll_name: TruePianosTrial/TruePianos.dll
id: 877024336
name: TruePianosTrial
is_synth: 1
parameter_count: 10
program_count: 1
has_editor: 1
editor_width: 794
editor_height: 360
name_abbreviation: TPNO
dirs_to_copy:
...
/Program Files/TruePianos/Content
...
files_to_copy:
...
/Documents and Settings/Demo/TruePianos Settings/default.fxp
...
registry_keys:
...
REGEDIT4

[HKEY_CURRENT_USER\Software\4Front\TruePianos]
"BankDirTrial"="p:\\TruePianosTrial\\Content"
"TrialUninstall"="p:\\TruePianosTrial\\unins000.exe"

[HKEY_CURRENT_USER\Software\4Front\TruePianos\appDefaults]
"optionsShown"=dword:00000001
"multicore"="false"
...
symlinks:
...
windows/profiles/0/TruePianos Settings/default.fxp:TruePianosTrial/default.fxp
...

Hi,
Spent hours yesterday trying to make truepianos demo work.
I've tried again today going through your 2 step directions(listed above)
I keep getting an error message:
ERROR FUT481
Anyone get this working yet?

I think one Problem may be that the Wizard-Files are written for english PC-Systems/Windows-Versions. The Names of the Paths are different in the non-english versions (for example, the Folder "Program Files" is "Programme" in german). So I'm afraid that these Wizard-Files are not just "Plug and Play": They need to be re-written by the User for his or her specific System...

Peter

[ptsound]

can someone test this on their vmachine please and let me know if it works for them?

To get TruePianosTrial to work you need to do 2 things.

1.Launch the plugin in standalone first, and press 'options' in the bottom of the plugins window. Disable the 'sympathatic resonances' box and press 'save current plugin state as default' this creates the default.fxp file the wizard refers to and will mean the polyphony of the plugin is higher. If you dont do this first the wizard will create an unknown error as the file is not yet created by the plugin.
2. You need to replace the word 'Demo' in the files_to_copy section to be the name you login to windows with. If you click on your starbar it will be the name at the top. Demo is my user name so this needs to be edited to your user name. You will get errors if you dont edit this correctly.

dll_name: TruePianosTrial/TruePianos.dll
id: 877024336
name: TruePianosTrial
is_synth: 1
parameter_count: 10
program_count: 1
has_editor: 1
editor_width: 794
editor_height: 360
name_abbreviation: TPNO
dirs_to_copy:
...
/Program Files/TruePianos/Content
...
files_to_copy:
...
/Documents and Settings/Demo/TruePianos Settings/default.fxp
...
registry_keys:
...
REGEDIT4

[HKEY_CURRENT_USER\Software\4Front\TruePianos]
"BankDirTrial"="p:\\TruePianosTrial\\Content"
"TrialUninstall"="p:\\TruePianosTrial\\unins000.exe"

[HKEY_CURRENT_USER\Software\4Front\TruePianos\appDefaults]
"optionsShown"=dword:00000001
"multicore"="false"
...
symlinks:
...
windows/profiles/0/TruePianos Settings/default.fxp:TruePianosTrial/default.fxp
...

Hi,
Spent hours yesterday trying to make truepianos demo work.
I've tried again today going through your 2 step directions(listed above)
I keep getting an error message:
ERROR FUT481
Anyone get this working yet?

I think one Problem may be that the Wizard-Files are written for english PC-Systems/Windows-Versions. The Names of the Paths are different in the non-english versions (for example, the Folder "Program Files" is "Programme" in german). So I'm afraid that these Wizard-Files are not just "Plug and Play": They need to be re-written by the User for his or her specific System...

Peter

I'm in England with an english PC.
I hope a few people will try to get this truepianos wizard working as there have been so many requests and demands(myself included) for a good piano sound.

[Nitrofunk]

[/quote]I'm in England with an english PC.
I hope a few people will try to get this truepianos wizard working as there have been so many requests and demands(myself included) for a good piano sound.[/quote]

AMEN!!!!!!!