Novation Launchpad

[Mike]

This topic is split off the External Controlle (http://forum.vidblaster.com/showthread.php?t=131)r feature request as it will focus on using the Novation Launchpad (http://www.novationmusic.com/launchpad/) as (a) controller for VidBlaster.

A quick recap.. This cool midi controller is available internationally, costs about US$ 150 (which remarkably translates to 175 euros) and therefore very affordable. Check out this YouTube video (http://www.youtube.com/watch?v=gMgxLPcq-3o) demonstrating its use for audio. Here's a link (http://www.illuminatedsounds.com/?p=583) of the controller's insides.

Please keep this thread exclusively to this controller and only post here if you own one.

[Mike]

I have the launchpad and wrote some code to control it, which works. I love it! Now I need a simple task to start with because

1. I am hoping others will feel encouraged to buy one and join us to think about the best way to use this controller,

2. I want to see if the little test code works fine on other machines,

3. I need to carefully think about the interfacing to VidBlaster, and

4. I want to make sure the communication between VidBlaster and the controller is in no way effecting the operation of VidBlaster.

Any suggestions?

[Mike]

Ed, do you have any app that makes a key do something when it is pressed? It looks like the controller sends the key when it is released. Although this is common for software buttons in Windows, I specifically changed this behaviour in the Video Switcher as it seemed more logical to take action when a key is pressed. I assume hardware video switchers work like this too.

[Mike]

Got confirmed by the experts (thanks twitter) that professional switchers switch on press, and figured out how to do that with the launchpad. Still loving this thing!

[EdEstes]

I am willing to help however necessary. If you post the test code I can run it for you to confirm it works in a couple of other environments.

I've thought about how I'd use the controller a little bit but need to take a little more time to flush out my thoughts. (didn't think you'd get to it so quickly!) I'll post a detailed message tomorrow after recovering from our Thanksgiving feast. :)

--Ed

[Mike]

Thanks. Meanwhile I hope more will join.

[Echo7]

If this thing works like it is said, and Mike is working it up for VB, it looks like VB can be hooked like a professional switcher??????

[Mike]

Yep. And if you buy one you too can join in and decide how this thing is going to function. We've got 80 buttons with multi-coloured lights to work with :P

[superroach]

This reminds me of a Kaossilator (http://www.youtube.com/watch?v=aeQOuNBuJwg), which is used as a live audio beat mixer. Heaps of fun to use.

The only main function I could imagine vidblaster integrating with it would be the slider function mapping to cameras. It would in one go emulate the entire idea of having a "group" of objects, such as multiple overlays with a scoreboard all fading in together.

The tutorial video which is a follow up to mikes video shows it in actual use in another program, which might gives others ideas for its use.
http://www.youtube.com/watch?v=6nOAtX_U2gk&annotation_id=annotation_16988&feature=iv

[Mike]

Thanks. But please note I am looking for feedback from those who actually have this controller (together with my test software) as you really need to be playing with it, pushing and feeling these buttons, to be able to translate it to VidBlaster. The audio demos are cool, but don't provide enough (tactile) info.

[Johan Lundberg]

Just ordered two of these. Exciting... :)

[Mike]

Good to have you onboard Johan! But two? I have been thinking it might be possible to use them side-by-side for major productions, but I'm not there yet.

[Johan Lundberg]

Well Mike, someone needs to push your development. ;-)

seriously, it seems to be a cool device which I think we can use for other stuff too. Also the price was good.

[Mike]

When do you get yours?

[Mike]

I've uploaded (http://mikeversteeg.com/temp/Launchpad.zip) a little demo program that allows you to play with the controller and hopefully get creative ideas :) Press a key on the first 6 rows and it will cycle between off - green - red - off etc. The bottom 2 rows act as a video mixer with preview and program bus, the bottom right round button is "Take". All that is required is you install the driver that comes with the Launchpad.

[Johan Lundberg]

Cool Mike! I guess I will get them beginning of next week. I'm currently in Düsseldorf working with the host production of "Race of Champions" (www.raceofchampions.com (http://www.raceofchampions.com)). Won't be back home until monday anyway, but now I got something fun to look forward to when coming home! :)

[EdEstes]

Very nice! I have the app running and the LEDs are working as expected.

So here are some of the initial thoughts. This is a very powerful piece of hardware and we can get overwhelmed with features if we don't take it slowly so I am only listing a few this time. Some of these you've already got in the demo but I will throw out anyway to be complete:

The round buttons along the top would be to switch the controller into different modes. Everything outlined here will be in the "mixer" mode.

Here is a image representation:
http://forum.vidblaster.com/attachment.php?attachmentid=148&stc=1&d=1290883502
The bottom row is the "Preview" source. Only one button can be select in normal mode.
The next row up is the "Program" source. Only one button can be select in normal mode.
The first two round buttons on the lower, right represent "Transition" and "Cut"
The third square row from the bottom is the "Overlay" source. The first time you press a button, it goes into queue mode (represented by yellow). The second time you press it it goes live. (represented by red) That way you can queue up a couple of overlays. Then you can press the third round button from the bottom on the right to turn on the queued overlays. The fourth round button from the bottom on the right is the turns off the overlays. When you press it, all active overlays are turned off. If no overlays are active, pressing it turns off all queued overlays.
The top row of square buttons are volume indicators - there are two modes. One is the live volume reading and the other is to set the volume. The round button to on the top-right (next to the row) allows you to toggle between these two modes.
The second row of square buttons from the top is for the video transition. The buttons light up from left to right, visualizing the fade during a transition. Toggling the mode allows you to manually control the speed of the transition by rubbing your finger across the buttons from left to right. The row turns to yellow when you are manually controlling the transition. As you rub across, the buttons turn to red, indicating the current transition setting) These two modes can be toggled using the round button to the right, second from the top.
The final feature is to allow for "Auto" Transition. When the user clicks the top-left round button (learn) then more than one Preview button can be selected. (like the Auto check boxes are in the Video Switcher panel now) When a preview source is selected the button lights up in yellow. If pushed again it is turned off. (this duplicates the checking of sources for auto) Once you have all the source selected you want, you press the second round button from the top-left (view) to start the auto transition. Pressing it a second time turns off Auto Transition.


There are a few rows that are not used. I didn't know if we wanted another Overlay row or if others had some additional ideas, so I left them open for now.

That's about it. Let me know if I need to clarify anything...

Later!

--Ed

[Mike]

Good start, thanks. A few things I will comment on later, I first want to concentrate on the switcher. I included it in the demo as it was obvious to make it like this, but also so you could use the round button as take, do you like it? I wish it were a larger button and find it a bit small. Could not come up with a better alternative though.

Do you have a background in broadcasting? I'm asking because you did not reserve more buses for the switcher, I foresee Aux buses for one..

Did you try the sliding thing? I find it works unreliable, you can easily miss buttons if you try to slide to fast, partially caused by the square corners of the buttons. I can't envision myself doing a transition that way, not live or prepped.

As for the overlays, great idea. I do think we should also see this back in the GUI. Maybe an extra row in the switcher? Or go bigger and make a macro bus, which could do the same but also other things.

It's good to look at the whole picture, but I'd like to stress I want to start with something simple so I can add something working to the next release. Nothing stimulates creativity then actually using this controller in real life. I feel the preview/program buses should be the first to be implemented. Next week I hope Johan and Peter will join us so they can offer feedback on this part as well.

[EdEstes]

I am not in the broadcast business directly but I have worked "around it" for years. Both of my existing SaaS businesses involve television broadcasters (http://www.webmediatools.com) and entertainment studios (http://www.mymediabox.com) and I have family that works at Harris Corporation (http://www.broadcast.harris.com/default.asp) here in Cincinnati, but I have never spent any significant time in the broadcast booth. (which is why I overlooked AUX buses and probably have a different flow for the Overlay buttons)

I have spent a great deal of time in the online/interactive streaming space. (I briefly dabbled in video editing, getting certified for the Radius VideoVison non-linear editing solution back in the mid 90s) My excitement with VIDBlaster is in the "personal broadcast" space, where you don't have a large studio but smaller venues. Something were one or two people can walk in and produce something of great quality for a smaller audience. (viewed by hundreds/thousands of people online or on air with mobile HD broadcast) This is what we are exploring for our customers, helping them create opportunities in smaller streaming/mobile broadcasts. I am in the process of creating some mobile studio examples where a whole broadcast can be created by equipment pulled out of a backpack. Not that I don't appreciate the traditional broadcast use of VIDBlaster, but I see a significantly larger audience using the professional/studio version. Church broadcasts, high school sporting events, business conferences/luncheons, etc. (OK, maybe I'm bias, but that's where my passion is...)

So back to the topic at hand. I agree, sliding buttons do not appear natural and it would be more obvious in video if it's not a smooth transition. It is something that most of the demos of this product show so I would think we would get use to it. (keeping in mind that this is the low-end solution for the masses) The high-end unit (which I think is for professional broadcasters) would have more traditional controls.

I think adding a row for the Overlay in the software would be great, a third row on the switcher module. I would vote for keeping a separate "macro" control panel since the two have different roles. (I'm thinking software macros, so forgive me if there's a macro term in broadcast! :))

--Ed

[Johan Lundberg]

Back home in cold and snowy(!) Sweden and got my launchpads today! First impression is that it seems really nice. No broadcast style buttons, no T-bar, no knobs to turn, but I still find it nice and am quite sure we will find it useful.

Regarding Ed's layout, I also think it's a good start.
From a professional TV-broadcasting point of view you would indeed expect to find the Program and Preview rows exactly as placed now. Above that you probably would like a row (or two) with assignable buttons for macros. Above that you would have your Mixer Effect rows (M/E), which doesn't exactly exist in Vidblaster. Vidblaster's "Video Effect module" is a bit like a light version of a M/E , but not quite the same. M/E rows would look exactly like the Program/Preview rows.

On top would be aux buses, where top row would select which aux bus to control and the row under it would choose what source to send to the selected aux bus. I guess aux buses in this case would correspond to the "Video output module" in Vidblaster.

You would expect to find the keyers (overlays) to the right, vertically layed out where the row with play buttons on the launchpad is located.

This is just taken directly from the broadcast world and I haven't had much time to think about a good Vidblaster layout yet. What's good for a TV-broadcast might not be the best solution for Vidblaster use.

I will have a play with this new toy and come back with some suggestions regarding layout.


Regards,
Johan

[Johan Lundberg]

Been thinking about this some more and I think focus must be only on what you need at your fingertips when in production. Everything else should be setup and adjusted in the software.

I find Ed's idea with the overlays interesting. It would be very logical if the play-buttons to the right always have take functions for. Bottom one works as a take for Program/Preview, just like in Mike's demo, switching Program/Preview. Play button to the right of the overlays could maybe function as a take (on/off) for selected overlays as in Ed's suggestion and so on.

I personally don't feel the need for either volume adjustment or the virtual T-bar, which i agree with Mike would not work very well.

Regarding the rows I would like to see (from top to bottom):
1 - Assignable video output
2 - Assignable video output
3 -
4 -
5 - Overlays
6 - Macros
7 - Program
8 - Preview

I'm not 100% sure of the placement of the overlays but I would personally much rather keep a row for assignable macros close to the PGM row than putting the overlays there.

I guess in a perfect world, the absolutely best and most flexible solutions would be if you could assign the rows yourself. I'm not talking about button for button assignment, but rather just which of the pre-made rows goes where. If you number the rows 1-8 you could let the user customize on what row to put each function. For instance assign Program to row 8, overlays to row 2 etc, making it very flexible regardless of type of production.

Imagine how cool it would be if you have user assignable rows and support for two or more Launchpads. This would truely open up for multi-person productions where one person could cut the cameras, an other person, on his own Launchpad controls the overlays, players etc. For larger productions this would be very very useful.

The video out selector (row 1-2 in my example) would be really great in cases where you need to change the source for a video output during production. For instance if you are feeding a screen that is used in your set or studio. This way you can easily change what's shown on that screen without moving away from the Launchpad. Even better would be if you could assign any routable output to a row.

I'm thinking that alot of this might be possible features for later versions of Vidblaster as they most likely involve alot of work to implement. I think the most important thing now is to get a working Video switcher (Program/Preview) with control of overlays (on/off). The rest is not in any way intended to be v1.22 features and some of them might not even be realistic to implement at all.

Will let this sink in to my head and give it some more thought.

Regards,
Johan

[Mike]

Johan, isn't video output done through an aux bus? I.e assign video output module 1 to aux1, and that makes your video switcher (top to bottom) aux1/program/preview? Which of course 1:1 translated to the launchpad, i.e. bottom 3 rows and not what you suggest.

[Johan Lundberg]

Normally it's done through an aux bus yes. In Vidblaster's case, since there is no such thing as an aux bus, I was thinking you could control the routing to the video output instead. Adding true aux buses would of course be a way better solutions since you could then route that aux bus to any video outputs, video effects, recorders or streamers. Absolutely the way to go if possible!

[Mike]

The video out module is part of the aux bus structure I have in mind. Which is part of the video routing I am (slowly) integrating. This is all part of a bigger picture that I have in my mind :)

OK, so we agree on that. I guess the bottom part has been defined then. You don't mind the small round take button? I find it works less intuitive then the keypad's enter key, but then I have been using that for 4 years so it may need some time.

@Peter: you still have not received your launchpad?

[Johan Lundberg]

Excellent Mike.

It would be really interesting to hear some more about the new structure and your plans. I will gladly discuss this further and support you in any way I might be able to.

:)

[Johan Lundberg]

I think the take button will work just fine.

[Johan Lundberg]

Also, I still think the aux rows should be on the top rows of the Launchpad, starting from the top and down, or of course user assignable... ;)

[PeterHazenberg]

Today I finally got some time to play with the Launchpad. I have to admit that it's more solid than I expected (which is good!)

@Mike: After installing the driver and the Launchpad demo software there was a nice "rainfall" ;) of lights and the buttons work like you described. Unfortunately the actual switching doesn't work, while the keypad (and of course the mouse) still work. I tried launching the program in different orders but without any difference. I have to figure out what's going wrong

BTW: I agree that AUX buses should be the top rows of the controller.

[weconverse]

I've just been lurking this thread. While the launchpad/external controller seems really cool (and affordable), it is nothing I personally need for our productions right now. And I need to focus my attention on some more urgent matters. Therefore I've been silent here.

Furthermore, Mike has a "bigger picture" in mind. So I find it hard to come up with valuable ideas without understanding that picture.

The video out module is part of the aux bus structure I have in mind. Which is part of the video routing I am (slowly) integrating. This is all part of a bigger picture that I have in my mind :)

[Mike]

For those not following my tweets (http://twitter.com/#%21/MikeVersteeg), I have started working on the External Controller module which will obviously support (only) the Launchpad. Are there any new owners?

@Richard: Thanks, but I only want hands-on feedback (http://forum.vidblaster.com/showpost.php?p=9920&postcount=10) for this controller. Feel free to post general comments in the External Controller topic (http://forum.vidblaster.com/showthread.php?t=131).

[Mike]

Figured out a way to interface with the launchpad (or any other midi controller) without affecting VidBlaster's operation. I use VidBlaster's API internally, which I obviously had to extend to accomodate the new commands. The more I work with the API the more I am liking it as a possible implementation for macro's. Instead of pulling commands from the TCP server, why not pull them from a text file? But that's for another thread..

I now have the preview bus, program bus and cut and trans buttons working so can fully operate the switcher with the external controller. Suddenly VidBlaster looks like a whole new program!

I'll be releasing this asap in v1.23 so you can play with it. Ed, any chance you could adjust that fancy graphic to show only the functionality I implemented? I'd like to add it to the Help.

(And I am silently hoping someone will make a cool video of this new feature to excite others.)

[EdEstes]

I'll be releasing this asap in v1.23 so you can play with it. Ed, any chance you could adjust that fancy graphic to show only the functionality I implemented? I'd like to add it to the Help.
I'd love to help! Let me look into it when I get to the office.

--Ed

[Mike]

Thanks! I did not want to hold up the release of v1.23 (http://forum.vidblaster.com/showthread.php?t=1793) any longer so will use your picture in the next release.

[Johan Lundberg]

Excellent Mike! It works just as expected. Can't wait to see what's next for the Launchpad, and the "big picture"! :)

[Rafal Oramus]

Sounds awesome! Could anyone make quick video, to see how does it work?

[PeterHazenberg]

Next week I hope Johan and Peter will join us so they can offer feedback on this part as well.

It took a week+ :( but herewith some first feedback...
1: Since many users use VB for different shows, Is it possible to have different "layouts" e.g. 2 by pressing "user 1" and "user 2" buttons on the top?
2: Can one of the layouts be a "16 input" switcher? This means the 2 bottom rows are preview and program representing button 1 to 8 of the switcher and row 3 and 4 representing input 9 to 16.
3: I'm thinking of a nice way to control my playlist. What about the 4 round arrowed buttons at the upper left corner. With "up" and "down" you should be able to scroll through the list. "right" should represent PLAY (and after finishing cue up the next in the list) and "left" should cue up the last played one back for a repeat of that one.

...more to come later ;)

[Mike]

@Ed: I'm about to release a new version. Any chance you can make me that graphic?

[PeterHazenberg]

I'm using 1.23 and Launchpad a lot lately. If you appreciate my personal functional layout just let me know.

PS: just finished guest seminar at University of Utrecht about VidBlaster. Guess what.... they loved it ;)

[Mike]

Yes, I always find it both fun and a potential source of inspiration to see how others use VidBlaster and/or related devices. Feel free to post a picture or video.

A seminar about VidBlaster in my own country? Is there a video of that?

[EdEstes]

@Ed: I'm about to release a new version. Any chance you can make me that graphic?Yikes! Sorry about that - I thought I posted the updated graphic. I should be able to get something up to you later this evening.

--Ed

[EdEstes]

Here you go!

http://forum.vidblaster.com/attachment.php?attachmentid=188&stc=1&d=1296783188

--Ed

[Mike]

Thanks Ed, it's in the new Help.

[PeterHazenberg]

A seminar about VidBlaster in my own country? Is there a video of that?

Part two is scheduled for next Tuesday. I try to get some pictures made :)

[feha]

I will be buying one, this is great if it can work as video switcher ...

[PeterHazenberg]

Hi Mike,

Last week I installed the Launchpad at The Crowds test setup. Since we use more than 8 "channels" on the switcher it would be nice to continue 9 to 16 at the 3rd (preview) and 4th (program) row. I installed Launchpads AutoMap but it doesn't show your configuration. How did you manage to assign the 1st and 2nd row and do you have a clue how to assign the switcher shortcuts (8 to .) to these rows?

[PeterHazenberg]

Here http://chris-peter.nl/wedding/wp-content/uploads/2011/02/screen1.jpg you see a screenshot of the midi inputs while pressing buttons 1 to 16 (row 1 and 3) of the launchpad...

[QuinnQuality]

I have just ordered one and hope to tell you more about my experiences soon.

[QuinnQuality]

I received the Launchpad today and i love it so far. The only thing i don't like, is that the bottom left knob, is not camera 1, but the "black" setting. Otherwise it's great and i am really anxious to see what more cam be done with this beautiful device. BTW, i bought it for 133,- euros included tax.

[Rinkfink]

Just received mine today...
Looking forward to testing it!

[QuinnQuality]

We tested it during a life broadcast of a local sport event, was great to use although it is not fully programmed by Mike yet. http://www.youtube.com/watch?v=IE0Twwa4d5U

[Mike]

@Greg: Great!

@John: Nice. Did not watch the entire video, assume there is no behind-the-scenes footage so we can see you use it?

As for the black, that's part of the video switcher. I think it would be illogical to have it missing.

[QuinnQuality]

Sorry, hope i can make it next time for you.
(can imagine why you did not look at the entire shoot, the show was horribly presented by a radio guy whom didn't understand the meaning of "TV")
Setting we used was 4 camera's connected to the EMS XtremeRGB-Ex8, build in a MacPro using Windows 7 64bit (Bootcamp), switched in VidBlaster with the Launchpad and recorded in VidBlaster.

[Rinkfink]

I'm very excited about the possibilities, now I just have to wait till I'm able to upgrade to Studio, hopefully sooner than later!

[QuinnQuality]

I love to work with it. I only would really have the most left button to be camera one instead of the "black" choice.

[Mike]

Peter asked to grow the video switcher from the bottom up if more than 8 sources are available, does everyone agree?

If we do this, wouldn't it feel more logical to have the numbering going from left to right and top to bottom, i.e. bottom row has the last sources, not the first?

[QuinnQuality]

Left to right and from the bottom to top is my preference. When the bottom switches are for camera 1 to 8, it will be used like this most of the times. More camera's can go to row 3 and 4 would be my humble advice.

[Johan Lundberg]

Buttom to top would be more logical to broadcast users as you expect to find the Program and Preview rows at the bottom.

Perhaps a separate request, but how about a way to enable/disable a module to show up on the switcher module?

Most of the time I end up having alot of Video Effects and players that only feeds another module and never ever will be cut directly on the switcher. Being able to disable those sources would make the rows on the Launchpad last longer.

[EdEstes]

Just out of curiosity, what are the most sources people typically have in a production? If we move to 16, is that enough for the high-end broadcasters?

--Ed

[Mike]

@Johan: Already had that idea. To avoid off topic posts I created this (http://forum.vidblaster.com/showthread.php?p=13055) place holder.

Why is bottom to top numbering more logical, and what does it have to do with the buses? They would be in the same place, I'm only asking about the numbering.. I do realize we could also alternate them.. Perhaps I should give some examples..

What we have now is
12345678 (preview)
12345678 (program)

a) What I think Peter asked for is
90123456 (preview)
12345678 (preview)
90123456 (program)
12345678 (program)

b) and what I asked was if it would not be more logical to do this
12345678 (preview)
90123456 (preview)
12345678 (program)
90123456 (program)

c) but I just realized there is another way to do this, namely
90123456 (preview)
90123456 (program)
12345678 (preview)
12345678 (program)

@Ed: Won't be a problem (http://forum.vidblaster.com/showthread.php?p=13055).

[Rinkfink]

My first inclination was along your line of thinking Mike, but after thinking about it, the flow is from bottom to top, and suggestion (a) follows that logic...
definitely not (c).

[PeterHazenberg]

option (b) has my preference since it's closest to professional switchers. (although extra rows are ME-rails in this case)

http://www.obgroup.com.au/mvS-6000d.gif

[Johan Lundberg]

Why is bottom to top numbering more logical, and what does it have to do with the buses? They would be in the same place, I'm only asking about the numbering.. I do realize we could also alternate them.. Perhaps I should give some examples..


What I mean is that a user coming from the professional broadcast world will expect to find the Preview bus at the bottom and the Program bus on top of it. If we want to extend it I (from a professional broadcast point of view) think I would like to see it as:

Row
8 -
7 -
6 -
5 -
4 - 90123456 (program extended)
3 - 90123456 (preview extended)
2 - 12345678 (program main)
1 - 12345678 (preview main)

You want to keep your main Program/Preview rows as close to the bottom as possible, and keep the concept of Program on top of Preview, as found on hardware mixers/switchers. This will at least make professional broadcasters feel at home. :)

If we also could get the option to assign the order of the buttons you could for instance put all your cameras on the main program/preview row while placing effects, players etc on the extended row.

To make it visually clear, Program rows will of course have red light while preview rows use green.

[Mike]

Sorry, mixed up program and preview. So you choose c. Cool, no one agrees :)

[PeterHazenberg]

Hi Johan,

This is actually what I ment. The PRV rail should be under the PGM rail and inputs need to be together as you mentioned.

Furthermore I would suggest to use row 5 and 6 to be used as AUX (output) bus. This leaves rows 7 and 8 for other features as titles etc.

[EdEstes]

My first thought was C as well, although I don't have any traditional broadcast experience to pull from. It just feels more natural to have the live button directly above the preview button. Then you can add as many of these combinations as you have sources. For example, if you need more than 16 sources, rows 5 & 6 could be configured for them. (according to the Johan's layout)

--Ed

[QuinnQuality]

I would prefer (C) because most of the users will be using between 2 and 8 camera's.
Those few whom have the luxury of more (myself included btw) probably won't have many productions per year with more than 8 cams, in my humble opinion.

[QuinnQuality]

Sorry, forgot to say i agree with Johan (this makes 2)

[marcovanzelst]

I would prefer option (c) like Johan and Peter mentioned: PRV below PGM.

[Johan Lundberg]

Does anyone else experience problems with Vidblaster not finding the Launchpad?
It's quite common for me that although connected and listed in the Windows device manager, the Launchpad can't be found by Vidblaster.

Solution that usually work is to (with Vidblaster still running)
- go to device manager
- uninstall the device
- unplug it and plug it back in again
- let windows install the drivers again
- remove the External Controller in Vidblaster
- add the External Controller in Vidblaster

After this Vidblaster finds the Launchpad, but if I restart Vidblaster I often have to take the same actions again.

Same problem on both our machines, running Win7 64bit. Tested with Vidblaster 1.25 and 1.27. Launchpad drivers v 2.1.128. Tried many different USB-ports/controllers.

Anyone else experience this problem?

[QuinnQuality]

@Johan, now you mention. Today, when testing the v1.27, i wasn't able to find my launchpad also. Thanks for the instructions. Mike will probably fix this as well.

[marcovanzelst]

@Johan, I have the same problem. I will try your solution tomorrow....thanks!

[Mike]

Upcoming v2.04 will support 16 inputs.

[Mike]

Anyone have a chance yet to film the launchpad in action? I have a feeling many are not aware of this feature, so would like to post something on youtube. Feel free to promote your company or show.