T7 horror experience
-
- KVRist
- 126 posts since 14 Dec, 2010
Hi there,
I recently installed the T7 demo on my system (Windows 7, 64 bit) and had difficulties to scan my VST pluins. Some were recognized by T7 and some were not. Since there obviously is no user manual to check if I was doing something wrong I gave up in the end and tried to remove it from my PC. But what happened when clicking the deinstallation button was that T7 started to delete the complete installation folder (C://programmes).
Before i could stop T7 from deleting some of my VSTs were gone and I couldn't load them into Studio One (which I currently use) anymore. Only a system recovery could cure that.
Horrible experience!
I recently installed the T7 demo on my system (Windows 7, 64 bit) and had difficulties to scan my VST pluins. Some were recognized by T7 and some were not. Since there obviously is no user manual to check if I was doing something wrong I gave up in the end and tried to remove it from my PC. But what happened when clicking the deinstallation button was that T7 started to delete the complete installation folder (C://programmes).
Before i could stop T7 from deleting some of my VSTs were gone and I couldn't load them into Studio One (which I currently use) anymore. Only a system recovery could cure that.
Horrible experience!
-
- KVRAF
- 1790 posts since 30 Dec, 2012
Hi there, sorry to hear about this. It sounds like you may have changed the installation directory to put T7 directly into your Program Files directory rather than in a Tracktion 7 sub-directory which is the default.
The un-installer will try and remove the directory specified at install time so if you've explicitly set this to your Program Files it looks as though the uninstaller has attempted to remove this.
I'll look into this and try and improve the behaviour but it's important to note that this is not default behaviour so will not affect the majority of users.
The un-installer will try and remove the directory specified at install time so if you've explicitly set this to your Program Files it looks as though the uninstaller has attempted to remove this.
I'll look into this and try and improve the behaviour but it's important to note that this is not default behaviour so will not affect the majority of users.
-
- KVRAF
- 2417 posts since 17 Jun, 2003
Wouldn't you need to install T7 to c:\program files, then run the uninstaller as admin, with UAC turned off for this to happen? Why did Studio One itself not get deleted?DIGIFEX wrote:Hi there,
I recently installed the T7 demo on my system (Windows 7, 64 bit) and had difficulties to scan my VST pluins. Some were recognized by T7 and some were not. Since there obviously is no user manual to check if I was doing something wrong I gave up in the end and tried to remove it from my PC. But what happened when clicking the deinstallation button was that T7 started to delete the complete installation folder (C://programmes).
Before i could stop T7 from deleting some of my VSTs were gone and I couldn't load them into Studio One (which I currently use) anymore. Only a system recovery could cure that.
Horrible experience!
"my gosh it's a friggin hardware"
-
- KVRist
- Topic Starter
- 126 posts since 14 Dec, 2010
Thanks for your reply dRowAudio,
any idea why some VST plugins are not recognized? It seemed as if the directory where the plugins are installed has an influence on the success of the scanning. Some of my plugins are put here: c://VSTplugins. I had to create this folder because these plugins don't work when they are put into the standard VST-folder (c://programmes/VSTplugins). All of the plugins that reside in c://VSTplugins were recognized by T7.
May be I'll try a second time to install T7 - choosing the default installation directory - and see what happens.
any idea why some VST plugins are not recognized? It seemed as if the directory where the plugins are installed has an influence on the success of the scanning. Some of my plugins are put here: c://VSTplugins. I had to create this folder because these plugins don't work when they are put into the standard VST-folder (c://programmes/VSTplugins). All of the plugins that reside in c://VSTplugins were recognized by T7.
May be I'll try a second time to install T7 - choosing the default installation directory - and see what happens.
-
- KVRist
- Topic Starter
- 126 posts since 14 Dec, 2010
I cancelled the deinstallation of T7 when I saw what was happening. But some files were already deleted.Why did Studio One itself not get deleted?
I swear I didn't run the deinstallation in administrator mode!
- Beware the Quoth
- 35529 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
FWIW, there is no standard VST folder. That might be where Tracktion looks by default (I cant remember), but its not standardised, anywhere, by any company. The closest thing to a standard is the location Steinberg used to use, which is actuallyDIGIFEX wrote:these plugins don't work when they are put into the standard VST-folder (c://programmes/VSTplugins).
C:\Program Files\Steinberg\VstPlugins
and some plugins try to install there by default, but not all of them.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
-
- KVRAF
- 2417 posts since 17 Jun, 2003
Windows doesn't use forward slashes (/) in it's file paths. It uses back slashes (\) and not doubles (//)
I'm a bit concerned you keep using forward slashes when referring to directories, eg
c://programmes/vstplugins
Is it possible that by using the wrong slashes in the file path when running the installer has installed T7 to a weird, unexpected directory?
I'm a bit concerned you keep using forward slashes when referring to directories, eg
c://programmes/vstplugins
Is it possible that by using the wrong slashes in the file path when running the installer has installed T7 to a weird, unexpected directory?
"my gosh it's a friggin hardware"
-
- KVRist
- Topic Starter
- 126 posts since 14 Dec, 2010
No, the slashes are not the problem. I'm not using the correct syntax here when I'm trying to explain the problem (sorry for this). I choosed the installation folder just by using the mouse and didn't type in anything.
But as far as the VST folders are concerned it seems as if it does matter to T7 where this folder is located (T7 itself resies here: C:\\Programme (x86)):
C:\\Programme (x86)\VSTplugins (not recognized by T7)
C:\\VSTplugins (is recognized by T7)
But as far as the VST folders are concerned it seems as if it does matter to T7 where this folder is located (T7 itself resies here: C:\\Programme (x86)):
C:\\Programme (x86)\VSTplugins (not recognized by T7)
C:\\VSTplugins (is recognized by T7)
Last edited by DIGIFEX on Thu Mar 24, 2016 12:08 pm, edited 1 time in total.
-
- KVRAF
- 2417 posts since 17 Jun, 2003
That's likely to be because the account tracktion.exe is running under doesn't have access to those folders. Try right clicking the tracktion.exe file, and running it as admin (after it's installed), then run the plugin scan. You're possibly trying to scan directories that the program is being blocked from accessing.
Either that, or you're scanning 32 bit plugins in the 64 bit version of T7, or 64 bit plugins in the 32 bit version of T7. Neither of which will work.
Either that, or you're scanning 32 bit plugins in the 64 bit version of T7, or 64 bit plugins in the 32 bit version of T7. Neither of which will work.
"my gosh it's a friggin hardware"
- Beware the Quoth
- 35529 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
Its probably not that it matters to T7, as such. I suspect though, it matters to the user account running T7.DIGIFEX wrote:No, the slashes are not the problem. I'm not using the correct syntax here when I'm trying to explain the problem (sorry for this). I choosed the installation folder just by using the mouse and didn't type in anything.
But as far as the VST folders are concerned it seems as if it does matter to T7 where this folder is located:
C:\\Programme (x86)\VSTplugins (not recognized by T7)
C:\\VSTplugins (is recognized by T7)
C:\Program Files
and
C:\Program Files (x86)
are both set up, in terms of file and directory security permissions, so that particular users cannot write to them. Those permissions get inherited by any folders inside them.
If you run your software with a normal user account which does not have the right permissions for those folders, you can run into problems. The solution is either to 'Run as Administrator' OR put your plugins in a different folder outside there (as per your C:\VSTPlugins) OR change the security permissions on the folder containing your plugins.
I'd recommend option 2 (different folder) as being the easiest with the least ramifications.
edit : as per chico's reply above, the C:\Program Files (x86) folder is where 32-bit software goes. C:\Program Files is where 64-bit software goes.
If you're running the 64-bit version of Tracktion, it cant use 32-bit plugins.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
-
- KVRist
- Topic Starter
- 126 posts since 14 Dec, 2010
Aaaah, yes, running the app as administrator may cure the desease. I'll try that later in the evening.
By the way: I have only 32 bit plugins and installed the 32 bit version of T7. So this shouldn't be the problem.
By the way: I have only 32 bit plugins and installed the 32 bit version of T7. So this shouldn't be the problem.
-
- KVRian
- 620 posts since 27 Jul, 2001 from france
32 bit or not, this should be the problem...
PQ
free software at : http://pquenin.free.fr/pqnaudio
free music at : http://www.soundclick.com/thepqueninproject
free software at : http://pquenin.free.fr/pqnaudio
free music at : http://www.soundclick.com/thepqueninproject
