Keni

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.

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.

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.

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.

Any chance the new menu system will reach the drum map selection menu?

Minor item for sure... If an item at all? For now, I like the new highlighted waveform images. But I have encountered an issue. When I assign a track color of yellow, there appears to be no highlighting. I'm guessing the highlight function is adding yellow to create the relative image? If such is the case, it appears a routine needs to be added for the situation where the selected color is yellow and substitute something else? White? Not visible enough? ...just a thought. I can live with it of course. Thanks Gang!

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.

Hi Noel Having trouble capturing a picture. As I run win8.1 on a macpro via bootcamp, I run into issues. The normal widoes+Printscreen doesn't appear to work, but then again my keyboard is a mac keyboard. Maybe I'm pressing wrong keys as I don't seem to find any pics with my attempts. I first tried to use Fastone to capture as I usually do, but the menus disappear from screen as I attempt to switch apps. I do understand your explanation. I'm also not troubled as it is better now than it was before. I honestly don't mind them both being listed as long as I can (as now) tell which is which. So thanks for the "fix" for me! ?

Just to note... First, thanks for listing the vst/dx version. At last I know which I am using. I have long wondered why so many items got posted twice in the lists. At last I understand! ? I posted an item about this in the feedback loop as I have the option in Preferences selected to hide VST2 when VST3 is also available. Was this a misunderstanding on my part or a bug?

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...

Just a note of thanks again. I just ran the update from inside CbB and it ran smooth and comfortable. Great work from the team as always! I look forward to exploring some of the many alterations asap!

Sounds very cool Noel. I’ll check it out for sure. I suspected something of this nature to be on the horizon. I’m glad to be seeing it come to life. Many thanks to You, Noel and all the Bakers who work so hard to make this stuff happen and the foresight our beloved owner has shown in directing the plan!

I don’t know if it is still available, but back in Sonar days, 12Tones released an ios app called Momentum (?) which allows 4 track recording and direct xfer of tracks to Sonar. I believe it still works but might not be available? just a thought.

Thanks Jonathan... Worked this time and all is well!

Thanks Jonathan... Problem seems to be the main link continues to show the original build not rebuild 2. I'll bootup my DAW again. Maybe a refresh will show the updated link. I know I already have the CA2a so it’s not that I need it but verifying the update works correctly. Edit: Update worked. This time I received the rebuild 2 version for download and now the PC2a works just as the CA2a does in the ProChannel... Thanks. I know this will bring joy to many CbB users!

It's only the ProChannel Module. Run a VST scan if you do so manually. Then you will see it in your available ProChannel Module list. Do note that it's currently not working for everyone even when it does appear...

Interesting... I notice that the error message popup regarding incorrect installation of Concrete Limiter pops up every time I add or remove the PC2A (non working) ProChannel module. The Concrete Limiter itself (which I own) is working fine.

I believe the same entry in the list is a toggle

I get it here, but though I've downloaded and installed from the main link twice, the pc2a does not function. The led next to it's power switch shows some signal, but nothing else... I did notice there was no difference in the filename for the download so I'm guessing I got the second file as my original but still not working here. I do have the CA-2A if that makes any difference... It is performing correctly as usual...

Thanks gang... Always happy for progress... I was curious what was gonna happen for those of us who have the CA-2A prochannel/vst plugin from previous purchase. Thanks for handling it as it appears two separate plugins. I doubt I'd notice a difference, but I feel better this way....

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!

Thanks Matthew! That sounds like a good solution. I'll give it a try later this morning when DAW is up and running...

Yeah, my fault. But trying to see if I can find a way... I bought the waves puigchild 670 without thinking. No returns on software. v12 plugins require win10 and I’m trapped at win8.1 so, I forced the install but it doesn’t appear after a vst scan so I searched for the plugins, found them and copied the dll to my vstplugins folder. Still no luck. Does anyone know of anything I’m missing or some trick, I would love to know. Thankfully, not a huge amount of cash to throw away, but.........