Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/02 19:02:53
(permalink)
Beepster TH2 Producer won't load in X1? hmm... And it sounds like maybe you bounce back and forth between tracking and editing so I guess my suggestion isn't ideal. It's a lot easier to edit with X2s drag zoom ruler thingy too so that's a drag. Hope you figure out a happy workflow. Cheers. Yes... I believe they are locked to "X2 only" ...and yes again. I do frequently edit while I'm tracking, tho I haven't gotten used to that zoom control well yet... I've got a new workflow for sure... It includes steps I would label as 1) scream 2) throw something 3) curse 4) blame the world for my predicament! ;-) Keni
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/02 19:09:10
(permalink)
stevec As someone who's prefered Lanes over Layers almost from day one in X2, I am completely on board with Keni's desire for more control over lane sizing. I can work with it as-is, but I'd really like to see the minimum and maximum sizes expanded so that more lanes can be viewed at one time and so that a single lane be expanded to fit the TV. Oh... and please move both Track and Automation Lane buttons on track strips so they're accessible from a minimized track. Can't forget that one. Hi Steve... Tho I will not like it, I will get used to Lanes and working with them... Tho I will scream forever (see previous post/reply)... The zoom's smallest level I understand it might have been to maintain keeping the buttons displayed... why the limitation to zooming Large? Maybe a limitation set by the way Lanes are defined relative to tracks? I don't really have any idea tho I know these two limitations make something I don't like into something extremely frustrating... I was really hoping and expecting them to address this issue for X2a even tho I did not expect them to address any of my other issues with Lanes. These two make the program feel broken to me... I use the zoom tool to lasso an area I want to make my whole screen and instead of seeing such I get a collection of tracks I was not expecting... It totally disorients my time relationships and I forget some of where I am.... Keni
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/02 19:11:21
(permalink)
stevec Max/min height is definitely a problem. Don't understand why it was made that way. Me neither. I like that I can resize one lane and they all change, but not each every and time. I think we need a modifier key for that and independent lane sizing otherwise. Absolutely! Tho I think this would rate as an improvement as opposed to a fix (for me)...
|
stevec
Max Output Level: 0 dBFS
- Total Posts : 11546
- Joined: 2003/11/04 15:05:54
- Location: Parkesburg, PA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/02 21:13:54
(permalink)
Absolutely! Tho I think this would rate as an improvement as opposed to a fix (for me)... Ditto, Keni. The "T0" issue seems to be fixed in 2a, and aside from some random copy/paste weirdness I'm really hoping for lane enhancements more than anything. And though it doesn't seem to get mentioned often, I'd like to see the same size enhancement for automation lanes too for better flexibility. Hehehehe... I said size enhancement.
SteveC https://soundcloud.com/steve-cocchi http://www.soundclick.com/bands/pagemusic.cfm?bandID=39163 SONAR Platinum x64, Intel Q9300 (2.5Ghz), Asus P5N-D, Win7 x64 SP1, 8GB RAM, 1TB internal + ESATA + USB Backup HDDs, ATI Radeon HD5450 1GB RAM + dual ViewSonic VA2431wm Monitors; Focusrite 18i6 (ASIO); Komplete 9, Melodyne Studio 4, Ozone 7 Advanced, Rapture Pro, GPO5, Valhalla Plate, MJUC comp, MDynamic EQ, lots of other freebie VST plugins, synths and Kontakt libraries
|
STinGA
Max Output Level: -79 dBFS
- Total Posts : 552
- Joined: 2005/11/06 14:51:38
- Location: Andover, UK
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 03:46:42
(permalink)
Keni STinGA Hey Keni, I am not getting the problem of empty lanes when loop recording, I was pre X2a but since, I've been loop recording plenty, and not one empty lane. However, once I've comped and bounced my midi to a single track the lanes are left empty, I'm sure they could be removed in the process. That said its a 2 second job to remove them after. Have you been opening the track's lanes prior to recording? If I do this I don't get the extra tracks, but as the track icon does not change color when the track is empty, I find it hard to know that Lanes are "exposed"... I have to watch the area that displays the db scale as that disappears when lanes are open (they show on each lane)... In X1, when it created the extra lanes, they were also in solo mode tho I don't think they forced actual solo to engage... Keni Ill double check Keni, but as I recall, no, the lanes have always been closed when recording. I have to do some more recording today, so I'll check again then.
Win 8 x64 Sonar X3b Producer X64 Edirol UA-101 BCF2000 A-Pro 500 Roland TD-6KV
|
SteveStrummerUK
Max Output Level: 0 dBFS
- Total Posts : 31112
- Joined: 2006/10/28 10:53:48
- Location: Worcester, England.
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 04:19:34
(permalink)
I much preferred Layers, and for most of the reasons others have mentioned above. But for the way I work, the big deal-breaker for me is the lack of a 'Rebuild Layers' type function. Here's a copy of a post I made in another thread, detailing my reasons: For me, the most important factor is the ' why' I use Lanes or Layers, as opposed to using separate tracks. And sadly, for the way I work, the single most important feature for me is no longer in Lanes, but I used it a lot in Layers, and that is the Rebuild function. Let me explain why. Lets assume I'm recording a 32 bar guitar solo. Unless it's a passage I know off by heart, there's a good chance that it's not going to get laid down successfully in one take. Therefore I'm going to have to do some comping at some stage. My approach may be dissimilar to how some of you might accomplish this. I know some like to record the whole solo a number of times and then use comping to piece together the best parts, and I know some like to punch record to correct the parts they might have misplayed. My modus operandi is slightly different. If I know I'm going to struggle to play the whole passage, I'll break it up into comfortable phrases and record them separately. Comping then allows me to trim and edit each clip as I assemble the jigsaw that is the complete solo. The most convenient method of doing this for me is to use Lanes or Layers (especially as in most of my templates, I have my tracks already set up with pre-assigned Pro Channel and VST effects, as well as panning, levels etc). In the interest of keeping the project 'tidy' and easier to manage, the Rebuild feature is ideal for my purposes. As I delete bits and pieces off the individual clips I've recorded, rebuilding the track does this for me. Here's an example of how the same solo looks in X2 Lanes and X1 Layers after comping. In X2 Lanes: Even when I now trim off the unwanted muted parts I'm still stuck with the same amount of Lanes: Contrast this with the same project in X1. Even before I trim off the muted parts, Rebuild gives me a much tidier view of the track: And once I do trim them off, I end up with this:
|
STinGA
Max Output Level: -79 dBFS
- Total Posts : 552
- Joined: 2005/11/06 14:51:38
- Location: Andover, UK
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 05:10:02
(permalink)
Hey Keni, Sorry to report mate but lanes working as advertised with loop recording. I've recorded about 20 takes this morning with lanes open and closed and there are still no empty lanes. For me this problem completely disappeared with the X2a update. Sorry I cant be more helpful.
Win 8 x64 Sonar X3b Producer X64 Edirol UA-101 BCF2000 A-Pro 500 Roland TD-6KV
|
joegab
Max Output Level: -82 dBFS
- Total Posts : 437
- Joined: 2003/11/08 18:42:43
- Location: Italy
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 06:33:00
(permalink)
I have a particular strange problem with lanes: sometimes I get 2 lanes named T1, one empty, and one with my recordings. Well, if I try to delete the T1 empty lane, the one with clips inside will be deleted.... grrr. Workaround found moving clips to another lane ..... Not a good deal... Giorgio
|
Funkybot
Max Output Level: -75 dBFS
- Total Posts : 796
- Joined: 2003/11/06 16:32:13
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 08:21:35
(permalink)
SteveStrummerUK I much preferred Layers, and for most of the reasons others have mentioned above. But for the way I work, the big deal-breaker for me is the lack of a 'Rebuild Layers' type function. Here's a copy of a post I made in another thread, detailing my reasons: For me, the most important factor is the 'why' I use Lanes or Layers, as opposed to using separate tracks. And sadly, for the way I work, the single most important feature for me is no longer in Lanes, but I used it a lot in Layers, and that is the Rebuild function. Let me explain why. Lets assume I'm recording a 32 bar guitar solo. Unless it's a passage I know off by heart, there's a good chance that it's not going to get laid down successfully in one take. Therefore I'm going to have to do some comping at some stage. My approach may be dissimilar to how some of you might accomplish this. I know some like to record the whole solo a number of times and then use comping to piece together the best parts, and I know some like to punch record to correct the parts they might have misplayed. My modus operandi is slightly different. If I know I'm going to struggle to play the whole passage, I'll break it up into comfortable phrases and record them separately. Comping then allows me to trim and edit each clip as I assemble the jigsaw that is the complete solo. The most convenient method of doing this for me is to use Lanes or Layers (especially as in most of my templates, I have my tracks already set up with pre-assigned Pro Channel and VST effects, as well as panning, levels etc). In the interest of keeping the project 'tidy' and easier to manage, the Rebuild feature is ideal for my purposes. As I delete bits and pieces off the individual clips I've recorded, rebuilding the track does this for me. Here's an example of how the same solo looks in X2 Lanes and X1 Layers after comping. In X2 Lanes: Even when I now trim off the unwanted muted parts I'm still stuck with the same amount of Lanes: Contrast this with the same project in X1. Even before I trim off the muted parts, Rebuild gives me a much tidier view of the track: And once I do trim them off, I end up with this: Looking at that, couldn't you accomplish the same thing working on a single track? I mean, it's not like you're recording overlapping versions of the solo, and trying to pull out the best parts (which is probably more of a common workflow), instead, you're breaking it up piece by piece. A single track with crossfading and slip editing might prove a more effective editing approach. Also, once you rebuild in X1, you end up with takes seemingly randomly scattered across three layers not knowing which belongs to which take. While it's taking up less screen real estate, the placement looks arbitrary. I wonder what that would look like if you had recorded the full solo 7 times and pulled out the best sections of each, as this is where take lanes would offer a huge advantage IMO. If you wanted, you could also always just record to different tracks and edit manually using an almost identical approach to how you worked with layers, and have more control over where things go and how they look, so that's still an option for you in X2.
Intel i7 4790k, ASUS Z97-A mobo, 16GB Kingston DDR3 RAM, Windows 10 x64, UAD2 Duo, RME Fireface 800, Sonar X1/X2 Producer
|
fooman
Max Output Level: -63 dBFS
- Total Posts : 1382
- Joined: 2006/06/26 14:47:44
- Location: Ontario, Canada
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 09:19:46
(permalink)
I agree with Steve. Screen real-estate is kinda important. Having overlapped parts all along 10 lanes/tracks is wonky.
It seems we should have went the other way, start with take lanes and moved to layers haha
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 10:28:32
(permalink)
stevec Absolutely! Tho I think this would rate as an improvement as opposed to a fix (for me)... Ditto, Keni. The "T0" issue seems to be fixed in 2a, and aside from some random copy/paste weirdness I'm really hoping for lane enhancements more than anything. And though it doesn't seem to get mentioned often, I'd like to see the same size enhancement for automation lanes too for better flexibility. Hehehehe... I said size enhancement. Absolutely... Tho I don't use the automation lanes, they should be able to be zoomed as large small as is possible on the screen... Is the size enhancement a plugin? ;-) Keni
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 10:36:06
(permalink)
SteveStrummerUK I much preferred Layers, and for most of the reasons others have mentioned above. But for the way I work, the big deal-breaker for me is the lack of a 'Rebuild Layers' type function. Here's a copy of a post I made in another thread, detailing my reasons: For me, the most important factor is the 'why' I use Lanes or Layers, as opposed to using separate tracks. And sadly, for the way I work, the single most important feature for me is no longer in Lanes, but I used it a lot in Layers, and that is the Rebuild function. Let me explain why. Lets assume I'm recording a 32 bar guitar solo. Unless it's a passage I know off by heart, there's a good chance that it's not going to get laid down successfully in one take. Therefore I'm going to have to do some comping at some stage. My approach may be dissimilar to how some of you might accomplish this. I know some like to record the whole solo a number of times and then use comping to piece together the best parts, and I know some like to punch record to correct the parts they might have misplayed. My modus operandi is slightly different. If I know I'm going to struggle to play the whole passage, I'll break it up into comfortable phrases and record them separately. Comping then allows me to trim and edit each clip as I assemble the jigsaw that is the complete solo. The most convenient method of doing this for me is to use Lanes or Layers (especially as in most of my templates, I have my tracks already set up with pre-assigned Pro Channel and VST effects, as well as panning, levels etc). In the interest of keeping the project 'tidy' and easier to manage, the Rebuild feature is ideal for my purposes. As I delete bits and pieces off the individual clips I've recorded, rebuilding the track does this for me. Here's an example of how the same solo looks in X2 Lanes and X1 Layers after comping. In X2 Lanes: Even when I now trim off the unwanted muted parts I'm still stuck with the same amount of Lanes: Contrast this with the same project in X1. Even before I trim off the muted parts, Rebuild gives me a much tidier view of the track: And once I do trim them off, I end up with this: Hi Steve... I too work much as you do... Some little differences but I often use looping to allow me to explore possibilities and then comp together the best portions of these ideas.... Lanes make this a lot more of a drudgery than Layers did in ever way... I must point out tho, that I don't have to end up with all those Lanes you show. Once it's been trimmed down I would move them manually to a single Lane.... So in the end I have a single Lane, but it must be done manually... (No Rebuild command) I am so uncomfortable with the way Lanes uses screen space it's beyond words at the moment... I think I'm losing my internet this morning so I'm a bit on edge... Keni
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 10:37:29
(permalink)
STinGA Hey Keni, Sorry to report mate but lanes working as advertised with loop recording. I've recorded about 20 takes this morning with lanes open and closed and there are still no empty lanes. For me this problem completely disappeared with the X2a update. Sorry I cant be more helpful. Thanks for trying... I'm glad it's working for you at least... Keni
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 10:39:53
(permalink)
joegab I have a particular strange problem with lanes: sometimes I get 2 lanes named T1, one empty, and one with my recordings. Well, if I try to delete the T1 empty lane, the one with clips inside will be deleted.... grrr. Workaround found moving clips to another lane ..... Not a good deal... Giorgio Hi Giorgio... <ouch>... That's even worse than mine... I get the blank lanes but I can delete them... Keni
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 10:45:27
(permalink)
fooman I agree with Steve. Screen real-estate is kinda important. Having overlapped parts all along 10 lanes/tracks is wonky. It seems we should have went the other way, start with take lanes and moved to layers haha Hi fooman... Yeah, I know how you feel, except that I feel we already had a good thing and in the spirit of solving some of it's problematic details, we got it replaced with a new method that for many of us is not as good.... The screen is our biggest connection to the work... Even more so with touchscreen... so while things need to be big enuf for clumsy finger touches, some of us need more detailed work than my fingers will allow for these on-screen edits... An example to me is that when I use touchscreen and try to do something that requires microscoping, I must zoom way more than with the more pinpoint touch of the mouse... Keni
|
fooman
Max Output Level: -63 dBFS
- Total Posts : 1382
- Joined: 2006/06/26 14:47:44
- Location: Ontario, Canada
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 11:05:25
(permalink)
I'm not sure how you took my comments, but to be clear: I agree with you ;)
|
VariousArtist
Max Output Level: -63 dBFS
- Total Posts : 1397
- Joined: 2003/11/07 15:03:09
- Location: London, UK & California, USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 12:34:22
(permalink)
joegab I have a particular strange problem with lanes: sometimes I get 2 lanes named T1, one empty, and one with my recordings. Well, if I try to delete the T1 empty lane, the one with clips inside will be deleted.... grrr. Workaround found moving clips to another lane ..... Not a good deal... Giorgio Hello Giorgio This is EXACTLY the problem I described in another thread here: http://forum.cakewalk.com/tm.aspx?m=2745484 I uploaded a video that demonstrates this exact problem: http://www.youtube.com/watch?v=KwsfmG2On6k I created a bug report on the Cakewalk Support site: CWBRN-14119 Please feel free to reference that bug in any communication to Cakewalk.
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 13:52:36
(permalink)
fooman I'm not sure how you took my comments, but to be clear: I agree with you ;) Hi fooman... I thought that was the case. Thanks for verifying it tho... I've been searching for a DAW that allows layered audio on a track and accesses it in some manner other than Lanes... This was actually a big reason that kept me away from ProT as I disliked the Lanes experience. Cakewalk offered an alternative which worked well for me. Now Cakewalk has followed the crowd and dropped their' unique operation... It's a very hard decision, but I'm being pushed away from Sonar more and more with time... I don't relish the idea of learning all the ins and outs of a new DAW after 20 some odd years with Cakewalk, but many of the decisions they've been making in the last few years have not been to my liking and I've managed to work with them to have the many wonderful features that I love with Sonar... but it's getting increasingly difficult and I'm "bleary-eyed" from trying to find a way to live with it. I will always manage to make music regardless of which software I use or even going back to tape! ;-) But this is a big issue for me.... How the DAW usues the screen. this is the "language" that the computer and I have in common and when the language barrier becomes too great, communication is interrupted... <sigh>... I don't say this as a threat as there's no one to threaten. Cakewalk would lose my sales along with many of my clients and students as I would probably draw them with me to whatever new system I decide works well for me... Probably wouldn't amount to a row of beans for Cakewalk's sales... and I truly do not wish to do this.... It's a decision I will make if/when the time actually arrives (hopefully not!) It took me almost a year before I recomended X1 to any of my clients... and even then it was with reserve... I've loved Cakewalk and their' products ever since I started with Cakewalk For Windows 1.0 running under Windows 3.1. I feel as if I'm "family" with so many years involvement... Here's hoping The Bakers rise to the occassion and find some solution(s) that will make this work for "both camps"... I am currently very sad, but continuing to work on music until they pry the tools out of my dead hands! ;-) Keni
|
Swiller
Max Output Level: -88 dBFS
- Total Posts : 110
- Joined: 2012/04/25 16:19:21
- Location: West Wales UK
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 15:01:56
(permalink)
Lanes not too important for me, but someone loyal to cakewalk for 20 years at least deserves some yes or no answers from the bakers as to whether this will be addressed in x2b, at least via a PM. Whilst not critical to my workflow, I do understand the frustration with the lanes thing and seems a logical step forward to address these issues as well as prioritising them for the more loyal long term customers. Development should always have an element of democracy to it , especially involving long term loyal customers (of which i am neither). I dont see much of it on here apar from bug reporting, which is not the same thing as contributing to a development strategy. Good luck keni, i hope you get a positive answer soon. Dont take "we will see what we can do" as an answer, thats much worse than a "no" in my book and probably fairer to everyone involved. At least then you can make a definitive choice. I do hope you get what you are looking for. Cheers. Swiller.
I7 3700k 3.5-3.9ghz, 16gb 1600 ddr3, 240gb ssd sata3, 2tb sata 3 hd, 2gb gt640 nvidia graphics, win 7 he, sonar x2 prod, a500pro, jd800,the magnificent juno 106, virus c, basstation rack, mpx1, xv5050, maschine mikro 1.8 with massive, kontakt,reaktor, mc505 groovebox, tlaudio 5021, 01x, Scarlett 8i6, prs ce24, squire classic vibe 60s.... tele,strat,jazz bass, blues jr 3 navy vintage 30 edition, orange ad5, line 6 ld15 bass amp, akg condenser mic, krk rokit 5, ns10s. Lots of thatchers gold.
|
VariousArtist
Max Output Level: -63 dBFS
- Total Posts : 1397
- Joined: 2003/11/07 15:03:09
- Location: London, UK & California, USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 15:27:13
(permalink)
SteveStrummerUK :
I much preferred Layers, and for most of the reasons others have mentioned above. But for the way I work, the big deal-breaker for me is the lack of a 'Rebuild Layers' type function. Here's a copy of a post I made in another thread, detailing my reasons: For me, the most important factor is the 'why' I use Lanes or Layers, as opposed to using separate tracks. And sadly, for the way I work, the single most important feature for me is no longer in Lanes, but I used it a lot in Layers, and that is the Rebuild function. Let me explain why. Lets assume I'm recording a 32 bar guitar solo. Unless it's a passage I know off by heart, there's a good chance that it's not going to get laid down successfully in one take. Therefore I'm going to have to do some comping at some stage. My approach may be dissimilar to how some of you might accomplish this. I know some like to record the whole solo a number of times and then use comping to piece together the best parts, and I know some like to punch record to correct the parts they might have misplayed. My modus operandi is slightly different. If I know I'm going to struggle to play the whole passage, I'll break it up into comfortable phrases and record them separately. Comping then allows me to trim and edit each clip as I assemble the jigsaw that is the complete solo. The most convenient method of doing this for me is to use Lanes or Layers (especially as in most of my templates, I have my tracks already set up with pre-assigned Pro Channel and VST effects, as well as panning, levels etc). In the interest of keeping the project 'tidy' and easier to manage, the Rebuild feature is ideal for my purposes. As I delete bits and pieces off the individual clips I've recorded, rebuilding the track does this for me. Steve This is brilliantly explained, along with images that make your point very well**. This clearly shows the workflow difference and impact, which pretty much makes one of the cases for layers and why it was so important to many of us. I understand that not everyone is impacted by the loss of layers, but for me the analogy would be getting touch screen functionality at the expense of mouse/keyboard access. Yes, the impact is that much for some of us... **note: I didn't copy your images in my response to avoid too much duplication of them, but they can be seen back here: http://forum.cakewalk.com/fb.ashx?m=2749131
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 17:17:06
(permalink)
Thanks Swiller... I don't expect to see/hear from The Bakers on this issue.... I can only hope that it's important enuf to be some kind of priority... Regardless of how long I've been with them they have to do what they think best for the company... even at the expense of long-time users... sadly... But somehow I can't imagine so many people complaining about the small solo/mute buttons in previous releases to warrant discarding the entire system to resolve... I'm here in the forum every day and tho I do remember hjearing some complaints about that, the more common complaints were simply to fix the bugs... Features not working as planned/advertised... Thanks Peter too... You're right that Steve's posting was very complete in quickly showing the many of the issues... Thanks Steve... Very eloquent and visually self-explanatory post! You guys manage to get this things said and shown so much better than I... I get too emotionally wrapped up! ;-) Keni
|
joegab
Max Output Level: -82 dBFS
- Total Posts : 437
- Joined: 2003/11/08 18:42:43
- Location: Italy
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/03 17:57:43
(permalink)
Uhm.... I really hope that Cakewalk will fix the various lane issues .... this is an important tool for us!!! Let's keep fing crossed ... It would be a good idea if someone at Cakewalk could give us some answer about that. Bye bye to everyone. Giorgio
|
Funkybot
Max Output Level: -75 dBFS
- Total Posts : 796
- Joined: 2003/11/06 16:32:13
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/04 11:37:34
(permalink)
VariousArtist SteveStrummerUK : I much preferred Layers, and for most of the reasons others have mentioned above. But for the way I work, the big deal-breaker for me is the lack of a 'Rebuild Layers' type function. Here's a copy of a post I made in another thread, detailing my reasons: For me, the most important factor is the 'why' I use Lanes or Layers, as opposed to using separate tracks. And sadly, for the way I work, the single most important feature for me is no longer in Lanes, but I used it a lot in Layers, and that is the Rebuild function. Let me explain why. Lets assume I'm recording a 32 bar guitar solo. Unless it's a passage I know off by heart, there's a good chance that it's not going to get laid down successfully in one take. Therefore I'm going to have to do some comping at some stage. My approach may be dissimilar to how some of you might accomplish this. I know some like to record the whole solo a number of times and then use comping to piece together the best parts, and I know some like to punch record to correct the parts they might have misplayed. My modus operandi is slightly different. If I know I'm going to struggle to play the whole passage, I'll break it up into comfortable phrases and record them separately. Comping then allows me to trim and edit each clip as I assemble the jigsaw that is the complete solo. The most convenient method of doing this for me is to use Lanes or Layers (especially as in most of my templates, I have my tracks already set up with pre-assigned Pro Channel and VST effects, as well as panning, levels etc). In the interest of keeping the project 'tidy' and easier to manage, the Rebuild feature is ideal for my purposes. As I delete bits and pieces off the individual clips I've recorded, rebuilding the track does this for me. Steve This is brilliantly explained, along with images that make your point very well**. This clearly shows the workflow difference and impact, which pretty much makes one of the cases for layers and why it was so important to many of us. I understand that not everyone is impacted by the loss of layers, but for me the analogy would be getting touch screen functionality at the expense of mouse/keyboard access. Yes, the impact is that much for some of us... **note: I didn't copy your images in my response to avoid too much duplication of them, but they can be seen back here: http://forum.cakewalk.com/fb.ashx?m=2749131 Sorry to be the Debbie Downer here...but I disagree. The above example, doesn't illustrate why lanes don't work as well as layers IMO, it illustrates why knowing when to "Auto-Punch" (or punch in) is so important. Look at the takes, there's no overlapping parts. Steve's recording one section at a time until right, then building a comp that way. That's exactly how auto-punching the different parts of the solo would work, meanwhile it would lead to the same result on a single track, without having to do additonal slip editing or muting. He's essentially auto-punching the hardest possible way. Even using his X1 example above (the one with Layers), he would have got the same result on a single track without having to mute/edit the clip start end times by auto-punching until nailing the take, then moving to the next part of the solo. Lanes/Layers aren't best suited as an auto-punch replacement, they're best used for recording the same passage, and identifying the best take. Example, the best of the singer singing "she loves you, yeah, yeah, yeah." The singer would sings it five times at the start of the song, and you sift through the fave takes to identify the best of those passages. If you were going to have the singer do it one word at a time, then move on to the next word, that's where you'd want to punch in. I'm not trying to discredit the idea that there's no room for improvement in lanes, but I just want Steve and others who might be using lanes for something like the above workflow, that auto-punch is the right tool for that particular job. If you're recording consecutive sections of a song: use auto punch. If you're recording overlapping sections of a song: use layers.
post edited by Funkybot - 2013/01/04 11:53:01
Intel i7 4790k, ASUS Z97-A mobo, 16GB Kingston DDR3 RAM, Windows 10 x64, UAD2 Duo, RME Fireface 800, Sonar X1/X2 Producer
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/04 12:23:41
(permalink)
We all/each have our reasons and methods to our work... I for one never use auto punch anymore as I've found more ease and accuracy using separate takes and editing/compositing afterwards... Of course we can find work arounds and other methods to accomplish our work but Cakewalk/Sonar has always made one of it's strong points that it allowed us each to work how best suited us... So I don't try to tell people how they "should" work... I only look to the programmers to supply us with the tools we each need to suite our work methods.... Not only a single work method... ...and Cakewalk has been wonderful about that until X1.... Now many methods have been trashed and replaced with things that (for some) make work easier and for others, not so... Keni
|
SteveStrummerUK
Max Output Level: 0 dBFS
- Total Posts : 31112
- Joined: 2006/10/28 10:53:48
- Location: Worcester, England.
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/04 13:12:23
(permalink)
Funkybot VariousArtist SteveStrummerUK : I much preferred Layers, and for most of the reasons others have mentioned above. But for the way I work, the big deal-breaker for me is the lack of a 'Rebuild Layers' type function. Here's a copy of a post I made in another thread, detailing my reasons: For me, the most important factor is the 'why' I use Lanes or Layers, as opposed to using separate tracks. And sadly, for the way I work, the single most important feature for me is no longer in Lanes, but I used it a lot in Layers, and that is the Rebuild function. Let me explain why. Lets assume I'm recording a 32 bar guitar solo. Unless it's a passage I know off by heart, there's a good chance that it's not going to get laid down successfully in one take. Therefore I'm going to have to do some comping at some stage. My approach may be dissimilar to how some of you might accomplish this. I know some like to record the whole solo a number of times and then use comping to piece together the best parts, and I know some like to punch record to correct the parts they might have misplayed. My modus operandi is slightly different. If I know I'm going to struggle to play the whole passage, I'll break it up into comfortable phrases and record them separately. Comping then allows me to trim and edit each clip as I assemble the jigsaw that is the complete solo. The most convenient method of doing this for me is to use Lanes or Layers (especially as in most of my templates, I have my tracks already set up with pre-assigned Pro Channel and VST effects, as well as panning, levels etc). In the interest of keeping the project 'tidy' and easier to manage, the Rebuild feature is ideal for my purposes. As I delete bits and pieces off the individual clips I've recorded, rebuilding the track does this for me. Steve This is brilliantly explained, along with images that make your point very well**. This clearly shows the workflow difference and impact, which pretty much makes one of the cases for layers and why it was so important to many of us. I understand that not everyone is impacted by the loss of layers, but for me the analogy would be getting touch screen functionality at the expense of mouse/keyboard access. Yes, the impact is that much for some of us... **note: I didn't copy your images in my response to avoid too much duplication of them, but they can be seen back here: http://forum.cakewalk.com/fb.ashx?m=2749131 Sorry to be the Debbie Downer here...but I disagree. The above example, doesn't illustrate why lanes don't work as well as layers IMO, it illustrates why knowing when to "Auto-Punch" (or punch in) is so important. Look at the takes, there's no overlapping parts. Steve's recording one section at a time until right, then building a comp that way. That's exactly how auto-punching the different parts of the solo would work, meanwhile it would lead to the same result on a single track, without having to do additonal slip editing or muting. He's essentially auto-punching the hardest possible way. Even using his X1 example above (the one with Layers), he would have got the same result on a single track without having to mute/edit the clip start end times by auto-punching until nailing the take, then moving to the next part of the solo. Lanes/Layers aren't best suited as an auto-punch replacement, they're best used for recording the same passage, and identifying the best take. Example, the best of the singer singing "she loves you, yeah, yeah, yeah." The singer would sings it five times at the start of the song, and you sift through the fave takes to identify the best of those passages. If you were going to have the singer do it one word at a time, then move on to the next word, that's where you'd want to punch in. I'm not trying to discredit the idea that there's no room for improvement in lanes, but I just want Steve and others who might be using lanes for something like the above workflow, that auto-punch is the right tool for that particular job. If you're recording consecutive sections of a song: use auto punch. If you're recording overlapping sections of a song: use layers. Hi Christopher I fully understand what you are saying about using auto-punch, but with all due respect what you say about the clips in my example not overlapping isn't true. This image clearly shows eight clips which all overlap. What I've done at this stage is to split them all into the parts I want to use and then muted the parts I don't want (that contain, e.g. unwanted string noise and/or amp hum): In these circumstances, I always check there are no pops or clicks where I've split the clips before deleting off the extranneous parts. In X2, as per this image, I'm now stuck with these eight clips in eight different lanes. My point was that, with this identical project in X1, all I have to do is hit Rebuild Layers and I'm done. Apologies if I didn't explain it very well (Edit) And I fully appreciate that there are many ways to skin this particular cat, all I was trying to say is that I could do it ' my' way in X1, but I've lost that ability in X2.
post edited by SteveStrummerUK - 2013/01/04 13:19:42
|
Funkybot
Max Output Level: -75 dBFS
- Total Posts : 796
- Joined: 2003/11/06 16:32:13
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/04 13:31:29
(permalink)
Keni We all/each have our reasons and methods to our work... I for one never use auto punch anymore as I've found more ease and accuracy using separate takes and editing/compositing afterwards... Of course we can find work arounds and other methods to accomplish our work but Cakewalk/Sonar has always made one of it's strong points that it allowed us each to work how best suited us... So I don't try to tell people how they "should" work... I only look to the programmers to supply us with the tools we each need to suite our work methods.... Not only a single work method... ...and Cakewalk has been wonderful about that until X1.... Now many methods have been trashed and replaced with things that (for some) make work easier and for others, not so... Keni I hear what you're saying, but ideally, you'd be looking at these features as tools, and you want to be using the best tool for the job. Can you use layers/lanes for recording consecutive parts? Sure...but they're not going to work as well for that because auto-punch is the right tool for that job. You can choose to ignore that if you'd like, but by doing so you'd only be making things harder on yourself. As I point out above, even the old layers approach doesn't work as efficiently as auto-punch for that task. Why make things hard on yourself when there's a better way? I'd suggest you stop fighting Sonar and try adjusting to it. And if you want to make things hard on yourself, why all the threads/posts about how awful lanes are? It took some getting used to for most, but right now, it seems like a lot of people (myself included) are happy with the new approach and prefer it. It could be improved, but it's a nice step forward.
Intel i7 4790k, ASUS Z97-A mobo, 16GB Kingston DDR3 RAM, Windows 10 x64, UAD2 Duo, RME Fireface 800, Sonar X1/X2 Producer
|
VariousArtist
Max Output Level: -63 dBFS
- Total Posts : 1397
- Joined: 2003/11/07 15:03:09
- Location: London, UK & California, USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/04 13:51:17
(permalink)
adjusting Funkybot Keni We all/each have our reasons and methods to our work... I for one never use auto punch anymore as I've found more ease and accuracy using separate takes and editing/compositing afterwards... Of course we can find work arounds and other methods to accomplish our work but Cakewalk/Sonar has always made one of it's strong points that it allowed us each to work how best suited us... So I don't try to tell people how they "should" work... I only look to the programmers to supply us with the tools we each need to suite our work methods.... Not only a single work method... ...and Cakewalk has been wonderful about that until X1.... Now many methods have been trashed and replaced with things that (for some) make work easier and for others, not so... Keni I hear what you're saying, but ideally, you'd be looking at these features as tools, and you want to be using the best tool for the job. Can you use layers/lanes for recording consecutive parts? Sure...but they're not going to work as well for that because auto-punch is the right tool for that job. You can choose to ignore that if you'd like, but by doing so you'd only be making things harder on yourself. As I point out above, even the old layers approach doesn't work as efficiently as auto-punch for that task. Why make things hard on yourself when there's a better way? I'd suggest you stop fighting Sonar and try adjusting to it. And if you want to make things hard on yourself, why all the threads/posts about how awful lanes are? It took some getting used to for most, but right now, it seems like a lot of people (myself included) are happy with the new approach and prefer it. It could be improved, but it's a nice step forward. I respectfully disagree. I'll repeat my analogy above. Touch screens are a step forward too -- but imagine if you upgraded to find out that it no longer supported a mouse. Imagine further that people like to tell you that you don't need a mouse because you can do everything with a touch screen and that you can get used to it. Which you probably could, and most of the advice would be well-meaning, as is yours. But at the end of the day I would argue why not continue to support the mouse and have touch screen support, rather than either/or? Analogy over now; what I would like to see is the ability to view layers the way we used to when the track is collapsed with the option to expand them into layers. This is similar to the way envelopes work in X2: you can see all the envelopes on one track, or opt to view them separately as lanes. I think there's an opportunity to do something similar with audio layers and audio lanes. FWIW, I often do complete takes of a solo that overlap from start to finish. I found with layers I could very quickly organize parts in a way that was flexible and suited my workflow. I have been really trying to do the same with lanes, but it is just not the same at all...
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/04 14:18:27
(permalink)
If programs started FORCING the user to use touchscreens I'd be pissed. I'm disabled and just using a mouse causes me pain. If I had to reach over and touch a screen every time I wanted to do something I'd be out of commission with an hour or so. I really hope Cakewalk doesn't start going down this path because I'd be forced to drop them. Windows 8 can bugger off as far as I'm concerned. Sure you CAN use traditional HIDs but it is designed in a way that seems to discourage it. The software manufacturers need to realize not everyone wants this shift.
|
Funkybot
Max Output Level: -75 dBFS
- Total Posts : 796
- Joined: 2003/11/06 16:32:13
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/04 15:03:33
(permalink)
VariousArtist FWIW, I often do complete takes of a solo that overlap from start to finish. I found with layers I could very quickly organize parts in a way that was flexible and suited my workflow. I have been really trying to do the same with lanes, but it is just not the same at all... Have you tried this (and I only found out about this recently and it really changed my attitude towards comping with lanes): 1. Record a bunch of takes to lanes 2. When you identify the best section from each take*... 3. Click the Mute tool, then hold down Alt (I think it's Alt, either that or Ctrl) as you drag the mute tool over the best take for each section Result: All other lanes are automatically muted with a single click and drag; you're done. Once finished with the entire comp, just hide the layers. You can even bounce if you really want to. *Note: no matter how you work, steps 1 and 2 are required. This means, you can now comp or audition each take with a single click and drag motion using layers. If you already knew about this, maybe someone else will find it helpful. I know I did...
Intel i7 4790k, ASUS Z97-A mobo, 16GB Kingston DDR3 RAM, Windows 10 x64, UAD2 Duo, RME Fireface 800, Sonar X1/X2 Producer
|
VariousArtist
Max Output Level: -63 dBFS
- Total Posts : 1397
- Joined: 2003/11/07 15:03:09
- Location: London, UK & California, USA
- Status: offline
Re:X2a - Lanes Are Still Pains!
2013/01/04 16:24:15
(permalink)
Funkybot Have you tried this (and I only found out about this recently and it really changed my attitude towards comping with lanes): 1. Record a bunch of takes to lanes 2. When you identify the best section from each take*... 3. Click the Mute tool, then hold down Alt (I think it's Alt, either that or Ctrl) as you drag the mute tool over the best take for each section Result: All other lanes are automatically muted with a single click and drag; you're done. Once finished with the entire comp, just hide the layers. You can even bounce if you really want to. *Note: no matter how you work, steps 1 and 2 are required. This means, you can now comp or audition each take with a single click and drag motion using layers. If you already knew about this, maybe someone else will find it helpful. I know I did... Thanks for the suggestion, it really is appreciated that you are taking the time to try and help. However, I think one of the missing functions for me is "rebuild layers" -- maybe it's there with lanes and I've missed it? Another item is the usage of screen real estate... Consider the following workflow, one of many that might illustrate where layers worked well: - you record a bunch of takes, say a baker's dozen - one of these takes is the "main one" but you have little bits here and there that you might include - you move the "main take" up to the top - you cut out various sections for consideration from the other dozen tracks - then you hit rebuild layers You should now be left with about 2-3 tracks. One of these is the main take that you are interested in, and the others are the bits under review. Now maximize that track and all your layers take up the full screen height without any waste -- that's 2-3 tracks spread across the entire height of the screen. Take this a step further, and imagine that you might be doing the same thing across two or three tracks simultaneously. In this scenario it's still possible to work effectively across multiple tracks, each with multiple layers. I may not necessarily make a habit of working this way, but as and when I do it is very fast and effective. I'll need to play around with take lanes more and find ways to get used to them. I suspect I may end up using tracks in places of lanes, and put those tracks in a folder. Or something. There are things I like about lanes, but I just wish we could have them AND layers too.
|