Updating H9 for CrushStation and Pre/Post Routing Options

you have to update the latest version of h9 control app as well

oh…..i missed that part.  thanx

Is OSX 10.5.8  insufficient for new H9 upgrade?  Up until I downloaded the new control app the old control app worked great.  With an H9 and Timefactor. As soon as I downloaded and installed the 2.4 app it quits immediately. 

We didn't intentionally drop support for OSX 10.5.  What happened was that Apple started requiring that the iOS version of the app be built against iOS 8 with 64 bit support.  So, we had to upgrade to the latest version of the framework H9 Control is built on top of, and apparently, that's causing problems on OS 10.5.  

We should be able to give you a build of this version of the app that will work on Leopard next week.  We had one ready to go built against the older version of the framework we're using before we learned about Apple's rule change.  For now here's a link to the previous installer: https://s3.amazonaws.com/com.eventide.downloads/Installation+Files/Installation+Files+Stompboxes/H9Control_230_MAC.dmg

I'm not sure if we're going to be able to continue to support 10.5 in future releases.  We'll have to look into what's causing the problem(s).

Thank you sir for the prompt response…Perhaps i should just upgrade to snow leopard 10.6 for $20.00?  Would that keep me cool with at least a few more updates?

Let me check that on Monday.  We should have a Snow Leopard machine in the office that I could try the latest build out on.

Perhaps i should just upgrade to snow leopard 10.6 for $20.00?  Would that keep me cool with at least a few more updates?

I just checked the latest build on Snow Leopard, and it works fine on Snow Leopard.  If you updated to Snow Leopard, you should be good for a while.  Eventually Apple will force us to build against iOS 9 of course just like they did iOS 8, and we'll have to upgrade again to the latest version of the framework we're using.  But iOS 9 hasn't even been released yet and who knows if doing so will even cause us the same problems as building against iOS 8 did.  

https://www.youtube.com/watch?v=X0VrNnnn4l0

Is the Sag parameter turned up?  This can act like a Gate. You can just turn it down if so.  Also, if the Gate is ON and your guitar signal is somewhat quiet this could happen.  Either turn the Gate OFF or increase the Input Gain into the H9.  

Do either of those suggestions help? 

https://www.youtube.com/watch?v=X0VrNnnn4l0

Is the Sag parameter turned up?  This can act like a Gate. You can just turn it down if so.  Also, if the Gate is ON and your guitar signal is somewhat quiet this could happen.  Either turn the Gate OFF or increase the Input Gain into the H9.  

Do either of those suggestions help? 

What I didn't do yet is to update the H9 app, I mean, I tried more than twice but when I unzip the folder it says "unable to open H9Control-2.3.0-osx-installer because impossible to confirm developer identity". So I don't know what else to do, the iMac and the H9 are with me together since 2014 and this gap drives me crazy. I would appreciate any help

Ok, to open the new release of H9 Control despite that warning, click on the Apple in the upper left hand corner of your Mac, open System Preferences, go to Security & Privacy, and in the first page set the 'Allow apps download from'  setting to 'Anywhere'.  Then, open and install H9 Control.  When you're done, you turn that security setting back to what it was if you like.

We do sign our installers for H9 Control so normally you shouldn't see this message, but Apple changed the way that their signing worked at 10.9.4 I think, and ever since then people using systems below 10.9.4 have had sporadic problems running our installers.

I set my H9 up for the pre/post setting. So far it's working great, though something happened and I'm not sure how. I got it set up and then activated the tuner. The signal was coming through despite being set to mute. As well, the tuner was having a real hard time tracking notes. I turned it off and on and it worked fine, but I really hope this doesn't happen during a gig

My colleague, Nick, was recommending that people reset their system settings after updating if it caused no great inconvenience to do so.  For some reason with this update in particular, people's system settings were getting messed up which was causing odd H9 behavior.  That may explain the strange tuner behavior you were seeing.

Is there any plans to be able to assign a Pre/Post setting to the defaults without having to save a duplicate copy?  It’d be nice so I don’t have two copies of a bunch of settings that make things on my screen a little more crowded.  (Even if we couldn’t change each preset individually, it would be nice to assign a Pre/Post routing default to an entire algorithm.  i.e. I don’t think I’d ever place something like “Blackhole” in front of my crunch section so it’d be nice to just say everything in that section defaults to Post and I can change it to Pre on an individual basis.)

Thanks!

Same here – there are some algorithms I’d rather defaulted to Post and if I ever wanted to change them I’d do that – at the minute I have to change almost everything to Post and only have a small handful that are Pre

Same here – there are some algorithms I’d rather defaulted to Post and if I ever wanted to change them I’d do that – at the minute I have to change almost everything to Post and only have a small handful that are Pre

Ditto. They released this with the CrunchStation update right? Most of the presets on my the box should be post IMO, or at least they will be in my setup. I think that would be nice to change the factory defaults per algorithm and then you can make individual user presets if you want to have some different.

Is there any plans to be able to assign a Pre/Post setting to the defaults without having to save a duplicate copy?  It’d be nice so I don’t have two copies of a bunch of settings that make things on my screen a little more crowded.  (Even if we couldn’t change each preset individually, it would be nice to assign a Pre/Post routing default to an entire algorithm.  i.e. I don’t think I’d ever place something like “Blackhole” in front of my crunch section so it’d be nice to just say everything in that section defaults to Post and I can change it to Pre on an individual basis.)

Thanks!

Same here – there are some algorithms I’d rather defaulted to Post and if I ever wanted to change them I’d do that – at the minute I have to change almost everything to Post and only have a small handful that are Pre

Ditto. They released this with the CrunchStation update right? Most of the presets on my the box should be post IMO, or at least they will be in my setup. I think that would be nice to change the factory defaults per algorithm and then you can make individual user presets if you want to have some different.

I’m guessing no word on this?  Love the pre/post feature but hate having to constantly switch the factory patches to “post”.  Even just a global setting to default all factory patches to “post” would be fine by me.

Why did you come with this great option of Pre/Post positioning and not thinking of setting In1 and In2 level gains separately in that only case?

Actually I have the Post (In2/Out2) H9 set in an FX loop. But this loop level is preset and it clips nearly systematically In2 whereas In1 (direct guitar) tops around -20dB.

The trouble comes only for the (clipped) sound going into the H9/Post Input, as my preset loop provides a good level regarding the overall output, and the poor level that may go into In1 (but that's not quite the problem for me).

The hardware design was done WAY before we thought about adding the pre/post feature.

The H9 is designed for guitar inputs – if you feed it from a hot effects loop it will overload the front end, meaning no gain controls or software would unclip it. Sorry.