303 request

[GoogleCodeExporter]

Some way of compensating for different ticks/beat other than 4. multiples of 4 
would probably be easy but don't know about odd ones. Don't know if there is a 
practical solution. 

Original issue reported on code.google.com by theorize...@gmail.com on 19 Oct 2010 at 5:02

[GoogleCodeExporter]

What do you mean ? The 303 should run on their own tempo base ?

Original comment by hhhikr@gmail.com on 22 Oct 2010 at 1:38

[GoogleCodeExporter]

just increase the tpb and the speed of the 303 will increase

Original comment by theorize...@gmail.com on 29 Oct 2010 at 9:30

[GoogleCodeExporter]

The 303s use the bpm/tpb pulse from the tracker, what else did you expect ?

Original comment by hhhikr@gmail.com on 31 Oct 2010 at 5:05

[GoogleCodeExporter]

Yes i understand that, now i see it as a problem since i decided to use 8 tpb 
more to help increase resolution for tracking, mostly for effects, because at 
134bpm and 8tpb i end up with the 303 running at 268bpm. im on mobile right now 
ill write more later when i have the tracker in front of me.

Original comment by theorize...@gmail.com on 1 Nov 2010 at 9:08

[GoogleCodeExporter]

If I'm understanding it correctly every time the trackeradvances a tick it 
sends a pulse over to the 303 and the 303 advances... a solution that wouldn't 
be all that bad and still retain module commpatability might be for the 303 to 
only advance ever x pulses. Its seems practical enough to me, what do you think?

Original comment by theorize...@gmail.com on 12 Apr 2011 at 5:34

[GoogleCodeExporter]

I'm implementing 303 patterns replay scaling, i think it'll fit the bill.

Original comment by hhhikr@gmail.com on 23 May 2011 at 9:42

[GoogleCodeExporter]

Testing the latest version, I noticed this problem too. Would be great to have 
the replay scaling implemented at some point. Not sure if it'd make sense to 
leave the scaling value user-configurable? Like, if you'd actually want to run 
the 303s "double tempo"..

One other thing; whilst playing the 303 over a synth patch, the 303 seemed to 
be slightly down-tuned in comparison. Tuning knobs are zeroed on both. 

Original comment by elbow...@gmail.com on 7 Jun 2011 at 11:44

[GoogleCodeExporter]

I'm beginning to suspect that synth might be tuned slightly too high... compare 
it to a chip that you've tuned mathmatically. My math isn't that great but I 
think Ive gotten close enough in this case.

Not sure how having the 303 scaling user configurable would interfere with 
wanting to have it run double tempo... just don't scale it and up the TPB... if 
I'm understanding what you mean that is.

Original comment by theorize...@gmail.com on 16 Jun 2011 at 10:16

[GoogleCodeExporter]

I didn't notice any tuning problem (make sure the tune knobs are reseted via 
the right mouse button).

Original comment by hhhikr@gmail.com on 7 Jul 2011 at 11:05

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

Attachments:

• tuning.ptk

[GoogleCodeExporter]

I think there's not an issue with the 303 tuning... I think it's the 
oscillators in the main synth. The 303 is perfect in my eyes, I've never had so 
much fun with a 303, partly because tracking makes it better.  

Original comment by theorize...@gmail.com on 13 Jul 2011 at 6:17

[GoogleCodeExporter]

Got the tuning file I'll look at it here when I install the new version.

Original comment by theorize...@gmail.com on 13 Jul 2011 at 6:18

[GoogleCodeExporter]

this has worked out great... I have one 303 going at normal speed and one going 
at half. I'm finding I use the track filter for automation a lot though, I'm 
not that good with traditional acid sounds but find ways to use the 303 still. 

Original comment by theorize...@gmail.com on 16 Oct 2011 at 9:16