July 31, 2015, 03:42:28 pm
Welcome, Guest. Please login or register.
Did you miss your activation email
News: Feel free to email any encountered problem at webmaster@arturia.com.

Arturia Forums



Recent Posts

Pages: 1 ... 7 8 [9] 10
81
When I did the above the octave of the Microbrute matched perfectly both my Bass Station and my TT-303's which I run using MIDI. Set the C0 value to C0 rather than C-2 (default) C-1 or C1 and above
82
BeatStep Pro - Technical Questions - FAQ / Re: TRACKING IS TOO HIGH (& MORE)
« Last post by Biosynth on July 28, 2015, 08:38:02 pm »

Try setting your CV0 to C0 rather than C3 (I think it defaults to C-2 in the MMC), it worked perfectly with my microbrute.
yes I tried but in C3 octave is lower.
I 'm on the last firmware.
I try with my micromoog and my korg odyssey. For this one in midi it's ok but not in cv-gate.
83
BeatStep Pro - Technical Questions - FAQ / Re: TRACKING IS TOO HIGH (& MORE)
« Last post by Sabatini on July 28, 2015, 08:23:36 pm »
- The tracking of the CV worked inproperly before my firmware update, too.
now using 1.1.0.3 - tracking is fine


- I've some ghost notes...
Check if the Probability and Randomness buttons are set to zero. That problem bit me a few days ago.

that is not a true solution....

Do following test.
Put your fingers on one of the 3 left sided knobs (f. e. random), and do like you want to turn, but keep the position with NO turning.
Then do a little bit lottering to the left and right. These encoders a wobbly and rocky, in comparison to the others.
That causes pulses in the encoder, that the values for the corresponding parameter is raising, even if you make NO turning of the knob.
Even knocking on the sides or on the table causes sometimes the same effect.  ???

I have 2 pieces of BSP here, and both have the same behaviour... what about yours?


T. S.

84
Hi CJMOR 1804


randomness should be default at zero. wouldn't it be hard to program a sequence if it started out 100% random?
- Did I say something different?

swing should be default at 50%. that is the zero position.
 - my saying, isnt it?


the encoders seem to be same quality as all my other midi controller gear that i've had for years
- ok, you are convinced about so I show you the problem.

Do following test.
Put your fingers on one of the 3 left sided knobs (f. e. random), and do like you want to turn, but keep the position with NO turning.
Then do a little bit lottering to the left and right.
That causes pulses in the encoder, that the values for the corresponding parameter is raising, even if you make NO turning of the knob.
Even knocking on the sides or on the table has sometimes the same effect. The problem seems to be, that this encoders have no latching or snapping.

I have 2 pieces of BSP here, and both have the same behaviour, so it is not a specific lack.

Maybe your machine does this not, then let me know.
I have to send all my devices back to my dealer then.

T. S.
85
Any news on this Terrym?

 :-*
86
Yeah, It's a a knock on error from the graphics resolution or similar, it's not necessarily a CPU spike but this is how is manifests itself in a DAW.

But as far as Ben is concerned, is a non error. Not a lot you can do.

Map a controller to the desired knobs, save your presets and control it via your controller with the plug in windows closed. That's the only way ou will get it to work successfully

Thanks, Stuart

 
87

I also noticed that
* different video card (the one from the previous machine) no change
* If I change the resolution to something really low like 1280x800 it doesnt seem to spike
* if my daw is not maximized it doesnt seem to spike as much but still does. For some reason window size of the daw seems to correlate to the amount of spiking.
88
Try setting your CV0 to C0 rather than C3 (I think it defaults to C-2 in the MMC), it worked perfectly with my microbrute.
89
Hey Vic-tor thanks for the reply. I will try when I get home but I feel like I have tried every configuration with no luck. I will let you know what happens.
90
I did find a solution:


Unfortunately that was not to use it. It's an issue with a graphical driver or some extension that Arturia haven't thought about. Saying it's a CPU overload is an easy way of saying, we don't know.

I have shown video footage of this error and it's plain as the nose on your face, but for whatever reason, they deem it not important enough to rectify. Or perhaps with recent updates, they have sneaked out a fix.

I don't use it open anymore, I have to close it which tends to mean I have only used it on things that Ive a mapped controller for.
I didn't use it that much anyway, the odd sound I do try if I need a specify thing but other than that I find I can get most stuff out of the Mini V and the Prophet

Sorry I couldn't be of anymore help

Thanks, Stuart
   

Pages: 1 ... 7 8 [9] 10
Carbonate design by Bloc
SMF 2.0.10 | SMF © 2015, Simple Machines