vArranger Forums

Hi Dan, can you send me this beta version please? Thanks.

Kenny.

Quote from: Lylo on January 11, 2016, 03:36:10 PM
Oh yes Dan, it's right.
So, Crisis must be better than standard voice of vA, but poor compared to the new soundbanks.

Hi Lylo, can you recommend some of these "new soundbanks"?

Thanks,
Kenny.

Dan, please send me the version with VST included! I have been longing for this feature ever since I start using vArranger!

Thanks,
Kenny.

Hi Dan, would love to beta test this version!

Thanks,
Kenny.

Hey Dan, I'd like to test the new features. By the way, we should be able to run them (stable and beta) side by side, correct? They just need to be in different folders?

Looking forward to use them!

Kenny.

Additional information on this issue: With the above setup, using the button and manually clicking on the Transpose -/+ or Octave -/+, the LED feedback DOES WORK CORRECTLY! But when using the physical button on the keyboard (Novation SL MkII), the LED feedback behaved incorrect.

For example, currently transpose and octave are all at 0. Using a keyboard, clicking on the Transpose - or +, and the LED on the keyboard lid up correctly. Using the mouse, clicking the buttons so that it reset to 0, and the lid turned off. But using the physical button doesn't work as intended Not sure if I need to set the params to some other param, I've been playing with different values but none seems to work as expected.

Thanks.

Hi all,

I got the LED feedback working for everything (voice, showing variation, intro, etc...). But LED feedback doesn't work with Transpose -/+ or Octave -/+. Not sure if these 2 are sending some sort of special command or what. The settings for all buttons are the same:

Using Automap, I'm setting the buttons as: Normal Mode; Min = 0.0; Value = 1.00; Max = 127.00.

Any help would be appreciated! Thanks all.

Kenny.

Hi Dan, can you add Transpose Reset to the list of "Controllers" that we can map to the MIDI controller CC? It probably doesn't have to be on the screen, but just something that we can map to.

Thanks,
Kenny.

vArranger (and Dan) can make you a very happy person, too It's the single best purchase I have made in a long... long... long... long time... (Last time it was my Inderbinen alto saxophone, but it costs more than 8000 euros).

Kenny.

I have to take my words back Figured out the issue of Automap constantly running at 50% CPU, which is the reason for all these mess and hours wasted! It was because I disabled 2 virtual MIDI ports that was created by Automap! When installing Automap, 3 virtual ports are installed: Automap MIDI, Propellerhead Reason, and Propellerhead Reason Mixer.

Somehow instead of getting MIDI output to Automap MIDI port when running Automap, the output was Propellerhead Reason Mixer. So I went into Device Manager and disabled those 2 ports, Automap then output to the "correct" port (according to all the manuals, posts, etc...). And that was the reason for Automap MIDI to run like crazy!!! After I formatted my HDD (see above), and all attempts failed, I decided to give Automap another try. This time I forgot to disable the ports, and Automap quietly ran in the background just like any other apps!

After about 30 minutes of reconfig the buttons/knobs/sliders using Automap, I'm now controlling vArranger with LED feedback, and it looks great! The LCD screen shows the patch, left/right voice, song name, etc... you name it! Whatever you can program, it'll display on the LCD screen.

So the moral of this story: DON'T DISABLE THE VIRTUAL MIDI PORTS Unless you want to spend 20+ hours, format your HDD, reinstall all your stuffs, only to find out it was your fault.

Kenny.

Dan, I think I give up!!! Spent the entire last night to do a full restore of my computer, which I didn't backup. Luckily vArranger ran without reauthorizing (I guess the machine/hardware ID remains the same even when I completely wipeout the HDD.) Anyway, back to Novation SL MkII and LED Feedback stuffs.

I couldn't get it to work WITHOUT Automap mode! It just doesn't work, no matter what I've tried. Somehow it doesn't seems to communicate back to the controller.

I found out that I can use the Ableton Live template (Advanced Mode, #32), and LED Feedback works! However, the LCD screen doesn't display anything but "Ableton is Offline" message! That means that this template is a special template, and I was able to verify that by open it using the Editor, on Mac, it displays a message saying that this template is a "Automap" template, so it probably have some special settings in it. (When I open on the PC editor, it doesn't say anything though!)

But since I was able to open it, I've created a new template and copied the exact button settings on the Ableton template! Of course I couldn't get it to work The template is a sysex file with a bunch of hex that I have no clue what is going on behind the scene, so I don't know what are the differences between a regular template and this template. But obviously, Ableton was able to do it.

I've attached my template as well as the Ableton template here, hopefully if someone know how to view/modify sysex, they could help me with this issue! I'm starting to give up since I've spent over 20 hours on this issue already. I can't use Automap, it's running at 50% CPU on my machine, ALONE! I also have links and resources for your reference.

SL MkII Editor - http://beta.novationmusic.com/releases/sl_mkii/

Ableton setup - http://www.novationmusic.com/answerbase/en/article.php?id=560
(I followed this routing and got the LED feedback to work, but LCD screen displays the message as mentioned above)

Some info on Ableton forum - https://forum.ableton.com/viewtopic.php?f=1&t=187834

Thanks!
Kenny.

Couldn't get it to work yet, when not using Automap software, I only have the MIN & MAX, no ON/OFF. Also it seems like the computer can't communicate back to the controller, and in the process of doing a bunch of things last night, I managed to uninstall (or installed) something that my computer wouldn't boot now I need to do a full restore!

I'll let you know once I got my computer back on. Hopefully all the hardware and machine ID stays the same so that I don't have to request for new code on some of the soft synths (including vArranger).

Cakewalk is having a big sale on pretty much all the software/virtual instruments. If you are planning to use vArranger with VSTi, products such as Dimension Pro or Studio Instruments sounds great, and with this sale, it doesn't cost much at all.

http://cakewalknews.cakewalk.com/public/?q=ulink&fn=Link&ssid=19702&id=emi2mkvahk1s0kqr8gh3chww9orgq&id2=4wu29einx47r2x4r2rxeaj6g94ym0&subscriber_id=bbensqzjtujrzknpaqtcqkbrbpznbae&delivery_id=aniubzenjobkkjcewpzfzjcionwabmi&tid=3.TPY.B-pAbg.B8gk.lOUk..As28kA.b..s.3tI.a.UaVZeg.UaVZeg.HDH7EA

Please do, those LED on the encoders are pretty cool! The SL MkII Programmers Reference that I attached have information about them Whenever you have time of course, as I know there are far more important features to be implemented.

Kenny.

Hi all,

Is it possible to create a custom "voice bank"? I'm talking about the "VOICE" section where it's currently having PIANO, EL.PIANO, CHROM, etc... This is NOT the same as MY SOUNDS

Also, I notice there are .INS files posted in the forum but I how do we load those .INS file?

Thanks all,
Kenny.

I think it's working now! Can't believe somehow I missed that. When setting up value for the buttons, there are actually 4 different options to chose from instead of 2:

Min | Off - On | Max

I had always thought that they are the same, and they usually updates themselves to be the same value so I didn't paid much attention. But in order for it to work in vArranger & SL MkII context, the ON value must be "1". As soon as I set that to 1 (see picture), the beta version that you sent me work perfectly!

Been almost 20 hours to try to get this to work but when it work, I think it really worth it! The controller have A LOT of buttons, and I can easily navigates between template, controlling vArranger with this is ease! Now I need to try this WITHOUT Automap, that thing sucks the heck out my system's resource! Constantly running at 30% when I don't even have my controller on!

Thanks again for your help, Dan! You are superb!
Kenny.

If vArranger output the MIDI message back to the controller, somehow it's not showing on MIDI-OX monitor screen. Anyway, still not getting it to work, here is my current setup:

I'm using Advanced Mode (I've tried Automap as well, with similar settings). I've setup couple of buttons that select the SOUNDS, with different values and button display type just to see if they make any difference, but they seems to be the same to me. The number/value in parenthesis are the value that set for a particular setting:

VARRANGER

MIDI IN #1
   MIDIIN2 (SL MkII port 2, *this is Port 2 == U2)

MIDI IN #2, with LED checked
   SL MkII | SL MkII (*this is Port 1 == U1)

CONTROLLERS
   GROUP 1 (PIANO)      MIDI IN PORT (2)   MIDI TYPE (CONTROL CHANGE)   MIDI CHANNEL (16)   CONTROLLER NUMBER (24)
   GROUP 2 (E. PIANO)      MIDI IN PORT (2)   MIDI TYPE (CONTROL CHANGE)   MIDI CHANNEL (16)   CONTROLLER NUMBER (25)
   GROUP 3 (CHROM)      MIDI IN PORT (2)   MIDI TYPE (CONTROL CHANGE)   MIDI CHANNEL (16)   CONTROLLER NUMBER (26)

==========================================================================================

SL MkII

TEMPLATE ROUTING:    KeybChan (1)   KeybPort (1)      ComnChan (16)   ComnPort (U1)

CC#24   ButtonType (Momentary)      Ports (ComnPORT)   MidiChan (ComnCHAN)
      Control (CC)            DispType (0-127)    Press (1)    Release (0)

CC#25   ButtonType (Momentary)      Ports (ComnPORT)   MidiChan (ComnCHAN)
      Control (CC)            DispType (LED)       Press (1)    Release (0)

CC#26   ButtonType (Momentary)      Ports (ComnPORT)   MidiChan (ComnCHAN)
      Control (CC)            LED             Press (127)    Release (0)


Thanks for looking, Dan!

Hi Dan, still couldn't get the LED feedback to work. When you made the change to the beta version, was that intended for Automap mode or Advanced mode? I've tried to reset the keyboard just to make sure that I'm not doing anything wrong since I've been trying to get this thing to work for the past +10 hours Let me know if there is a specific mode I need to be in, and if you could give me an example of what the min/press and max/release (or maybe min/release | max/press, I forgot the order displayed on the keyboard), I'll give it another try.

Also, how exactly is vArranger communicate with the MIDI controller? I have vArranger as well as MIDI-OX open, but I can't see output from vArranger to the selected port for the LED feedback. Pressing a button on the keyboard shows the INPUT on the MIDI-OX monitoring screen, but then I don't see any OUTPUT from vArranger?

You are AMAZING with the Karaoke encoding option, works perfectly. THANK YOU!

Kenny.

Sorry for all the messages, I really want to get this thing to work Doing some more research and it seems like to get the LED feedback to work, the button needs to set as "TOGGLE" (maybe NORMAL too), not MOMENTARY. Some of the posts regarding this issue:

http://www.freestylersupport.com/fsforum/viewtopic.php?f=19&t=2109
http://www.fxpansion.com/forum/viewtopic.php?p=79126

I have MIDI OX and MIDI Translator Pro, is there anyway that I can use those products to manipulate the data coming in/out between vArranger and the SL MkII to be able to work with TOGGLE mode AND having LED feedback?

Kenny.

I'm doing some more experiment it by using MIDI OX to simulate the MIDI out from vArranger. It seems like setting the button as TOGGLE mode instead of MOMENTARY works. But I'm not sure if it's because the nature of the button type. Not sure if since it's toggle, the LED feedback is working by design, and it doesn't have anything to do with the way it receives the value.

How exactly is MOMENTARY work in vArranger? Are you constantly streaming the "ON" value so that the LED stays on?

Thanks.

Still couldn't get it to work, but here are some information from the user guide, hopefully it sheds some light on the issue:

Quote
ADDITIONAL OPTIONS FOR BUTTONS ONLY

DispType (Display Type): Control value displayed as either ON or OFF. The low value setting determines the ON value and the high value setting determines the OFF value. This is best suited to a bi-state parameter where you want to see whether it is in an on or off state e.g. phase reverse on a mixer channel.
LED: This is like ON/OFF except that nothing is displayed when the control is in an OFF state. ON/OFF & LED display types should be used with control type Momentary or Toggle.

For buttons, drum pads and the sustain pedal, the Press Value and Release Value should be set in conjunction with the BtnType (Button Type) setting (see below).
BtnType (Button Type): This setting is only available for buttons, drum pads and the sustain pedal. Where available, it can be found on the second page of control settings so scroll up to access it.

It should be set in conjunction with the Press and Release values for the control to determine how the button works. The options are as follows:
NORMAL: The Press Value is sent when the button is pressed, nothing is sent on release.
MOMENTRY: The Press Value is sent when the button is pressed and the Release Value is sent when the button
is released.

...
...

The 'MOMENTRY' option is not available for the drum pads because they only respond to a hit and do not have a mechanism to detect when you release your finger from them. Instead of 'MOMENTRY' they have a special 'VELOCITY' option. When this is set, the value sent out when you hit the pad will depend on how hard you hit it. The control value is still constrained within the Low Value and High Value settings. As an example if Low Value is 0 and High Value is 127 then a soft hit will give a value near 0, a medium hit will give a value near 64 and a hard hit will give a value near 127. If Low Value is 2 and High Value is 0 then a soft hit will give value 2, a medium hit will give value 1 and a hard hit will give 0.

Hi Dan, attached are the screenshots. Not sure if these are what you looking for, let me know if you want more information or something else. The MIDI settings on the SL MkII are pretty much the default values.

3 more hours wasted, couldn't get the darn thing to work Tried with Automap (using user custom template with just some CC to test), and LED feedback once again does not work. Not sure why it's so complicated with this thing? Novation kinda failed twice on me, it was the Ultranova before and this time with the SL MkII.

Anyway, with Automap, I clicked on the "Advanced", select "Automap MIDI" as the I/O, channel 1, which gave me a "Thing" to setup CC. I went into vArranger, select SL MkII as the MIDI Input #1. In MIDI Input #2, selected Automap MIDI. Was able to let vArranger learn the CC and able to change sounds, etc..., but no LED feedback.

Kenny.

Just tried to use templates 31 & 32, couldn't get any of them to work since they requires Reason or Live to be running which I don't use both. The SL MkII displays "Ableton Live Offline" and the same for Reason, I guess they did some kind of detection. I'll try Automap next but that's the last thing I'd like to do, I hate that software from my previous experience. And I'm trying to avoid adding another layer to my setup. But I'll give it a try and will let you know if it work or not.

By the way, I've been researching like crazy on this issues fo the past couple hours and found this document from Novation, maybe that shed some light on how you can make vArranger to work with Novation products I've read through the doc (didn't understand most of it), it seems to geared toward Automap but I guess you can based on that to figure out the Advanced Mode stuffs

I'm not sure if there are differences between the Novation SL MkII and Korg nanoKONTROL in term of getting LED feedback, but I can't get the SL MkII to work (nanoKONTROL works fine!). Here's my setup for the SL MkII:

Buttons 1 - 8 sends CC #1 - 8
Buttons are setup as Momentary
DisplayType: I've tried all possible combinations, which are: LED, ON/OFF, 0-127, and 64 (can't remember exactly on the 64 piece.)

All the settings are saved in a template for the SL MkII, and I've set the Keyboard communication to Channel 1 U1/M1 (Channel 1, MIDI port 1, USB port 1).
For the Common communication (which is where the buttons and controllers on the SL MkII are send to), I've tried to set them as the same as Keyboard (above), as well as I've tried to set them to a different channel and or different port, i.e.: MIDI Channel 2, MIDI port 1 (or 2), USB port 1 (or 2). None seems to work.

I can control vArranger with those buttons just fine, just that the LED does not lid up I did check the box that says "LED" and selected SL MkII output port for LED. Can anyone help as I really hope to get this working and just use the SL MkII as my controller since they have a tons of knobs and buttons that should cover pretty much everything that I need to control vArranger.

Thanks,
Kenny.

I've used the Surface Pro briefly before changing to a Dell XPS 12. It's a solid unit, very fast and perfect for vArranger with smaller VSTi/Libraries. If I didn't get the XPS 12, I definitely is going to use the Surface Pro, I think you'll like it!

Kenny.

You (and vArranger2) are amazing Thanks Dan.

Hi all,

Not sure if this is possible yet or not: I use vArranger with other VSTi plugins and other sound sources, is there a way to add "custom" voice to the "My Sounds" bar? i.e. right click on the bar, and there is an option for "custom" voice which I can specify however I want, such as Program/Bank, Preset, MIDI CC, etc...? This way, I can have this "custom" voice send a CC# or patch/bank number to my external sound sources or VSTi plugins.

Also, is it possible to send additional MIDI messages when selecting a voice? Again, there are some complex routing and multiple sound sources that I'm using and it would be great if I can use vArranger to control them all!

Thanks,
Kenny/

@jon - there are no issues, just a suggestion based on what I've seen on all the hardware/physical midi controllers out there.

@Dan - That is what I'm going to do By the way, I've used vArranger on my first gig last night and it was great, no issues at all and the other keyboardist in my band is very interested, you'll probably see a new purchase coming soon your way

Kenny.

Hi Dan,

Just a suggestion as I have spend the past couple days preparing for my upcoming gigs. In vArranger, VOICE GROUP, MY SOUNDS, MY SONGS, and the number of items on each "PAGE" varies (10, 12, 20, etc...), and that make it quite difficult to map to a physical midi surface controller, such as nanoKONTROL, Novation Zero SL, Launchpad, or pretty much any surface controllers. Pretty much all physical controllers have sets of 8 knobs, 8 buttons, 8 sliders, etc... I wonder if at some point, you could have an option to be able to layout vArranger in that MIDI "standards" so that it make it easy to control.

For now, imagine you have rows of 8 buttons, trying to map SOUNDS 1 - 10, results in having to use 2 buttons from another row, that leave the other 6 buttons somewhere in between and it's a little bit difficult to remember

Just a suggestion to make vArranger better! I'm very excited with its abilities and really looking forward for more features to come!

Thanks,
Kenny.

Superb! You are my hero 

Thanks Dan.

Hi Dan,

It doesn't display unicode at all for the entire file, attached are the screenshot from vArranger vs. a karaoke player that I found on the internet that displays unicode via its settings (Font03.png). I have also attached the MID file.

On vArranger (Font01.png), notice the 2nd and 3rd line. On the Karaoke software that was able to display correct Vietnamese (Font02.png), you'll see the characters rendered differently:

Walaoke 1st line = vArranger 3rd line
Walaoke 2nd line = vArranger 2nd line

The font that I've used in Walaoke is just a standard font that came with Windows that supports Unicode, such as Arial, Times, Verdana, Tahoma, etc...

Thanks!
Kenny.

Can we change the font displayed when opening a text/MID/Kar file for international language? I might have missed it but couldn't find an option to change the font. I have MID and Karaoke files that are in Vietnamese and they are not displayed correctly.

Thanks,
Kenny.

Yep, it's so portable and perfect for home uses when I just want to playing around with different styles, testing out songs for chord progressions, etc... Also, the nanoKONTROL can be powered from the Microkey so I just need to use 1 USB port from the computer.

It seems to be my virtual ports routing (http://www.varranger.com/vforum/index.php/topic,988.0.html) has been the issue! Today when I use the physical port, almost all the style sounds better and I don't have as much as the PERC track issues (although there are still some but I can change them.)

Thanks.

Hi Dan,

I play with several different bands and also travels all the time, as well as practicing at home (or at my bandmate locations), and therefore at each location I have slightly different gears. I have always been a "digital" musician, been playing all VSTi with laptop/tablet and just recently added vArranger to my rack (actually, been trying to incorporate vArrange at home, not yet on live gig since I just got it and still trying to know learn all its tricks - which is a lot!).

For example, at home I would just have a master midi controller (usually Axiom 61, although sometime a ROLAND A-37 connected to a USB-2-MIDI cable) and a nanoKONTROL connects to my computer. At my friend's house, I might have a Korg also connect to a USB-2-MIDI cable, but it's a different USB-2-MIDI, so I might have different port name. At local gig, I usually have 2 MIDI controllers, one is the Novation Ultranova which have a USB MIDI, and either an Axiom or something else. And when I travel, it's whatever they have at that location, I just need to connect to my USB-2-MIDI. I usually have my iPad connected to my rack as well to send MIDI controls (patch/program changes, mixer, live controls, etc...)

As you can see, I can have all kind of device names appear in my computer depends on where I'm at, and what I have been using all along was loopMIDI (for virtual ports) and MIDI-OX to route between them. It has been working great for VSTi plugins hosted inside MusicOS (from Open Labs) or MAGIX Independence LIVE host. Now I'm trying to add vArranger to my rack and I was thinking about using the same loopMIDI/MIDI-OX combo so that I can avoid having to change MIDI Ports every time (which might mess up my learned CONTROLS).

It seems to have problem with some virtual ports as mentioned. This morning I've tried to use just physical real ports and everything is working great! The LED feedback on the nanoKONTROL2 is just pure genius! Thanks for making this happen Although, I still like to be able to change physical hardwares without changing vArranger MIDI routings

I notice on another forum post, you mention having multiple vArranger2.ini files, that might work but it would be also if I don't have to think about it! How about a dialog for "saved profile"? That way if I forgot to change vArranger2.ini file, I can just browse to a different profile and bam, my mappings are all there!

Have a great weekend!
Kenny.

I'm running into issues with having multiple midi controllers (a keyboard and a Korg nanoKONTROL2 control surface). Basically I changes gears a lot and depends on the set (at home, at gig, which stage, etc...), I use different midi controllers, therefore, I'm using MIDI-OX with loopMIDI so that if I change my physical hardware gears, I just need to go to MIDI-OX and reroute/reconfig the settings, instead of manually changing the MIDI ports in vArranger.

The issues I'm having right now is that vArranger is doing a pass-thru for the nanoKONTROL and therefore, sending a bunch of unwanted CC to the SD2 (that explain why I'm having a bunch of unwanted FX or other CC-related from the SD2). Not sure how I should change my routing so that vArranger Controllers works with multiple devices.

Here is my setup:

1. vArranger is connects to a Master Control virtual MIDI port. Depends on the gig, I can have different keyboards connect to this virtual port using MIDI-OX. vArranger also connects to another virtual MIDI port, called "Controller Surface". Again, this can be changed depend on the hardware, most likely it will be the nanoKONTROL but it can also be wireless midi control signals sending from my iPad. I have set them up so that they all have the same CC# settings. The OUTPUTS for vArranger is vArranger SD2 (another virtual MIDI port that will send the signal via a USB-to-MIDI to the Ketron SD2), and vArranger VSTi (virtual port, can be used to send signals to VSTi plugins). See image #1.

2. To test out, I've open vArranger -> Options -> Controllers. I then select the Master Volume, and then move the control on the nanoKONTROL (which is current mapped to Controller Surface port). See image #2.

3. When I look at MIDI-OX, I see that instead of vArranger "translate" the CC# message send by the Controller Surface to CC7, do its magic, and sums up all the midi events then output to the vArranger SD2 port, it doesn't! It just do a pass-thru and therefore, instead of changing the volume, I'm now doing some CC Modulation in the SD2 instead. I also have the nanoKONTROL maps to other CC# that really affects the SD2 such as reverbs/distortion, etc... See image #3.

I'm not sure what I'm doing wrong here, would someone please help? I really need to be able to use the virtual midi ports, like I've mentioned, I changed gear a lot and I need the ability to set them from MIDI-OX instead of having to change them from the application.

Thanks for looking!

Kenny.

I've been doing some more reading on the forum's archive and seems like the issue with the Perc track that I've mentioned is very similar to this post by user angel1000 . I have a SD2 with SN that ends with 16xxx so I think I don't have to do the update, but not sure how to make this issue go away!

What is the proper way to mix/match vArranger with Ketron SD2 and VSTi plugins? This is my current setup but sometime the styles didn't played correctly, especially with drums/perc tracks:

vA MIDI In 1: M-Audio Axiom 61 keys.
vA MIDI In 2: Korg nanoKONTROL2
vA MIDI Out 1: USB-to-MIDI (connect to the SD2, SD2 mode was selected)
vA MIDI Out 2: loopMIDI virtual port (GM2 mode was selected)

My VSTi plugins (Hypersonic 2, SampleTank 2 for GM, as well as several other modules for specific sounds) are hosted by a VSTi host, the host'd MIDI IN is loopMIDI (output 2 from vArranger).

When changing styles from vArranger, my GM modules (Hypersonic 2, etc...) responded correctly and I got the sounds from them just fine, however, a lot of the styles (downloaded from the "Download" area) have problems with several channels, most noticeably Drums and Perc track. Not sure if that is the way it should be and I need to fine tune those problematic styles, or I'm doing something wrong?

Also, it seems like the SD2 module works best with Ketron styles (understandably, since they are from the same maker), but a lot of the Yamaha TYROS and Roland styles (again, downloaded from this forum) are also having with Drums/Perc tracks. Often time I heard weird sounds coming out of them, most of the time, from the Perc track. Any recommendation? I'm totally a vArranger newbie and I really looking forward to learn more about this amazing software!

Thanks,
Kenny.

Thanks Dan, that did the trick!

I have no idea what I did but styles are having tons of fx coming out of the Ketron SD2 (reverbs, distort, chorus, etc...) and it's unplayable at this time Is there a way to reset all the FX from SD2?

And on the same line, is there away to NOT modify the SD2 effects at all? I've remap some of the CC# to my keyboard to control vArranger buttons but I'm not sure if that somehow sent to the SD2 and changes the FX level.

Thanks,
Kenny.

Thanks Dan, I'm really digging vArranger more and more each day! Glad I made the purchase.

Can someone please reup the file? Thanks a lot.

I'm having same issue and having not running vArranger with any other Windows versions before, I didn't know that it was strictly a Win8 issue It doesn't take as much as 3 mins but about 1 1/2 min is normal for vArranger2 1.17 to show up. Hopefully it can be fixed soon.

Kenny.