Keni

I must admit I’m surprised no one else is experiencing this... It’s been an issue so very long here.

Are there any shortcuts to reset this to default I may be accidentally triggering? I have not found any.

I can’t believe I'm the only user preferring curves to linear?

<sigh>

3 hours ago, Klaus said:

I'm pretty sure that this setting is saved with Screensets.

If you save your templates with a locked Screenset (one or more), it will open again with the same fade/crossfade settings, regardless any changes you made while working on your project.

 

Thanks Klaus...

Sounds like a possible work around if I ever brave using screensets. I had issues with it, no real need I could see, so avoided.

Might see what it does...

...but this has existed since long before screensets. The settings should be saved with the project, but for some reason I have been unable to discover, this continues to randomly happen.

This is definitely not new and I’m surprised I haven’t mentioned it more often.

The settings for fade in, fade out, and crossfade. I set them in my templates. Always the same curves, but periodically I go to use a fade only to discover it gas been changed back to linear. I can then reset all settings, save, re-open, verify settings are still my selections only to discover some time later I've been reset again!

Not a show stopper, but a continuous pita and we all know how such grates over time.

Is it something I'm doing unknowingly? Is anyone else seeing this?

 Thanks 

1 hour ago, InstrEd said:

Now that is some nice customer service. 

I agree! ...and they did all this within minutes of each email I sent them. Excellent!

1 hour ago, jesse g said:

Keni, that's great.   

You can get Windows 10 from ~~>  PC WORLD  for about $89.99 per single computer license.  Windows 10 Home is only $69.99

Get it and save it for when you decide to switch to Windows 10 . 

Thanks Jesse.

Probably not gonna happen anytime soon. Win10 install fails on this machine due to hardware age. Replacing this machine is not reasonable for me. I was gifted a mac pro with dual xeon 3.06Ghz 6core processors (12 total) and 64G RAM. The cost if this machine's replacement would be near $10k. So for the foreseeable future, I am trapped with win8.1 which other than some issues such as this update, I am quite comfortable with. Funny how I hated win8, but 8.1 runs well and painless and not suffering the update plague of win10.

While it would be nice to have melo5, I really wanted studio more than 5. $199 was an acceptable upgrade for that and I now own license to melo5 should I ever need it.

They just did me a good favor.

i bought the v5 upgrade from editor v4 and they supplied me with an upgrade to v4 to fill my needs trapped at win8.1 while also giving me a future upgrade to v5 if I can ever use it.

 I’m a happy camper. I do a lot of multi voice harmonies so the studio's option for multiple tracks simultaneously in a single view seems so very inviting.

1 hour ago, Brian Walton said:

Don't they have a trial version?

Thanks for the idea, but this machine is too unusual for me to take a chance. It was gifted to me and far beyond my ability to replace so I stick with it until such time as bang4buck brings me this kind of power (or better) within my reach.

MacPro dual 6 core xeon processors 3.06Ghz (12 cores) 64G RAM and huge dual radeon video cards though un-necessary for CbB...

Hmmm... just thinking I wonder the current cost of v4 editor to studio upgrade (if available). I’ll have to take a look.

I wish I could jump on this, but due to old hardware, I'm trapped at win8.1 and when I asked them for opinions of attempting to install on anything older than win10 is uncertain (as opposed to unsupported) and I stuck with 4.x that time as recommended by the tech. Policy?

Does anyone know if it will install and operate on win8.1 though "unsupported "?

 Thanks 

Done! Thanks for the help scook!

43 minutes ago, scook said:

It appears to be a separate account.

After completing the support login, I can still access BA, this forum and BandLab account using  my original ID and password created during the migration from Cakewalk.

 

Excellent! I will do this in the am for sure. Thanks again scook!

2 hours ago, scook said:

I was roaming the menu and clicked on the support link on the help menu.

It appears there is a new account database for support.

The login screen supports authentication via Google/Twitter and email.

One of the screens mentioned that if I had sent them email in the past my account was already set up  and I needed to request a new password. Otherwise, I needed to create a new account. 

Since I had sent email to support in the past I...

• requested a new password,
• got a link via email,
• followed the link,
• added a password

and the support page opened.

Thanks scook!

I thought of trying that but didn’t want to risk it affecting my other bandlab accounts. If I understand you correctly, this is a separate account with separate password.

OK. I’ll give it a try in the morning.

55 minutes ago, scook said:

This is one of the first posts on the forum

 

Thanks scook.

Yes, I know that one, but I thought we still had a more "formal" bug reporting form. Thanks for the info.

2 hours ago, treesha said:

I haven't reported it just worked around it. If you find out something please post it! 

Absolutely!

1 hour ago, John Vere said:

Might be a bug in version 4? I just did it again in the same song same guitar but a different clip.. The song has a lot of audio and midi going on. And doing this I created a cool sound by now doubling the guitar riff with a Banjo VST called YoJo. 

Anyhow in the past I've probably converted close to 100 bass tracks into midi. I even did this with Home studio. 

So I'm not sure if anyone else has this problem but here's what we do now.. @Noel Borthwick   - now Noel will read this thread. 

He'll probably ask for you to send a copy of the project. 

Thanks John.

Pretty big project to send but I will if needed. Bug appears in both melo 4&5. I've done this many times over the years starting back before Melodyne was involved, so I doubt it's something I'm doing. When I moved (copy/pasted) the track to an empty project and it worked fine.

55 minutes ago, scook said:

email support@cakewalk.com

it goes to the same place

Thanks. I did send an email there but I don’t remember detailing the actual issue being derailed by the login confusion of mine.

Is there no longer a link to a bug reporting form? My memory (organic) is shot. Should I simply bug it up and send to the support email?

Don't know what's going on here.

My email/password works fine on both bandlab home page and forum, but trying to login to support from the bandlab support link refuses the credentials.

I'm trying to file a proper bug report to begin with and ran into this along the way. Is there some new place I'm to use for bug reports? I was a bit surprised to see an email address of support@cakewalk.com on this bandlab support page?

Anyone have any thoughts here?

Thanks...

1 minute ago, treesha said:

I have used  cakewalk and melodyne for years too and only recently encountered this too, not even after a specific upgrade if I recall right. I am still on 9.2020  and current melodyne studio 5. 

I’m running 2021.04 and melo 4 editor as I’m trapped at win8.1

Has anyone formally reported this to bandlab/celemony?

I may post such for additional support anyway.

6 minutes ago, John Vere said:

I don't know but I just tried this were I took a lead guitar solo and dragged it to a new midi track and I got a pretty good tracking of the guitar solo. Only a few octave jumps to edit and it's done. Did you set the dialog to "melodic" ? 

Thanks John...

I’ve used the pitch to midi conversion many times in the past but not recently. The conversion is working even now, but for some reason it's converting every clip in the audio folder into a midi clip and depositing them all on my destination track.

As I explain above, doing this in a project with only one audio clip got around the issue for now.

26 minutes ago, treesha said:

I have been having this for many months now using melodyne studio 5 and i am behind on my cake update version. I adapted by moving anything i want to change to midi to  beyond the end of the song so the only midi i get is the clip or track i want, then move the midi to the location it belongs back in the song. Otherwise like you say every single track in the project will convert to midi on the destination track all lumped together. I hope to learn why this happens and how to make it work right.  

Thanks Treesha...

Yes. My workaround was to copt/paste the track to a new project and convert where it was the only clip in the project. Then copy/pasted the midi back to my project.

It does a decent job of converting. I’ve long known that but hadn’t encountered this issue until just now.

I have a monophonic guitar recording.

When I drag it to a midi track, i get the conversion dialog followed by every clip on every track getting a midi track written to my destination track including clips that were deleted from the song file.

What's going on? I haven’t used this function in a long time, but it never did this before.

I have Melodyne Editor 4 installed.

6 minutes ago, scook said:

It may but a clue to its main duties could be in its name...BandLab Assistant.

This tool, written by a dev team in Singapore, was originally designed to support BandLab, the web-based DAW.

After BandLab acquired Cakewalk IP, BA was pressed into service to handle CbB install,  activation and update.

With in-app updates and re-activation added to CbB,  reliance on BA is not as critical for CbB users as it once was.

BA does offer a loop library and  most recently a front-end for BandLab's mastering service.

 

 

 

Thanks scook.

I totally understand and was glad to have any method of maintaining updates for CbB. I would be using it (gratefully) still with my continued appreciation, but even more appreciation for the continued development and evolution of this great work which has progressively been freeing CbB from this need.

I think the Bandlab project is a wonderful service and seeing it integrate and evolve with CbB is much appreciated.

If I could, I'm sure I would be making more use of it.

Yeah. Updating BA has been difficult since the beginning. At this point, all updates fail. I simply download the latest version on top (no uninstall) and all is well. I maintain the updates but I never use it anymore. I run CbB updates from within CbB.

Unless BA evolves to something more useful for me as was CCC back in Sonar days, it’s only a maintenance task for me.

Thanks both Noel & scook for taking the time to examine my issue and explain.

I appreciate it very much.

Funny, but in this situation I’m fine with the status either way.

I posted this here as opposed to the EA release as I don't think this is EA related.

I have the option selected in Preferences to hide vst2 when vst3 is available yet I still see both listed in my VST lists... Is thi as expected? I thought the purpose of the button was to hide the VST2 version if the VST3 version is available?

Maybe not a good idea to do and I guess with the new EA feature, it's no longer a problem...

7 hours ago, Matthew Sorrels said:

Can you run the older pre-v12, Windows 8.1 compatible version?

https://www.waves.com/support/how-to-roll-back-to-waves-v10

V10 looks like it runs on 8.1:

https://www.waves.com/support/tech-specs/system-requirements#plugins|version-10

 

Thanks again Matthew!

That solved the problem very nicely. V10 is up and running fine and I'll never know what v12 has that I'm missing. It preforms as I expect just the way it is!