ckd2013 Posted August 2, 2013 Share Posted August 2, 2013 I have got the Midi Environment window open in Logic Pro but it's started to see which track is which when I have to do the patching. The track names at the bottom of each track overlap each other and it looks really messy - see attached Screenshot. Anyone knows how I can fix this? Thanks. Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted August 2, 2013 Share Posted August 2, 2013 It's a bug. The environment has a very strange look in LPX and looks unfinished. Quote Link to comment Share on other sites More sharing options...
ski Posted August 2, 2013 Share Posted August 2, 2013 Yes indeed. The 'ing Game • The font size is now too large, and that's a problem because... • Text displayed in objects (menus) in older projects opened in LX now extend beyond the bounds of the text object boxes (which don't resize to accommodate the larger font). Most of my environments from L9 projects now look like total crap. • The align objects function still works, but the large lettering of object names isn't accounted for, so even after applying that function to clean up the position of objects, names and labels coliide & overlap with adjacent objects . • if you try to move objects by dragging them they either fly off to the right, or they fly down to the bottom of the window out of view. It's a huge annoyance. • It's nearly impossible to see what kinds of events are being displayed in monitor objects because the symbols on the left are so faint as to be unreadable • Floating environment windows now display both horizontal and vertical scrollbars no matter what Quote Link to comment Share on other sites More sharing options...
ibt Posted August 2, 2013 Share Posted August 2, 2013 • Environment objects are renamed to GMDevice by default, even if name spaces are deliberately left blank. Quote Link to comment Share on other sites More sharing options...
ruari Posted August 4, 2013 Share Posted August 4, 2013 The environment has a very strange look in LPX and looks unfinished. +1 Quote Link to comment Share on other sites More sharing options...
ski Posted August 5, 2013 Share Posted August 5, 2013 Attached is a PDF of my environment punch list to date... 10.0.1 Environment Punch List.pdf Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted August 7, 2013 Share Posted August 7, 2013 Is this just an impression or LX was simply not ready yet to hit the market? Quote Link to comment Share on other sites More sharing options...
ruari Posted August 19, 2013 Share Posted August 19, 2013 As I've been slowly moving old templates over to LPX I've got a few more environmental disasters for you to witness. What were they thinking when they signed off on this? Notice the faders in the LPX VPG300 are not stock colours available from the colour palette, I wonder how LPX came up with those hideous hues I've added the L9 versions for comparison, also I apologise for the size of some of these pictures but I do think they need to be appreciated in their full glory. (I didn't create the USS but it's such a mess in LPX I had to show it here) Quote Link to comment Share on other sites More sharing options...
ski Posted August 19, 2013 Share Posted August 19, 2013 "Arrgh my eyes" indeed! Man, that's a mess. And I'm seeing differences in the cabling too in one screenshot. Ouch. Quote Link to comment Share on other sites More sharing options...
ski Posted August 26, 2013 Share Posted August 26, 2013 New Environment Woes (as well as some encore performances) with 10.0.2... • CRASHES: when attempting to set the range of cable switchers. Been like this since 10.0.0. • COLORS: Only the top row of colors is available to color environment objects. Try it: select an object and color it red. Now try and color it dark red. It stays red. Same with the other colors. • COLORS: We don't even have black and white in the color palette any more. So if you color an object, forget about changing your mind by hitting it with white. • OBJECT NAMING: gone are two key behaviors for naming groups of objects: 1) select a group of transformers. Click on one of them with the text tool. Call it "Bob", hit Return. In all previous versions of Logic, this would cause all of the transformers to be named "Bob". Now only the one you specifically renamed is called Bob. 2) select a group of (whatevers) and with the text tool, call it "Bob 1". In all previous versions of Logic, this would cause the (whatevers) to become sequentially numbered, i.e., "Bob 1", "Bob 2", "Bob 3". But not any more. Only the one you named "Bob 1" gets renamed. Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted August 26, 2013 Share Posted August 26, 2013 • CRASHES: when attempting to set the range of cable switchers. Been like this since 10.0.0. The only way I can get a Cable Switcher to crash Logic when setting its range is if its Style parameter is set to "As Text". Same for any other type of fader object. J. Quote Link to comment Share on other sites More sharing options...
maceasy Posted August 16, 2014 Share Posted August 16, 2014 Resurrecting this topic, does anyone know if any of the skins revert the environment object text to the logic 9 one, which was so much better? Quote Link to comment Share on other sites More sharing options...
Neil Parfitt Posted January 15, 2015 Share Posted January 15, 2015 It's an absolute piece of s#!+ gongshow disaster. Imported stuff or opened session don't work properly that were fine from L5 to L9. Visually - awful - fonts - bugs - colours not working - misaligned everything... bad contrast. Whoever signed off on this BS should be fired from the Logic division. I've invested so many hours into workflow enhancements, only for this to be an absolute LX deal breaker. I'm in absolute disbelief. I can't even quickly trace problems that it's caused as it no longer highlights *all* attached cables to the selected module. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted January 17, 2015 Share Posted January 17, 2015 Anyone posted something about it on the Logic Feedback page? Quote Link to comment Share on other sites More sharing options...
Neil Parfitt Posted January 17, 2015 Share Posted January 17, 2015 CONSTANTLY. And please… everyone do the same. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted January 18, 2015 Share Posted January 18, 2015 I did... Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted January 22, 2015 Share Posted January 22, 2015 • OBJECT NAMING: gone are two key behaviors for naming groups of objects: 1) select a group of transformers. Click on one of them with the text tool. Call it "Bob", hit Return. In all previous versions of Logic, this would cause all of the transformers to be named "Bob". Now only the one you specifically renamed is called Bob. 2) select a group of (whatevers) and with the text tool, call it "Bob 1". In all previous versions of Logic, this would cause the (whatevers) to become sequentially numbered, i.e., "Bob 1", "Bob 2", "Bob 3". But not any more. Only the one you named "Bob 1" gets renamed. This is working in 10.1. Also the symbols that identify the type of data in monitor objects is back to having a lighter color: However, there's some new little visual glitches when dragging objects: J. Quote Link to comment Share on other sites More sharing options...
fastfourier Posted February 1, 2015 Share Posted February 1, 2015 I discovered another little annoying one in 10.1.0. Buttons in the Environment don't work very well anymore. The first click on a button will only work sometimes. That's the most annoying part. If you keep clicking, you have to do it really slow - about 2 per second is the fastest - for it to work, that is if they work at all. Holding down the mouse button and moving the pointer over the button's surface will always register a click though. Quote Link to comment Share on other sites More sharing options...
ibt Posted February 1, 2015 Share Posted February 1, 2015 If you want an environment object to have a blank name space, and so you delete it's name e.g. '(Fader)', the behaviour since LP X is to rename the object as "GM Device". Workaround : enter a blank space in place of the objects name. Quote Link to comment Share on other sites More sharing options...
fastfourier Posted February 1, 2015 Share Posted February 1, 2015 Jesus. Who the hell is testing this stuff?? Quote Link to comment Share on other sites More sharing options...
ibt Posted February 1, 2015 Share Posted February 1, 2015 ...and Channel strip + cmd X + cmd V = Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted February 1, 2015 Share Posted February 1, 2015 I discovered another little annoying one in 10.1.0. Buttons in the Environment don't work very well anymore. The first click on a button will only work sometimes. That's the most annoying part. If you keep clicking, you have to do it really slow - about 2 per second is the fastest - for it to work, that is if they work at all. Holding down the mouse button and moving the pointer over the button's surface will always register a click though. Yeah, that one was already reported over here: viewtopic.php?f=42&t=113788 J. Quote Link to comment Share on other sites More sharing options...
ibt Posted February 1, 2015 Share Posted February 1, 2015 New in 10.1 : Ninja monitors Quote Link to comment Share on other sites More sharing options...
ibt Posted February 16, 2015 Share Posted February 16, 2015 Something else that is (newly?) broken in LP X 10.1 - being able to view/edit the contents of transformers which are inside macros, without having to unpack the macro. Incorrect behaviour, 10.1: FeedBass.cst.zip9.1.8[/attachment] Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted February 16, 2015 Share Posted February 16, 2015 This is already documented here: LPX: Double click transformer inside macro bug Quote Link to comment Share on other sites More sharing options...
ibt Posted February 16, 2015 Share Posted February 16, 2015 This is already documented here: LPX: Double click transformer inside macro bug Ah... August 2013. One and a half years ago. Thanks Eric. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted February 20, 2015 Share Posted February 20, 2015 Anyone cared to report those on the Logic Pro feedback website? Quote Link to comment Share on other sites More sharing options...
jaffasplaffa Posted April 10, 2015 Share Posted April 10, 2015 Seems like there is some naming problems in Logic X. I also noticed that if you try to rename several regions you see "X regions selected" and if you dobbelt click where you change the name and push enter it should be the same name as before you edit name, but now the regions are named "X regions selected". I have also made alot of things in environment and they all looks like, well like nothing nice, after opnening it in Logic X. Seems like everything has been resized, and not for smaller versions but bigger version... hm.... Quote Link to comment Share on other sites More sharing options...
sambosun Posted July 20, 2015 Share Posted July 20, 2015 Let's hope the environment will be cured with the coming updates. Fingers crossed. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted July 25, 2015 Share Posted July 25, 2015 Let's hope the environment will be cured with the coming updates. Fingers crossed. +1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.