July 31, 2021, 02:11:20 am
Welcome, Guest. Please login or register.
Did you miss your activation email

Arturia Forums

Recent Posts

Pages: [1] 2 3 ... 10
I'm using Presonus Studio One 5 as my DAW. I have PB Connect working well, but when I record a sequence of midi events in S1, then play them back (triggering Polybrute from events in in DAW track), it takes like 2-3 bars for Polybrute to settle down to the tempo the DAW is set to. Even if PB tempo is already set to the same value as that of the DAW, it will wonder around a bit (+/- a few bpm).

This causes problems because it makes not only timing oddness, but pitch is off, too, until Polybrute tempo settles down to that of the DAW, usually within a couple seconds, but in that couple seconds, things can sound pretty sour.

I've tried setting Clock on the PB to different values (One step, 24PPQ, 48PPQ...) No effect.

Anyone else have this issue?
Spark unfortunately hasn't been updated since it was last sold with V Collection 4 so it didn't receive the UI upgrade.

My totally personal opinion without the benefit of any inside knowledge is that it's verging on being 'abandonware'. The minute they stopped shipping it with V Collection I realised it was the beginning of the end.

Thanks for the response and for your insight. Even at 50% off, it seems expensive for abandonware, so I'll hold off for now ;)
... but for me worked :)
Both standalone and plugin loads now fast as expected.
In regards to recording pitch bend, mod wheel, and aftertouch data, I have been told that there may be memory limitations that would make that difficult. And also that the sequencer, being a "step" sequencer, can't send data continuously. Even tho Control Mode records CC data, and CC stands for Continuous Control.
So, seriously. How much RAM/storage does the KSP have? How limited is it? RAM is incredibly cheap, so I see no reason Arturia would skimp on that. Or did you?
MIDI data is inherently small. Takes up very little space. CC data is only 8-bit and PB, MW, and AT are 14-bit. VERY VERY little data. We're talking a few hundred kilobytes for a complete classical work in MIDI including all the instruments and control data for those instruments.
Soooo .... How is it even REMOTELY possible that memory could be a potential issue in recording such data? What, did you only put a couple megs in this thing? If so, shame on you! If not, then what's the problem? Is the data not stored as standard MIDI data and in some proprietary format instead? Why would you do that? That would be a ridiculous design decision.

Furthermore, regarding being a "step" sequencer and thus not being able to actually send continuous data.
Okay. Um ..... Well ... If we record notes without quantize on, it'll record EXACTLY as played. Not directly on the beat. This means that the data storage of notes is granular. I.E.- The data is not simply stored "per step." There are many many tinier divisions of each step. If this weren't true, then quantize mode wouldn't matter. All notes would be triggered on the beat.
As such, it makes zero sense that the KSP wouldn't be able to send continuous data. (See above regarding what "CC" means)

Finally, why are you ignoring the KSP so much? It's almost like you're embarrassed by it, when it could be one of your flagship products. HELL! You pushed the KeyStep 37 harder than you've pushed the KSP. WTAF.
Perhaps you should fire the KSP design team and put the original designers of the original KeyStep and BeatStep products on it. Why you didn't do that in the first place boggles my mind.

I have repeatedly defended Arturia. I have many Arturia products and, in general, am quite happy with them.
The way you've been treating the KSP tho .... Like it's some "problem child" that you'd rather not deal with. It's aggravating as hell. Seriously!! It took a year to get the 2.0 firmware out, which then broke several things. What, is it gonna be another year before there's another REAL firmware update? 2.0.1 doesn't count since it's pretty much just a bug fix.

Get on the ball here Arturia. WTAF. C'mon. You're a major company and there is ZERO excuse for this crap.  >:(
Analog Lab V - Technical Issues / Re: Slow loading time on a powerful computer?
« Last post by moaby on July 30, 2021, 09:06:48 pm »
That makes absolutely no sense.

After deleting the Presets Data File ALab starts quickly - but then it takes several minutes to relocate  all instruments banks and (16.000) preset files.

After that, any new start of ALab is as slow as befor.

KeyStep Pro - Feature Requests / Re: One set of Control knobs per Track
« Last post by artao on July 30, 2021, 08:57:46 pm »
The manual is not clear on this. I just re-read the entire section on Control Mode.
It sure sounds like every track (and every pattern in every track) can indeed have its own set of control knobs and CC data.
On top of that, one track can be put into a "Live Mode" Control Track.
Nowhere in the manual can I find any indication that only one track at a time can play recorded CC data.

If this is indeed the case (that the KSP can't do those things) the manual is VERY misleading and the design team really FSKED UP!
I honestly haven't explored Control Mode a helluva lot. I am now curious and want to dig into it. My brain OTOH has zero creative potential right now, so it'll hafta wait.
KeyStep Pro - Technical Issues / Possible FIX For Broken MIDI Clock Sync
« Last post by artao on July 30, 2021, 08:39:59 pm »
I also posted this in the thread all about this problem. I'm starting this new thread for greater visibility.
I may have found a "fix" for this problem. It seems to be related to this new "feature" regarding how the KSP "samples" the Tap Tempo button.
Go into the Utility Menu on the KSP. Scroll all the way down to Misc and open that. Scroll down to Step Listen and enter that.
Turn OFF Step Listen. Save and exit the menu system.
This appears to have fixed the problem for me. Does it work for you?
I sent an email to Arturia support.
As a solution they suggested this procedure:

"Delete a specific temp file called "db.db3".

MAC: /Library/Arturia/Presets
WIN: C:\ProgramData\Arturia\Presets

If you have not enabled the display of hidden folders please go to your file explorer -> display -> check "show hidden folders"

Alternatively, you should be also able to directly copy/paste the path indicated above in your Windows File browser address bar.

Once this file is deleted, the preset list will be updated on software opening."

My comments:
Indeed the loading time of both standalone and plug-in dramatically changed to very fast. 
Please update to latest version and use vst3 if you can.
I think that's a solution !!! ;)

Modular V Users Community / Re: Recording of the sequencer in midi
« Last post by LBH on July 30, 2021, 06:32:31 pm »
Hi nohijo,

Please keep in mind, that you have posted in a forum for a legacy product.

Modular V does'nt output midi.

The OP say it's possible to record the audio outout live. That's true. But if it can be done live, then i don't know which parameters that can't be recorded as midi automation data, and then be played back and control Modular V afterwards.
You can allready record and/or add both midi notes and automation in a DAW.
It's also possible to use multiple instances and presets of modular V in a DAW.

Keep in mind that the sequencer in Modular V also is used for modulation instead of midi notes.
And keep in mind, that the sequencer in Modular V can control individual modules individually with individual sequences. That can't be done, if Modular V just is being played by a simple midi note from a DAW on a single midi channel. Something far more advanced would be needed - also certain advanced functionality from the DAW.
MicroFreak - Feature Requests / Re: Custom wavetables
« Last post by adrianskerbage on July 30, 2021, 06:17:37 pm »
+1000 to custom wavetables!
Pages: [1] 2 3 ... 10
Carbonate design by Bloc
SMF 2.0.17 | SMF © 2019, Simple Machines