Eventually you should get that little message that says "your hardware is ready to use". If not, re-install, unplug it then plug it back in, go to the manufacturer's website and try to install the drivers there, make sure your adapter is compatible with your PC and with a wiimote-- you know the drill. I have heard of people using Bluesoleil software to access their Bluetooth, but I always like to use the software that comes with the device, and I thought Bluesoleil was kinda buggy.
Configure your Bluetooth adapter. Once your driver and the Bluetooth adapter is installed, you should see the funky blue Bluetooth logo in your toolbar.
A folder will open up, click on "Bluetooth Setup Wizard", and you will get this dialog box. Click on the second radio button to "find a specific Bluetooth device and configure how this computer will use its services". Hit the 1 and 2 buttons simutaneously on your wiimote switches it to "discoverable mode" then hit "next" in the dialog box. Watch the flashing blue lights while the wiimote tries to talk to your Bluetooth adapter! Select your Bluetooth device in this case, a wiimote.
Now the dialog box will say "Select a Device" and there will hopefully be a picture of your wiimote to select. Select it, then hit "Next! Once you select your wiimote and hit "next", you will get to the "pairing" screen.
Ignore it-- hit "skip pairing". I tried to initiate pairing, but I couldn't find a number on my wiimote, except some weird serial number that didn't seem to do anything. What is pairing? I don't know. This is taking too long. Configure your wiimote. Now that your computer sees your wiimote, you need to select it.
It seems like I needed to constantly switch to "discoverable mode" on my wiimote hit the 1 and 2 buttons simultaneously during this entire process. Hit "Finish". Your Bluetooth logo in your toolbar should turn green. Your wiimote is now connected to your PC! A Start up GlovePie. I don't recall if it even needs an install, but I remember having some problems when running it off my desktop, then moving it to my Programs folder, then running it again.
Anyway, when you open it up it displays an empty script editor, basically you type in the commands you want your control module in this case, the wiimote to execute and hit "Run". There's an autogenerate, but I have not really experimented with it yet. Our sounds were all based on the human voice. When I shook my Nunchuk hard, it sent the message to Max to move to the next section. Phil designed a very clever visual feedback screen so that we could see what we were doing in each section: the screens reminded us which synth parameters were assigned to which controls in the patch we were playing, and also showed us the current values of all of the adjustable parameters.
We called the piece 'Imaginary Dialogues', since it was about two people trading vocal sounds that were mostly devoid of meaning. At the end, as the sounds got louder and nastier, a member of the audience walked up on stage and picked up the computer, closed it, put it down, and walked off.
Phil's and my sounds started drifting upward in pitch, until they disppeared into the ultrasonic ozone in a cloud of reverb, and we were silenced. This ending — which I must say was very effective — was the only part of the piece not controlled by the Wiimotes: it was generated by the laptop itself. For the past three years or so, Apple have included a feature called the 'Sudden Motion Sensor' in their laptops, which parks the internal drive head if you should drop the computer, protecting it hopefully against damage.
The sensor it uses is very similar to the one in the Wiimote: it's a three—axis 2G accelerometer. A number of hackers have found a way to tap into the data produced by this feature to play games or to turn a MacBook into a seismograph. In addition to his 'aka. We simply looked for those numbers to change, indicating that the computer had been picked up, and when they did, Max executed a subroutine that ended the piece for us. Swinging things around in the air to control electronic sound may seem like a new idea, but in fact it's not.
Max Matthews, 'father of computer music', with the Radio Baton. It uses two 'wands' that resemble small gong mallets, within each of which is embedded a low—frequency radio transmitter. You play the instrument by waving the wands over a flat surface containing five copper plates that act as antennas. The signals from the transmitters are compared at the different antennas, and are processed mathematically to determine the position of the batons in three—dimensional space.
The Radio Baton was never a commercial product, but several were built and are still in use by composers such as Richard Boulanger and Andrew Schloss. The Airdrums. Introduced in , the Airdrums consisted of two cylinders, each about the size of a cucumber, inside of which were three accelerometers responding to vertical, horizontal, and rotational motion. The cylinders were connected to a hardware controller box, which interpreted the accelerometer data and let you turn it into MIDI notes, chords, controllers, patterns, rhythms and tempos, and also let the various dimensions interact with each other.
For example, one motion might set up the notes in a chord while another motion would execute it. Programming — deciding which accelerometer in which hand was going to perform which function — was done entirely on the box, using some 54 membrane switches and a two—line LCD. The Airdrums got stunning reviews in the electronic music press, but never really caught on, for a number of reasons.
First, the system was not easy either to program or to learn, and the MIDI community at the time was hungrier for familiar interfaces keyboards and guitars that could produce new sounds than for devices that required a whole new mindset to play. Second, the electronics were fairly delicate, which was less than ideal for musicians who wanted to use it on the road. Lehrman Published October Creating A Performance Piece For Two Wiimotes One of the challenges of building new musical instruments isn't so much getting them to do things as limiting what they can do.
You can see our performance of 'Imaginary Dialogues' at tuftsemid. Buy PDF version. Previous article Next article.
This is common when developing interactive MIDI applications on the go with a laptop. Although another good solution is to carry a small keyboard like a Korg nanoKey2 or a QuNexus, they are not the only option.
From the list of software earlier in this document, you will need the following:. Then, take input from the same virtual port in the application requiring MIDI input. I have been in this position many times.
And then, off you go with laggy kazoo fun. Not all old software can be configured to do otherwise unfortunately. However, those programs that can usually have an option somewhere for setting the MIDI output device. Set the synthesizer to take input from the same MIDI port. NOTE: the port should have messages flowing through it in one direction only. In other words, one program should talk while the other listens. Again, bi-directional communication between the programs would require twice as many ports to avoid feedback.
First, if you are attempting to minimize the latency of the Windows default synth, it is a lost cause. Your best bet is to use a different synthesizer and follow the instructions in the previous subsection. I usually recommend starting with a value of 10 and testing playback with at least some chords in it to hear some MIDI polyphony.
Some systems can go as low as ms latency with this synth, although this is somewhat rare and requires a pretty beefy machine often a desktop tower and good audio hardware. Many lesser machines, however, will still work with ms. On laptops in particular, the degree to which you can reel in the latency can be affected by power settings. High performance modes can typically function with lower latencies without audio glitching than battery saving modes are capable of.
If you are using ASIO drivers, you may need to adjust the buffer size to optimize the performance of the device on your system. The larger the buffer, the worse the latency will be, but the less likely you will be to have audio quality problems clicks, audio dropouts, etc. High-end audio devices meant for serious music development usually can have the buffer size set quite small. How powerful a PC the audio device is on also impacts this process. I own a brand new PC Win 8. Ans less and less of hairs!!!
Idem with asio4all. Buy an other! To get the same problems? Those people are bad programmers I was researcher in computers, the URL sows you a little part of my job, fully working in the end of , recently retired and not goog commercials too!
So, I permit to call for some help everywhere I can, hoping someone will find the right and probably esy to do manip. Thanks for your help. I realize this is a horrendously late response to your post and do apologize for that. Backwards compatibility is a much complained about topic in music, and the options can be pretty limited when you have a really old device.
Similarly to what you have seen, some parts of the device worked but others were unresponsive no matter what I tried, and I ended up having to just buy a new piece of hardware.
Can I download one? Nest step would be playing along with the midi and recording the result. Would the same thing work for that? Sorry to be using you for tech support. I thought your classical woodwind trio generated from number 6 was scarily real. Does it ever end? I mean Can you give the program the means to create a start and a finish? There are download links for a couple different virtual MIDI ports under section 4.
Adding support for more intelligent generation of time-sensitive musical events endings, bridges, etc. Drop down to Windows 7? Surely someone has designed a midi interface that runs on windows 8. The only thing it has dropped is support for setting a default output device at the operating system level. Some very basic MIDI players have this problem as do some very old pieces of software. Having been brought to realise that this was not a trivial problem, I thought to try this with a virtual Windows 7 computer running on VMware Workstation 12 Player, which I have had to set up for other purposes.
The latency is dreadful, but the virtual computer approach will meet my very modest needs, and which is why I write this might be of interest to others, since VMware Player is free for non-commercial use, and recipes for obtaining free limited-lifetime Windows XP are easily found.
Thank you again. Richard Corbett. Hi, my question is simple. Is there any way to get a midi keyboard working on a laptop any laptop without latency? I have to use my old bulky windows 95 desktop with a soundblaster card to play midi instruments without latency. Better spec laptops can typically get down to 10ms latency on high performance mode with non-ASIO drivers, but you need a software synthesizer that works without them. Some very high spec laptops can go down to 2ms with that synth, but how well it does is not just dependent on the machine and power settings, but also use-case factors like how much polyphony is happening at any given time i.
If you use that synthesizer, you will need a program like MIDI Ox to rout messages from the keyboard to the synth. I have noticed that some Bluetooth controllers can lag visibly with this test on some laptops, and this is sometimes solved by kicking the machine into a more power hungry mode, but not always.
Regarding how things have changed between Win95 with SoundBlaster cards and the standards in , the expectation these days for serious real-time work with audio and MIDI is that you offload a lot of the burden to an external USB card.
This is true of both desktop and laptop rigs; PCI cards are no longer the norm and on-board chips are not sufficient on many systems. Similarly the kind of built-in MIDI synth features of older Soundblasters is not something that exists on most modern sound cards, and the expectation is to use software synths within a digital audio workstation.
The only issue worth noting is that older software and operating systems can sometimes experience problems with the new trends in bluetooth-based MIDI controllers.
If you are wondering what variety of equipment exists I recommend browsing shops that have electronic music equipment since the options are vast. Hi Donya, you might be the one having an answer to my question. Now when I connect the other device to have a backup none of the functions are working input and ouput wise because the software expects to get data from another Device ID. Do you know if there is like a virtual Midi driver avaialble that merges from several physical Midi devices to one virtual device?
Set MIDI Ox to listen to incoming messages on all of the devices you want to receive from, and then send out through a virtual port. Then, the software on the receiving end only needs to listen to the virtual port and you can use MIDI Ox to decide what you want sending to that port at any given time.
Loopbe1 is probably the better virtual port for the situation you described, since the device number for it remains constant unless you uninstall and reinstall after adding other devices in between. Hi Donya, great info on this page, thanks. But I just cant get routing the P to the OP I use a Windows 8.
The next step I would like to achieve is to recreate this set up using an Andriod device with no PC.
So, do you know an android app to capable of this? Just make sure you start MIDI Ox and have the ports configured as you want before you run your other software. Devices were recognized in my tests, but no messages would pass through. However, I have never spent the time to debug the issue in a serious way.
Thank you.
0コメント