asked Mar 20 at 17:21 by vkh (101)

Two quick suggestions for how Bitwig's handling of missing (moved) samples could be improved:

  1. Add an option to automatically scan all configured sound locations for the missing files and update the paths. Currently, as far as I can tell, this must be done manually for each sample, which can be quite tedious.
  2. Add an option in settings to automatically "collect and save" each time a project is created/saved.

i agree with you saying

link

answered Mar 21 at 06:36 by YYBY (66)

This is not an answer

I've been finding this a pain too. I've only just started back producing but the few tacks i've made had missing samples (as i moved some folders).

I didn't think i'd have to navigate all the way to the actual sample (just the root folder i hoped). It's achievable now as i've only been going for a short time, but i can't imagine being able to do this when i have many old tracks and thousands of samples.

link

answered May 26 at 12:46 by sygboe (0)

Thanks for the information. It was very helpful for me. Visit site

link

answered May 31 at 19:25 by solarpower947 (11)

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×97
×50
×25
×21
×11

Asked: Mar 20 at 17:21

Seen: 212 times

Last updated: May 31 at 19:25