Solo Update using EZdrummer

EZdrummer Help
Viewing 14 replies - 1 through 14 (of 14 total)
  • Scott
    Moderator

    64-bit EZD & S2 with 64-bit Solo? Or some other combination?

    Scott Sibley - Toontrack
    Technical Advisor

    anonymous_3
    Participant

    I’m on a 32-Bit Machine.

    anonymous_3
    Participant

    Update: I reverted back to Solo 1.2.2 and all is well again! Something’s goin on…

    Rogue
    Moderator

    well, the second ‘issue’ is not really one – graphic calls are definitely not prioritized on purpose, since doing so can degrade the reliability of the (sonic) playback. That said I wouldn’t expect solo 1.3.0 to be any more ‘uncooperative’ with the animation than 1.2.2 was – I take it from your comment that it is?

    For the first one, graphic glitches would be indeed one of the concern of the latest round of updates. I’m guessing that this (possibly both) could be a similar issue as we have found with EZplayer a couple of days ago, i.e control can be not very responsive at times, but I will probe the programmer.

    Rogue Marechal - Toontrack
    Configuration Manager

    anonymous_3
    Participant

    As I said, after reverting back, the issues listed above were gone and everything is fine now.

    Rogue
    Moderator

    after re-reading your post I think I got my wires crossed – it is not a visual issue you are reporting but some sounds not being produced, including from playing MIDI? Is this using the internal Browser or using an external MIDI controller?

    Rogue Marechal - Toontrack
    Configuration Manager

    Rogue
    Moderator

    err no, I think I was right in my understanding of your issues the first time.

    As I said the graphical side of things of the animations is really down to the exact CPU load i.e tempo/speed, business of groove, and number of voices (mic bleed). If it’s high then animations are skipped… I can’t see any reason for solo 1.3.0 to be anything but minimally more CPU intensive than its predecessors but just a visual cue is not going to tell if that’s the case on your particular machine.

    When it comes to the preview not working, I can’t think of a cause as – unlike EZplayer – we can’t reproduce this on any PPC 10.4 based systems. I guess the first thing that comes to mind is that the kit is not fully loaded when that happens, but I won’t do you the insult of taking that option too seriously.

    Anyway, if you feel inclined to try some more and perhaps identify some possible factors then please do, otherwise I’m afraid a fix is not likely as solo seems to behave correctly for other PPC users and ourselves, thus far at least. I’ll subscribe to this tread to make sure I get pinged if any concurring report gets added here.

    Rogue Marechal - Toontrack
    Configuration Manager

    anonymous_3
    Participant

    These issues are very hard to describe and put into text. If you or someone from TT would like to call me at the phone number listed on my account to discuss this further, that would be great! Thanks for the help!

    Christian Derdul
    Participant

    Hello,

    I updated to solo 1.3.0 yesterday and had the same type of problem. The sound seemed to be in time but the animation was off completely. Night and day compared to 1.2.2. Tried it in 32 bit and 64 bit, EZ and Superior. I tried it as a plug-in and had the same results. I know the animation should be secondary but this was not some kind of subtle compensation. It basically ruined the whole toontrack set-up.(completely out of sync GUI, unresponsive to mouse click, maybe 1 out of 6 times).

    Only one other person had this happen is strange to me because my computer set-up has been stable. EZ Drummer and Superior Drummer worked perfectly before installing Toontrack Solo 1.3.0. I was going to see if somebody could post 1.2.2 in my account to download but I ended up reverting back to a cloned drive.

    I hope this can be of some use.

    Thanks,
    Christian

    Mac Pro 4.1, 2.26 GHz 8 Core, 28 GB RAM, OS X 10.10.5, Logic Pro 10.2.0, Apogee Duet

    Rogue
    Moderator

    Thanks for feedback. I’m confused by your report however – what do you mean by ‘I tried it as a plug-in’? If you experienced issues with EZDrummer or Superior in Logic, then this has nothing to do with solo, obviously.

    … graphical calls, again, are skipped when the demand on the CPU is such that honoring them would degrade playback. So there could be any number of causes, from a background process running, network activity, etc.

    If you experienced this in the first half an hour after booting the machine it could for example be due to the app store database updating that is notoriously an issue in 10.6.6. If you have a bootcamp partition then it is very likely going to cause such problems.

    One interesting experiment, if you can produce this problem on demand, would be to monitor the disk and CPU Activity of the running processes to see where your CPU cycles are being engulfed. If it is solo then supplying us with a tts file would at least allow us to estimate what would be the expected CPU load on the target machine, and possibly reproduce.

    … but again, if symptoms exist in Logic then you’ll probably find the cause has nothing to do with your audio application.

    Rogue Marechal - Toontrack
    Configuration Manager

    Christian Derdul
    Participant

    Hi,

    Yeah I know it doesn’t make sense. I thought okay it should be fine in Logic but it behaved exactly the same as it did in solo. I’ve never opened the app store and don’t have a bootcamp partition or any partition on the system drive. In iStat Menus there’s no excessive activity after booting up.

    So yeah I have no clue what happened but it’s all back to normal with 1.2.2. I’ll just stick with 1.2.2 solo for now and maybe you can help me figure it out if I try updating again.

    Thanks,
    Christian

    Mac Pro 4.1, 2.26 GHz 8 Core, 28 GB RAM, OS X 10.10.5, Logic Pro 10.2.0, Apogee Duet

    Christian Derdul
    Participant

    So it seems something got messed up along the way. Not sure when. EZ Drummer is acting weird(as described above) in Logic but seems ok in Solo 1.2.2. EZ Drummer and Superior did act like this in Solo 1.3.0 though, so it’s two different issues? Now after installing Electronic and Metalheads EZ Drummer and Superior Drummer will not load Cocktail in Solo or Logic.

    I refuse to let this get to “me”!

    Mac Pro 4.1, 2.26 GHz 8 Core, 28 GB RAM, OS X 10.10.5, Logic Pro 10.2.0, Apogee Duet

    Rogue
    Moderator

    well, again, there is no connection between EZDrummer/Superior as used as plugins in Logic or ‘stand alone’ in solo. By that I mean that solo is just a host like any other in most respects, and issues you observe in Logic simply cannot be related to the version of solo that you have, or solo being installed on the computer for that matter.

    Besides that, EZdrummer has yet to go through the overhaul required for 64-bit support, so it’s hard to think the problem is not on the OS side, since our code is virtually unchanged for the last year or so, on the Mac side at least. What version have you been running prior to recently, if any change on that front?

    … regarding your Cocktail set, I see you have many EZX-s, did you only lose access to Cocktail? I’m not sure what would cause just a particular set to disappear, but perhaps it is a permission issue – have you tried to re-apply the latest Cocktail update?

    Rogue Marechal - Toontrack
    Configuration Manager

    Christian Derdul
    Participant

    Hey Rogue, I had been using 10.6.5, all this general weirdness must be due to the 10.6.6 update. I do have all the EZX’s working now.

    Thanks

    Mac Pro 4.1, 2.26 GHz 8 Core, 28 GB RAM, OS X 10.10.5, Logic Pro 10.2.0, Apogee Duet

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

No products in the cart.

×