Would be great if you setup a support ticket on the smproaudio website and attach the logfile so the developers can look at it ASAP for you.VSTinus wrote:Just checked my log-file after trying to use asio, and V-machine finds 3 different asio-drivers on my system: ASIO DirectX Full Duplex Driver, ASIO Multimedia Driver and the E-MU ASIO. I want to use the last one but instead the V-machine uses ASIO DirectX Full Duplex Driver. It doesn't crashes immediatly, but i get an error-message that my audio input is not activated. Where can i change this for the Full Duplex driver? Or is there a way to use the EMU asio driver instead?
V-Machine
-
- KVRist
- 390 posts since 4 Dec, 2008
The sun is going to shine in the morning, at least above the clouds.
-
- KVRist
- 175 posts since 27 Aug, 2002 from Sweden
How does this work? Please, I have been waiting for almost two months now. I tried to install Sampletank XL 2.5.2 yesterday, keeping all the default-folders. The VFX-app complains about registry-error etc. Sampletank XL 2.5.2 works great in other apps on this PC.VFXAU wrote: * IK Multimedia License tool integration in wizard.
This means all the IK products can be authorised properly!
/Anders
-
- KVRist
- 390 posts since 4 Dec, 2008
Hi, you need the wizard file for it, they are just finishing them so if you cannot make one it is ok, you will have it in a day or so.janka wrote:How does this work? Please, I have been waiting for almost two months now. I tried to install Sampletank XL 2.5.2 yesterday, keeping all the default-folders. The VFX-app complains about registry-error etc. Sampletank XL 2.5.2 works great in other apps on this PC.VFXAU wrote: * IK Multimedia License tool integration in wizard.
This means all the IK products can be authorised properly!
/Anders
The sun is going to shine in the morning, at least above the clouds.
-
- KVRist
- 175 posts since 27 Aug, 2002 from Sweden
-
- KVRer
- 25 posts since 12 Oct, 2007
Did that, unfortunatly i played with the different ASIO drivers a bit too much to sort out the problem, so at the moment i don't get any audio at all(accept the annoying bleep that the Synthcore has some sort of problem :D ) Will fix it tonight and see if the suggestion (asio4all) works.Would be great if you setup a support ticket on the smproaudio website and attach the logfile so the developers can look at it ASAP for you.
-
- KVRist
- 285 posts since 19 Nov, 2004
anybody got ASynth working on the v-machine? a wizard-file would be very cool. without wizard file its nor working 
. i only got the nagscreen .dll.
any help would be very nice
max
. i only got the nagscreen .dll.any help would be very nice
max
-
- KVRian
- 1297 posts since 17 Aug, 2003 from Italy
Hi Danny,VFXAU wrote: For string parameters we don't limit the steps, so if you want more then 16 steps you should assign the parameter as a string parameter in the VST code.
In the VFX API which I think you got, you have the ability of popping up information to the screen. If you don't have the API please send me a private Email.
a couple of things...
1) I sent you an email for the VFX API but it bounced back 3 times...
2) What do you mean for "string parameters"? AFAIK, VST parameters are floating point values ranging from 0 to 1. You can assign them to lists of choices by scaling the float value to a fixed list, and show the results in getParameterDisplay() or graphically on your plugin's GUI. Maybe there's a way to set the parameter type but I'm not aware of it?
And, yes, I know that you can use the VFX app to tweak your sounds and save your presets, but please tell me something I still don't know. Don't tell me that you never had to tweak sounds "on the fly" before starting to play when you already were on the stage... This happens all the times, especially with effects levels (reverbs, delays, etc.)
-
- KVRian
- 1297 posts since 17 Aug, 2003 from Italy
Also, FYI, the V-Machine doesn't support the getDirectory() function.
This is part of the VST SDK and returns the directory where the DLL file is located, very useful to locate external files.
If I compile my plugin with this call, the plugin crashes in the V-Machine (of course, doesn't crash in any other Win or Mac host).
I have to use other boring methods to find the plugin location.
Lastly, is it normal that if I leave the USB stick connected while booting the V-Machine, I always get a "boot timeout" error? The stick is regularly formatted in FAT and doesn't have any boot sector.
This also happens if I leave a USB controller connected. In other words, before starting the V- I have to disconnect all USB devices and reconnected once done. Quite annoying, isn't it?
This is part of the VST SDK and returns the directory where the DLL file is located, very useful to locate external files.
If I compile my plugin with this call, the plugin crashes in the V-Machine (of course, doesn't crash in any other Win or Mac host).
I have to use other boring methods to find the plugin location.
Lastly, is it normal that if I leave the USB stick connected while booting the V-Machine, I always get a "boot timeout" error? The stick is regularly formatted in FAT and doesn't have any boot sector.
This also happens if I leave a USB controller connected. In other words, before starting the V- I have to disconnect all USB devices and reconnected once done. Quite annoying, isn't it?
-
- KVRian
- 1297 posts since 17 Aug, 2003 from Italy
I know I can be a PITA, but there's another bad news.
With the latest firmware the V-Machine is slower than before.
I don't know how to explain but... given a plugin X that isn't changed between old and new firmware, with the old one I could play 64 notes WITHOUT clipping, even if the CPU indicator went all the way up. Now, the same plugin clips with way less than 64 voices. WTF?...???
With the latest firmware the V-Machine is slower than before.
I don't know how to explain but... given a plugin X that isn't changed between old and new firmware, with the old one I could play 64 notes WITHOUT clipping, even if the CPU indicator went all the way up. Now, the same plugin clips with way less than 64 voices. WTF?...???
-
- KVRist
- 390 posts since 4 Dec, 2008
Lots of developer tech questions here, not sure if we should bore the forum with them, but that is not my choice.ZioKiller wrote:Also, FYI, the V-Machine doesn't support the getDirectory() function.
This is part of the VST SDK and returns the directory where the DLL file is located, very useful to locate external files.
If I compile my plugin with this call, the plugin crashes in the V-Machine (of course, doesn't crash in any other Win or Mac host).
I have to use other boring methods to find the plugin location.
Lastly, is it normal that if I leave the USB stick connected while booting the V-Machine, I always get a "boot timeout" error? The stick is regularly formatted in FAT and doesn't have any boot sector.
This also happens if I leave a USB controller connected. In other words, before starting the V- I have to disconnect all USB devices and reconnected once done. Quite annoying, isn't it?
Controller? I have used many ocntrollers and never get an error booting up with a controller in the machine. USB stick, it is how it is right now, as the system gives USB stick or drive a boot priority, you know we had to right a bios to speed up booting and this is one of the results right nowm, it is on the list of things we want to fix but their are many more important fixes before this which help support more plugins.
I will certainly talk to the team about the get directory issue and see if this is correct or not.
As a developer you should be in direct contact with them anyway. I rather deal with customer support as much as I can.
The sun is going to shine in the morning, at least above the clouds.
-
- KVRian
- 1297 posts since 17 Aug, 2003 from Italy
How can I contact them?VFXAU wrote: As a developer you should be in direct contact with them anyway. I rather deal with customer support as much as I can.
-
- KVRist
- 390 posts since 4 Dec, 2008
Which plugin?ZioKiller wrote:I know I can be a PITA, but there's another bad news.
With the latest firmware the V-Machine is slower than before.
I don't know how to explain but... given a plugin X that isn't changed between old and new firmware, with the old one I could play 64 notes WITHOUT clipping, even if the CPU indicator went all the way up. Now, the same plugin clips with way less than 64 voices. WTF?...???
The changes that were made to this firmware should not have changed the engine in anyway. Please if you post something about a plugin let me know the name of it so we can test it ourselves. Less then 64 is what 63 32?
The sun is going to shine in the morning, at least above the clouds.
-
- KVRian
- 1297 posts since 17 Aug, 2003 from Italy
In the first place, Samplelord. I had set it up to play up to 56 notes, which is the highest limit I could reach to avoid CPU clipping. Now it clips with 52 ~ 53 voices.
Then, the plugin I'm working on... I reached a nice result of 64 voices. The critical limit was 66 voices, but 64 was safe. With this new firmware, it clips at 58~59 voices.
I switched back to the old firmware and everything is like before.
The new firmware has definitely reduced the CPU power, making the V-Machine even slower than before.
Also, I don't see any improvement in the S/N ratio. The sound level isn't changed and the background hiss is always there.
Then, the plugin I'm working on... I reached a nice result of 64 voices. The critical limit was 66 voices, but 64 was safe. With this new firmware, it clips at 58~59 voices.
I switched back to the old firmware and everything is like before.
The new firmware has definitely reduced the CPU power, making the V-Machine even slower than before.
Also, I don't see any improvement in the S/N ratio. The sound level isn't changed and the background hiss is always there.
-
- KVRist
- 390 posts since 4 Dec, 2008
Which plugin?ZioKiller wrote:I know I can be a PITA, but there's another bad news.
With the latest firmware the V-Machine is slower than before.
I don't know how to explain but... given a plugin X that isn't changed between old and new firmware, with the old one I could play 64 notes WITHOUT clipping, even if the CPU indicator went all the way up. Now, the same plugin clips with way less than 64 voices. WTF?...???
The changes that were made to this firmware should not have changed the engine in anyway. Please if you post something about a plugin let me know the name of it so we can test it ourselves. Less then 64 is what 63 32?
The sun is going to shine in the morning, at least above the clouds.