Slate Virtual Console Plugin is now available
-
penguinfromdeep penguinfromdeep https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=193898
- KVRAF
- 1993 posts since 18 Nov, 2008
Yes, 1.1.2 out now and all the bugs (mainly the gui issue) I had with previous version are gone!
circuit modeling and 0-dfb filters are cool
-
- KVRAF
- 14739 posts since 19 Oct, 2003 from Berlin, Germany
Sorry, not convinced.
Just ran v1.1.2 on my i7 rig, and:
- random "slowdowns" as if the plugin or something else is constantly reloading a license, settings or something (only happening with Slate VCC so far, haven't tested other iLok related VST plugins)
- VU is still off (by actually 8 to 10dB - tested with a sine at 1kHz, and several sweeps)
- CPU usage skyrocketed to 14% with only 5 instances of a channel and one master buss plugin - and yes, Oversampling was off.
To be honest, the beta was more usable and better CPU optimized than v1.1.2 - but I can't use the beta in Cubase 6.
Off to filing a bug report.
EDIT:
Did an ongoing test with Beta 2.5 (up to Cubase 5 only) to v1.1.2 - the higher the version, the more CPU usage. Also, the random "accesses"/slowdowns started with the full version.
Bug report filed, looking forward to a fix. At the moment - no fun in using VCC, so I can relate with the complaints.
Just ran v1.1.2 on my i7 rig, and:
- random "slowdowns" as if the plugin or something else is constantly reloading a license, settings or something (only happening with Slate VCC so far, haven't tested other iLok related VST plugins)
- VU is still off (by actually 8 to 10dB - tested with a sine at 1kHz, and several sweeps)
- CPU usage skyrocketed to 14% with only 5 instances of a channel and one master buss plugin - and yes, Oversampling was off.
To be honest, the beta was more usable and better CPU optimized than v1.1.2 - but I can't use the beta in Cubase 6.
Off to filing a bug report.
EDIT:
Did an ongoing test with Beta 2.5 (up to Cubase 5 only) to v1.1.2 - the higher the version, the more CPU usage. Also, the random "accesses"/slowdowns started with the full version.
Bug report filed, looking forward to a fix. At the moment - no fun in using VCC, so I can relate with the complaints.
-
- KVRist
- Topic Starter
- 228 posts since 12 Nov, 2005
The current 1.1.2 and 1.2beta are doing really well on Macs.. Windows is a lot harder because there are so many configurations, but we are working very hard on it and I expect to solve the issues soon.
The 1.2 that is in beta right now WILL reduce the CPU down to what you see in the older 2.5 beta, so that's good news!
The 1.2 that is in beta right now WILL reduce the CPU down to what you see in the older 2.5 beta, so that's good news!
-
- KVRAF
- 14739 posts since 19 Oct, 2003 from Berlin, Germany
My account only has access to the "official" releases, not the beta releases anymore?
Are the "beta" releases for Mac only?
Also, can you reproduce the random "slowdown" bug?
I did open a ticket at the support area, don't know if any of you found some time already to take a look.
Oh and Steven, there's still an answer left in terms of my last email to both you and Fabrice.
Are the "beta" releases for Mac only?
Also, can you reproduce the random "slowdown" bug?
I did open a ticket at the support area, don't know if any of you found some time already to take a look.
Oh and Steven, there's still an answer left in terms of my last email to both you and Fabrice.
-
- KVRian
- 676 posts since 22 Sep, 2007 from Caracas, Venezuela
@Compyfox
Take your "Global Calibration Level" a.k.a headroom down to -23.5dB (maybe -22.0dB if you plan to use the Brit N Discrete a lot, since this console seems to have less headroom). This should work pretty good for signals around -18dBFS.
Meters are weird indeed but probably Slate Team will work on them once they squash most bugs. In the meantime I'm quite happy with this setup I suggested above.
Take your "Global Calibration Level" a.k.a headroom down to -23.5dB (maybe -22.0dB if you plan to use the Brit N Discrete a lot, since this console seems to have less headroom). This should work pretty good for signals around -18dBFS.
Meters are weird indeed but probably Slate Team will work on them once they squash most bugs. In the meantime I'm quite happy with this setup I suggested above.
-
- KVRAF
- 14739 posts since 19 Oct, 2003 from Berlin, Germany
Headroom good and fine, but the 0VU point also shifts when the signal starts to get distorted (aka saturated, aka "getting harmonics". So if my initial signal is at -18dB RMS, and VCC is off, even a shift doesn't help.
I constantly need to adjust the trim/gain to get a steady signal before editing further. This is IMO a PITA. On top of having CPU spikes and slowdowns.
Then again, just my 2c. Maybe I'm just too much of a perfectionist (or in other words "picky") in terms of tool-usage.
But for the time being, I need to ditch VCC again - too unstable, too unprecise. Maybe VCC should have really been longer in Beta Phase?
I constantly need to adjust the trim/gain to get a steady signal before editing further. This is IMO a PITA. On top of having CPU spikes and slowdowns.
Then again, just my 2c. Maybe I'm just too much of a perfectionist (or in other words "picky") in terms of tool-usage.
But for the time being, I need to ditch VCC again - too unstable, too unprecise. Maybe VCC should have really been longer in Beta Phase?
-
- KVRian
- 676 posts since 22 Sep, 2007 from Caracas, Venezuela
Sorry to hear that. Latest official version 1.1.2 and beta version 1.2.0 work great here on Windows 7 64-bits + REAPER 64-bits (yeah, I'm using the bridge with it and zero problems). Did you try to submit a ticket asking for 1.2.0? Maybe that version will sort your problems out, who knows. You can also try a different USB port or just unplug it and plug it back again, I've read people have solved problems doing this.
By the way, you'll see the same thing in SatSon (0VU is not really your 'breaking point' and it starts to saturate, clip, etc., way beyond that point). I wouldn't care too much about those VU meters in VCC since they're meaningless once you've changed the headroom because they don't shift relatively. You know what's a good indicator? That led in meters, that's a good way to know when things are getting slammed (as far as I can hear they react pretty good to the console(s) "ceiling", so to speak)
By the way, you'll see the same thing in SatSon (0VU is not really your 'breaking point' and it starts to saturate, clip, etc., way beyond that point). I wouldn't care too much about those VU meters in VCC since they're meaningless once you've changed the headroom because they don't shift relatively. You know what's a good indicator? That led in meters, that's a good way to know when things are getting slammed (as far as I can hear they react pretty good to the console(s) "ceiling", so to speak)
-
- KVRAF
- 14739 posts since 19 Oct, 2003 from Berlin, Germany
Well I did switch USB ports for the iLok the first time I tried it, and I had the same issues. iLok2 is at an independent USB2 port (no hub, no extention cable), rig rebooted several times. Crazy stuff.
Filed a support ticket at slatedigital.com/support, but haven't checked that one yet. Didn't ask for a v1.2 beta since I didn't know there was one existing (shouldn't it be at your user account anyway?).
Regarding the VU.
I know its not the "breaking point" at 0VU - but sure is crazy to have a 10dB offset. And frankly, I didn't hear any real different if I shifted the "headroom" (reference point). So I consider this a major bug/issue hat needs to be fixed. Clip LED wise, VCC is "fast" indeed - so if it goes on, "distortion" taking place (but no digital clipping, more of the analog based if I understood that right - damn the manual sure is shallow in terms of information).
[EDIT]
Actually no, to my experience, everything hovering around VU or above should "saturate", if the LED goes on, game over for the signal.
[/EDIT]
Still I want to have a fix first before I can really work with it. Beta 2.5 was more hassle free indeed. And CPU friendly to no end. I don't know what monster-rigs the Slate crews have, but saying "Mac performs better, PC has like 5000 different configurations" is a crazy excuse since you can mod your Macintosh as much as you can a PC.
Regarding SatSons... as long as it's not available, I can't test it. And since I'm no Beta Tester, I can't comment on it either.
[EDIT]
Just checked my ticket - no response yet. And I just saw Slate's own board... should I rather post there since it also has a bug report section? Which way do you prefer, Steven?
[/EDIT]
Filed a support ticket at slatedigital.com/support, but haven't checked that one yet. Didn't ask for a v1.2 beta since I didn't know there was one existing (shouldn't it be at your user account anyway?).
Regarding the VU.
I know its not the "breaking point" at 0VU - but sure is crazy to have a 10dB offset. And frankly, I didn't hear any real different if I shifted the "headroom" (reference point). So I consider this a major bug/issue hat needs to be fixed. Clip LED wise, VCC is "fast" indeed - so if it goes on, "distortion" taking place (but no digital clipping, more of the analog based if I understood that right - damn the manual sure is shallow in terms of information).
[EDIT]
Actually no, to my experience, everything hovering around VU or above should "saturate", if the LED goes on, game over for the signal.
[/EDIT]
Still I want to have a fix first before I can really work with it. Beta 2.5 was more hassle free indeed. And CPU friendly to no end. I don't know what monster-rigs the Slate crews have, but saying "Mac performs better, PC has like 5000 different configurations" is a crazy excuse since you can mod your Macintosh as much as you can a PC.
Regarding SatSons... as long as it's not available, I can't test it. And since I'm no Beta Tester, I can't comment on it either.
[EDIT]
Just checked my ticket - no response yet. And I just saw Slate's own board... should I rather post there since it also has a bug report section? Which way do you prefer, Steven?
[/EDIT]
-
- KVRist
- 216 posts since 11 Apr, 2005 from Hamburg, Germany
Hi Compy.Compyfox wrote:Filed a support ticket at slatedigital.com/support, but haven't checked that one yet. Didn't ask for a v1.2 beta since I didn't know there was one existing (shouldn't it be at your user account anyway?).
Still I want to have a fix first before I can really work with it. Beta 2.5 was more hassle free indeed. And CPU friendly to no end. I don't know what monster-rigs the Slate crews have, but saying "Mac performs better, PC has like 5000 different configurations" is a crazy excuse since you can mod your Macintosh as much as you can a PC.
The current betas are only for 'selected' users.
I have no more freezing' issues with 1.1.2 on Win7 64bit / Cubase 6.0.1 32bit / i7 @ 4x 3,8gHz.
CPU usage is the same as with beta 2.5.( not using any grouping, here )
I still can use beta 2.5 in Cubase 6.0.1.
Did you double check if Your really using 1.1.2 ? ( sometimes some dlls keep lying around
) Did You install the latest Pace driver ? ( also available on Your VCC user account ).
And yes, you can mod a Mac ... but in real life, that's pretty rare ...
PCs still have a wider variety of Hard- and Software
bye, Jan
Last edited by _dada_ on Thu Apr 21, 2011 7:20 pm, edited 1 time in total.
-
- KVRian
- 676 posts since 22 Sep, 2007 from Caracas, Venezuela
@Compyfox
What sample rate are you working with? A couple of weeks ago I submitted a ticket at Slate's support reporting a bug where meters and global calibration levels are sample rate dependent and they don't work properly at 44.1kHz. Even meters ballistics change at 44.1kHz. I work at 96kHz and as far as I can see/hear things work properly with that SR (meters are still a bit off but a calibration level of -23.5dB/-22.0dB solves pretty much my issues here, like I said).
What sample rate are you working with? A couple of weeks ago I submitted a ticket at Slate's support reporting a bug where meters and global calibration levels are sample rate dependent and they don't work properly at 44.1kHz. Even meters ballistics change at 44.1kHz. I work at 96kHz and as far as I can see/hear things work properly with that SR (meters are still a bit off but a calibration level of -23.5dB/-22.0dB solves pretty much my issues here, like I said).
-
- KVRAF
- 14739 posts since 19 Oct, 2003 from Berlin, Germany
Don't tell me it's the "closed beta crew" yet again from the switch to iLok2?_dada_ wrote: The current betas are only for 'selected' users.
Why? Other firms do the same in terms of offering Betas for current versions. It's not like there are new features or a complete new-to-be-released VST.
Strange... slowdowns while using VCC (tested all available versions) starting with v1.06 to v1.1.2. Not happening with Beta 2.5 (before iLok2). I jumped directly from Beta 2.5 to v1.1.2 the other day._dada_ wrote: CPU usage is the same as with beta 2.5.( not using any grouping, here )
I still can use beta 2.5 in Cubase 6.0.1.
And I still use Cubase 6.0.0 (stable for me) - could this be the case why Beta 2.5 doesn't show up and only in Cubase 5.5.2? Then again, I rescanned several times.
Yes, always checked my versions while testing through clicking on the Slate logo with the open plugin._dada_ wrote: Did you double check if Your really using 1.1.2 ? ( sometimes some dlls keep lying around
Using the one from 30.03.2011 from Pace directly. Is the Slate one newer? If so, how - they're not affiliated with Pace?_dada_ wrote: Did You install the latest Pace driver ? ( also available on Your VCC user account ).
I meant "modding a Mac" in terms of using different hardware (recording cards, DSP, etc) and software (tons of different hosts, not the usual suspects)._dada_ wrote: And yes, you can mod a Mac ... but in real life, that's pretty rare ...
PCs still have a wider variety of Hard- and Software
48kHz, 24bit. Best latency balance for my recording device.Mercado_Negro wrote: What sample rate are you working with?
So... if the meter balistics and the VU changes with each samplerate change... Fabrice really needs to get that thing fixed. To me it's not just a visual gimmick, it's an important indicator. Which is the reason why I use PSP VU in front of VCC CHANNEL/MIX to check if I'm at the right levels before working further. But... this doesn't help of the plugins are internally off as well?
BTW:
Ticked answered for the time being, BRs and FRs forwarded. I'll check the iLok "replug" thing again, and Anthony from the support section told me to maybe delete the VCC Settings in the Documents and Settings directory. Though I don't keep my hopes up.
Even requested access too v1.2. Sure hope Steven doesn't stick to "keep betas private". It works pretty well with Rayzoon Jamstix and Cockos ReaPlugs. Strangely, sometimes the "Betas" perform better than the "finals" - as is the case with VCC as well.
- Fox
-
- KVRist
- Topic Starter
- 228 posts since 12 Nov, 2005
Hi there.. the betas aren't necessarily "private".. its just that Anthony chooses certain users who reported problems via a ticket to test out fixes to these problems so that we can make sure that the issues are fixed. So if you are one of the first people to report an issue, chances are he'll have you test out beta versions before we release it publicly.
Hope that makes sense.
Hope that makes sense.
Last edited by Slate on Fri Apr 22, 2011 10:31 pm, edited 1 time in total.
-
- KVRAF
- 14739 posts since 19 Oct, 2003 from Berlin, Germany
Makes sense (I guess it's to tone down the complaints if the Beta doesn't work). Will test it later today (everything: rescan the Cubase 6 VST2 folder for Beta 2.5, replug the iLok2, kill the settings file, try the "internal" version).
If I still run into slowdowns... I think there's more to it.
If I still run into slowdowns... I think there's more to it.
-
- KVRist
- 216 posts since 11 Apr, 2005 from Hamburg, Germany
regarding : not seeing 2.5 :
yep, Cubase can sometimes be a bit 'choosy', which plugins to show.
Often a rescan does not help.
Try to move the 2.5 dlls to a different place ( e.g.: a new sub folder ).
Also double check, to not have hidden VCC dlls, still lying around.
( to do so, just remove the dlls and start a project,
if VCC is still loaded, You'll have to do a search )
regarding Pace drivers :
The drivers on Your user account are the same as the 30.03.11 from iLok.com.
... and yes, I predicted a vast number of issues, when Steven decided to switch to iLok2.
Especially as the new Pace Eden uses virtualization ...
Pace is known to dig deep into the OS and system ... 'screaming' for issues ...
I really hope it has helped Steven, in terms of sales ...
It surely did not help, making a flawless release.
bye, Jan
yep, Cubase can sometimes be a bit 'choosy', which plugins to show.
Often a rescan does not help.
Try to move the 2.5 dlls to a different place ( e.g.: a new sub folder ).
Also double check, to not have hidden VCC dlls, still lying around.
( to do so, just remove the dlls and start a project,
if VCC is still loaded, You'll have to do a search )
regarding Pace drivers :
The drivers on Your user account are the same as the 30.03.11 from iLok.com.
... and yes, I predicted a vast number of issues, when Steven decided to switch to iLok2.
Especially as the new Pace Eden uses virtualization ...
Pace is known to dig deep into the OS and system ... 'screaming' for issues ...
I really hope it has helped Steven, in terms of sales ...
It surely did not help, making a flawless release.
bye, Jan
-
- KVRAF
- 14739 posts since 19 Oct, 2003 from Berlin, Germany
I'll try the research again. So far I didn't have any "hidden" plugins, and VCC was always in a dedicated folder. Yet Cubase 6 ditched it (not sure on WL7, but I remember something along those lines, elder WL versions found it).
I'm more surprised regarding the iLok2 being more CPU intensive. This new "system" should be better/faster/smaller, no? Aparently, not (though I don't know what the drivers do, and why). But if one wants to use certain tools, you have to cave.
At least all other iLok tools I use don't have such issues - yet.
EDIT:
Just tried the most recent "internal" (1.2.2). The CPU usage has indeed drastically dropped (48 VCC channel instances plus 1 Mix Buss resulted in 15-18% along with 48 instances of Steinberg's TestTone as signal generator). Also the random "slowdown" bug has mostly vanished. But there were newly introduced ones.
One being the already known (and earlier fixed) "open plugin/GUI results in audio dropout" bug. The VU is still off as well. Didn't test much else (no beta, though I did delete the settings file). Else it's working... well... somewhat stable (even with wild BCF2000 fader rides).
Let see when all issues will be fixed.
I'm more surprised regarding the iLok2 being more CPU intensive. This new "system" should be better/faster/smaller, no? Aparently, not (though I don't know what the drivers do, and why). But if one wants to use certain tools, you have to cave.
At least all other iLok tools I use don't have such issues - yet.
EDIT:
Just tried the most recent "internal" (1.2.2). The CPU usage has indeed drastically dropped (48 VCC channel instances plus 1 Mix Buss resulted in 15-18% along with 48 instances of Steinberg's TestTone as signal generator). Also the random "slowdown" bug has mostly vanished. But there were newly introduced ones.
One being the already known (and earlier fixed) "open plugin/GUI results in audio dropout" bug. The VU is still off as well. Didn't test much else (no beta, though I did delete the settings file). Else it's working... well... somewhat stable (even with wild BCF2000 fader rides).
Let see when all issues will be fixed.