• SONAR
  • So what's the verdict on Lexington? Anyone found any problems yet? (p.5)
2015/12/28 21:27:25
Anderton
arlen2133
Good to know. I'll update that plug and see what we got.
Thanks again.



I have the most recent build of Anthology X because I'm doing an in-depth Pro Review of it on Harmony Central. It's been totally painless, mono or stereo, on Lexington.
 
2015/12/28 21:59:53
arlen2133
scook
Eventide rarely announces updates to their products. I just checked and there was an update last Oct. I just tested UltraChannel v2.0.23 and the Oct 2015 update 2.0.29, by adding the plug-in to the master bus, toggling the track interleave while the transport was running. Lexington did not crash on me.


Thanks again Steve for the advice..
UPDATE: This is v2.1.2 now.  Worked like a charm. 
So, as I said before, I don't have any issues with Lexington.  I'm good for now. 
 
Craig, thanks for checking in and letting me know.  Sometimes i forget to check for updates.  Forum is a good reminder. 
2015/12/28 22:16:10
scook
Yeah, I misread the update page. The latest is 2.1.2. Glad the update works for you.
 
Craig, thanks for the link.
2016/01/19 13:04:15
wtreppler
1) Delete/Cut special not pulling all clips to the left if a portion of the selected track does not have a clip in it.
2) When trying to delete multiple clips in a track all at once, only a portion of them are deleted.
 
Bug reports submitted. Not, got to figure out how to roll back to a previous version so I don't have to be Gibson's (unwilling) beta tester.
2016/01/19 13:43:12
jeteague
   I do not want to derail this thread, so I will simply state that I seem to be having difficulties similar to what "BeerFox" describes.  See thread "Sonar Crash with multiple MIDI Take Lanes" in Problem Reports.  I hasten to add that my problems may be a quirk of my setup.
2016/01/19 13:59:12
Beepster
I've been working with Lex since I first posted this and have had nothing but problems (compared to Foxboro).
 
Lexington is sluggish, glitchy and erratic. I am very disappointed with this update and am going to have to try installing an earlier version.
 
Also the Aux track stuff, which was one of the main reasons I updated, are kind of more hassle than they're worth because of the screwed up Solo stuff (which does not allow you to just solo a track... you have to solo the track and the Aux... and of course UNsolo them again after... bad workflow).
 
So yeah... ya'll know I'm not one to crap on a release for no reason but I am seriously underwhelmed with Lex.
 
The performance improvements (another thing I was updating for) seem to be non existent on my system and actually taken multiple steps backwards on my rig.  Must only be for Win10 users or something (I'm on Win7).
 
Ugh. Seriously I don't like making negative reports like this but it ain't good. Maybe Kingston will be better.
2016/01/19 15:48:52
jih64
No, I'm on Windows 10, and when I updated to Lexington after a long hiatus, just to see how things were going, I found it to be a noticeable step backwards as well performance wise.
2016/01/19 16:01:01
Bristol_Jonesey
It's odd how people's experience differs.
 
I'm running Lex on 2 systems - 1 Win 7 & 1 Win 10 and Lex, for me, is by far the most consistently stable release ever.
 
Hell, I've even got Pentagon to work on both!
2016/01/19 17:00:19
mettelus
Manchester looks like the aux track Solo is resolved.

I am also not seeing any noticeable "speed" improvements on my machine either, so not sure where the common thread lies (also Win7 here).
2016/01/19 17:27:18
Beepster
mettelus
Manchester looks like the aux track Solo is resolved.

I am also not seeing any noticeable "speed" improvements on my machine either, so not sure where the common thread lies (also Win7 here).



Yeah... I saw that in the eZine which is great. But if the performance is similar to Lex i'mma gonna be in a conundrum.
 
Do I go forwards for the Aux Solo (and maybe be stuck with crappy performance) or backwards (and be stuck with crummy Aux routing solo functionality... or no Aux tracks at all).
 
Thing is I KNOW some of this performance stuff is because I switched back to using 96khz but still, it should not be THIS bad. I used 96khz on many projects in the past and it was fine. Now I'm having to REAM my i/o and interface buffers and freeze stuff.
 
Methinks us Win7 users have been left in the dust. They said they were gonna drop us at some point but wouldn't say when (after I asked).
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account