-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SmartAmpPro (Pre-Release) not giving any good experience. #12
Comments
@38github Thank you for the feedback, you are not the only one having issues with the pre release binaries. Do you get any sound from the Windows 10 VST in Reaper using the default model? And when you say "load any of the models" do you mean when you change the model selected in the dropdown, or when you use the "Import Tone" button? Or do you even see any model names in the drop down? Keep in mind that the SmartAmp Tonepack models are not compatible with the SmartAmpPro, even though they use the same .json extension. Some more info that may help troubleshoot: what audio interface are you using, and what version of Reaper are you using? When you go to "C:\Users<your_username>\AppData\Roaming\GuitarML\SmartAmpPro\tones", you should see 5 .json files there, which get put there when you first load the VST3. If these files are missing, it may be a permissions problem and the files are not getting copied over. |
[WIndows] The file was just a VST3 and no files with it so I copied it to my vst folder. I downloaded two compatible json files from this project and tried to load by choosing the button that says to load file or something. When the file was choosen and opened nothing happened and the plugin did not become responsive. |
Right, so what's supposed to happen, is when the DAW scans the VST3, it actually copies 5 json files to the directory I mentioned from the VST3 binary data. This is supposed to give the user 5 default tones to use without having to train or import models. I have not done this in a plugin before, but it worked on my machine. Possibly a permissions issue, and since I built it on my machine it accepts it with no problems, but could give issues for other machines. What kind of device/audio interface are you using? Is it an ASIO device in Reaper/preferences/ device settings? Also I'm going to ask the go-to IT question.. have you restarted your computer and rerun Reaper? |
For anyone running on Mac and not getting the SmartAmpPro running, you may need an additional step to allow the plugin to run, by telling the Mac to trust the developer of the plugin. Here are the steps: I also recommend rebooting after copying the AU to the Components directory. As a developer, I can pay apple $100 a year to be a “trusted developer”, which is a future possibility but the project is not quite there yet. |
I tried the Ubuntu vst3 placed in usual VST folder under OpenSUSE Tumbleweed but would not show up in Reaper. I then tried the windows vst3 in Windows 10 which showed up in Reaper but when I load any of the models available here it stops to respond.
The text was updated successfully, but these errors were encountered: