Samplitude ProX3 and Arturia V Collection V5. Silence after re-opening project.
- KVRian
- 1028 posts since 11 Jun, 2004 from London
I don't really expect anyone to reply to this as Samplitude seems to be the least popular DAW on this forum.
But anyway just in case here goes:
If I create a new project in Samplitude and insert some of the Arturia V5 VSTi's the records midi. When I save the project and reopening it all the Arturia VSTi's are silent. The only way to get the sound back is to open the GUI and switch to the next preset. The sound then returns. The This ionly VSTi not causing this problem is Spark. It's also happening in V4 collection.
If anyone does happen to have this combo of Samplitude and Arturia could you please test it. Also happens in Pro X2.
Thanks
Kraznet
But anyway just in case here goes:
If I create a new project in Samplitude and insert some of the Arturia V5 VSTi's the records midi. When I save the project and reopening it all the Arturia VSTi's are silent. The only way to get the sound back is to open the GUI and switch to the next preset. The sound then returns. The This ionly VSTi not causing this problem is Spark. It's also happening in V4 collection.
If anyone does happen to have this combo of Samplitude and Arturia could you please test it. Also happens in Pro X2.
Thanks
Kraznet
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
- KVRian
- Topic Starter
- 1028 posts since 11 Jun, 2004 from London
Thank you!!Silaris wrote:I will test later this evening when I arrive home.
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
-
- Banned
- 453 posts since 30 Mar, 2016
I used to have the same problem with Xils PolyKB 2 in any DAW I ran it. Eventually they released a new version installing which fixed it for me.
I bet it's not Samp related, probably OS stuff like Vsiual C++ Redistributables, or registry entries or some such stuff which your plugin should have installed/modified but didn't or they got changed later on.
I hope someone can pinpoint the source of the problem, would be nice to have a solution next time when it happens.
I bet it's not Samp related, probably OS stuff like Vsiual C++ Redistributables, or registry entries or some such stuff which your plugin should have installed/modified but didn't or they got changed later on.
I hope someone can pinpoint the source of the problem, would be nice to have a solution next time when it happens.
- KVRian
- Topic Starter
- 1028 posts since 11 Jun, 2004 from London
Thanks for your input it's much appreciated. I did contact Arturia support and received a reply today. The crucial thing is that they don't officially support Samplitude so it's unlikely they even have a copy. He also said they haven't tested their VSTi's in Samplitude either.sfxsound3 wrote:I used to have the same problem with Xils PolyKB 2 in any DAW I ran it. Eventually they released a new version installing which fixed it for me.
I bet it's not Samp related, probably OS stuff like Vsiual C++ Redistributables, or registry entries or some such stuff which your plugin should have installed/modified but didn't or they got changed later on.
I hope someone can pinpoint the source of the problem, would be nice to have a solution next time when it happens.
He suggested the usual things like running Samplitude as administrator which I've already tried but made no difference. I'm working with a clean install of Windows 10. I reported the problem to Magix support and they confirmed it. I've noticed after reopening the project when the VSTi's are silent, if you open the GUI and advance the preset forward or backwards the sound returns. But then if you save the project and reopen it all the Arturia VSTi's are silent again. It would be nice if this problem could somehow be solved.
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
-
- KVRist
- 385 posts since 15 Jan, 2003
I ran a test and experienced the same bug, as stated in the initial post, with the Arturia Collection v4 and v5 instrument plugins in Samplitude Pro X2 and X3.
Considering that I did not notice the bug until now, it is a reminder that I should use my Arturia plugins more often.
Considering that I did not notice the bug until now, it is a reminder that I should use my Arturia plugins more often.
- KVRian
- Topic Starter
- 1028 posts since 11 Jun, 2004 from London
Thanks for testing much appreciated.Silaris wrote:I ran a test and experienced the same bug, as stated in the initial post, with the Arturia Collection v4 and v5 instrument plugins in Samplitude Pro X2 and X3.
Considering that I did not notice the bug until now, it is a reminder that I should use my Arturia plugins more often.
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
-
- Banned
- 453 posts since 30 Mar, 2016
Maybe ask Arturia if their plugins need some specific OS stuff to run properly. I'm sure a clean Windows 10 is not fully equipped with everything any app might need.
I'm on Windows 7 and a few days ago installed a demo of Geist - just wouldn't run on startup. I couldn't be arsed to find out why.
I'm on Windows 7 and a few days ago installed a demo of Geist - just wouldn't run on startup. I couldn't be arsed to find out why.
- KVRian
- Topic Starter
- 1028 posts since 11 Jun, 2004 from London
I have an update on the situation. One of the Samplitude developers sent me a special build (I'm a beta tester) and this seems to have fixed the problem with the VSTi's being silent. This works with VSTi2 versions of the Arturia plug-ins. It doesn't magically fix any previous projects which are silent but any new projects created will work as expected when re-opened. VSTi 3 versions will need a separate fix although I'm not sure of the timescale that fix. The VSTi 2 fix will appear in the next patch.
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
-
- Banned
- 453 posts since 30 Mar, 2016
See, I don't think this is a 'real' fix. Older projects should play too, I think... Maybe they did a workaround to brute force the plugins to play and this now gets saved in the project file. Actually, did he say how they fixed this or what was the cause? Coz as I said, I've experienced such behaviour with other plugins and hosts - so it's gotta be more than Samplitude's fault.Kraznet wrote:It doesn't magically fix any previous projects which are silent but any new projects created will work as expected when re-opened.
- KVRian
- Topic Starter
- 1028 posts since 11 Jun, 2004 from London
He didn't go into the details of the fix. I was just happy they finally worked. I will inform Arturia support but the problem is they don't support or even test their VSTi's in Samplitude. I mentioned I could arrange for them to have a copy of Samplitude but they need to be willing to add it to their list of supported DAW's and I'm waiting to hear back from Arturia about that.sfxsound3 wrote:See, I don't think this is a 'real' fix. Older projects should play too, I think... Maybe they did a workaround to brute force the plugins to play and this now gets saved in the project file. Actually, did he say how they fixed this or what was the cause? Coz as I said, I've experienced such behaviour with other plugins and hosts - so it's gotta be more than Samplitude's fault.Kraznet wrote:It doesn't magically fix any previous projects which are silent but any new projects created will work as expected when re-opened.
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
-
- KVRist
- 385 posts since 15 Jan, 2003
Thank you for the update, Kraznet!Kraznet wrote:I have an update on the situation. One of the Samplitude developers sent me a special build (I'm a beta tester) and this seems to have fixed the problem with the VSTi's being silent. This works with VSTi2 versions of the Arturia plug-ins. It doesn't magically fix any previous projects which are silent but any new projects created will work as expected when re-opened. VSTi 3 versions will need a separate fix although I'm not sure of the timescale that fix. The VSTi 2 fix will appear in the next patch.
Also, at least for VSTi2 versions of the Arturia plugins, a big thanks to the developers for promptly addressing the stated issue.
With the exception of a few plugins that require VST3 installs (i.e., Celemony Melodyne Assistant, etc.), I only have Samplitude mapped to my VST2 (64-bit) folder path. Therefore, this solution works perfectly for me. Nevertheless, for the sake of other users, I hope the VSTi3 versions will be fixed soon.