Avian Waves : Blog
Topic: All
Search Blog
 
Recent Comments
A Real Future for Windows Phone Classic? (7)
cheap beats by dre: cheap beats by dre the 21 year old has become...

Using a Reverse Proxy to Automatically Force External Lync Meeting Guests to Use Silverlight Client (7)
buy facebook fans: I am very much impressed from this excellent...

I've Been Blog-Memed? Who Knew I Was So Popular! (3)
college term papers: Hi there. Truly cool Anime ... I only got into...

Mystery of the Server 2008 + IIS7 + OLE = "MDAC Not Installed" Error (20)
Carlos: great article. I had that setting set to True at...
Last 15 Posts
Archives
Posted By Timothy • Topics: Music, Tech
Apr 22, 2008 9:49 AM EDT

Quietly, and without much fanfare, nerds.de released an updated version of LoopBe30, a virtual MIDI patchcable driver, which now supports 64-bit operating systems, such as Vista 64 and XP 64.

Users of 64-bit operating systems have been getting the middle finger from many audio companies (such as these guys, although recently they have taken a slightly softer approach). It is/was really short-sighted, because 64-bit operating systems are, in general, higher performance and can address more RAM, which are both monumentally important to audio production. It doesn't matter that audio width greater than 32-bits provides little more (no perceptible) clarity than 32-bit. That is not the issue. If the OS has less overhead and greater bandwidth, more registers, and more RAM, the entire system will be faster, releasing resource pressure for the audio application, leading to overall higher performance. These guys understood and were the first to fully embrace 64-bit computing. Good for them.

Whoa, I went on a rant there. Sorry. The point of this post is to introduce you to the first (that I know of) 64-bit version of a virtual midi patchcable. What the heck does that do? It allows you to pipe midi-enabled software and hardware through multiple chains of midi within your computer. A good example is to pipe your sequencer's output through the mighty, mighty Midi-Ox, which will send the signal out your interface's midi-out to your hardware device.

Now 64-bitters can join the party! It's a niche market, for sure, but it's important when you rely on it!

It's worth noting that developing a 64-bit driver is not trivial because Microsoft requires that all 64-bit drivers be signed, which takes time and money, working with MS's quality labs, to make sure it won't crash the operating system and follows "best practices" set up by MS (a good thing). Thankfully, nerds.de took the time to do it.

I'll give a review of LoopBe30 in a later post. This is just to announce it's release! The big question for me? Will it work with the old school 32-bit Midi-Ox (another powerful program that refuses to make the jump to 64-bit at this point).

Trackbacks :
Send trackbacks to this URL:
http://www.avianwaves.com/Blog/track.aspx?id=85
In your blog post, you must link back to my post using this URL:
http://www.avianwaves.com/Blog/default.aspx?id=85
Comments :
Just wondering if you ended up testing whether Midi-OX (32-bit) works with 64-bit LoopBe1 on a 64-bit OS?

Nice blog btw, good articles :-)

M
Comment By Misha At 9/23/2009 6:56 PM EDT PermaLink
I need to do that. I actually found non-MidiOx workarounds for what I used to use MidiOx for regularly. I sort of forgot about this article. :-)
Comment By Timothy At 9/23/2009 9:10 PM EDT PermaLink
All this was certainely true with 32 bit applications working on 64 bit OS. I recently try to use PLAY (from EWQL) in standalone mode, witch is now aviable in 64 bit, with Midi Yoke and LoopBe1, it doesn't seems to work at all... :=(( And i think there is no issue, i can't find any virtual midi cable for 64 bit applications....
Comment By Phil At 6/6/2010 1:51 AM EDT PermaLink
Ok i'm very sorry, after many research and discussions, it seems to be a problem with SC configuration (chose multis voices, not solo !) LoopBe30 works like a charm in this case !
Phil
Comment By Phil At 6/10/2010 3:53 PM EDT PermaLink
Just thought I'd update you on a test I did.

Running Windows 7 64-bit edition, I installed Reaper 64-bit (a DAW application) and the latest LoopBe1.

Then I wrote a tiny 32-bit app in VB6 that would send some MIDI data to a device of my choice.

I couldn't believe it. My 32-bit app recognized the LoopBe1 device. Reaper 64-bit also recognized the LoopBe1 device. So I was able to send MIDI data from my 32-bit app to 64-bit Reaper.

How can this be? Is it LoopBe1 or Windows that's making this 32-bit to 64-bit communication possible?

M
Comment By Misha At 6/15/2010 7:32 PM EDT PermaLink
Drivers are not linked in to the address-space. They are used by sending IRP-messages. This can be done explicitly by an API DeviceIoControl or implicitly when the devices exposes itself as a 'file'. The functions for using files are, of course, available for both 32 bit and 64 bit applications. The API DeviceIoControl is also available in a 32 bit and 64 bit fashion. I hope, this clarifies the mystics a little.
Comment By Frank1119 At 5/27/2011 5:50 PM EDT PermaLink
Wow !! 64 bit virtual MIDI is great as many users have switched from 32 bit interface to 64 bit interface. Great post shared!!
Comment By MIDI Files At 9/26/2011 1:59 AM EDT PermaLink
Thanks! :) I struggled with this for an hour and loopbe was just what I needed.
Comment By Tom At 2/16/2013 10:40 AM EDT PermaLink
Add Comment :
Name :
Email :
URL (Optional) :
       
Comments :
Allowed BBCode Tags : LINK (URL), BOLD, ITALIC, UNDERLINE, QUOTE


By posting a comment to this blog, I agree to the blog rules.

This Avian Waves blog is powered by a modified version of Presstopia Blog




Avian Waves Logo