Jump to content


  • Posts

  • Joined

  • Last visited

About Wyoming

  • Birthday January 13

Profile Information

  • Gender
  • Location
    Skara, Sweden

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Wyoming's Achievements


Member (2/8)

  1. My major backups are not on projects depending on a DAW, they are just containing independant audio files that can be used in any music software. I just make project backups for a shorter term, say a year or so (until I release an album). The reason for that is a long history, first recording on tape recorders, then on harddisk recorders and finally working with several softwares. You can never be sure when you backup a project whether you will/can use the same DAW/recorder in the future, you never know whether the future version will be compatible, you never know if the company still exists (see cakewalk), you never know whether all plugins will be there and will be compatible. Thus when you backup all your recorded wave files, all your laborious tracks saved as wave files and all your MIDI tracks as wave files (and as MIDI), you will be safe for future use of that material, IMHO. Regarding the sort order (by type) I use this rarely, because in my song folders (outside of DAW projects) I have some header files with notes that I start with # (that they are on top when sorted by name) and below there are files starting with the track numbers (waves, midi and others). Like that I have quite a good overview and find quickly the files I need (there are even more conventions in the names). I do not have to scroll all the time. But this is only my way to work, I am aware that this is not practical for everyone.
  2. Well reasoned! I agree that the coding would be simple and it is also no problem to implement backwards compatibility.
  3. I do not completly agree with that. For sure like that you have your waves together, but if you have other files too, then those are also sorted out of your view. And that's probably not want you want! And 2nd: If you backup those folders (I do), then you have always to exclude those annoying H* files!
  4. Thanks for the answers, there has been said a lot that is true. But my concern is more using wave files OUTSIDE OF THE PROJECT folder and I do not like Samplitude to mess around there, i.e. I do not mind if those H* files are aside with their wave files within the project directory (even if I agree with JoaCHIP that it would be better to separate them). It is very uncommon that an application creates help files outside of the project directory when you reference files anywhere on the system. And IMHO it is not always a good solution to copy all files to the project if you want that there exists only 1 single version!
  5. I would not recommend to have the VST2 and VST3 plugins in the same folder though! That maybe alright for Samplitude, but for most other applications this will not work, because it is standard that the VST3 base folder is C:\Program Files\Common Files\VST3. But it is possible to move the VST3 plugins into own subfolders.
  6. Concerning VSTs I have created an own VST2 folder for Samplitude with subfolders like "Delay", "Distortion", "EQ", "Reverb", ... Then when I install any VST I link (or copy) the VST DLL in the matching subfolders. Like that you have your own nice VST menu in Samplitude after "VST FX" or "VSTi". If you do the same thing with the VST3 plugins (I keep them still in the standard directory C:\Program Files\Common Files\VST3) and use the same subfolder names, then they are properly merged together in the VST menus. The only drawback is that you must not forget to update the Samplitude VST folder after installing or removing a plugin, or if you have copied the DLLs (not linked).
  7. Thanks Phil! Well this is really a problem if you want some of your files to be outside of your project! I usually need this, because I do not like to have only one project per song. I prefer to have several projects for a song, each for a specific task like creating VST instrument tracks, recording and editing vocals, ..., mixing. And then I export (bounce) the final tracks to a song directory from where I import them to the following projects and do backups. There I do not want Samplitude to mess around! And there are 2 reasons why I do not want to copy those wave files to each project: First, I want that changes to the waves are automatically represented in all projects and second, I do not want to waste space on my disks! So it seems the only solution is to create links to my wave files (mklink) in the project directory and import them from there into Samplitude. But that is quite cumbersome!
  8. For each wave file that I import Samplitude creates a *.H2, *.HDP and *.HS file. If I import the wave file into the project (=copy file to project), then this is okay. But if I want to reference only a wave file from another place (copy to project = OFF), is there a way to tell Samplitude to store the H2/HDP/HS file in the project directory instead of the default (=wave file location)?
  9. But not me! I love some great old freeware 32-bit plugins that I would miss. I never had any issues with Sonar and 32-bit plugins, only once together with a USB driver from Focusrite. But that time it was possible to go back to the previous driver version and since then I had no problems. There is now a new Focusrite driver and I have downloaded, but not testet it, since I use now a Behringer USB interface.
  10. That's precisely the thing I have noticed. After several tries to start SF I found out that it crashed loading the independence VST. But when I took that out of my MAGIX VST folder it ran perfectly (Yes, I have a seperate VST folder for Samplitude and SF, because like that I could create a helpful folder structure like in Sonar)!
  11. Hey Bitflipper, I have already committed such a crime!
  • Create New...