Indeed!chk071 wrote:Very cool. Wish you guys all the best for your project.
I also wish you, you three, a good luck with your project as well And thanks for all who are participating in skinning or/and presets
Indeed!chk071 wrote:Very cool. Wish you guys all the best for your project.
Thank you for answering.... there is no other option for the Nova. Would you be willing to make the change and charge for the upgrade? I can't imagine it would take more than a couple hours of your time. Your Nova VST is a beautiful thing... just needs to be able to import existing patches. I am not a programmer, wish I could do it.graywolf2004 wrote:I'm pretty sure no, sorry. I just dont have time for everything and BlueARP is a priority.SayersWeb wrote:Any chance Nova Control will ever be able to import patches? It would really be amazing if it could.
Thanks!
However, I released the source code of NovaControl (made with SynthMaker, now Flowstone) on sourceforge, so anyone can pick it up to modify it, study it or whatever you want.
.jon wrote:Is there any prospect of improving the timing accuracy of BlueARP? I know that it's not that crucial for performance, but it sometimes causes problems when using it as a sequencer. Notes can always be quantised after recording the passages, but at 256 samples buffer the timing jitter is sometimes big enough to affect the rhythmical feel and thus sound design and other decision-making before recording.
Thanks for support. Currently we're in choice dilemma, but the best option goes for a tactile interface coupled with knobs buttons and sliders. The hard part will be the Matrix interface, since not only is it a metric butt ton of buttons to wire in, but it's also variable (between key select and scale note for example). So touchscreen it is for that sucker ..jon wrote:Good luck with the project! Will the main interface be a touchscreen, or button grid?
Also, still interested in the future development of BlueARP plugin, and especially the problem below.
.jon wrote:Is there any prospect of improving the timing accuracy of BlueARP? I know that it's not that crucial for performance, but it sometimes causes problems when using it as a sequencer. Notes can always be quantised after recording the passages, but at 256 samples buffer the timing jitter is sometimes big enough to affect the rhythmical feel and thus sound design and other decision-making before recording.
Hi. I know about accuracy issue and tried some stuff already, but still no luck. The problem is BlueARP sends arpeggiated notes on process() call, i.e. each time hosts requests an audio buffer. And I dont yet know how to make it send notes on exact stap start. But somehow it's possible, since some other arps do that..jon wrote:Good luck with the project! Will the main interface be a touchscreen, or button grid?
Also, still interested in the future development of BlueARP plugin, and especially the problem below.
.jon wrote:Is there any prospect of improving the timing accuracy of BlueARP? I know that it's not that crucial for performance, but it sometimes causes problems when using it as a sequencer. Notes can always be quantised after recording the passages, but at 256 samples buffer the timing jitter is sometimes big enough to affect the rhythmical feel and thus sound design and other decision-making before recording.
Ok, thanks for looking into it.graywolf2004 wrote:Hi. I know about accuracy issue and tried some stuff already, but still no luck. The problem is BlueARP sends arpeggiated notes on process() call, i.e. each time hosts requests an audio buffer. And I dont yet know how to make it send notes on exact stap start. But somehow it's possible, since some other arps do that.
It's not of high proirity for me, but I have it in my ToDo list.
Actually, i'm the main guy in the team promoting Raspberry Pi, because of my long experience with it. However, most RB-Pi chips are not suited for the use, and the complaints of boot latency makes it even worse...zxant wrote:
You could base it on Raspberry Pi, maybe?
Most of it can be found on RB-Pi chips, at the expense of the internal storage, "crucial" if i quote Oleg.Graywolf (From Email) wrote: What do I need:
1. Good enough ARMv7 (or better) CPU running at 60 Mhz +
2. SDRAM installed, at least 1 MByte
3. External re-programmable flash, at least 1 MByte
4. USB OTG on-chip
5. At least 2 UARTS on-chip (4 is better)
6. SDIO interface on-chip
LexDV wrote:Hi everyone,
I need some help. I work in FL Studio 12 and want to use BlueArp with an native FL synth, but they aren't VST's.... So how do I set it up if I want to use Sytrus or Harmor in combination with BlueArp? I use it with other VST's no problem, it's awesome, but I could never get it to work with native synths.
Many thanks in advance!
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement