mdiemer

Wow, thanks bvideo, I'll have to check that out!

I want to delete a Dim Pro synth. But it appears it is not recognized in the synth rack. I mean, yes, it is there, but where its name should be, another synth's name is. Also, the freeze button is greyed-out, and the option to unfreeze it also is greyed-out. If I delete this "ghost" instance, I may delete the synth whose name appears in its slot. In the past, I have had trouble deleting instances of DP, but usually because it causes Cakewalk to crash. I figured out a away to do it, but can't remember what I did. I need to delete all instances of it, because they are screwed up, misnamed and so on, and I want t start over and add only the ones I need and get rid of the rest. Honestly, it's almost not worth using this thing anymore. anybody have a clue what is going on here?

Craig, I had a similar experience with W7. I ended up having to reinstall. The same thing, Windows was searching for something that was no longer connected. In my case, I'm pretty sure it was an external drive. Why windows goes insane over something like this is beyond me. You can connect/disconnect things all day with Linux, force it to shutdown; throw it on the floor (well maybe not that), and it just starts up again. Windows... anyway, I now always make sure I disconnect safely. Maybe this is what happened to you, or some other ridiculous thing. It's enough to make one consider switching to Apple. Linux is years away from being usable for music creation for most of us.

Craig, I haven't read thru all this, but have you tried restoring the boot with the Macrium rescue CD? It will fix broken boot problems that can prevent booting. Rebuilds the master boot record.

Thank you msmcleod! Clonezilla is a beast, but very difficult to use. It took me months to figure out how to use it. but once you get the hang of it, it's very powerful, can image any OS. Too bad it doesn't have a GUI. Text-based instructions for something this complicated turn a lot of people off, but your tutorial will really help.

Well, I have learned something, namely that part of the problem appears to be the result of having activated the native reverb on the Synchron and Vienna players. So I turned it off and used Lexicon Pantheon on the synths instead. I'm working on a three movement piece, and the first movement had the native reverb on, the second had it off. The second movement sounded better, there was less latency. I have gone back to the method of not using any native reverb on my vsti, instead using Pantheon on the synths, then sending them to the EW Spaces Reverb bus. This also results in better sound overall. Still some minor latency but much better.

Thanks for your input, Larry. I am definitely leaning toward that conclusion. Work arounds are the key here, as in so many complications we encounter in this work.

Hi scook, thanks for responding. The delay does vary within libraries based on the inst. Strings in Vienna are bad; Cinematic Strings (which uses Kontakt) also but less; some wind inst's. in East West have it; some don't. Garritan insts. are fine. It's been a problem for a long time, which I have dealt with in various ways. Often I can't use the desired inst. because of it. But your suggestion before, to use the timing feature, at least gives me a work-around. Incidentally, the folks on the Vienna forum also have suggested to me that it's due to the strings being slow to speak, as they say, because of the bowing. Except for one guy, who said most DAWS have a way of dealing with this, which is why I posted this thread. Most folks probably deal with it in PRV or track view, where it's easier to move stuff around. But I work in staff view, where doing that messes up the note values, which throws me into conniption fits as I am so tied to working with notation. Finally, the problem persists after opening a closed project.

You may be correct Canopus, it doesn't make sense to me either. Not sure what was going on there. Anyway, I guess I am resigned to working with the time thing. It's a pain though, because, say you are working on measure 20. you do something and rewind to ms. 20. But there is no sound. You have to go ms. 19 and go from there, because you altered the starting time, and it now really starts in ms. 19. Another workflow blocker. Oh well...Cakewalk is still the best for me, I'll just have to put up with it. but you are right, it's the strings that are the biggest offenders. It's the bow thing. A case where making the sampled inst. so realistic, it screws up your workflow...

I think I solved this. We had a power failure, and my computer was asleep, so it had to be restarted. I think the project got corrupted. I first rolled Cakewalk back to the previous version, problem still there. That's what made me think, corruption. I decided to open the project from a different saved version, on a USB drive. The problem did not happen. This confirmed my theory, the project probably got corrupted due to the forced shutdown, and Windows' weird recovery process from same.

Suddenly Can't Copy/Paste, without notes I copied disappearing. This is happening in staff view. I installed the latest version a couple days ago, and at first everything seemed fine. Now today, this problem has appeared. Maybe it doesn't happen in other views, but staff view is what I use, and I do a lot of copy-and-paste, so this is a huge problem. Actually, what it's doing is pasting to the second instrument, and moving the original to the last measure of the pasted track. So, for example, I'm copying 10 bars from the clarinet to the oboes. The oboe gets the notes I coped from the clarinet, but the clarinet's notes get shifted ahead to 10 bars. So it's not deleting the clarinet's notes, just shifting them ahead. Never seen anything like this before!

Yeah, that thought has crossed my mind. The fact that it was less of a problem in Reaper was why I thought it was a Cakewalk problem. But you may be right. Maybe Reaper has some way of adjusting for this. If so, I doubt that Cakewalk has, or someone would have told me about it by now. Looks like I'm stuck doing those fine time adjustments.

Ditto, although it was a mile over my head. Edit: Oops, I added an emoticon to sjoens' quote. Sorry, it was meant for my reply. I did not intend to imply that sjoens is as confused as I am; few people are.

Thanks Mark, I am using the Steinberg UR-22 USB interface. Using ASIO drivers. Currently have latency at 256. What 's interesting is that when I was using Reaper I didn't seem to have this problem. So it does appear to be a Cakewalk problem, but just what is a mystery. I'll go lower on the latency, but with so many plugins I may not be able to get away with it.

I do midi only (not GM but with sound libraries). I use various vstis, like GPO, EW etc. Some of the instruments have a delay in starting, or latency. Especially happens with strings. Until recently I didn't know how to deal with this except by using the slide function, which didn't work very well, and caused the notes in staff view to display incorrectly. So, scook told me I could adjust the timing feature on the track inspector. Indeed, that works. However, it is hard to get right, and with an orchestral piece very tedious. Someone on the Vienna Inst. forum said most DAWS have a way to compensate for this latency, usually just a single setting. Well, I've looked around, and I see things like clocks and SMTPE and time stamping, all of which are completely mysterious to me. So, is there such a setting on Cakewalk? Thanks, Mike

Yeah, that's pretty much what I thought it meant. Thanks for the description. I will keep it in mind when evaluating software and their respective forums. As for Reaper, I used it for about a year, and I didn't get much of a sense that it was in that category. Sure, there were the usual fanboys. Reaper is of course very customizable, and you would constantly hear about that; but the other side is that it is not beginner-friendly. I think the tremendous enthusiasm for the fact that it's highly customizable is really a cover for that fact. It tool me a LONG time to figure out midi routing, which is a breeze in Cakewalk. I did get to the point where my workflow was similar to Cakewalk, but there were always extra mouse clicks, extra steps. On the other hand, the end result was better, mainly because Reaper, along with other DAWS, automatically compensates for differences in latency between different vstis. With Cakewalk, I have to adjust the timing for different instruments on the track inspector, so everything starts at more or less the same time. This is something I just learned from scook (may his name be blessed). As you said, they all have their respective strengths and weaknesses.

What do you mean by Moonieware? I have not heard that term before.

Thanks scook, I don't use DP for much. But it does have some things I like. I never had Rapture, unless the light version if it came with earlier Sonar versions (8.5 was my last). I don't have it on my system now. I am setting the pan directly on the synth, it only needs to be set once. I do like to use CC events for volumes however, so I'll just use 10 and pretend it's 7. The challenge will be in remembering two months from now that that is what I'm doing. I'll consider buying Rapture if they offer it. Personally, I would rather see them offer the Roland VSC, but that of course involves negotiating with another company. I will probably buy it myself at some point. It has stuff you don't find anywhere else, assuming it's the same as when Cakewalk had it. I do have an early version on Cakewalk 2002 I believe, but that doesn't do me any good.

The pan and volume knobs on Dimension Pro are reversed. If I put in a CC10 event (Pan), it actually controls the starting volume. If I put in a CC7 (volume) it changes the pan. For example: I put in a CC10 of 20, which should change the pan to about 68% left. but instead it reduces the volume to 20. And if I put in a CC7 of 100, it changes the pan to about 75% right. The knobs actually move on the synth in response to these CC events, only in reverse of what they should do. You change CC7, the pan knob moves. you change CC10, the volume knob moves. It should be exactly the opposite. This gets confusing as you have to use different CC events for the DP than you use for the rest of your instruments. It affects both the 32 and 64 bit versions of DP.

Yep, it sure does help, scook. you did it again! the best thing is, the notes still display correctly in staff view. I found I had to use a value of -10 to even it out with the other instruments. I'm going to post this on the Vienna forum, for any CW users there (or anyone at all who might have this problem). Edit: the time I have to set varies with the instrument, the strings being the worst. Also, some of my East West Inst's. hve the problem too. I feel so stupid. This is probably a midi 101 thing...

Thank you scook, I'll give it a try. I appreciate your help so much!

I use several Vst instruments, Garritan, East West, Vienna, and Cinematic Strings. Latency is fine on all but vienna. Ever since I have used their libraries, there is this maddening latency. I just got my first Synchron library with them, and hoped I would not experience this, but it is on that as well, just like the regular Vienna player. Adjusting latency in CbB doesn't seem to do anything. The result is that my Vienna sounds lag behind the others, which sounds terrible. I try to use the slide feature, but it doesn't help. It's like they just insist on being late! Can anyone shed some light on what is going on here? Thank you, Mike

Well, considering the software is free, I don't think it's cool to demand anything of Cakewalk/Bandlab. We should be thanking them every day for it. But it's fine to ask for things, and give them feedback. It works fine for me, not perfectly, but then it wasn't designed with me, specifically, in mind. If you take the time to learn how to use it (yes, it does take time and a lot of hard work), it will work fine for you too.

Cakewalk is far easier to use than Reaper. If you think CbB is esoteric and difficult to use, don't even think about Reaper. As for lazy people: they never get anywhere. Any significant accomplishment requires significant learning and effort.

You need to put in an event to set the modwheel at a minimal value. I do this in Event List, using CC events. Put in an event for CC=1, or CC=7, and a value of 80-100. Then the modwheel will reset to that value. It's not really a velocity event per se. An easy way to do it is, just insert a duplicate of the first note in your track, and change it to a CC event (CC=7) and set the value to 80-100, depending on how loud you want the base volume. To easily insert a duplicate note, just highlight the first note and hit the "insert" key on your keyboard (i.e. typewriter).