'303' day, TB-303 released on Roland Cloud

[iixorb]

Just downloaded it.....

[Rockky67]

Me too, but can't seem to get it working yet (on Reaper).

My Cloud Manager Update got stuck at 99% updating, but the TB-303 seemed to install OK (and then update a couple of times), however Reaper (latest version on Windows 10) won't load the TB-303 saying it caused an error.

Is it working for you? What OS and DAW are you on?

Update: Cloud Manager eventually updated and the TB-303 seems to install and run fine on Bitwig Studio, but I keep getting an error on Reaper so maybe it's DAW specific issue.

Sounds great so far, especially at the bottom end. Glad I finally noticed the panel in the top right hiding the delay and multiFX controls.

[iixorb]

Initial thoughts (as an owner of a real Roland TB-303, a Boutique TB-03, a Bassbot TT-303, ABL 3 vst and a former owner of the Aira TB-3).

Pretty good. The effects work better here than they do on the Boutique TB-03.

Interesting curve visualisation for slide behaviour makes it easier to understand what's going on.

Great that they included a VCF Trim pot which replicates the TM pot inside real 303's (which can make a 303 sound darker when turned down, or squelchier / more piercing when turned up - the result is more apparent in a real 303 however).

Not sure yet if it sounds more authentic than ABL 3 but does sound good with the built-in effects.

Still not quite as 'wholesome' as an original 303 - but what is, apart from original 303's ?!?!

Overall, a good, respectable and welcome addition to the cloud, and may well be one I opt to keep.

[Windows 7, Ableton 9.7.7]

[hesnotthemessiah]

Me too, but can't seem to get it working yet (on Reaper).

My Cloud Manager Update got stuck at 99% updating, but the TB-303 seemed to install OK (and then update a couple of times), however Reaper (latest version on Windows 10) won't load the TB-303 saying it caused an error.

Is it working for you? What OS and DAW are you on?

Update: Cloud Manager eventually updated and the TB-303 seems to install and run fine on Bitwig Studio, but I keep getting an error on Reaper so maybe it's DAW specific issue.

Sounds great so far, especially at the bottom end. Glad I finally noticed the panel in the top right hiding the delay and multiFX controls.

Looks like I got the same error with Reaper:-

Plug-in 'TB-303(VST3 64bit).vst3' executed invalid operation during scanning

AND

Plug-in 'TB-303(VST2 64bit).dll' executed invalid operation during scanning

Both of the above messages appear with the heading "VST scanning error + note" whilst Reaper scans for new plugins upon launch and finds the newly installed TB-303 plugins for the first time. No Roland TB-303 plugins are then available in Reaper.

TR_808_VST3_64bit_.vst3=004C34390287D401,1961593337,TR-808 (Roland Cloud) (24 out)!!!VSTi
TB_303_VST3_64bit_.vst3=000D1EBD3ED0D401

TR_808_VST2_64bit_.dll=0086DA7C0187D401,1449227065,TR-808 (Roland Cloud) (24 out)!!!VSTi
TB_303_VST2_64bit_.dll=002735733ED0D401

The above is copied directly from the reaper-vstplugins64.ini file and shows that both the VST3 and VST2 versions of the TB-303 have data missing from their entries here.

Using latest versions of Reaper (5.9.71) and Windows 10. Using TB_303 File Version 1.0.1.11940 - downloaded and tested about 10.30 PM Monday (GMT). No problems with other Roland plugins.No problems with other Roland plugins.

[Rockky67]

Saves me pulling my hair out as it seems to be a Reaper/TB303 specific issue (as I said I can run the 303 in Bitwig just fine). I guess we wait to see who comes up with the fix first.

[hesnotthemessiah]

Saves me pulling my hair out as it seems to be a Reaper/TB303 specific issue (as I said I can run the 303 in Bitwig just fine). I guess we wait to see who comes up with the fix first.

There seems to be a few people at KVR with similar problems aswell and not all on Reaper:

https://www.kvraudio.com/forum/viewtopi ... start=1710

I contacted Roland Support with my problem. Not enough space in their contact form to give links to other forums though. Might be worth contacting them, it might encourage them to take it a bit more seriously...I need my Roland Cloud TB-303, the low quality Youtube demo sounded damn good and the MIDI export looks great!!

[mathurgood]

Hi

I've installed Roland Cloud Manager and TB-303 v1.0.1 using my extended trial. When launching Reaper v5.971 it takes around 40 seconds to scan the VST files (this is slow; it generally takes 2-10 seconds) and then the following error messages are displayed:

"Plug-in TB-303(VST3 64bit).vst3 executed invalid operation during scanning."
"Plug-in TB-303(VST2 64bit).dll executed invalid operation during scanning."

When Reaper opens, TB-303 is unavailable (VST2 or VST3). Relaunching Reaper does not solve the problem. I'm using Windows 10 Pro X64. All of my other plugins are working normally. I would be very grateful if you could investigate. It seems that other users are experiencing this issue - please see:

https://www.kvraudio.com/forum/viewtopi ... start=1710

Hope that this info is of use.

Many thanks

Matt Thurgood

[thartnett]

In the Fx Browser in Reaper:
Select the Options menu
Select Fx Preferences
Select the VST node
On that pane, there is a checkbox that says “Do not scan VST names/types (deprecated). Check this
Click the “Clear Cache/re-scan” button.
The TB-303 will be successfully scanned and available

[hesnotthemessiah]

In the Fx Browser in Reaper:
Select the Options menu
Select Fx Preferences
Select the VST node
On that pane, there is a checkbox that says “Do not scan VST names/types (deprecated). Check this
Click the “Clear Cache/re-scan” button.
The TB-303 will be successfully scanned and available

That worked for me. Thanks thartnett.

[iixorb]

There was another update last night; not sure what they changed but maybe Roland are sorting the issues people with Reaper are having.

Seems to be fine with Ableton 9.7.7.

[Manic]

Curious if anyone has compared (soundwise) the TB-03 with the VST already?

With the TB-03 being a perfect midi controller for it, it should be really easy to compare them, because the controls keep synced after tweaking a bit :)

[mathurgood]

In the Fx Browser in Reaper:
Select the Options menu
Select Fx Preferences
Select the VST node
On that pane, there is a checkbox that says “Do not scan VST names/types (deprecated). Check this
Click the “Clear Cache/re-scan” button.
The TB-303 will be successfully scanned and available

I received an email from RolandCloud Support suggesting the above method. While this works (i.e. the TB-303 is scanned and made available), it modifies reaper-vstplugins64.ini so that the numerical block (after the hex block) for ALL non-native VST plugins is changed to a single zero. Here's an example:

Reaktor_6_FX.dll=003AFE07BA07D401,0,Reaktor 6/Reaktor 6 FX
Reaktor_6.dll=00E09B05BA07D401,0,Reaktor 6/Reaktor 6
RandARP.dll=0FCB7D46C975D401,0,RandARP/RandARP
Podolski_x64_.dll=00D48B73E87AD101,0,Podolski/Podolski(x64)
Phasis.dll=A9895F4CCF96D301,0,Phasis/Phasis
PG_8X.dll=9E1711ED0066D301,0,PG-8X/PG-8X ...etc.

You get the idea. As a result, VST instruments no longer appear when using the "VSTi" or "Instrument" filters in the FX Browser. They do still appear using the "VST" or "All Plugins" filters, however. Not a major problem, but being forced to run a deprecated scan for the sake of one plugin is annoying. I've replied to Roland's email to ask whether or not there will be a fix for this at some point.

[Rockky67]

Cheers guys for the workaround and the side-effect doing that has on the plugins listing.

I've posted it up on the Cockos (Reaper) forum in case others are affected.

[Rockky67]

One further little fly in the ointment I've found with the very latest Reaper build (v5.972) is that if your current project contains a track with a TB-303 VST then you can't delete the track with that VST in, can't close the project and can't open another project without crashing out to desktop. Workaround is to use 'Replace FX' on the VST and swap it out for anything else, save and then you should be free to open another project without issues.

Fun thing #2 - just also found that none of my Waves plugins work through this deprecated method, so that sucks.