Replies created

 

Viewing 7 replies - 1 through 7 (of 7 total)
  • Steffan Andrews
    Participant

    Good call.

    In 44.1k it’s stable as a rock. In 48k the second instance of EZdrummer crashes the host immediately.

    I also noticed that the samples load blazing fast in 44.1k with EZdrummer, but in 48k they take close to 2 minutes to load.

    All my sessions run at 48k so this is definitely a problem.

    Steffan Andrews
    Participant

    No sir, I checked thoroughly through both the All Users and the current user’s data files on the PC. There are folders for EZdrummer, but no errlog inside. Just for SD2.

    Same on the Mac – there are folders for both, but only one errlog for EZdrummer with just the “Illegal command” lines as stated above, with an old file date.

    Steffan Andrews
    Participant

    I checked those locations on the Mac and PC and I’m not sure they will be of any use to you. The errlog.doc files I found had modification dates weeks old.

    Additionally, I have a utility on the Mac that monitors system wide file/disk activity. I did not see any Toontrack error log files being written or accessed. Only the system crash log file and other non-related files.

    If it’s of any interest, the only contents in these files were these lines, and they were from an old copy of SD2’s errlog, and not EZdrummer’s.

    Error in configfile ‘Save Chunk’ line 3 :Illegal command ‘CurrentKey’
    Error in configfile ‘Save Chunk’ line 4 :Illegal command ‘currentTrack’
    Farray::AddMemUse underflow 32300 -8075 -32300 -169
    Farray::AddMemUse underflow 292 -73 -292 -73

    Steffan Andrews
    Participant

    That’s a good question. I can see if there are any I can dig up.

    I found the Cubase 6 crash report on the Mac:

    http://dl.dropbox.com/u/1477110/ezd/Cubase%206_2011-05-01-112539_Rig.txt

    Steffan Andrews
    Participant

    I’m fully aware of that. I have explicit control over where they reside. But it’s a further proof that there is something wrong with EZdrummer in this new version because of the identical crash behavior across multiple platforms. It has NOTHING to do with 32 or 64 bit.

    Steffan Andrews
    Participant

    It seems rather inexplicable that 1.2.1 would perform fine on two different platforms in different hosts, then both break in the exact same way when upgraded to 1.3.0. I tested multiple 32-bit and 64-bit hosts on both machines.

    At this point I don’t know what to assess. It’s not a plug-in mixup on the PC. On the Mac it’s impossible to mix up 32/64 bit VST plugins because they’re part of the same binary file. And yet this crash behavior persists. I am wondering if it has something to do with a corrupt EZX data folder or something. I just don’t have the time to be screwing around with this. I’ve rolled back to 1.2.1 and forging ahead for now.

    Steffan Andrews
    Participant

    I had this same problem – the 32-bit 1.3.0 updater would not run. I uninstalled EZdrummer and reinstalled from the “DVD” image then updated straight to 1.3.0. Worked fine.

    I think there is a problem with the 1.3.0 updater that needs to be addressed. This should not be happening.

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

No products in the cart.

×