1.13 FW minor issue

Welcome to the Taurus, Minitaur and Sirin Forum
Post Reply
shanef
Posts: 14
Joined: Sat Nov 28, 2009 1:24 pm

1.13 FW minor issue

Post by shanef » Fri Jul 02, 2010 7:18 pm

If I modify the Taurus preset (A2), change the octave parameter to HI, and also toggle the octave footswitch
on, and then hit the high C note it sounds like the B-freq is the same as the main freq. It loses that
Taurus sound characteristic. All of the other notes are fine, it's just the high C that is wrong.

Can anyone corroborate this?

rkharper
Posts: 25
Joined: Wed Nov 18, 2009 2:30 am
Location: Schlieren, Switzerland
Contact:

Re: 1.13 FW minor issue

Post by rkharper » Sat Jul 03, 2010 3:29 am

yeah, you're right, sounds like a stinging bee! (only the highes C in HI Setting with Octave Switch Pressed)

User avatar
MC
Posts: 2907
Joined: Tue Aug 12, 2003 2:20 pm
Location: Secluded Tranquil Country

Re: 1.13 FW minor issue

Post by MC » Sun Jul 04, 2010 4:25 pm

The VCOs have a five octave limit due to the faithful repro of the original v/hz design. v/hz means the CV doubles for every octave, and five octaves (1V, 2V, 4V, 8V, 16V) puts you at the power rails and you can't go beyond that. v/oct has wider range since the frequency doubles for every voltage not the CV. If you attempt to exceed the range, the VCO will max out at top frequency. Hey you wanted a faithful reproduction, you got it!
Gear list: '04 Saturn Ion, John Deere X300 tractor, ganged set of seven reel mowers for 3 acres of lawn, herd of sheep for backup lawn mowers, two tiger cats for mouse population control Oh you meant MUSIC gear Oops I hit the 255 character limi

Mr Arkadin
Posts: 600
Joined: Fri Jun 06, 2008 8:43 am

Re: 1.13 FW minor issue

Post by Mr Arkadin » Sun Jul 04, 2010 5:04 pm

We're talking about using high C on this bass machine? Get outta here...
http://soundcloud.com/luke-antony

Amos
Posts: 2438
Joined: Wed Jul 23, 2003 3:11 pm

Re: 1.13 FW minor issue

Post by Amos » Tue Jul 06, 2010 10:08 am

MC is correct, this is a hardware limitation. The oscillators top out at high C; try to push them beyond that and they will limit to the highest in-tune note they can play (C).

One trick you might be able to use to nail this high C but still keep some beating between the oscillators, is to set the BEAT parameter below halfway, so that Osc. B is tuned a bit flat relative to Osc. A. Then as long as you are just hitting the high C and not trying to go an octave above it, say, you should still get some beating between the oscillators as osc. B will be just below the maximum limit and Osc. A will be at the limit.

Cheers,

Amos

User avatar
Voltor07
Posts: 5197
Joined: Sun May 25, 2008 3:04 am
Location: Waukegan, IL USA
Contact:

Re: 1.13 FW minor issue

Post by Voltor07 » Thu Jul 15, 2010 12:02 pm

Geez...why would you want to go to C? :?
Minitaur, CP-251, EHX #1 Echo, EHX Space Drums/Crash Pads, QSC GX-3, Pyramid stereo power amp, Miracle Pianos, Walking Stick ribbon controller, Synthutron.com, 1983 Hammond organ, dot com modular.

shanef
Posts: 14
Joined: Sat Nov 28, 2009 1:24 pm

Re: 1.13 FW minor issue

Post by shanef » Thu Jul 15, 2010 2:09 pm

The trick that Amos suggested work, thanks! Apologies if the implication was that it was a bug.

Not sure I understand the negativity surrounding my question. Yes, they're called bass pedals but they support higher octaves and there are no right or wrong ways to create music. Why would I want to play a high C? Cuz I felt like it :).

Specifically, I was messing around with a tricky pedal part on Rush's Cygnus X-1.

Stick_Player
Posts: 67
Joined: Thu Nov 26, 2009 6:56 pm
Location: Los Angeles

Re: 1.13 FW minor issue

Post by Stick_Player » Thu Aug 19, 2010 9:16 pm

Any 'news' on adding MIDI Clock Start and Stop capability?

:D :D :D :D

Amos
Posts: 2438
Joined: Wed Jul 23, 2003 3:11 pm

Re: 1.13 FW minor issue

Post by Amos » Tue Aug 24, 2010 2:51 pm

Hi there! I'm working on Little Phatty code at the moment, taking a bit of a breather from the Taurus... hope the latest firmware is working well for folks in the meanwhile. I recognize that there are still some improvements to be made; in fact I have a list... ;) Remind me what we were talking about doing with MIDI stop and start?
Thanks,

Amos

patobrujo
Posts: 135
Joined: Tue May 27, 2008 3:17 pm
Location: Santiasko, Chile

Re: 1.13 FW minor issue

Post by patobrujo » Tue Aug 24, 2010 4:56 pm

those are good news Amos! :D can you tell us what other improvements are on that list?? thanks
..::PATOBRUJO::..

Stick_Player
Posts: 67
Joined: Thu Nov 26, 2009 6:56 pm
Location: Los Angeles

Re: 1.13 FW minor issue

Post by Stick_Player » Wed Aug 25, 2010 3:15 pm

Remind me what we were talking about doing with MIDI stop and start?
I have the T3 synched to a Roland RC-50. It would be wonderful if when I stopped the RC-50, the T3 would also stop playing the arpegiator.

Start would also be good.

Amos
Posts: 2438
Joined: Wed Jul 23, 2003 3:11 pm

Re: 1.13 FW minor issue

Post by Amos » Wed Aug 25, 2010 3:31 pm

Interesting! This must mean that the Roland continues to send MIDI clock even after you hit Stop. I wonder why it would do that?
In any case, I can add this... not sure how soon exactly, as I think I will be tied up with other projects at least through September... but perhaps not long thereafter. Thanks for the reminder. :)

-Amos

Stick_Player
Posts: 67
Joined: Thu Nov 26, 2009 6:56 pm
Location: Los Angeles

Re: 1.13 FW minor issue

Post by Stick_Player » Fri Aug 27, 2010 10:21 pm

I can add this... Thanks for the reminder.
That would be GREAT! I believe a few others thought it would be a good feature, too.

Post Reply