The Yamaha AN1x Synthesizer mailing list

Hi all,
 I know it's been asked before but couldn't see any answers.
my prob is the following .

When assigning cut off to ribbon-X controller in the matrix control 
routing, the ribbon position never acts the same.
according to the operation manual it should hold its position after 
being released and not go center ( operation manual p75).
Well, at least in my case, it's not true, sometime the cutoff 
assigned ribbon keeps its position sometimes it reset to center.
a few patches tend to be more "reset centered" than "held to the 
their last ribbon position", but you never know.

When the performance goes through editing (neither-ribbon nor cuttof 
related editings BTW) these "tendencies" might  swap to one another.

Am I missing anything, has anybody noticed the same problem ?
thx for your help

fred

--- In AN1x-list@y..., "pixie130672" <frederic.chen@w...> wrote:
> Hi all,
>  I know it's been asked before but couldn't see any answers.
> my prob is the following .
> 
> When assigning cut off to ribbon-X controller in the matrix 
control 
> routing, the ribbon position never acts the same.
> according to the operation manual it should hold its position 
after 
> being released and not go center ( operation manual p75).
> Well, at least in my case, it's not true, sometime the cutoff 
> assigned ribbon keeps its position sometimes it reset to 
center.
> a few patches tend to be more "reset centered" than "held to 
the 
> their last ribbon position", but you never know.
> 
> When the performance goes through editing (neither-ribbon 
nor cuttof 
> related editings BTW) these "tendencies" might  swap to one 
another.
> 
> Am I missing anything, has anybody noticed the same problem 
?
> thx for your help
> 
> fred

Hi Fred,

Yes, I've managed to recreate your problem as described. Very 
odd indeed.

I leave my AN1x in Mode 2 99% of the time so I thought perhaps 
the problem was specific to Mode 2. I rebooted my AN1x into 
Mode 1 and the problem disappeared. My edited voice retained 
the Filter Cutoff value when I removed my finger from the Ribbon.

I rebooted back into Mode 2 and the problem did NOT reappear, 
i.e., the voice behaved correctly with the Ribbon X assigned to 
Filter Cutoff. Very strange?!?! Guess the problem is not specific 
to Mode 1 or 2.

So I edited another voice - making the identical Matrix 
assignment - and of course it did not work! The Filter Cutoff 
setting returned to 'center' whenever I removed my finger from 
the controller. Aaargh!

 So, I powered off and on my AN1x and the problem disappeared 
- again. BUT once I issued a program change the problem 
reappeared! Very confusing...I rebooted BACK into Mode 1 and 
the behavior was identical to Mode 2.

I'm at a loss to explain this irradicate behavior :-( Perhaps we 
need to report this to Yamaha.

As a work around I suggest you use the Ribbon controller only 
for dynamic changes and assign the Mod Wheel or an Assign 
Knob to the same parameter when you require a fixed value.

When I have time I'll boot up LOGIC AUDIO and place a Monitor 
into my Environment Layer to see what MIDI CC's are coming 
and going - and maybe test with LOCAL=OFF too.

regards,

Jon

--- In AN1x-list@y..., "jondl_2000" <jondl_2000@y...> wrote:
> I'm at a loss to explain this irradicate behavior :-( Perhaps we 
> need to report this to Yamaha.
> 


That's suppose to say 'erratic' not irradicate...bwah! 

Jon

Hi Jon,

Sorry for the delay, but here's my $0.02 on the problem:

1.  It happens regularly in Mode 1:  I almost never use Mode 2 because my setup has a couple of keyboards that use a number of MIDI CC#'s, and I can't deal with the overlap issues.

2.  It's more than an internal AN1x issue, as I tried using the ribbon controller to select dry or vocoded voice on my WarpFactory vocoder, which uses 0-64 = dry and 65-127 = vocoded.  (FWIW, I was sending CC#40 as Ribbon-X.)  For the first few days, it always acted as a "sticky" control -- i.e., if I touched the far right side, I had continuous vocoding, while if I touched the left side, I had continuous dry mic.  Then one day, it started only staying in vocoder mode while my finger was on the ribbon!  Like you, I determined that it was returning to CC=64, and had something to do with patches.  At that point, I gave up using the ribbon to control the vocoder.  :^(

3.  Powering on and off may have an effect; I was a little confused about the reason for the problem at first, and would need to repeat the tests to be sure.


Regards,

-BW

--
Bruce Wahler
Design Consultant
Ashby Solutions\ufffd   http://consult.ashbysolutions.com
CloneWheel Support Group and HiNote moderator
978.386.7389  voice/fax
bruce@...

--- In AN1x-list@y..., Bruce Wahler <bruce@a...> wrote:
> Hi Jon,
> 
> Sorry for the delay, but here's my $0.02 on the problem:
> 
> 1.  It happens regularly in Mode 1:  I almost never use Mode 2 
because my setup has a couple of keyboards that use a 
number of MIDI CC#'s, and I can't deal with the overlap issues.
> 

Thanks for the confirmation. 

> 2.  It's more than an internal AN1x issue, as I tried using the 
ribbon controller to select dry or vocoded voice on my 
WarpFactory vocoder, which uses 0-64 = dry and 65-127 = 
vocoded.  (FWIW, I was sending CC#40 as Ribbon-X.)  For the 
first few days, it always acted as a "sticky" control -- i.e., if I 
touched the far right side, I had continuous vocoding, while if I 
touched the left side, I had continuous dry mic.  Then one day, it 
started only staying in vocoder mode while my finger was on the 
ribbon!  Like you, I determined that it was returning to CC=64, 
and had something to do with patches.  At that point, I gave up 
using the ribbon to control the vocoder.  :^(
> 

Thansk for providing this info. When I hear back on my problem 
report I'll pass this along.

> 3.  Powering on and off may have an effect; I was a little 
confused about the reason for the problem at first, and would 
need to repeat the tests to be sure.
> 

I found the problem would clear - temporarily - by powering off/on 
my AN1x but as soon as a program change was issued the 
"bug" would reappear.

I know that both Ed and I are using the 1.04 EPROM - I'm 
uncertain what EPROM you and the author of this thread are 
using?


Jon

Hi Jon,

>I know that both Ed and I are using the 1.04 EPROM - I'm 
>uncertain what EPROM you and the author of this thread are 
>using?

I've also upgraded to v1.04.

It's a shame that the AN1x uses a hard-coded ROM, rather than flash like my Korg CX-3, or most of the Nord products.  Getting someone at Yamaha to investigate, and even fix, the problem is easy; getting them to go through the trouble of making and distributing a hardware update on an out-of-production product is a long shot.

Regards,

-BW

--
Bruce Wahler
Design Consultant
Ashby Solutions\ufffd   http://consult.ashbysolutions.com
CloneWheel Support Group and HiNote moderator
978.386.7389  voice/fax
bruce@...

--- In AN1x-list@y..., Bruce Wahler <bruce@a...> wrote:
> Hi Jon,
> 
> >I know that both Ed and I are using the 1.04 EPROM - I'm 
> >uncertain what EPROM you and the author of this thread are 
> >using?
> 
> I've also upgraded to v1.04.
> 
> It's a shame that the AN1x uses a hard-coded ROM, rather than 
flash like my Korg CX-3, or most of the Nord products.  Getting 
someone at Yamaha to investigate, and even fix, the problem is 
easy; getting them to go through the trouble of making and 
distributing a hardware update on an out-of-production product 
is a long shot.
> 

Agreed.

Typically, I'd take some satisfaction at getting the problem report 
into the pipeline so they'd _at_least _ be aware for future 
development but it's been awhile since they've released a new 
product with a RIBBON Controller so...

Regarding FlashROM updates - one of the determining factors 
for me when I was shopping for a hardware sampler was the 
FlashROM OS update offered on the Ensoniq ASR-X Pro. 
Unfortunately, Ensoniq was bought up by Creative Labs and 
merged with E-mu (that was a GREAT idea ;-) and only one OS 
update ever saw the light of day!

sigh

regards,

Jon

p.s. - OT but has your clonewheel group compared/discussed 
any of the  drawbar VSTi's to each other? Maybe I should just 
search your list archive...

Hi Jon,

>p.s. - OT but has your clonewheel group compared/discussed 
>any of the  drawbar VSTi's to each other? Maybe I should just 
>search your list archive...

Most of them who are using a softsynth for organ are using the NI B-4 -- typically, in stand-alone configuration.  Our group is not as "avant guarde" as this one, and only about 10-15% of the list even uses a sequencer; most of them use it just for librarian duties and playing around at home.

Regards,

-BW

--
Bruce Wahler
Design Consultant
Ashby Solutions\ufffd   http://consult.ashbysolutions.com
CloneWheel Support Group and HiNote moderator
978.386.7389  voice/fax
bruce@...