Jump to content

a.t. vish

  • Posts

  • Joined

  • Last visited


0 Neutral
  1. a.t. vish

    Loom II

    So, has anyone had trouble running Loom II in Cakewalk? Everything installs fine for me, but, after opening, it routinely crashes Cakewalk when clicking on the "Edit" tab in the synth. Sometimes, it has the typical error message about crash dump etc, but usually it just closes Cakewalk and thats it. Really unstable in my system for some reason. I think this synth is great, but AIR has horrible customer service. They have been no help and really dont care. Kind of confusing that I bought it thru ADSRSounds, but made by AIR, so confusing about who to contact. V
  2. For some reason, I have had horrible times with installing ALL versions of Dimension Pro (so confused by all the versions and whether they are 32 or 64 bit, etc). For what ever reason, I had to reinstall Dimension Pro, trying to get some old projects working. I just installed every version of Dimension Pro in my old products page at Cakewalk, figuring what ever version the old project needs, it will access it. Dimension Pro installed but when it asks to register with the registration code, the registration code listed at my old Cakewalk account Products page, does not work. Im simply looking at the dialogue box that pops up with the serial number of the current Dimension Pro and I am copying and pasting the registration code that corresponds to the serial code (according to my Products list). And further, NONE of the registration codes listed for all the versions of Dimension Pro I purchased over those years will work, which I didnt think they would, of course, because they arent the reg codes for the corresponding serial number.
  3. Yes, i set the sonar project tempo to match fruityloops, then import the wave file. And what you are saying is not the issue anyway. There is no "morphing" of a wave file when importing it. A wave file will always have the same tempo it was rendered at when one imports it into sonar. You can then change it by other means once its in sonar, but if your wave file is 50 bpm and you import it into a sonar project that is 72 bpm, its still going to be a 50 bpm tempo wave file. It just wont match your 72 bpm click tempo in sonar.
  4. Im finding wave files that are exported out of fruityloops at a particular bpm, drift from a corresponding bpm when imported into a sonar project. I just checked this issue in reaper and i am not seeing the same thing. Infact, i exported the audio out of reaper and it is correct when i import it into sonar. So to be clear, my fruityloop project is 150bpm. I set up a sonar project same bpm/sampling rate, etc. Import wave files from fruityloops into the sonar project and they do not line up on the time grid and drift from the established 150bpm in sonar.
  • Create New...