Tagged: H9000R Network
- This topic is empty.
-
AuthorPosts
-
-
April 17, 2019 at 9:38 pm #115290
donrwatters
ParticipantHi,
I’ve finally gotten over the initial learning curve of managing things through the Emote application for the H9000R, but I haven’t found a solution for managing the network interface settings within the Emote application. How do I set the Subnet, Default Gateway and IP address on the Ethernet interface, through the Emote app? As a work around, I was able to see the IP address being presented back to me on that interface, by mousing over the H9000R in Emote. Then I just set everything in the network to match that interface and subnet. I assume that the current Ethernet settings are the settings of the test lab or something…so, now my home network matches the test lab, yay! But, I’d like to be able to control the IP address, subnet mask, default gateway, etc for either the Ethernet port or even the Wifi Access Point.
Thanks in advance for any pointers you can pass along.
— Don
-
April 17, 2019 at 9:47 pm #151754
It seems this was an oversight for our H9000R customers — we only recently added static IP configuration in the H9000 software and it hasn't been added to Emote yet, but we should be able to do this fairly quickly within the next few days.
-
April 17, 2019 at 10:56 pm #151755Participantjfirlik wrote:
It seems this was an oversight for our H9000R customers — we only recently added static IP configuration in the H9000 software and it hasn’t been added to Emote yet, but we should be able to do this fairly quickly within the next few days.
Thanks for the speedy reply. I can appreciate that some things are missing in Emote. It’s fine, since there’s a work around. I just wanted to make sure that I wasn’t missing it in the application.
-
April 24, 2019 at 6:20 am #151787Participantjfirlik wrote:
It seems this was an oversight for our H9000R customers — we only recently added static IP configuration in the H9000 software and it hasn’t been added to Emote yet, but we should be able to do this fairly quickly within the next few days.
If there’s a wish list being formed, I’d also like to be able to name the H9000R within Emote, please and thank you.
-
-
May 6, 2019 at 2:34 pm #151855
These changes are in the pipeline. It required a change to the H9000 software as well, so there's a little more testing to be done but we hope to have a new release soon.
-
June 14, 2019 at 3:01 am #152105Participantjfirlik wrote:
These changes are in the pipeline. It required a change to the H9000 software as well, so there’s a little more testing to be done but we hope to have a new release soon.
Any chance of hearing about a release timeframe for the updated software? My H9000R has been misbehaving on the network lately (not staying connected on Ethernet or on Wifi) and it’s really difficult to troubleshoot, since I’m unable to change any network settings or set the IP Addresses. Will we also be able to set the Dante IP Addresses after the next update?
-
June 17, 2019 at 5:50 pm #152124donrwatters wrote:jfirlik wrote:
These changes are in the pipeline. It required a change to the H9000 software as well, so there's a little more testing to be done but we hope to have a new release soon.
Any chance of hearing about a release timeframe for the updated software? My H9000R has been misbehaving on the network lately (not staying connected on Ethernet or on Wifi) and it's really difficult to troubleshoot, since I'm unable to change any network settings or set the IP Addresses. Will we also be able to set the Dante IP Addresses after the next update?
We're planning to push out a minor 1.1 update sometime this week (most of our focus has been on the next major release which is close to beta). It will contain static IP functionality for the H9000 control port. For Dante, this can't currently be done on the H9000 itself but it is possible through the Dante Controller app.
-
June 18, 2019 at 1:05 am #152128Participantjfirlik wrote:
We’re planning to push out a minor 1.1 update sometime this week (most of our focus has been on the next major release which is close to beta). It will contain static IP functionality for the H9000 control port. For Dante, this can’t currently be done on the H9000 itself but it is possible through the Dante Controller app.
The update will be a welcome upgrade to what we have now! Thank you so much.
As for using Dante Controller to update the IP Address for the Dante Card, I’m not saying that you’re wrong, but my experience is different. The message that Dante Controller gives me doesn’t really jive with what you’re saying. Maybe I have something configured incorrectly.
-
June 18, 2019 at 11:39 pm #152136donrwatters wrote:
As for using Dante Controller to update the IP Address for the Dante Card, I'm not saying that you're wrong, but my experience is different. The message that Dante Controller gives me doesn't really jive with what you're saying. Maybe I have something configured incorrectly.
Hmm, perhaps you need a Dante firmware update. Here are some corresponding screenshots from one of our Dante cards. Could you check your firmware version?
-
-
June 19, 2019 at 12:18 am #152138Participant
It looks like that’s the culprit. I’m on Firmware 3.7.1.10. Where does one find the firmware? I hope it’s not in Emote. Anytime I try to click “Updates” on the Devices tab in Emote, the application crashes. Is there a download on the site, that isn’t in the normal download area? I have the Dante Firware Updater, but still need the Brooklyn II firmware file for v4.0.
-
June 19, 2019 at 12:08 pm #152139donrwatters wrote:
It looks like that's the culprit. I'm on Firmware 3.7.1.10. Where does one find the firmware? I hope it's not in Emote. Anytime I try to click "Updates" on the Devices tab in Emote, the application crashes. Is there a download on the site, that isn't in the normal download area? I have the Dante Firware Updater, but still need the Brooklyn II firmware file for v4.0.
We haven't published the firmware to our web site downloads area, which we probably should. For now, we can upload it to our file share server and you can get it from there. I haven't done this in a while but I think you can just use the Dante firmware manager to install it.
We'll follow up with a link to the firmware file once it's uploaded.
-
June 19, 2019 at 2:54 pm #152141donrwatters wrote:
It looks like that's the culprit. I'm on Firmware 3.7.1.10. Where does one find the firmware? I hope it's not in Emote. Anytime I try to click "Updates" on the Devices tab in Emote, the application crashes. Is there a download on the site, that isn't in the normal download area? I have the Dante Firware Updater, but still need the Brooklyn II firmware file for v4.0.
Here is the latest firmware for the Brooklyn module, which should enable static IP addressing:
https://share.eventide.com/wl/?id=AL2KncgPsrqxnA3aD9cmKpmYKiM6ze9I
-
-
June 20, 2019 at 4:01 am #152148Participant
That did it! Thanks so much for helping me resolve the issue. Looking forward to the Emote update, so that I can update the H9000R network settings too…but for now, it’s all working as expected. Happy days!
-
June 24, 2019 at 4:18 pm #152192donrwatters wrote:
That did it! Thanks so much for helping me resolve the issue. Looking forward to the Emote update, so that I can update the H9000R network settings too…but for now, it's all working as expected. Happy days!
Here's the latest build 1.1.8[2]:
USB installer:
https://share.eventide.com/wl/?id=e2YKtaEZmVi58hYGpodxFaccOuhbjtk6
Emote macOS:
https://share.eventide.com/wl/?id=9i3v6AZENRhsvGeB4GootNwI10RG6VuK
Emote Windows:
https://share.eventide.com/wl/?id=nRdfZva9pLpyD8NbrBbGh18akuA04jyn
Posting it here first so you can troubleshoot your network issues. We hope to push it out to the public after a bit more testing.
-
-
June 24, 2019 at 10:16 pm #152202Participant
How does one boot into update/failsafe mode on the H9000R? If I’ve guessed right, then I just hold down the paperclip button hole while booting. Unfortunately, I don’t get very far after that. Emote crashes when I try to connect when in RECOVERY. Since I can’t see when it’s gone through the boot process, I’m just waiting for the network light to stop blinking.
Appendix B in the H9000 User’s Manual isn’t very helpful, since it’s only for the regular H9000. So, I did my best here. 🙂
It seems as though I can’t connect at all now. Even after a reboot and trying to get in via the wifi connection or the ethernet connection.
Here’s the WER appcrash info:
Version=1EventType=APPCRASHEventTime=132058870035199363ReportType=2Consent=1UploadTime=132058871886150401ReportStatus=268435556ReportIdentifier=b9d02600-b165-4edc-8da5-baf4e7cda20aIntegratorReportIdentifier=9fbec196-8df2-4389-8d14-a9ccda64df77Wow64Host=34404Wow64Guest=332NsAppName=Emote.exeAppSessionGuid=00002664-0001-0015-f218-12b4d72ad501TargetAppId=W:0000429bc4edb5067efe64568123742ca6f40000ffff!00000e055cfeb5aa2b1b5ddefb350f53ab37efa1eb0d!Emote.exeTargetAppVer=2019//06//24:15:29:47!0!Emote.exeBootId=4294967295ServiceSplit=2009363780TargetAsId=725Response.BucketId=8aff0f597fd58ad0f7b25238e593bd80Response.BucketTable=1Response.LegacyBucketId=1707517613050150272Response.type=4Sig[0].Name=Application NameSig[0].Value=Emote.exeSig[1].Name=Application VersionSig[1].Value=1.1.8.2Sig[2].Name=Application TimestampSig[2].Value=5d10ec6bSig[3].Name=Fault Module NameSig[3].Value=Emote.exeSig[4].Name=Fault Module VersionSig[4].Value=1.1.8.2Sig[5].Name=Fault Module TimestampSig[5].Value=5d10ec6bSig[6].Name=Exception CodeSig[6].Value=c0000005Sig[7].Name=Exception OffsetSig[7].Value=00019e76DynamicSig[1].Name=OS VersionDynamicSig[1].Value=10.0.16299.2.0.0.256.48DynamicSig[2].Name=Locale IDDynamicSig[2].Value=1033DynamicSig[22].Name=Additional Information 1DynamicSig[22].Value=e2a5DynamicSig[23].Name=Additional Information 2DynamicSig[23].Value=e2a5934c14e66921972cbe137a4819ffDynamicSig[24].Name=Additional Information 3DynamicSig[24].Value=db0dDynamicSig[25].Name=Additional Information 4DynamicSig[25].Value=db0d3763e70b9cfed2ebac71f0dca988UI[2]=C:Program FilesEventideEmoteEmote.exeUI[3]=Emote has stopped workingUI[4]=Windows can check online for a solution to the problem.UI[5]=Check online for a solution and close the programUI[6]=Check online for a solution later and close the programUI[7]=Close the programLoadedModule[0]=C:Program FilesEventideEmoteEmote.exeLoadedModule[1]=C:WINDOWSSYSTEM32ntdll.dllLoadedModule[2]=C:WINDOWSSystem32KERNEL32.DLLLoadedModule[3]=C:WINDOWSSystem32KERNELBASE.dllLoadedModule[4]=C:WINDOWSSYSTEM32apphelp.dllLoadedModule[5]=C:WINDOWSSYSTEM32AcLayers.DLLLoadedModule[6]=C:WINDOWSSystem32msvcrt.dllLoadedModule[7]=C:WINDOWSSystem32USER32.dllLoadedModule[8]=C:WINDOWSSystem32win32u.dllLoadedModule[9]=C:WINDOWSSystem32GDI32.dllLoadedModule[10]=C:WINDOWSSystem32gdi32full.dllLoadedModule[11]=C:WINDOWSSystem32msvcp_win.dllLoadedModule[12]=C:WINDOWSSystem32ucrtbase.dllLoadedModule[13]=C:WINDOWSSystem32SHELL32.dllLoadedModule[14]=C:WINDOWSSystem32cfgmgr32.dllLoadedModule[15]=C:WINDOWSSystem32shcore.dllLoadedModule[16]=C:WINDOWSSystem32RPCRT4.dllLoadedModule[17]=C:WINDOWSSystem32SspiCli.dllLoadedModule[18]=C:WINDOWSSystem32CRYPTBASE.dllLoadedModule[19]=C:WINDOWSSystem32bcryptPrimitives.dllLoadedModule[20]=C:WINDOWSSystem32sechost.dllLoadedModule[21]=C:WINDOWSSystem32combase.dllLoadedModule[22]=C:WINDOWSSystem32windows.storage.dllLoadedModule[23]=C:WINDOWSSystem32advapi32.dllLoadedModule[24]=C:WINDOWSSystem32shlwapi.dllLoadedModule[25]=C:WINDOWSSystem32kernel.appcore.dllLoadedModule[26]=C:WINDOWSSystem32powrprof.dllLoadedModule[27]=C:WINDOWSSystem32profapi.dllLoadedModule[28]=C:WINDOWSSystem32OLEAUT32.dllLoadedModule[29]=C:WINDOWSSystem32SETUPAPI.dllLoadedModule[30]=C:WINDOWSSYSTEM32MPR.dllLoadedModule[31]=C:WINDOWSSYSTEM32WINSPOOL.DRVLoadedModule[32]=C:WINDOWSSYSTEM32IPHLPAPI.DLLLoadedModule[33]=C:WINDOWSSYSTEM32bcrypt.dllLoadedModule[34]=C:WINDOWSSYSTEM32sfc.dllLoadedModule[35]=C:WINDOWSSYSTEM32sfc_os.DLLLoadedModule[36]=C:WINDOWSSystem32IMM32.DLLLoadedModule[37]=C:WINDOWSSystem32COMDLG32.dllLoadedModule[38]=C:WINDOWSSYSTEM32WINMM.dllLoadedModule[39]=C:WINDOWSSystem32ole32.dllLoadedModule[40]=C:WINDOWSWinSxSx86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.16299.1087_none_3edce3bab923e35cCOMCTL32.dllLoadedModule[41]=C:WINDOWSSystem32WS2_32.dllLoadedModule[42]=C:WINDOWSSYSTEM32WINMMBASE.dllLoadedModule[43]=C:WINDOWSSYSTEM32WININET.dllLoadedModule[44]=C:WINDOWSSYSTEM32MSVCP140.dllLoadedModule[45]=C:WINDOWSSYSTEM32VCRUNTIME140.dllLoadedModule[46]=C:WINDOWSSYSTEM32dnssd.dllLoadedModule[47]=C:WINDOWSsystem32uxtheme.dllLoadedModule[48]=C:WINDOWSSystem32MSCTF.dllLoadedModule[49]=C:WINDOWSsystem32dwmapi.dllLoadedModule[50]=C:WINDOWSSYSTEM32CLDAPI.dllLoadedModule[51]=C:WINDOWSSYSTEM32FLTLIB.DLLLoadedModule[52]=C:WINDOWSSYSTEM32AEPIC.dllLoadedModule[53]=C:WINDOWSSYSTEM32ntmarta.dllLoadedModule[54]=C:WINDOWSSYSTEM32cryptsp.dllLoadedModule[55]=C:WINDOWSSystem32clbcatq.dllLoadedModule[56]=C:WINDOWSsystem32propsys.dllLoadedModule[57]=C:WINDOWSWinSxSx86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.1087_none_573dab8d6ee1b2bdcomctl32.dllLoadedModule[58]=C:WINDOWSSYSTEM32WindowsCodecs.dllLoadedModule[59]=C:WindowsSystem32thumbcache.dllLoadedModule[60]=C:WINDOWSsystem32dataexchange.dllLoadedModule[61]=C:WINDOWSsystem32dcomp.dllLoadedModule[62]=C:WINDOWSsystem32d3d11.dllLoadedModule[63]=C:WINDOWSsystem32dxgi.dllLoadedModule[64]=C:WINDOWSsystem32twinapi.appcore.dllLoadedModule[65]=C:WINDOWSsystem32RMCLIENT.dllLoadedModule[66]=C:WINDOWSsystem32mswsock.dllLoadedModule[67]=C:WINDOWSSystem32TextInputFramework.dllLoadedModule[68]=C:WINDOWSSystem32CoreUIComponents.dllLoadedModule[69]=C:WINDOWSSystem32CoreMessaging.dllLoadedModule[70]=C:WINDOWSSYSTEM32wintypes.dllLoadedModule[71]=C:WINDOWSSYSTEM32mscms.dllLoadedModule[72]=C:WINDOWSSYSTEM32USERENV.dllState[0].Key=Transport.DoneStage1State[0].Value=1OsInfo[0].Key=vermajOsInfo[0].Value=10OsInfo[1].Key=verminOsInfo[1].Value=0OsInfo[2].Key=verbldOsInfo[2].Value=16299OsInfo[3].Key=ubrOsInfo[3].Value=1087OsInfo[4].Key=verspOsInfo[4].Value=0OsInfo[5].Key=archOsInfo[5].Value=9OsInfo[6].Key=lcidOsInfo[6].Value=1033OsInfo[7].Key=geoidOsInfo[7].Value=244OsInfo[8].Key=skuOsInfo[8].Value=48OsInfo[9].Key=domainOsInfo[9].Value=0OsInfo[10].Key=prodsuiteOsInfo[10].Value=256OsInfo[11].Key=ntprodtypeOsInfo[11].Value=1OsInfo[12].Key=platidOsInfo[12].Value=10OsInfo[13].Key=srOsInfo[13].Value=0OsInfo[14].Key=tmsiOsInfo[14].Value=73097OsInfo[15].Key=osinstyOsInfo[15].Value=3OsInfo[16].Key=ieverOsInfo[16].Value=11.1087.16299.0-11.0.120OsInfo[17].Key=portosOsInfo[17].Value=0OsInfo[18].Key=ramOsInfo[18].Value=32675OsInfo[19].Key=svolszOsInfo[19].Value=1042OsInfo[20].Key=wimbtOsInfo[20].Value=0OsInfo[21].Key=blddtOsInfo[21].Value=180808OsInfo[22].Key=bldtmOsInfo[22].Value=1748OsInfo[23].Key=bldbrchOsInfo[23].Value=rs3_releaseOsInfo[24].Key=bldchkOsInfo[24].Value=0OsInfo[25].Key=wpvermajOsInfo[25].Value=0OsInfo[26].Key=wpverminOsInfo[26].Value=0OsInfo[27].Key=wpbuildmajOsInfo[27].Value=0OsInfo[28].Key=wpbuildminOsInfo[28].Value=0OsInfo[29].Key=osverOsInfo[29].Value=10.0.16299.1087.amd64fre.rs3_release.180808-1748OsInfo[30].Key=buildflightidOsInfo[31].Key=editionOsInfo[31].Value=ProfessionalOsInfo[32].Key=ringOsInfo[33].Key=containeridOsInfo[34].Key=containertypeOsInfo[35].Key=eduOsInfo[35].Value=0FriendlyEventName=Stopped workingConsentKey=APPCRASHAppName=EmoteAppPath=C:Program FilesEventideEmoteEmote.exeNsPartner=windowsNsGroup=windows8ApplicationIdentity=B21CBB63D3956E978DFF75308415EFCDMetadataHash=1668642302 -
June 25, 2019 at 12:15 pm #152208
I’ve targeted your unit to see the update over the network – could you boot into normal mode and try it there?
Unfortunately those windows crash logs aren’t very revealing, but we’ll investigate. If you keep seeing issues, it may be worth downgrading to the Emote version you had previously, since it’s generally best to connect to the device with the same version number. Once the update succeeds on the H9000, then it’s safe to also update Emote.
-
June 26, 2019 at 3:22 am #152217Participant
After some trial and error, it’s back on track and working!
I got it back into normal mode. But, Emote kept crashing on the Windows computer that the H9KR is connected to when I click on “updates” using any version of Emote. So I used my work Mac Book Pro and that was able to pull the install list. Once I select the new build, and select install, the download went to completion, then the install began. I got about 20 seconds in and the Emote app on the Mac crashed. So, I did that a few times. Then decided to reboot the H9KR. Once that was back up, I was able to connect with the newest Emote version, and was able to change the IP Network settings and the Host Name!
There’s some intricacy there though. When I tried to set the Ethernet connection, I wasn’t able to finish the settings, before it took the IP address and ran with it. We need to be able to finish all of the setting, like DHCP and Gateway, before it just takes on the new IP address. I still don’t see the IP settings on the Windows Emote application, but at this point, I don’t need to. Also, the View ->Meter Bridge is gone from the Windows version, but is there on the Mac. :/
Thanks so much for getting this out to me. It’s a giant help in getting things settled in the studio. Really appreciate the extra effort and care, for just one user. Great service.
-
-
-
AuthorPosts
- You must be logged in to reply to this topic.
