Any chance to look at issue I reported a few posts ago?
Dependency on loop while syncing to beat drives me crazy
![Sad :(](./images/smilies/icon_sad.gif)
Since Graywolf is not free lately, I'll try to assist...maxym.srpl wrote: ↑Thu Jul 18, 2019 9:56 pm Hello
Any chance to look at issue I reported a few posts ago?
Dependency on loop while syncing to beat drives me crazy![]()
Appreciate your input matePeteInNeedOfABeat wrote: ↑Fri Jul 05, 2019 11:30 am
1. ..... Maybe an option to set a "custom scale" would be the perfect solution here.
2. A "random"-step-type in semitone-window that selects a different note each runthrough. Maybe this would be better as an option in the "Auto Filter-Section": "Rand Key Select" in percentage?
Sunny greetings from Germany,
Pete
I'll try to find such option
How much BPM needs to be changed and what should I expect?
As low as possible, to find out if the speed up faulty notes coming from BlueARP are result of multiplying DAW BPM or just merely random glitch.maxym.srpl wrote: ↑Thu Jul 18, 2019 11:39 pm
How much BPM needs to be changed and what should I expect?
That's intended actually, for the reason of maintaining arp/phrase timing aligned to the DAW sequencer pattern(s), any song/project mainly is a cluster of several 16 or 32 steps phrases.And question on additional issue. Why BlueArp when in sync to beat mode, syncs to loop beginning not to project beginning? In other words, it takes loop beginning as beat reference. Is it intentional? Could be disabled?
Hmmm, interesting indeed!boriskarloff wrote: ↑Fri Jul 19, 2019 4:23 am Hi, guys. Few weeks ago I discovered exactly the same behaviour like in maxym.srplvideo. But with one difference - I was at 138 BPM and the dots were much faster and jumping randomly across the pattern width.
My specs: i7-860, Win7 x64, Reaper x64
Indeed, then it's not a hardware issue at all... Apparently it's Reaper vs. BlueARP, I'm sure Graywolf can provide the solution for this issue.maxym.srpl wrote: ↑Fri Jul 19, 2019 8:58 pm I'm on Win 10 64bit
MSI Tomahawk, i5 6700K (skylike), Realtek HD through ASIO4ALL.
I don't think it's related to audio interface, because there are scenarios which makes it working properly.
Also what is is interesting, this issue is dependent on loop existence.
Guess reaper segmentation is varied from other DAWs, else, what you need can be done using other DAW.Regarding dependence of 'sync to beat' on a loop: I don't use project loops at all as song parts. But I often (almost always recently) use sync to beat. I would like to make BluArp dependent on project beat, being loop independent.
You're rightI'm using loops occasionally to temporarily focus on some details of composition (ie during mix). But then I need to take care about proper placing the loop to not shift sequence. It's disturbing/annoying.
Good idea...maxym.srpl wrote: ↑Fri Jul 19, 2019 9:19 pm If it's indeed Reaper issue, I could report it or file a feature request. To do so I probably need more details to pass to developers. Could you provide description what would I ask for?
Thank you for your help
with regards
DigiPRO wrote: ↑Sat Jun 22, 2019 9:17 amBlueArp VST doesn't seem to transmit midi out all with Maschine software environment. Wondering if that is a Maschine software limitation as BlueArp works well in Cubase etc.phreaque wrote: ↑Sat Jun 22, 2019 8:01 amhttps://support.native-instruments.com/ ... nstruments
Check the link above, consider BlueARP as an external midi device at some point that is virtually talking to internal midi inputs.
Maybe the developer has some workaround to share?
Cheers.
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement