![]() Just realized i've drifted right off the point-i also have a urei 565 filter which is cool for bass. a lot of the new neve mixers are summing mixers and look wicked but the system 8 is just right for me at the mo. A lot of the guys these days are opting for summing mixers just to run the component tracks down to use a proper summing amp. With an analogue mix what you hear is what you get. When using the bounce option it breaks up the bottom end and it just doesn't sound the same as it did. I think theres still a place for an analogue desk in digital recording, The summing of the master bus in software just doesnt cut it for me. I use an an allen and heath system 8 mixer with just 8 channels from logic. Would love to know everyone's opinion, and how and if you integrate your gear in your Logic productions. I don't want to let go of my gear lol, i mean I def won't i spent so much money on it back in the day and am really attached, however im starting to think that most of it won't get much use, but it makes me sad for example seeing my mpc2000 relegated to a drum pad and my korg prophecy to a Controller keyboard. what do you sample? Do you play it back midi and eventually bring it into logic? Is there any advantage in doing this or is recording into logic same difference/less hassle? I have a Korg TR Rack, and im still on the fence about it compared to soft synths, more then anything im curious, do you guys use external samplers? I have an Akai s5000 and I m wondering, what are the advantages if any of a hardware sampler? If some of you use one, how do you integrate it in your productions, i.e. ![]() Love my Nordlead 2, thats not a problem, also my drumstation is a keeper. However i own a bunch of gear and am really attached to it and really want to "keep it in the loop". I have prepared a small & simple to use SDK with bindings for C/C++, Delphi, Java and C#.Ok so i just got back into making noise in my basement after a few years hiatus, and have just recently gone digital, loving every minute of it If you have a music-application that needs to create its own freely named MIDI-devices on-the-fly – virtualMIDI is exactly the right tool. But it can be used for other tasks as well. The driver is currently part of the rtpMIDI-driver network-MIDI driver and the loopMIDI virtual loopback MIDI cable. Since that time it is also possible for individuals to get their own code-signing certificate to be able to run their drivers on the 64bit versions of Vista and Windows 7. And finally in May of 2010 it has been done. Many people in the driver-development-community urged Microsoft to rectify this. Only companies incorporated could apply for such a code-signing-certificate. Though the idea itself is pretty nifty – to know the specific company that the code running in the kernel comes from – it had a severe drawback: One problem remained: Since Microsoft introduced Vista, all drivers for 64bit need to be code-signed. It still took quite some time to get everything going smoothly, but I finally succeeded in creating this driver. Finally I had been able to locate a guy who was doing something similar for a virtual soundcard-driver for digital-audio-broadcast. This was not satisfactory, so I looked some more and I found references to dynamic creation of sub-devices. Static meaning that the number of ports and their names would be fixed at install-time of the driver (via the inf-file of the driver). Loopback meaning that both ends of this port would be public. Nevertheless all the stuff people had done prior to my attempts would not quite achieve what my requirement were.Īll of those other virtual MIDI miniport driver implementations actually developed simple static “loopback” MIDI-ports. So that’s what I did and creating the actual driver had been not too hard after getting enough insights at the WDK-documentation. Since I had been hanging around on the wdmaudiodev mailinglist for quite some time due to my interest in kernel-streaming, I had already read quite a bit on the topic over there.Īll of the people there suggested to use the DMusUart and the MPU401 sample as a starting-point. The other side only visible via a private interface.Only one side of the ports was supposed to be visible to the public.On-the-fly creation (and destruction) of freely nameable virtual MIDI-ports.Compatibility from Windows XP to Windows 10.Later I also used this driver when I created loopMIDI for people who only need simple loopback MIDI-ports. The necessity for virtualMIDI came along when I implemented my rtpMIDI-driver. Virtual MIDI driver for Windows 7 up to Windows 10, 32 and 64 bit with the ability to dynamically create and destroy freely nameable MIDI-ports.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |