Replies created

 

Viewing 11 replies - 1 through 11 (of 11 total)
  • Tommy
    Participant

    This just happened to me also. Luckily, I figured out that the copy protection system may be incredibly stupid, and I was right.
    I qoute from the aforementioned FAQ:

    “….in particular disabling your network device or wireless modem.”
    “Other major changes such as replacing your motherboard or internal harddrives could also cause the computer ID to change”

    **** Since when was disabling the wifi card a MAJOR change? ***

    I disable WiFi before I start recording, so I’ll not risk it creating interrupts interfering with my recording.
    If I’m to continue using the Toontrack products I’ve spent a lot of money buying, I’ll have to get used to disabling my WiFI *after* loading the plugins.

    The copy-protection was cracked about 7 minutes after you released EZdrummer; all you are doing is creating problems for your loyal customers.
    This is beyond stupid.

    Luckily, Toontrack isn’t the only company around.
    (Native-Instruments Studio Drummer sounds better too, and their copy-protection, whilst stupid, ain’t THIS stupid)

    Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64

    Tommy
    Participant

    My previous installation was at S:Program FilesEZdrummer and after the disk failure I reinstalled at W:Program FilesEZdrummer

    I’ve created a S:Program FilesEZdrummer and copied all files in there also, just in case it’s looking for files there also.
    Didn’t help.

    Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64

    Tommy
    Participant

    Yes, it is version 1.21.

    Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64

    Tommy
    Participant

    *bump*?

    I still can’t use Nashville. Help!

    Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64

    Tommy
    Participant

    ORIGINAL: Dave Modisette

    Just wondering if it could be some sort of bit depth conversion issue. Could you try it in your host at a 16 bit bit depth and see if that solves it? Also, does the problem manifest using different kit pieces? IOW, change the snare and see if that helps. Also if you haven’t tried it, resist the temptation to trigger the kit pieces while the kit is loading and see if that changes anything.

    Tried that, didn’t help.

    Thanks for the tip anyways 🙂

    in summary: Nashville loads, up to ca 72mb. Ie: All kit pieces EXCEPT toms! (and possibly less layers on the others, but atleast they make a sound)

    Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64

    Tommy
    Participant

    ORIGINAL: John

    Bit depth is highly unlikely to cause any problems.
    Any Anti-Virus program at the same time?
    Which version number is reported for the Nashville EZX in the Help menu?

    Nashville 1.1.3 it says.

    Changing bit depth (to 16) and bitrate (to 48) didn’t help.

    No antivirus installed on my studio computer, but I occasionally run MCAfee Security Scan.

    Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64

    Tommy
    Participant

    ORIGINAL: bradch00

    Have you tried going through the default kit that loads up, setting all the drum types to “none” and then back to something else and see if they load normal…. not that this is the way you want to work… but it may reset something in Nashville….

    I’ll do that, and also look into bit-conversion type problems.
    Thanks,

    Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64

    Tommy
    Participant

    Using Pro Tools M-Powered, Ableton Live, Reaper, Tracktion, Toontrack Solo. it ain’t the host 🙂

    Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64

    Tommy
    Participant

    I’ve tried copying the EZX_Nashville folder off to another location to see if Windows complained about broken files. All good.

    The folder itself is:
    Size: 957MB (1 004 495 212 bytes) big.
    Size on disk: 976 (1 024 315 392 bytes)

    Contains 9668 Files, 11 Folders

    Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64

    Tommy
    Participant

    Ok,
    -moved off the EZX_Nashville to temp (in case there were corrupt files in there, the reinstall would not happen to reside on the same blocks)
    -Checked disk for errors (there were none)
    -Defragmented
    -Uninstalled
    -Reinstalled
        -Stopped loading at 71mb
    -Ran the Nashville updater
       -Stopped loading at 72mb.

    Same behaviour in Ableton Live as in Toontrack Solo.

    This is very annoying, as I’m mixing down ~30 tracks right now for a gig on saturday, many of which uses Nashville.

    Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64

    Tommy
    Participant

    As they haven’t changed I can’t quite see why, but here they are:

    -AMD Phenom II X3, 2.8ghz
    -4Gb DDR2 memory
    -500Gb SATA for OS & Misc
    -500GB SATA for Apps & Data
    -ATI Radeon HD4870X2 gfx

    -Running Windows XP SP3
    -M-Audio USB Micro soundcard.

    Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64

Viewing 11 replies - 1 through 11 (of 11 total)

No products in the cart.

×