Jump to content

Noel Borthwick

Staff
  • Posts

    4,819
  • Joined

  • Last visited

  • Days Won

    64

Everything posted by Noel Borthwick

  1. We mute uploaded mixdowns if you are also uploading tracks, otherwise you would get doubled audio. If you upload just a full mixdown it shouldn't be muted. Are you seeing that happen? Its possible that there could be tiers for more than 16 tracks but I don't know of any immediate plans. Feel free to contact BandLab support for enquiries or requests. For BandLab specific help you can contact support@bandlab.com
  2. Its most likely because those folders are not sub menus as I explained above. So you need to click them to open a new menu.
  3. I’m not sure what you mean by “manually click on them”. If a plugin folder contains a large number of plugins it pops in a new menu window rather than a sub-menu. That’s previously existing behavior. At some point we may try and remove that behavior but its a relatively minor issue and only affects large lists of plugins. Glad you like the feature.
  4. Today if you import into an existing project its always appended. We could insert at the current track position but it might get confusing if the user didn’t intend it. I’ll take a look about the clip names and see if there is an issue.
  5. This is the same behavior if you create a new project and import or record audio then close before saving.
  6. Looks like something blocked the installer. Restart your PC, disable any Antivirus and try reinstalling.
  7. This is literally as simple as bringing up the export to BandLab option and choosing to export a final mix or include the stems you want for accompaniment. Then share the project with in BandLab to the vocalist and have them sing in the new track while listening to the comp. When they save their version, it should appear as a revision automatically in the library view. You can then open the main CWP project and import their revision into it and continue from there.
  8. This will come in a future update. Already working on it.
  9. You can sign out from your account anytime from the help menu and then sign in as another user.
  10. This is light years more powerful than what Momentum did. Just use the BandLab iOS or Android app. And the projects will automatically be available in Cakewalk.
  11. It should be completely fine and I do this often. Just use the BandLab app on Android or iOS and record there. Your project should automatically show up the next time you open the library view in CbB. Then either directly open the project or import the track into your current CbB project. You can also use BandLab like a cloud audio clipboard this way to share audio between different PC's or mobile devices. The integrated cloud support is a very powerful tool.
  12. Hi everyone, We just dropped an early access release that has a lot of new exciting new features including deep BandLab integration via a brand new library view. Not only can this feature be used to publish to BandLab and collaborate with other musicians, you can also use it to save stem mixes of your project and play them anywhere, which can be very useful when testing mixes or trying to get opinions from other folks on your mixes such as in the songs forum. This is much more powerful than posting a stereo mix to your song, because if you additionally provide stems others can offer more constructive advice feedback on your mixes. (there are options to provide a full mix in addition to individual track/bus stems) Please try out this feature and let us know your thoughts in the early access thread.
  13. Hi folks, There are a lot of new exciting features in this release. A reminder to please also take some time to also evaluate the new integrated BandLab library capabilities. Not only can this feature be used to publish to BandLab and collaborate with other musicians, you can also use it to save stem mixes of your project and play them anywhere, which can be very useful when testing mixes or trying to get opinions from other folks on your mixes such as in the songs forum. This is much more powerful than posting a stereo mix to your song, because if you additionally provide stems others can offer more constructive advice feedback on your mixes. (there are options to provide a full mix in addition to individual track/bus stems)
  14. @Milton Sica we will look into your issue but keep in mind that this issue is not related to the EA release and should be posted in a different thread. As per the details in the main post: Please keep responses specific to problems or comments on this release. Unrelated bugs or feature requests should be posted in other threads or the feature request channel.
  15. Actually bundles are not so susceptible because the bulk of the data is the wave data which is at the start of the file. Any small corruption there wouldn’t prevent the bundle loading typically. The CWP is tagged on at the end. That’s the dangerous bit.
  16. Do you hear the distortion even when you freeze or render the track? Looking at the rendered wave may give you some clues. Also check if the gain is clipping in your signal flow.
  17. Your status bar says “Saving file”. Were you saving the project or do you have auto save enabled?
  18. You can upload the zipped dump to any sharing service like google drive and send a link.
  19. Its in the bus compressor. Is this reproducible? If so please PM me the project file and steps.
  20. Knowing patches is not possible because that is managed by the plugins preset management directly. Cbb doesnt know what patch is selected. Im not surprised that you corrupted the file haha. The data structures are quite complex and there are sizes stored for chunks so if you are not careful you can corrupt the data very easily. I had some rudimentary XML extraction built in a long time ago that could output a file that had the basic track properties but you wouldn't be able to get patch names. We can consider having some basic text extraction for the project for documenting whats in the project without having to open it.
  21. If this same a bundle file make sure that you can open it successfully from the bundle. Any file can get corrupted on disk and since a bundle is a single file there is a risk of the entire file getting corrupted. Hence the recommendation you save both the bundle and the actually project file with it's audio.
  22. A bundle file is a multi chunk RIFF wave file. The compacted audio data for all regions is stored first (per wave file format - stereo/mono/32 bit/24 bit, etc) followed by the CWP chunk. This is why if you rename it to wave it will play because media players ignore the subsequent chunks. As long as you download the file in entirety from google drive you can save as with the CWB extension and it will load fine. FWIW there is nothing wrong about saving as bundles. All known previous issues have been addressed a long time ago and yet people keep repeating the same incorrect info. You should always additionally save as CWP with external audio since its a lot more efficient to load and it provides a secondary backup. Bundles are convenient when you want to collaborate or simply store a single file.
  23. I'm saying that the the user interface load (drawing clips, scrolling, etc) can also have an impact on streaming because it consumes CPU resources and in some cases can also affect DPC latency. Some applications have less going on in the user interface than Cakewalk and so performance can be affected because of that as well. Additionally plugins can have load that can impact different DAW's differently such as plugins that do OpenGL graphics. My point was without investigation you can't easily draw an assumption that the issue is directly related to the audio engine. There are many moving parts in a DAW besides the engine itself. We can investigate it further if you send us the sessions. As part of our ongoing efforts, we continue to try to improve performance in various areas of the DAW.
  24. Let me know if it happens again in the next release. I’ve prevented the actual crash from happening.
  25. @Andres Medina I tried to look for cases where this issue would occur and was not successful. Does this crash only occur with the Listento receiver and is it a reproducible problem? Also I see you are running a behringer audio interface. Did you notice any particularly odd behavior when loading templates with this plugin? We also tired making a template with the plugin and it does not crash. I've added code to prevent the crash itself but the cause is a mystery.
×
×
  • Create New...