BlueARP VST Arpeggiator development - let's discuss! (Apple M1 ready, 4K)

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
BlueARP

Post

Wow, looks like BlueArp has come of age on the Mac! I can report that after using v2.07 today in Cubase 7.5, I've not had GUI, Saw wave noise, Skins going back to default, or crashes all day today. I closed an alternate skin in one project, and it reopened right back with that skin in another.

If I do get a crash, I'll send another Cubase crash report, but so far it seems pretty stable and I am forever grateful. Thanks Wolf, you are beyond cool.

Post

Having no progress with BlueARP this and previous weekend, I had to work on Sunday. Probably next weekend will be less crazy.
But I didn't forget what's on my todo list.

Post

Just downloaded today. Excited to use this on a performance this Friday. However, is there a way to call up program changes on the fly without using the GUI? Can I send a Pgm change to the plug-in? Maybe this is VST 101 but I can't seem to get more than one pattern / synth without loading several instances on several channels and then I have to load several channels of synths to control. I'm using Ableton Suite 9.

Great work!

Post

I haven't figured out how to automate program change per se, but the Current Chain control is automatable. So I create chains for all the patterns I want on a given track... some as few as 1 pattern, but I usually have 2-4 patterns per chain anyway. I'm using Studio One, so its Control Link kerjigger picks up any automatable parameters when I change them in the GUI. Live is very good at that sort of thing too, but I don't know the exact steps in Live 9. In 8 you had to explicitly enable a control mapping mode for the instrument then, after tweaking the GUI control, you'd get a Live-native control to which you could assign an automation channel. Once you have an automation channel for Current Chain, the chains are available as values 12.5, 25, 37.5 etc. (at least in S1)... I guess its 100 divided by 8 possible chains? YMMV, but it'll work.

Post

Hey thanks so much psmacmur! I didn't understand what the chain thing was so thanks for pointing the way. I was trying to change the pattern patch but the chain switch is better since it changes in time. What a great piece of software!

Post

Hi Wolf, hope all is well with you in your busy schedule.

This crash happened as I was switching the default sync to 3/8 while the music was playing. Upgraded Op to Yosemite.


Thread 44 Crashed:: Baios Processing Thread
0 com.graywolf2004.vst.BlueARP 0x000000013871dab7 BlueARP::RequestNote(KeyInfo_t (*) [8]) + 487
1 com.graywolf2004.vst.BlueARP 0x000000013871ede7 BlueARP::ProcessDoubleReplacing(double**, double**, int) + 567
2 com.graywolf2004.vst.BlueARP 0x000000013872c795 IPlugBase::ProcessBuffers(float, int) + 69
3 com.graywolf2004.vst.BlueARP 0x000000013874c5ab IPlugVST::VSTProcessReplacing(AEffect*, float**, float**, int) + 139
4 com.steinberg.VSTPlugManager 0x000000010fdbbf7c 0x10fdb3000 + 36732
5 com.steinberg.cubase 0x0000000100dcf6b5 0x100000000 + 14481077
6 com.steinberg.cubase 0x0000000100e21bb8 0x100000000 + 14818232
7 com.steinberg.cubase 0x0000000100e23463 0x100000000 + 14824547
8 com.steinberg.cubase 0x00000001010790f2 0x100000000 + 17273074
9 com.steinberg.cubase 0x0000000100e4c513 0x100000000 + 14992659
10 com.steinberg.cubase 0x0000000100e4bf17 0x100000000 + 14991127
11 com.steinberg.cubase 0x0000000100e4c9ee 0x100000000 + 14993902
12 com.steinberg.cubase 0x0000000100e4ca5d 0x100000000 + 14994013
13 com.steinberg.baios 0x000000010f11793c 0x10f100000 + 96572
14 com.steinberg.baios 0x000000010f1135b3 0x10f100000 + 79283
15 com.steinberg.baios 0x000000010f12859f 0x10f100000 + 165279
16 libsystem_pthread.dylib 0x00007fff8e7f12fc _pthread_body + 131

Post

Happened twice now. It said the same thing at Thread 44.

I didn't have the music playing this time as I switched from 1/16 to 3/8 and then hit play. Spinning beachball ...DAW crashed immediately.

Here's some preliminary info at the top of the crash report;

Process: Cubase 7.5 [7647]
Path: /Applications/Cubase 7.5.app/Contents/MacOS/Cubase 7.5
Identifier: com.steinberg.cubase
Version: 7.5.30.243 (7.5.30.243)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Cubase 7.5 [7647]
User ID: 501

Date/Time: 2014-10-23 09:37:02.694 -0500
OS Version: Mac OS X 10.10 (14A389)
Report Version: 11
Anonymous UUID: 41D5F7A1-4579-E7A8-1DB0-6F5F6EF3668B

Sleep/Wake UUID: 78B57CB3-3E01-4573-BED9-4B2732161708

Time Awake Since Boot: 110000 seconds
Time Since Wake: 7000 seconds

Crashed Thread: 44 Baios Processing Thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000a62d0ea8

VM Regions Near 0xa62d0ea8:
-->
__TEXT 0000000100000000-000000010280b000 [ 40.0M] r-x/rwx SM=COW /Applications/Cubase 7.5.app/Contents/MacOS/Cubase 7.5

Post

Finally I got a normal weekend! Proceeding with my todo list. Also will look at this mac issue.

Post

Molodetz! Looking forward to hear from you soon. Time to support the best developer. :)

Post

funkystrings wrote:Happened twice now. It said the same thing at Thread 44...
Thanks for report. Having the same crash in Reaper, OSX 10.6. Will try to fix.

phreaque Finally I added the feature you requested - input range (wrap). Now testing it myself. Looks really useful - I can play bass line on any octave - and it never gets loo low ot too high.
Will upload the update after I fix this OSX issue, tomorrow I think (here we have 4 days long weekend till Tuesday due to local holydays).

Post

I'm speechless Oleg! Bolshoye spacibo!

Post

Update: BlueARP v2.08
Windows:
http://www.graywolf2004.net/files/2/Blu ... _v2.08.zip
OSX:
http://www.graywolf2004.net/files/2/Blu ... _v2.08.zip

Changes:
1. Bugfix: crash when sync = 3/8 selected (both windows & osx)
2. Added "input range (wrap)" parameter, not yet reflected in the manual
3. Created separate "Settings" panel, moved "semitone range" and "fine velocity" there.
Now I can add more settings and keep it logical.
4. BugFix. It seems like step mode = Tie didn't work when sync < 99%.
Maybe this bug was introduced in recent versions.

Post

Hello Oleg,

Thanks a lot for this update... :)
Till this moment, the skin issue still exists.. The BlueARP can't memorize the selected skin, it always recalls the default blue skin.
Giving a test for the new (output wrapping function) it is so great... Well done indeed :)

Post

Thank you, Oleg

Post

Hi Oleg,
the new settingspage ist a good idea. there is much space for things and it looks nice.
sometimes i have a strange issue with the velocitypage, intruduced in v2.07
Can you reproduce it? i use fl 11.1.1
Unbenannt.jpg
You do not have the required permissions to view the files attached to this post.
The good old 80s never come back
a old FLStudio nerd

Post Reply

Return to “Instruments”