I'm using Tracktion 7.1.1 on Linux . When I previously used T7.1, all of my plugins in the Ultimate pack worked fine, no problems. Now, in T711, I scan for plugins abd get the error message:"Scan Complete. Note that the following files appeared to be plugin files, but failed to load correctly: Master Mix.so, FM Synth.so, BioTek.so, Analog Synth.so " All of those plugins are in /usr/lib/vst.
Now if Tracktion can find the plugins, why can they not load correctly?
BTW-ladspa plugins work fine, no problem.
SOLVED:T711 Linux kills my vst plugins
-
- KVRAF
- 1790 posts since 30 Dec, 2012
Do they scan if you drag and drop the plugin files (the ones ending in .so) directly on to the plugin list?
That should scan them individually.
Also, they the stop working when you updated? You shouldn't have to scan for new plugins after every update, they should have just remained in the list.
That should scan them individually.
Also, they the stop working when you updated? You shouldn't have to scan for new plugins after every update, they should have just remained in the list.
-
- KVRist
- Topic Starter
- 460 posts since 12 Sep, 2008 from Canada
No nothing happens when I d'n d.dRowAudio wrote:Do they scan if you drag and drop the plugin files (the ones ending in .so) directly on to the plugin list?
Yes, that is correct. (BTW, I have the plugins in usr/lib/vst; one of the default paths in Tracktion Linux)Also, they the stop working when you updated?
-
- KVRer
- 27 posts since 26 Aug, 2007 from Sweden
Hi Doug
Im still on 7.1 and, as you said, everything is working fine, so I hesitate to upgrade. (reading posts like yours
However I keep my vst's in /home/myname/.vst
(I only have the minisynths from Tracktion)
I dont know why that would make any difference but it might be worth testing?
Anders
Im still on 7.1 and, as you said, everything is working fine, so I hesitate to upgrade. (reading posts like yours
However I keep my vst's in /home/myname/.vst
(I only have the minisynths from Tracktion)
I dont know why that would make any difference but it might be worth testing?
Anders
"Ubuntu Studio 16.04 with KXStudio"
-
- KVRAF
- 1790 posts since 30 Dec, 2012
I don't think there should be anything different in unlocking the plugins between Tracktion versions, they should be independent of that. They have their own settings files and authorisation mechanisms.
If you move the plugin files around, the machine ID may change as it's based on the root folder. We'll look in to making that more stable but you shouldn't have to move the plugin files around if you install them to one of the recommended locations.
If you do move them, generate a new key file from the Offline Unlock page on our website. (If you purchased any plugins as part of a bundle we're currently resolving as issue where these products won't show up so email support and we'll send you key files).
The most important thing to sure of is that you report the correct machine ID to us. It must be the one shown in the plugin UI. To be safe, send a screenshot with the request.
If that still doesn't work, try unlocking making sure only one plugin instance is open as there's a chance they may override each others settings files if they're being run in a different process (like BitWig does).
If you move the plugin files around, the machine ID may change as it's based on the root folder. We'll look in to making that more stable but you shouldn't have to move the plugin files around if you install them to one of the recommended locations.
If you do move them, generate a new key file from the Offline Unlock page on our website. (If you purchased any plugins as part of a bundle we're currently resolving as issue where these products won't show up so email support and we'll send you key files).
The most important thing to sure of is that you report the correct machine ID to us. It must be the one shown in the plugin UI. To be safe, send a screenshot with the request.
If that still doesn't work, try unlocking making sure only one plugin instance is open as there's a chance they may override each others settings files if they're being run in a different process (like BitWig does).
-
- KVRist
- Topic Starter
- 460 posts since 12 Sep, 2008 from Canada
Thanks for replying, Anders. I keep my vst's in /home/myname/.vst just like you do.Storfot wrote:Hi Doug
Im still on 7.1 and, as you said, everything is working fine, so I hesitate to upgrade. (reading posts like yours
However I keep my vst's in /home/myname/.vst
(I only have the minisynths from Tracktion)
I dont know why that would make any difference but it might be worth testing?
Anders
As for 7.1, is it possible to still download that one? I may go back to 7.1 and forget about 7.1.1 for now.
Cheers
Doug
-
- KVRist
- Topic Starter
- 460 posts since 12 Sep, 2008 from Canada
I have tried all of your suggestions, and Brian emailed keys last week-nothing worked. Should I submit another request?dRowAudio wrote:I don't think there should be anything different in unlocking the plugins between Tracktion versions, they should be independent of that. They have their own settings files and authorisation mechanisms.
If you move the plugin files around, the machine ID may change as it's based on the root folder. We'll look in to making that more stable but you shouldn't have to move the plugin files around if you install them to one of the recommended locations.
If you do move them, generate a new key file from the Offline Unlock page on our website. (If you purchased any plugins as part of a bundle we're currently resolving as issue where these products won't show up so email support and we'll send you key files).
The most important thing to sure of is that you report the correct machine ID to us. It must be the one shown in the plugin UI. To be safe, send a screenshot with the request.
If that still doesn't work, try unlocking making sure only one plugin instance is open as there's a chance they may override each others settings files if they're being run in a different process (like BitWig does).
Doug
-
- KVRAF
- 1790 posts since 30 Dec, 2012
Are you sure the machine ID was correct?Doug B wrote:I have tried all of your suggestions, and Brian emailed keys last week-nothing worked. Should I submit another request?
Doug
You could try re-installing v7.1, I'd be interested to know if that makes a difference as I can't think why it would. The only thing I can think of is that the plugins have been moved on disk?
Yes, I would send another support request and include screenshots of all the machine IDs.
-
- KVRist
- Topic Starter
- 460 posts since 12 Sep, 2008 from Canada
All I know is that the machine ID was the one listed in the ABOUT window at the time.dRowAudio wrote: Are you sure the machine ID was correct?
How can I tell which one is 7.1? I see in my downloads that 7.1.1 is marked as such, is 7.1 the other Tracktion Linux listed?You could try re-installing v7.1, I'd be interested to know if that makes a difference as I can't think why it would. The only thing I can think of is that the plugins have been moved on disk?
Support request sent with screenshot of the about page showing the current machine ID.Yes, I would send another support request and include screenshots of all the machine IDs.
-
- KVRAF
- 1790 posts since 30 Dec, 2012
It sounds like you're sending a screen shot of the Tracktion About window, this contains the machine ID to unlock Tracktion, not the plugins (otherwise how would anyone unlock the plugins if using a different host?).Doug B wrote:All I know is that the machine ID was the one listed in the ABOUT window at the time.
You need to open the plugin UI, click the "Unlock" button (then the "Offline Unlock" button if there is one, it depends on the plugin). There you'll see a machine ID for that specific plugin.
No, to the right of the "T7 Installer - Linux 64bit v7.1.1" item in your downloads you'll see an "archives" link.Doug B wrote:How can I tell which one is 7.1? I see in my downloads that 7.1.1 is marked as such, is 7.1 the other Tracktion Linux listed?
This contains links to all previous versions.
-
- KVRist
- Topic Starter
- 460 posts since 12 Sep, 2008 from Canada
Sorry, I got confused and thought that that was what you were asking for. However, I am doing the proceedure that you mention here:dRowAudio wrote:It sounds like you're sending a screen shot of the Tracktion About window, this contains the machine ID to unlock Tracktion, not the plugins (otherwise how would anyone unlock the plugins if using a different host?).Doug B wrote:All I know is that the machine ID was the one listed in the ABOUT window at the time.
You need to open the plugin UI, click the "Unlock" button (then the "Offline Unlock" button if there is one, it depends on the plugin). There you'll see a machine ID for that specific plugin.
Thanks, I'll download T7.1 and see how it goes.No, to the right of the "T7 Installer - Linux 64bit v7.1.1" item in your downloads you'll see an "archives" link.
This contains links to all previous versions.
Doug
-
- KVRist
- Topic Starter
- 460 posts since 12 Sep, 2008 from Canada
Thinking that T 7.1.1 might be to blame for my problems, I tried every 7.x archived version of tracktion back to 7.0.23. Problems with the plugins remained the same-either it told me that the vst key was corrupt, or else it told me that the vst was unlocked-but the unlock box still appeared on the synth and the demo sound still sounded. I have also tried using Linux Mint 17.3, Debian Stable, Debian Testing, Ubuntu 14.0.4, and Ubuntu 16. Nothing worked.
At this point, I'm just going to wait until Tracktion gets their act together and fixes the problem.
At this point, I can't use what I paid for and I don't think it would hurt if Tracktion offered me a refund. Just saying.
At this point, I'm just going to wait until Tracktion gets their act together and fixes the problem.
At this point, I can't use what I paid for and I don't think it would hurt if Tracktion offered me a refund. Just saying.
-
- KVRAF
- 1790 posts since 30 Dec, 2012
I think you're getting confused with how the authorisation process works. Every machine will generate a different machine ID, for each machine ID you need a specifically generated key file. You can't get one key file then try and unlock the plugin on different distros.
If this was possible, there would be nothing to stop users posting key files on the internet letting everyone unlock their software for free!
I just tried the following at it worked flawlessly:
1. Launch my Linux Mint VM that is only a week old. The only thing that I've done is to install T7 and BioTek on it
2. Go to tracktion.com/downloads and downloaded "Master Mix - Linux 64bit - Linux 32bit v1.2.0"
3. Copied the "Master Mix.so" file in to "~/.vst"
4. Opened T7 and scanned for new VST plugins (ensuring "~/.vst" is in the search path
5. Master Mix scans and shows up in the plugin list
6. Add Master Mix to a track. It comes up unlocked.
7. Click on the "Unlock" button and copy the machine ID code (see image below)
8. *** Go to tracktion.com/downloads then click on the "unlock offline" link at the top
9. Enter the product type, machine ID and OS type to generate and download a key file
10. Back in Master Mix press the "..." button to browse for the just downloaded key file
11. Master Mix unlocks, no more hiss and "Unlock" button disappears
*** As previously mentioned if you purchased as part of a bundle the product may not appear on the offline unlock list. We are working to resolve this but in the mean time if you email the "Product Name", "OS Type" and a screenshot of the plugin UI showing the "Machine ID" to support, we'll generate and send you a key file very quickly.
I know this looks like a lot of steps but I've been deliberately verbose to be as clear as possible. It should only take a minute.
We need to be sure this isn't user error before issuing refunds as there are many users who have been able to unlock without issue.
If you move the plugin files, change OSes etc. you are likely to cause the plugins to become locked again.
If this was possible, there would be nothing to stop users posting key files on the internet letting everyone unlock their software for free!
I just tried the following at it worked flawlessly:
1. Launch my Linux Mint VM that is only a week old. The only thing that I've done is to install T7 and BioTek on it
2. Go to tracktion.com/downloads and downloaded "Master Mix - Linux 64bit - Linux 32bit v1.2.0"
3. Copied the "Master Mix.so" file in to "~/.vst"
4. Opened T7 and scanned for new VST plugins (ensuring "~/.vst" is in the search path
5. Master Mix scans and shows up in the plugin list
6. Add Master Mix to a track. It comes up unlocked.
7. Click on the "Unlock" button and copy the machine ID code (see image below)
8. *** Go to tracktion.com/downloads then click on the "unlock offline" link at the top
9. Enter the product type, machine ID and OS type to generate and download a key file
10. Back in Master Mix press the "..." button to browse for the just downloaded key file
11. Master Mix unlocks, no more hiss and "Unlock" button disappears
*** As previously mentioned if you purchased as part of a bundle the product may not appear on the offline unlock list. We are working to resolve this but in the mean time if you email the "Product Name", "OS Type" and a screenshot of the plugin UI showing the "Machine ID" to support, we'll generate and send you a key file very quickly.
I know this looks like a lot of steps but I've been deliberately verbose to be as clear as possible. It should only take a minute.
We need to be sure this isn't user error before issuing refunds as there are many users who have been able to unlock without issue.
If you move the plugin files, change OSes etc. you are likely to cause the plugins to become locked again.
You do not have the required permissions to view the files attached to this post.