yep.. you are right once again rob.. its SD3 choke/mute trigger setting that causing it.. thanks again for ur enlighment..
btw, should i upgrade to 2.3.2? whats major difference from 2.3.1.35? do they had dedicated midi box for rim only Articulation in snare now? thats the latest thing i cant achieve still (well beside brush mode, which now i started to forget. LoL) . still dunno the root cause it? is it depends on snare pad (hardware)? EDC update? or tweaking on SD3? im stil using bar trigger that caused me another channel on SD8 for now
thanks again Rob..
issues ED4R4 on EDC 2.3.1.35
Re: issues ED4R4 on EDC 2.3.1.35
The new features / improvements / bug fixes are listed in the version 2.3.2 BETA thread.
viewtopic.php?f=29&t=2308
viewtopic.php?f=29&t=2308
Re: issues ED4R4 on EDC 2.3.1.35
Hi Rob,
Just update. . the ssues is happening again... and after i try ur suggestion to power cycle the ED8 and power hub... none of them works.
i attached the SS of error ED4R4 (it should be 1:Floor1, 2:Floor 2, 3: crash3, 4:china..but all showed like a snare configuration with different treshold setting as i run it this time) what should i do?? thanks for ur enlighment
- Attachments
-
- ED4R4-CONF-ERROR.png (240.99 KiB) Viewed 109 times
Re: issues ED4R4 on EDC 2.3.1.35
The settings being displayed are all the default settings, so basically the ED4 devices haven't sent any data to the control application at all. Can you disconnect the power from the the hub and use it unpowered for a while and see if the issue still returns. If it does, you might want to update your firmware be the result of a bug that has been fixed in version 2.3.2. (although I don't recall fixing any show stopping, hardware crashing issues).
Re: issues ED4R4 on EDC 2.3.1.35
Sory for late respon.. just came from out of town n thanks for ur previous guidence Rob
just want to update.. direct connection wasnt working.. ED4R4 still unable to send data to 2.3.1.35.
So i decide to keep my old existing connection after i rebuild all over again the configuration of the problematic ED4R4 (strange only one of them behave like this)
Still keep the faith on 2.3.1.35 as it has served me flawlesly.. also condensering that 2.3.2 risk on reset device if i hav to be downgraded (dont wanna loose all my pads setting)
with hoping ull provide an excelent solution as always for my issues here
Thanks again for ur hard work n profesionalism Rob.. really appreciated
just want to update.. direct connection wasnt working.. ED4R4 still unable to send data to 2.3.1.35.
So i decide to keep my old existing connection after i rebuild all over again the configuration of the problematic ED4R4 (strange only one of them behave like this)
Still keep the faith on 2.3.1.35 as it has served me flawlesly.. also condensering that 2.3.2 risk on reset device if i hav to be downgraded (dont wanna loose all my pads setting)
with hoping ull provide an excelent solution as always for my issues here
Thanks again for ur hard work n profesionalism Rob.. really appreciated