John Vere

It’s not in sync but myself I can clearly see where the now time is in relationship to the song. I actually gave up on the Arranger finding it very buggy. I still use good old fashioned markers. I would never re arrange a song anyhow. I’m not that indecisive. But it does have a fan club for those who need it. It was a very cool feature that was added, just not something I found useful.

Glad that my info helped. Understanding Cakewalks signal flow is paramount to good mixing skills. It’s simply top to bottom more or less. So the Gain is very critical as it sets the level for the whole track channel strip. This includes pro channel, the effects bin. So keeping the faders at unity is the only way to see what is really going on.

I have also noticed that when for the very first time you open Melodyne as a regional effect on a project that you get a blank screen. All I do is click in the middle of the clip I have opened in track view and it will now show in the editor. After that all clips will open in focus. @Olaf Melodyne opens its editing view in the multi dock. When you render and close it you will still be in the multi dock. So the default is the console view. Just hit D to close if you are single screen.

I have developed a workflow that involves using the gain on the tracks to set a target of around—8.0db to -12db depending on my mixing goal for that track. I leave all faders at unity. The vocals are the exception where I will go a bit higher -6.0 db to no higher than-4.0db. like you I will combine lead and harmony to a sub bus. I also treat the gain of all sub buses like tracks. Faders at unity. If adding effects pushed the level past my target I will turn down the gain. Using the faders won’t solve the issue. The gain is before the effects and the faders after. So if an effect is being over driven you need to use the gain. I will only use the bus faders a little bit in the final mixing stage. If you’re interested in my workflow watch #22 Oh and reading this again, most De-essers have a preview where you can listen to what it's actually removing. I know the Izotope Nectar has this and when I listen I usually hear nothing so I remove it.

Yes it’s easy. This will apply to using one screen not a second monitor. From track view with Arranger showing open the multi dock and drag the top edge either down a little or up.

It’s been a while but I lowered the pitch of a song by a whole step ( E down to D). and I’m pretty sure I just used the same transpose I use for Midi short cut N. it was 2 Acoustic guitars and an electric lead. Worked just fine. But as Bitflipper has said the tracks need to be clean. It one reason I try and start with as much midi as possible until I do the vocals. I always record the final guitar parts after the vocals so I don’t walk all over them.

No , you can bounce to clip but the recommended method is to render it. After you are finished editing you re click on the Regional Effect/ Melodyne/ And then Render. This totally removes Melodyne from the clip and CPU/ Memory etc. The people who can get away with not doing this are most likely running much more powerful computers than people like me. The other reason to do this as was recently reported is,if you save a project with Melodyne still active and then update Melodyne to a newer version, that project might not open. After you render a Melodyne clip it reverts back to being a regualr audio file just like any other clip. That's what the word Render means. It's a destructive process as the original audio is now changed and cannot be undone which is why we always have back ups if this bothers you. If it was a client for sure I'd have 20 backups, but for myself it's not a big deal to just re sing something I didn't like and on the ocation that Melodyne made it worse and not better. It does only take 2 seconds to press CTRL/shift and drag the original to a new track before editing.

X

And just add. I worked at 128 for years with my Focusrite interface but I bought a Motu more than a year ago and it crackles at 128. I had to bump up to 258. Same system, same projects. So it’s complicated, the person who ever 100% understands PC audio will rule the world.

The following tutorials will help you # 104. Changing Sample rates # 1 Audio Set up #20 Audio Interface set up

This is repeated over and over on this forum. Best dependable results with Melodyne is to always Render the clip when finished. Otherwise clips can become corrupted. If further editing is required it is very easy to simply re apply the regional effect later.

#27 tutorial is how I use Melodyne

Developers take note of this person s issue. This is exactly what happens because of the poor quality of Cakewalks whole installation system as well as the outdated information on the web sites. That video the op watched should be updated I never included anything about installing Cakewalk in my tutorials because it would be wrong the next week.

I hope that they fix this someday. The claim is it’s less confusing for new users to not have all the options. I think I has the opposite effect and it’s confusing to everyone because there’s been a zillion posts with the solution always being — “ Change to the Advanced Workspace and the missing feature will return “. We have the flagship top of the line version of Cakewalk installed but the default is Cakewalk LE.

There is definitely something that is buggy about using save as and rename to a different location sometimes. I’ve had those same messages and similar ones too. But it seems to work on the second try.

Yes I found that if I set the sample rate the same in every setting location Windows , Cakewalk etc it seems to work better. For me that’s 48 because video is 48. It’s better quality anyhow and i convert all my projects to that format if I open older files.

Did you watch my midi set up video?

Your issue is probably related to how your audio interface ASIO drivers handle switching sample rates and other details. Example is my Focusrite interface has always worked no matter what I do it plays the audio from different apps and the internet even with Cakewalk open. My Motu interface doesn’t like sharing. It seems mostly to do with sample rate. So I have started using only 48 hz and for the most part, I have fewer issues, but it doesn’t work as smoothly as the Focusrite. Watch tutorial #1 and see if some of those settings help.

I updated my post to include the proper link to my tutorials. But because people reposted it a few times I can’t fix those. The tutorial I made that has clear instructions on one way ( the easiest) to do this. It is found in video # 105 Importing Midi. The title was on purposely wrong as it’s actually about Opening a midi file. I will no longer post direct links to my tutorials as I cannot control dead links when people repost. My thread in the Tutorial sub forum can be kept updated so this will be the best way to direct people needing help. That way they can also discover other tutorial options.

I still can’t use Strike drums because it can’t find the library. And when I try to uninstall it it crashes. I just wrote it off as not worth the hassle. But I have a lot of projects that use DB33 and so far that is miles above any other B3 I’ve tried. I’d hate to lose it. The company makes good stuff but there are bugs and they do not seem to answer e mail. I don’t think they have updated most of the collection in over 10 years. Must be why it’s so cheap. I got their entire collection for less than $100

Absolutely you just need to make your own custom templates if the default ones don’t work for you. You can actually use an empty project as a template. I like that because then it shows on the default start screen. Just remember to use Save As and rename it before you start adding stuff.

Seems obvious but did you connect the audio outputs of the module to your interface? Or as @parboo12 is saying possibly the Roland has a ASIO driver and transmits digital audio over the same USB connection as the Midi. Seems the only connection you would need is the USB if so. And hopefully you are reading the manual for instructions on setting it up

This ones better Tutorial #1 and #2 have all the information only difference is you will concider your Keyboard your Audio interface as well as the controller. Should not be a problem as I have used the Yamaha Steinberg ASIO driver before and it's a good driver. Unlike the Steinberg Generic Driver which I don't like. That gets installed with Cubase and Wave Lab and you have to remove it.

I always have a hassle when I rebuild installing the Air products. Great stuff but terrible installers. The pathways go nuts and you loose the libraies etc. But what you can do is use the search found in the upper right corner of explorer by opening your This PC and open C drive. Type in Air and it will show you where everything went.

Just start with tutorial 1 and keep watching and you’ll have everything working just fine.