Hi Folks.

Got this issue in BIAB (64bit) when using Halion Sonic. When I try to adjust volume of individual tracks in Halion. (I set Halion as a default VST).
The error is this:
Address violation at address 00000000269FB100 in Module "Halion Sonic.dll"
Read of address FFFFFFFFFFFFFFFFFFFFFF

This happened at least 5 times, so it is not a random thing. Couple of times I tried to send error log to PG from the program, on second occasion whole thing (BIAB) just froze.

Can anybody suggest how to fix this?

Thank you,
Misha.

there's ANOTHER file that needs to be collocated with with the .dll called "HALion Sonic.srf"

Larry

Larry, thank you for the reply!
Can you please explain what to do with the file in BIAB: HALion Sonic.srf
To stop "address violation" crashes?

Thank you.

Address violations are often related to permissions. You can either try 'take ownership', a registry tool, or reset your permissions with Tweaking.com 's free Windows Repair AIO. There's a portable version around too. Use it in safe mode, the program has an option to reboot in safe mode. While at it you can repair the windows installer and run SFC.exe ..F

nothing you can or even should do with it - it just needs to be where the .dll is

- as far as other issuers see fiddlers response

Thank you!!!

Unfortunately did not help.

1) HALion Sonic.srf is where dll is.
2)I changed permissions to full
3)run BIAB as administrator.

Everything works well in Sonic except when I try to change volumes on channels.

More... When I try to "Send" error log to PG through their reporting system, BIAB crashes (becomes unresponsive)

I believe I saved the error log to PC, if PG wants to help or need my help to try to figure out why their own reporting system crashes BIAB, you are welcome to contact me.

Thanks.

Location: C:\Program Files\Steinberg\VSTPlugins\HALion Sonic

Lol, just today i had volume issues too in Cubase .... had to use the slider in the HS mixer to set it right.

BIAB: Try channel 16, i had some issues with sound, and found it worked there only for some reason with BIAB 2019 x64.
Later i changed it to Main, without further problems. See picture:

Thanks Fiddler, switching channel did not work.
Per suggestion from PG tech.... I re-installed H.Sonic. Did not do it. It crashes when volumes on HS are moved. Strange thing is... I have tried a midi file that had volume program changes, sliders were moving like a brand new train on oiled tracks-no crashes. Happens when I manually move them. With several other indications, I am 90% sure it is BIAB bug. It works solid in DAW and other places as VST.

OK you are correct - I was able to duplicate similar HS as well as in the full HAlion 6 itself (when I use the volume in the instruments rack slot)

For HS:

I CAN change overall Volume (top middle of HS screen) or even the mixer windows FX1-FX4 sends even with OUTPUT set to 16 (far right hand side of MIXER window part/track) – it sometimes moves up or down a little with NO CRASH but more than a little and I get a crash (obviously in a different memory location – but a crash nonetheless (actually it’s an access violation at a memory address with a an all “F” read at that address = means it sees max machine negative value – means nothing to me without source code or machine code )

As soon as I try and change the volume or Pan in the same mixer window (or in case of Halion 6 in the tracks slot window) and try to change an individual parts/tracks volume I get a crash - same (similar) error

but I also get a pop-up with option to send PG the crash log – did you FORWARD that info (like the attached which I sent one for both HS and full H6 just did to help them trouble shoot?)


Larry

I had several GUI problems with plug ins. I thought then they were Cubase 10 related. Turned out to be Visual Basics installed. I downloaded all the latest, both x96 and x64 versions from Microsoft, also the obscurer ones i could find, 2011, 12,13 etc. and DotNet (472?) De-installed all the ones from Windows, and reinstalled the lot, IN SEQUENTIAL ORDER by date. You could check your graphics drivers too. Some say when possible you should turn hardware acceleration OFF. Reinstall DotNET too.

On the Steinberg forum: Halion 3 crashes

You could check your DirectX too, DXDIAG, built into windows somewhere ...

PS i have still appearing audio stutters, but only when i am time-stretching and pitching in Cubase's audio editor. Can't find that one but IMO also Graphics related. Frigging windows, once it runs it's fine, but GRRR at times. -F

Larry, Thank you for your time and testing!

A person from PG (no names) was extremely rude to me when I called about this issue today. I did not expect that. I was trying to make a point, that H.Sonic works everywhere seamlessly except for BIAB.
I sincerely hope that it is not usual behavior for that rep and it was just a rare event - a result of long day stress.

Larry, yes I tried sending the report. As soon as I click that send button BIAB freezes/crashes.
If (If I do not click it, I am able to revive about 1/2 of the time)

This is not a random thing. It directly relates to how BIAB handles this VST. Sonic Halion is the only professional GM MIDI VST available that is up to date. PG, please look into to it.

I mentioned (to the same rep) that BIAB crashes when I try to send report. I hope that it will get fixed too.


P.S. I will not call again concerning this issue, but In case this post is read by the rep that answered my call today: I followed your suggestion and completely re-installed Halion Sonic. As I suspected, it did absolutely nothing. BIAB still crashes when volumes in HS are moved manually. HS still works perfectly everywhere else.

well I sent in my one for Halion Sonic and one for HAlion full v 6 - so we'll see

I know there are other here that have HAlion 6 (as well as Sonic) so maybe they could chime in if it works in 64 bit BIAB or not : Just move the part's volume slider (not the master vol.) or pan back and forth and see if it crashes

Larry

Larry,
I am using 64bit. As I mentioned, it works absolutely perfect in other software or as a VST or standalone.
I am glad, you were able to send the report and it did not crash your BIAB. You mentioned feedback from people who are using 64bit BIAB.... Are you using 32Bit?

What I am afraid of, and I hope it is just that one person who I spoke to yesterday at PG, is in state of denial about this H.S. issue. I actually bought H.Sonic for the most part, specifically to use it in BIAB...

In my opinion, this is what PG should do. If they do not have H.Sonic on their test computers, download a 30 day demo and pinpoint exactly what is going on. If they need my help in testing, they know how to find me. I will not be calling about this issue again as I do not like to be insulted.

Thank you.

working with PG now on it

I'll give this a try this weekend with Halion Sonic.

John,
Thank you for willing to test... But I would not even go there.
If Larry was able to replicate the problem in same manner that it got me , it exists.

I am very sure the problem is with BIAB / How it handles the plugin.

If you google:"access violation" "halion sonic 3" you will see that this is not a global and most hits point to this post.

P.S. As it goes: First step to recovery is acceptance. Until PG looks at it, I doubt users can resolve this.., but who knows?

Misha.

Actually the more folks that test it and REPORT it to PG with details, assuming they have issues, the better.

I also reported that this THREAD was here when I replied back to a support email this afternoon with more details from my end.

Larry

These BIAB crashing issues were driving me absolutely nuts.
I think I fixed it. So far no crashes when using H.S. channel volumes or other VST settings.

What I did:
1) Uninstalled H.S. (I reinstalled it before, did not help)
2)Uninstalled BIAB
3)Clean install Halion Sonic version 3.2.10.94 (64 bit) Oct 12/2018 (latest)
4)Installed BIAB w latest 612 build.

I hope this helps to somebody in same situation.

Misha.

I got the same result. I used Halion Sonic as my default sound source. As long as I left everything on the mixer (in Sonic) alone, everything seemed to work fine. However, once I started moving the sliders around, I got an exception error and ultimately BIAB crashed on me.

So I can confirm this is an issue.

John,
See my post above. I think it fixed the issue.

Also, I was getting crashes and complete BIAB shut downs (no errors or such) when I changed filter / EQ parameters in Sonic.

Seems complete re-installation of both programs fixed this.
Version of my H.Sonic is: 3.2.10.94 (64 bit) Oct 12/2018 (latest)

Glad you got it sorted Rusty.

What do you guys think of the sounds of Halion as a default synth compared to TTS-1 or others that you may have?

Was first aware that I could use Halion when Fiddler mentioned it, and have to agree with him that it sounds better than others as a default synth.

Just looking for more opinions here.

musiclover,


It is a bicycle vs car question.
H.Sonic is the king of GM playback (*software) as of today. To my knowledge....
TTS-1 has its place (I think development stopped about 15 years ago)

I think H.S. should have a demo. Try it

Nope even with new 612 build I still had the issue and I have latest HS and Halion installs. Now that John also reports the same issue - it work until using mixer/part parameters, so there is a real issue.

This might even occur in NON Halion stuff - when I have time I will load up some other complex/multipart capability VSTi's and play around with them.


Larry

Larry,
I reinstalled both, BIAB and H.S. and this crash thing is gone for me.

Two things that I did not mention:

A) I reinstalled H.S. by re-downloading it from Steinberg updater program and secondary package to update Halion Sonic to 3.2.10.94 Check your VST version (Click on Steinberg logo in VST-->About)

B) There was a recent Windows update that was pending (Win 10).

So far crashes are not coming back. I was pretty rough on mixer and other controllers of HS, while several channels were playing just to test it.

Misha.

Guess that's why mine seems to work OK. PS I have windows update switched off, and let an external application suss out and manhandle the really needed updates.

I already had the latest Halion Sonic (and I have it because I have Halion 6, so you automatically get Sonic as a bonus) before I ever installed BIAB. I'm going to wait to see for a better solution before uninstalling and re-installing.

John,
you can try downloading just the update package for Sonic 3 (it is a separate package), it is relatively small and reinstall just that. Might do the trick. That should not touch your libraries.

Check H.Sonic VST version. Should be this: 3.2.10.94 (64 bit) Oct 12/2018

P.S. So far, knock on wood, no crashes for me.

I just tried for the first time using halion sonic 3 as the default synth with program changes set to GM mode and was able to change volume in the plug in without a crash (so far!). I never changed the default synth before, so now I think I will play around with this. Can one use different plugins per instrument? Might be interesting. FWIW, I am on the latest version of Windows 10, BIAB 612 and latest Halion/Sonic.

try the pan and volume on the PART i.e., open its mixer and change vol/pan's ?

While being rude fixes nothing. I've gotten mad over this & in turn so has support,but NONE of this is the consumers fault. I'm live on the gig with Access violations between every son g really makes me look bad to the owner & management. Good luck(we all need it)Jim

Jim,
if you have "Access" issues with Halion Sonic 3, try my method in this post. It worked for me. Testing for 3rd day, so far stable.

Misha.

Jan 21st same problem since December 17th.

tried the latest version, there should be something fixed: HS SE 3.2.15

(For Halion Sonic the latest is 3.2.10)

I'll have to look at the version this evening.

John

Yes do that I still have the "crash" when moving vol and pan and I have PG support aware of it and they have responded twice I've not heard more back since they recommend I use the then latest 612 build, which didn't fix it

and neither does current 613

if you still have issues then when it crashes (more often using pan then vol) send of the debug that comes up to PG so they have a second sample

FYI I'm still on Win 10 pro Version 1803 (latest build 17134.523) NOT the "October surprise" one that they JUST released (and may pull back yet again)

Larry


EDIT I didn't see the 614 build of BIAB so standby..... Yep same crash so 614 still didn't correct issue with Halion

Just read these recent posts is about Halion3/6 (also Sonic) and the latest updates on the Steinberg Halion forum:

=============================
MOD MATRIX Offset default BUG

#1 Unread post by abject39 » Thu Apr 05, 2018 6:04 pm
This isn't particularly a bug but I am almost certain it is a program error. The mod matrix sources offset defaults to -100/-200 instead of 0. It is a bipolar parameter that seems to default in a unipolar manner. I assume this is a mistake.

To reproduce...

1. Open an initialized program in Halion.
2. Navigate to the edit/zone tab.
3. Scroll to mod matrix.
4. select any mod matrix source.
5. Hold Ctrl and click Offset. At this point the Offset will go from 0 to a negative value instead of centered.

---------------
Re: MOD MATRIX Offset default BUG

#2 Unread post by Gerrit Junge » Tue Jan 22, 2019 3:13 pm
Hi abject39,
I'm able to reproduce it here. Its now in our Defect-Tracking-System and listed as Bug-ID "HALLY-7733".
I hope we can provide a fix for it soon.

Thanks for your report and please accept my apologies for any inconvenience caused.

============================================================================
About a steinberg registry-fix called d2dfix.reg:

----------------------------------------------

New Issue!

#3 Post by Fantacyzer » Wed Dec 12, 2018 6:02 pm
Since 6.2 there is a new issue: when the d2dfix.reg is activated (Intel HD graphics), cascaded sub menus are not shown. For example - click on modulation matrix "Source" and you'll only see a list of the main menu entries, no indicators of sub menus. Futhermore the selection hook of selected menu entries is not shown.

Obviously the menu font has been changed. The new font ist rather unreadable and probably leads to the above described problems. The previous menu font was perfect - why had it been changed?
Top
--------------------------------------

Re: UI Glitch Query

#4 Unread post by Gerrit Junge » Thu Jan 17, 2019 7:35 am
Hi Fantacyzer,
we had to change several things for a better HiDPI support. I'm able to reproduce it here. Its now in our Defect-Tracking-System and listed as Bug-ID "HALLY-7728". I hope we can provide a fix for it soon.

Thanks for your report and please accept my apologies for any inconvenience caused.
Gerrit Junge
Senior Quality Engineer
VST Instruments
Steinberg Media Technologies GmbH
Top

====================================
Moral, there are some bugs with Halion, probably Intel graphics related.
F

I am confused about your post Fiddler - what are you trying say with that post of posts?

Since the crash we, or at least I am talking about,ONLY occurs in BIAB 64 bit, it does NOT, repeat does not, occur in 32-BIT BIAB (yes JBridged to 64 bit). So I would suggest it is something that PG side of the house needs to dig into before looking at Steinberg for a cause & solution.

(and I am no Steinberg fan boy - nor am I a PG "basher."))

Larry

Only that there are (more) problems with Halion Sonic (&SE) related to f.i. intel graphics. Steinberg is in the process i think of overhauling graphics in relation to HDMI. Cubase 10 seems loading so much faster compared to 9.5. And that Gerrit Junge is the Halion Sonic man there .... if HS is updated we might see some fixes, and BIAB might not be the problem, only maybe in relation to graphis etc. Read somewhere that if you have a graphics card with an assignable Hardware Acceleration option, one can better switch it off.

Haven't looked at this or used Halion with BIAB since last post here and last report to PG back in Mid Jan.

Finally got a reply from PG today (they've been busy with other thigns ) they (Kent) says it's all fine on their end.

So I fired up 64-BIT BIAB and switched VSTi to Halion 6, been playing with new Sampletank 4 MAX and remember I use 32 bit BIAB, I have no issues with anything at all that way and I'm a big believer in: "if it ain't broke don't fix it!"

In any case, at least with current BIAB release 622 PG Kent is correct - I cannot seem to crash BIAB using Halion 6 and only change was which release of BIAB I am using.

So I suspect OP probably has no more issues either at this point??

Good Luck
Larry

I still tend to think Halion's issues are graphics and GUI related, not BIAB's fault. Had problems again with volume changes controlled by Cubase; NoGo.

Before it worked fine, but i had to reinstall some old plugin, and some doggone old Visual Basic 2008 C+++ overwrote something probably that was OK earlier i guess. Wish that all these software makers get their acts together, and the culprit of all is of course Micros ****.

Hi,

I spent a big chunk on Halion 6 on Friday, and on Halion Sonic today, trying different styles and patches, and changing volumes, filter settings, envelopes effects, etc, and haven't been able to trigger a crash yet.

If anyone is still having trouble with these plugins, please let me know. I have Sonic installed, and am happy to keep trying to replicate the problem if needed.

Thanks
Kent
PG Music

Thnx for the offer ... i occasionally only have problems with midi controllers, and can't get my finger behind it why it works at times. Some Steinberg forum posters also mention similar issues.

PS you know the trick how to keep all the large *.vstsound Halion files off your boot drive C's user or common files folders? Do a search, cut/paste them elsewhere, create shortcuts for them there, and cut/paste the shortcuts only back to the original location where the large files were before. F

Another thing that could be crashing Sonic for some users is NVIDIA Video card driver. I had severe crash issues with Sonic standalone and VST. Tried many things, but then gave up and sent crash log to Halion team in Germany.

Their solution worked. Pasting from email:

I have heard back from the team in Germany, they found crashes in the Nvidia card, windows components and dependencies.

They are recommending initializing preferences for Halion Sonic (See link below for initializing preferences), then repair of the 2017 redistributable and the .net framework. Also they recommend reinstalling the Nvidia Driver.

The instructions for clearing preferences are below. The instructions are writing for Cubase but apply to most of our software.


Instructions for Initializing preferences, go to the section on initializing preferences.

https://helpcenter.steinberg.de/hc/en-us/articles/206618850-Troubleshooting-for-Cubase-Nuendo-and-Sequel-on-Windows

Thanks. That worked ...

I've been using Halion Sonic (I have the full Halion 6, but this is a lightweight way to have a GM synth and I'm pretty sure the GM-designated sounds in Sonic are the same as in the full Halion). I use it in GM mode as the BIAB default synth. It has worked great so far, but the one thing I recently noticed (this morning) is if I change instruments on a track at a specific bar (using F5), it seems to take a beat before it kicks in. So on beat 1, I hear the previous instrument and then the new instrument on beat 2. It would be great if someone could check that out on their system.

I noticed that some times a persistent patch change was impossible to remove from the (multichannel) melody track in BIAB. You could check that in the pianoroll editor window, select the track and adjust the info from velocity to program changes ..

Added info: happens especially with imported midi files i think, the fix used i done is editing out the program changes in Cubase first.

I'll do that, but I know that when I imported the MIDI from my notation program, I deselected patch changes, so that I could set them from the BIAB program rather than having them hard written to the MIDI stream.