when is the next fix ?

You’ve just described a three step issue. It IS in the manual, and plenty threads here on the forum address this same question.

  1. Put the samples, presets, and VSTsound files into any directory/folder you like. If you got some content that suggests a specific directory you many optionally use that (even if you must create it). If you use the authors recommended directory then there is less chance that Halion will need to ask you questions later about where content is located.

  2. In Halion, or in Cubase, with the Media Bay/Browser, open the system directory tree and put a check mark by the directory(ies) that hold your user content. Click the rescan icon (or just wait a while). If you’ve added content that is not in one of the directories already being auto scanned by Halion, then you’ll need to tell it about the new directory (Just like EVERY other VSTi on the market that allows user content).

The reason it works this way (through a relational database) is so you can have a robustly searchable and pre-viewable library, where everything is tagged and categorized…even if the raw samples do not support embedded meta data protocols. It also lets you keep libraries in as many directories and drives as you like.

Media Bay is a power user relational database. It makes it much easier to maintain massive libraries…all tagged and sorted so you can find stuff. You can ‘click’ it and preview things without having to manually walk through dozens of steps to load up a plug in and audition it.

If the user content was distributed with separate presets and raw samples (as opposed to archiving them in a VSTsound container), and you installed it to a different directory than the initial creator was using; then, Halion might ask for the location of the samples again the first time you run it. It’s a simple matter of directing Halion to look in the proper director(ies) for the missing samples.

If you ever move some of the content to a new directory or device, the next time you start Halion it will inform you that something is missing, and will allow you to redirect it to the new location.

Which defeats the purpose of H5 or HALion in general… We don’t get the necessary updates to addressed reported bugs and now we gonna jump to H6 while H5 was never taken care of.
Nothing has changed Matthias… same moves for 15 years on this product (and others).
We needed those fixes last year. We gonna jump on H6 and nothing was done to H5 in its lifetime. Same will be for H6… “HEY H7 is here… yeah we didn’t want to fix H6 but hey here is a new one. It’s better.!!” It’s all to familiar since I’ve been on this sampler since it came out.

That whole mentality has to change.
People pay a lot of money for a product and its never at 100%

I can’t sit for a good 30min or 45min. to make a decent tutorial of HALion when It crashes while editing. ALWAYS! SO I give up and just use my old libraries and lose all inspiration to create new content or do tutorials. HATE to be telling people to buy this product and then I have to be their tech guy because I feel responsible for telling them to buy it. I want HALion to be on the top… not where it is now.

Not quite so. Omnisphere installs by clicking the installation file. It places presets and tables in the correct folders automatically. Omnisphere has the same kind of browser information as HALion only more thought through. It even tops the information by adding graphics (sometimes the graphics tell a story too) and/or much information on the source of the patch. Where HALion is overwhelmingly complicated, with a lot of completely unnecessary buttons, Omnis is simpler and faster to use. Steinbergs Mediabay is something that some like and some dislike. I dislike it. I have been working with relationship databases since 1993 and to my knowledge the Mediabay does not hold up to standards of a “great” GUI. It is a programmers GUI and not a user GUI. A “great” user GUI you can find in Omnisphere.

And btw, the procedure you described for installing 3. party stuff in HALion, did not work with the presets in question.


… writing as a long time user (and software developer), it seems that the business model is market-driven (and not product driven {as to be honest Steinberg once were} sell, up-sell, cross-sell , release new version (and involve the users community to participate as alpha/beta testers), and then, get all ‘GlossWare’ with more marketing and inferences of what we need and what the new version will deliver.

(Q) what are the other “big topics” for next version : now|wow that we have been hinted that a “more convenient” patch browser will be available

Where is the innovation, the product leadership,
I hope to see the ‘technology ball’ picked up again, and you run with it.

… as you can see by my ‘hope’, I like most of your users out there want you to succeed,
and maybe Steinberg is just relying too much on our loyalty over the last 10 years or more,
because, seriously - you are letting us long time users down.

What’s the logic or reasoning behind that?

We don’t want the users to update to HALion 6 because of bug fixes, but because of the new features and improvements. All bug fixes that were done during the development of HALion 6 will also be available for HALion 5 customers within the final maintenance update.

Thank you for explaining the reasoning!

IF they give us the MACRO page with editor like I have asked since 4 came out, filling up the surveys and what not, and have it running rock solid, (AS IT SHOULD) you can rest assure that HALion would be on the top of any sampler right now. We have very little companies doing libraries or anything to be a competition for Kontakt. Right now we are a joke to them. “HALion? ehg!”

I’m not the CEO nor the owner of Steinberg and I’m more embarrassed than they are.
I have more pride and determination to see Steinberg kick some competition’s butt.
But I can’t promote HALion in the current state. I can’t create content if it would crash on me with a simple Drag and drop.

Matthias Quellmann! If you hold on the update past the release of H6, you are forcing people to jump to H6 and then there is no reason to be on H5.
I don’t think they see the point that its not a good practice to play around with their customers like that…The H5 update is embarrassingly delayed. FEB 2015 till now late, post H6 late. :frowning:

I hope they can read the passion and frustration in my words and not that I’m trying to bash.

Problem signature:
Problem Event Name: AppHangB1
Application Name: HALion 5.exe
Application Version:
Application Timestamp: 54b8eef4
Hang Signature: 2b1e
Hang Type: 2048
OS Version: 6.1.7601.
Locale ID: 1033
Additional Hang Signature 1: 2b1e4108ba6ebf1eb5788b9bc3be390b
Additional Hang Signature 2: 3191
Additional Hang Signature 3: 3191064041925227a78bca9a96123de4
Additional Hang Signature 4: 2b1e
Additional Hang Signature 5: 2b1e4108ba6ebf1eb5788b9bc3be390b
Additional Hang Signature 6: 3191
Additional Hang Signature 7: 3191064041925227a78bca9a96123de4

All the time… just tried to load a patch and it can’t find the sample for whatever the heck reason and I can’t stop the search. it freezes. Can’t even capture the screen…

Hi Salvador,

I can assure you that we not holding back anything and we are definitely not playing with our customers. The H5 maintenance update will be available close to the release of H6, so that all of the fixes of the H6 development can be implemented in the H5 update. There is a team of quality assurance engineers constantly working on HALion and the other instruments. Before every release there are months of beta testing to make sure that the software works as expected. Of course there can always be bugs (we are talking about software with thousands of lines of code…), but we would never release a version knowing that there are crash bugs. As I mentioned before there is a whole team at Steinberg that has created HALion 4 from scratch. Since The Grand 3 and HALion Sonic 1 all of the VST instrument have been developed by this team and we are very passionate about our work.

So please, let’s work together on this one. I will send you a PM with my email and it would be great if you could send me the crash log so we can have a look at it.

Logs Sent…!

Just to balance out perspectives here (and companies like Steinberg do listen to and consider many different perspective).

One of my favorite things about Halion is that “I” get to design the UI. I don’t have to conform to someone else’s cheesy work flow ideas. It’s a power user’s dream, in that I can design a UI that spreads across three monitors and shows tons of information in a single window, or I can make a very simple single instrument 600x400 UI that only shows the ‘tactile’ basics. I can make it ‘visually’ appealing with lots of pretty graphics, or I can make it look like a power user’s binary data tank. I can split, drag, pop-out windows and frames and make it MY UI.

I’ve no problem seeing waveforms and such in the Cubase/Halion Media Browser. While icons and such would indeed be nice for some users to have in the relational database (and not that difficult to add at some point), I’d personally elect NOT to use those features for my own projects if given the choice. I’d rather not have a 4meg bitmap image taking up space on my relatively expensive SSD media when text gets the job done just as well (and is fully searchable). I’d rather NOT have a window or dialog take up massive amounts of screen real estate (I use three screens, and it’s still not enough). I’m seriously buggered by the ‘progressive RACE’ to make things so ‘user friendly’ that we can’t just hit a key combo and type in three letters to find what we need anymore. I’d much rather spend an afternoon reading a manual than many minutes every single day scrolling windows that take up too much screen real estate looking for ‘image based visual cues’. I’ve no problem with a db that ‘supports’ tagging with images and icons…but if it’s forced on me, and if I lose power searching functions and ‘documentation’ in the process…I’ll be pretty upset.

Case in point…Opera Browser with Prestige and earlier engines was a total JOY to use. Not only was it the leanest and fastest browser out there…it had all the best POWER USER features in one simple installation, under ONE user agreement/contract. Now it’s a one tab, third party ‘plugin’ nightmare that needs far more resources to install and use, is arguably less secure, and ‘relies’ on third party ‘plugins’ to get a single ‘power user’ ability. Push-centric…app-store…crap. I hope Halion doesn’t attempt to do the same sort of ‘user/consumer’ friendly thing. I want Steinberg’s tools to be a PRODUCER of content…not so much to be a ‘consumer’.

I’ve had ‘third party libraries’ for various products, including Kontakt, ARIA, etc…which can be a pain in the rear to install and get working. The ‘library’ wasn’t built correctly or was poorly documented, etc. It wasn’t the fault of NI, or Plogue that someone put a garbage library out, and was too lazy to make and test an installer for it.

I’m far from a ‘programmer’, and my so called IQ and ‘education level’ is actually on record as being ‘quite low’, but I have no problem making an installer for Halion content that extracts things to a sub directory of one of the default directories holding factory Halion content. I can even make it put the content on any ‘removable’ device I want and implement plug and play scripts that’ll drop file-system links into these default directories ‘as needed’. It’s really not that difficult to do with free multi-platform installer tools.

If I were going to sell or otherwise mass distribute a library for Halion 5, I’d take the time to get advice here on the forums, and also contact the Halion Dev team (providing samples of my Library) to see how they recommend packaging and distributing it so end users will not face the installation problem you’ve described. It’s really not that hard to get the information and support required.

There’s a point where I’d rather not pay a premium for ‘rebadged tools’ (such as basic archivers and extractors) we’ve all bought, paid for, and had at our disposal for decades. If Steinberg decides to either develop and service their own, or pay the royalties to rebadge and bundle some other company’s installer tools, then the total cost of the product goes up (even for users who have no intention of packaging and selling their libraries). The more of that kind of stuff a sound engine developer packs into a product, the more resources they must dedicate to supporting and maintaining them…across all of the wild and wacky ‘OS related’ standard changes that seem to come every few months from the likes of Microsoft and Apple.

I believe that Halion 6 is highly likely to include more of the power tools that third party content developers have been asking for. Perhaps it’s been a ‘long time coming’, but it’s not due to a lack of effort and dedication from the “Halion Team”. I’m eager to see what direction it all goes. It’ll be interesting to see how they manage the pressure to copy cat the dumbed down ‘consumer driven’, subscription based rapid prototyping and app-store models, vs keeping a solid focus on providing power user ‘production tools’ for ‘producers’ to ‘create with’.

I’m cool with user friendly. I just don’t want to lose, ‘user choice’, and ‘power’. I’m also getting frustrated with being forced to pay multiple times over for technologies we’ve already paid for and mastered many times over as general personal computer users (such as reading a REAL product manual, then making a simple self extracting archive/installer with a few user options on launch). I get pretty tired of paying twice as much for a bundle of tools we’ve already got, or running into brick walls in apps that point us to ‘third party app stores’ demanding ‘cloud based subscriptions’ to get anything done.

This is good to hear and very appreciated.

I’m far from a ‘programmer’, and my so called IQ and ‘education level’ is actually on record as being ‘quite low’, but I have no problem making an installer for Halion content that extracts things to a sub directory of one of the default directories holding factory Halion content. I can even make it put the content on any ‘removable’ device I want and implement plug and play scripts that’ll drop file-system links into these default directories ‘as needed’. It’s really not that difficult to do with free multi-platform installer tools

Hi Brian.

Could you explain that, please?
I’d be very interested in how you create an installer for Halion content. Do you mean user content?

I know you already explained how to move content and create file-system links in other threads.
But I didn’t know you can actually create an installer.

Yes, I mean making an installer for user content libraries that you wish to distribute to other systems/users.

The simplest form is to use your favorite archival program and set it to make self extracting files. Set flags that allow the user to extract it to the same directory structure that the archive was made with. Some of these self extracting files can also be set to run batch files or other scripts after detarring/decompression.

One can also perform a search to find a variety of tools for creating installers for PC and Mac platforms. I.E. MSI or PRG files that self extract and run BATCH files or other scripts, while presenting users with options.

The general idea would be to provide the user with a self extracting file that puts complete VSTsound archives in one of the directories that Halion already scans for content by default on a regular basis.


Thanks Brian.

It’s Thursday, the days on which VST stuff always is released. So how about a surprise release of Halion 6 today?

Well, I have to disappoint you regarding a surprise release today, but I can confirm that H6 is planned to be released on a Thursday.

:smiley: today maybe ? :wink:

Maybe next…or… :wink:

The point of this is the fact the current version had no support, no matter how much
you want to talk about the next version. this is wrong !
they say the HAlion team is committed and hard at work, well when did they start
to do that, is 6 going to be the same ? release it and forget it…
:imp: :imp: