agent314 wrote:It keeps freezing up my machine when it scans the presets for the first time
This has been reported by some other customers too. We're not sure yet what it causing the initial scan to get stuck for some people, but we're looking into it. Thankfully, it can be resolved pretty easily.
Win:
1) Quit Live
2) Go to Start Menu > All Programs > Camel Audio > Alchemy > Alchemy Configuration
3) Delete Alchemy_Preset_Ratings_And_Tags and Alchemy_Preset_Ratings_And_Tags.bak.
4) Start Live and launch an instance of Alchemy. The scan should restart, and ought to complete successfully this time.
Mac:
1) Quit Live
2) Go to /Library/Application Support/Camel Audio/Alchemy
3) Delete Alchemy_Preset_Ratings_And_Tags and Alchemy_Preset_Ratings_And_Tags.bak.
4) Reboot your computer
5) Start Live and launch an instance of Alchemy. The scan should restart, and ought to complete successfully this time.
agent314 wrote:I just wish they would improve sample browsing when loading patches for the individual voices. It's such a pain in the ass to navigate (not even scrollwheel support? WTF) that I end up almost never using it for sample manipulation, despite it being really good at that.
Also improving the additive editor would go a long way
The scrollwheel problem is an odd bug - it is affecting only some hosts, and seems to be system dependent too. We apologize for this, and we're working on a solution.
On KVR, someone mentioned a free utility that resolved the problem - not just in Alchemy, but in other programs:
http://www.pcworld.com/article/160068/m ... g_fix.html
However, it really should not be needed in Alchemy and we're working to fix that.
Regarding other changes...now that the browser is done (with the exception of fixing these problems) we're going to start focusing our efforts on v2, which will bring improvements to many other areas of Alchemy.
sporkles wrote:A few missing sounds here and there – should I reinstall the soundbanks?
If you are missing samples on factory presets, then you will need to download a new copy of the Factory Samples Part 1. If you're missing samples on library presets, you'll need Factory Samples 2 and/or the samples that come with the libraries. Also, there are two new batches of samples: the bonus factory samples (linked as #3 on the downloads page), which are needed for some of the new presets...and the Taste of Camel samples.
When you download the files again...if you don't already use one, I highly recommend you use a dedicated download manager such as Orbit Downloader or iGetter. We find them to be far more reliable than downloading with just what comes with the browsers.
Even though you can hide the actual presets you don't own, they seem to be popping up now and then.
Even though another member here already mentioned it, I thought I'd give an official statement here that this is indeed a bug. We apologize for this and are working on fixing it.
And the soundbanks you DO own are frequently greyed out.
I apologize if I am misunderstanding the problem you're encountering on this one. If you are selecting options in the browser to narrow your search results (or using the text search) and the criteria you've chosen doesn't match any presets in a library, then it will be grayed out.
Also, be sure you installed the "all presets" file linked at the top of the downloads page. This updates all your factory and library presets, so that everything is properly tagged for the new browser.
Also please note that 3rd party presets that haven't yet been updated for 1.5 may not show up in expected searches. We've tried to add some helpers in there, such as automatically having VA presets show up when you select VA from the articulations list, but there were limits to what we were able to having Alchemy determine just from the preset structure.
agent314 wrote:Seriously, no scrollwheel support for the new browser?
Get it together, Camel. I love Alchemy, but that's a bushleague oversight
We were convinced we had that one solved, as it was working in earlier betas, but somehow things went awry in the last RC and it managed to get past all of the beta testers because it is so host/system dependent. The good news is that we can reproduce the problems now, so we expect be able to resolve them quickly.