Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Q&A, Tips, Tricks and Howto

Thread Tools Display Modes
Old 01-09-2008, 05:00 PM   #1
Human being with feelings
Join Date: Oct 2007
Posts: 133
Default [HOWTO] WineAsio + REAPER for linux beginners!!



A guide designed for beginners to linux


/* preface */

Hello REAPER community! I am blessed with a little spare time today and i would like to give something back to this wonderful movement we call REAPER. There is a lot of talk around here about Linux (mostly audio related) and some of you may be curious about Linux and how it could be used in conjunction with REAPER. You may be thinking to yourself "Hmm seems interesting, but I don't even know WHERE to start!" Well, hopefully this guide will serve as a starting point for people who think just that, and of course anyone who wants a very simple A to B guide to getting up and running with REAPER on Linux.
w00t is offline   Reply With Quote
Old 01-09-2008, 05:01 PM   #2
Human being with feelings
Join Date: Oct 2007
Posts: 133

section I: Genesis- in the beginning

Okay since this is a guide aimed for beginners, lets try and get some terminology and what not out of the way. If you start reading this stuff and you get bored or feel you are "above" it, feel free to scroll to more relevant parts

Im not going to dive into a deep history of Linux, but for our sake I will go ahead and define Linux as this:

"...A Unix-like computer operating system. Linux is one of the most prominent examples of free software and open source development; typically all underlying source code can be freely modified, used, and redistributed by anyone."

(this is taken from the Wikipedia article on Linux, feel free to read up on that for more on the history etc...)

Why is this important? well, I feel its important to understand what Linux and its community of users are, and what they stand for. The way some of the things work in Linux won't seem so "weird" when thought about with this knowledge. What I'm trying to say is, a lot of the differences in Linux versus windows or OS X have to do with the fact that the Linux community is an OPEN one, not simply because they want to remain cryptic and obscure and secretive or "different".

At its base, Linux has a Linux kernel. this is what makes everything go. you can Google to find out exactly how this works, but for this guide's purpose we will call it the "Linux brain". as like with almost everything in Linux, you will have choices with the kernel. some kernels are for 64 bit architecture, some are for servers, some are "generic"....we are going to mostly be concerned with what is called a "realtime enabled" kernel or "realtime kernel", as it has to do mostly with low latency operation ala the ones we do with audio in REAPER. dont worry you can get a special kernel like this with a few clicks in our software or "package" manager. (more on this later)

One issue that causes a lot of confusion about Linux is its many [url=http://en.wikipedia.org/wiki/Linux_distribution]"distributions"[url]. One way to think about distributions is like ice cream flavors. The Ice cream shop has all those ice cream flavors, but that doesn't deter you from going in to get a cone or two does it :P . In Linux there is a lot of "choice", and much can be argued about having too much choice is a bad thing, but is it worse than having no choice at all? We'll leave the philosophical stuff for another day but lets get a basic rundown of what we mean.

Distributions, or "distros" for short, are complete Linux systems based on various styles of Linux. you have different package/software architectures all based around the "Linux" kernel ...dont worry your head about that, but there are a few different architectures: Knoppix, Debian, RPM/RED HAT, Slackware and Gentoo are probably the most common. Think of these as "methods to eat the ice cream" , like cone, cup, over apple pie etc...but the base of a distribution is just one part. The "flavor" typically comes from what a distribution is intended to be used for. Is it for small business servers? Is it optimized for Older hardware? Or maybe it is for Multimedia? Which desktop environment does it use? Which file-manager? This is where the choice in Linux is great. you get tons of different "flavors" to choose from. In this guide, we will be choosing from the Ubuntu flavors )

(note: Our guide basically forces you to use an "Ubuntu" distribution, which is hands down the BEST distro for beginners to Linux in my experience, in particular people coming from windows. The most important part of this guide will be done in Ubuntu so in order to follow it to a "T", you must also use an Ubuntu distribution or at the very least, a Debian based distribution.)

As a long time Windows/Mac user, the first thing you will probably recognize IMHO (would like feedback on this) is the difference in how you typically install a program. This will most likely feel immediately foreign to a Windows users for example. The modern Linux desktop uses what is called a "package manager" which is a utility that keeps your Linux software up to date, and offers you the optional software you may want/need in the future. This may sound weird, but its actually a GREAT concept. a concept that doesnt....really work in the current model for 3rd party/proprietary software on closed source OS platforms. Its immensely powerful, and easy to use whether by command line in the terminalwith apt or the GUI based applications like Synaptic. software is kept in "repositories", which store the "packages" to be downloaded and installed by the Linux system as the user sees fit. You have different kinds of software repositories as well. Typically the install disc is a repository, then you have official repositories for your particular Linux distribution which keep system packages and bundled/official software up to date. then you have 3rd party repositories which can keep other software (which could include some proprietary stuff) that you can manually add to you "repository" list. typically, they come with special "keys" to let you know when you download a new version of something, your downloading from its "official" source. How cool would it be in Windows to open up a "package manager" and search for "programming tools" and have whats available ready to download from secure repositories to test out! Ahh well...maybe one day...probably wouldnt work though...


So now that you know a little about how linux works, how about some sound? For our intents and purposes, I will talk a little about "Advanced Linux Sound Architecture" or ALSA for short. This is typically how you get Linux to make noise. ALSA is a great project that is continually getting better, and supports lots of GOOD audio cards such as echo MIA, M AUDIO, Hammerfall, lots of "factory" cards and much more....so as you may have guessed, ALSA is more or less a foundation of audio drivers for Linux. you can refer to their web pages for more on that project.
Another audio project to become familiar with in linux (and this has more to do with 'manipulating' audio as we reaperites love to do) is the Jack Audio Connection Kit (JACK) project. A simple way of thinking about this is to think of Propellerhead's Rewire technology. The twist with JACK is, the JACK audio server is the "rewire Master" and when launched, any JACK compatible audio app becomes connectible to any OTHER JACK compatible app that you may launch. most Linux native audio apps are jack compatible which means you can do a lot of interesting, powerful routing. this is integral for "low latency" audio on Linux as well, so even if complex routing doesn't stir you, its there and your gonna need JACK anyway to achieve REAPER on Linux so do yourself a favor and familiarize yourself with it (JACK that is) just a taste.

And lastly lets talk about how we get REAPER (the Windows version) to work with Linux. WINE (Wine Is Not an Emulator) is an Open Source implementation of the Windows API on top of X, OpenGL, and Unix. from the WINE HQ website:

"....Think of Wine as a compatibility layer for running Windows programs. Wine does not require Microsoft Windows, as it is a completely free alternative implementation of the Windows API consisting of 100% non-Microsoft code, however Wine can optionally use native Windows DLLs if they are available. Wine provides both a development toolkit for porting Windows source code to Unix as well as a program loader, allowing many unmodified Windows programs to run on x86-based Unixes, including Linux, FreeBSD, Mac OS X, and Solaris."

Wine is what we will basically be using to run REAPER. The REAPER dev team do a great job of keeping REAPER "Wine friendly". in conjunction with Wine, we use a special ASIO driver, aptly named "WineAsio" which we use within wine to be able to use a true blue windows vst host to use windows-compiled VSTs, and any other great DAW features like midi sequencing, in-house effects etc. There will be more on this as we go through the guide. lots of info on Wine and what it can/cannot do on teh internetz.

Hopefully this can give someone who knew nothing or little about Linux a little background to lean on. I tried to keep the "technobabble" to a minimal and i hope it can benefit someone who reads this, because a lot of stuff written about linux is very "passionate" which is great but sometimes your in tangents that may confuse newer users sometimes. Perhaps watering it down will spark interest in someone who can grow to become an 'expert" themselves! Im certainly no linux "master", just as you don't have to be a "Windows" master and can be perfectly fine....


Last edited by w00t; 01-09-2008 at 05:04 PM.
w00t is offline   Reply With Quote
Old 01-09-2008, 05:02 PM   #3
Human being with feelings
Join Date: Oct 2007
Posts: 133

section II: The Game Plan

Okay, so we have gotten the primer out of the way, what exactly do we NEED to do to get REAPER working in Linux? well this guide will give you the play-by-play rundown, and all things needed to make this work. make sure you can cover all criteria or it may not work out in the end....

Hardware requirements

-PC with HD space for linux
-ALSA compatible soundcard
-internet connection (the faster the better obviously); attempting to do this with packages alone/internet on another computer is NOT for the beginner, at least without someone who knows what they are doing close by

(hint: to check out hardware compatibility, use a Linux "livecd" the one you plan on installing of course. this will let you know how much of your hardware works "out the box" by loading up the OS in your ram...when you restart the comp witout the live cd in, it boots as normal.)

Software requirements
-linux distro (we are going to be using newest (7.10) Ubuntu flavor(s) )
-realtime kernel
-qjackctl (gui jack configuration and server)
-newset WINE
-newest wineasio driver for WINE
-and of course REAPER

So it goes like this: we install Linux, get a realtime kernel, install JACK, get "realtime" going, install WINE, install REAPER in WINE, enable wineasio and then...MAKE NOISE!!!!!!! I will go in detailed steps in the HOWTO section, this is just a simple summary of what to do for reference.

first things first: get Ubuntu Linux installed and ready to go. Pick your "flavor"; Ubuntu the normal setup with gnome/nautilus, Kubuntu with KDE; Xubuntu with xfce/thunar (i use this version as i find it much lighter and pleasant than gnome). Please try and get this done on your own. I flirted with writing a part to show you how to do this, but there are {numerous guides on this available on the internet}, and this thing is already a little long winded. So go forth, get linux installed, and once you have that done, come back and go to section III. you can do it!!! lol


new edit: 404NotFound has created an excellent tutorial for getting reaper up and running from a 64studio live cd. so for you 64 bit people I encourage you to try it! remember with a live cd you are just *checking it out*, not actually installing so thats even more incentive just to see whats up.

just follow the link below


Last edited by w00t; 02-22-2008 at 01:30 PM.
w00t is offline   Reply With Quote
Old 01-09-2008, 05:03 PM   #4
Human being with feelings
Join Date: Oct 2007
Posts: 133

section III: lets get going (the HOWTO)

Okay now we have a basic Ubuntu desktop install going. now look in your software menu. under "System" you should see a program called "Synaptic Package Manager" (in Kubuntu its called "Adept") ...this was the package manager I mentioned in section I. this will be your best friend in Linux for a lot of reasons. ...but alas we will not be using it (a lot) in this guide! it can easily be used for this guide, but we will be using another utility called "terminal" (Kubuntu's is called "Konsole") to achieve most of this stuff very easily and quickly. In linux you use the terminal to run commands and whatnot while bypassing typical GUI protocol. it is imperative to a good linux experience to familiarize yourself with the terminal at least a little bit.


....for now lets go into our package manager and under the settings menu look for repositories.... make sure under "ubuntu software" we have the "main" "universe" and "multiverse" repositories checked. you may also want to enable the "multiverse" and "restricted drivers" as well because they may come in handy for codec issues and other things. once this is done close the repositories dialog window and hit the "refresh" button. this will refresh your package manager's index and will prepare us to get all the software we will need to make REAPER work. After this, you can close Synaptic and we will turn to the terminal. (should be under accessories in your program menu)

first lets download/install some stuff we will need. in order to do this, you will need "administrative privileges" aka your "password"; we prefix commands that need this with a "sudo" flag in Ubuntu and most Linux environments.

in the terminal copy and paste this command:

sudo apt-get install linux-image-rt jackd jack-rack qjackctl wine

what does this do you ask? its basically a package manager shortcut that will download and install the realtime kernel, jack audio and its gui, and the wine we talked about earlier. If you used "Ubuntu Studio" you should already have a "realtime' kernel and perhaps the jack stuff. thats okay, because our command will just tell us if we have the newest versions installed and not do anything in that case.

when this is done, you will need to restart and reboot into the "realtime" kernel. you will want to use this kernel for realtime everytime you wanna make music.

okay now back on the ubuntu desktop running the realtime kernel, lets open up the terminal again.

(and for beginners, if you are not sure if you picked the right kernel use the command "uname-r" in the terminal without quotes. this will print which kernel you are currently using. it should have -rt at the end or else you picked the wrong one and have to reboot)

Okay know we are going to do a little "studio preparation". most of this is shamelessly taken from the ubuntu guide, so please refer to it for issues such as firewire cards, multiple sound card issues, other linux audio applications and a few other specific inquiries. I tried to take only what was relevant to the guide as setting up REAPER on linux. We will be using the terminal for this portion. copy/paste the commands one by one until finished. i will briefly describe what each command is doing. and also, If you chose UbuntuStudio as your ubuntu version, you should not have to do this. this is specifically for the 'normal' ubuntu distros.

1. Making sure ALSA stuff is kosher

sudo apt-get install alsa-firmware-loaders alsa-tools alsa-tools-gui
This will make sure you have all the alsa stuff...in particualr the alsa-tools gui will proably come in handy for adjusting various properties of your soundcard.

2. Enabling realtime support

 sudo su -c 'echo @audio - rtprio 99 >> /etc/security/limits.conf'
 sudo su -c 'echo @audio - memlock 250000 >> /etc/security/limits.conf'
 sudo su -c 'echo @audio - nice -10 >> /etc/security/limits.conf'

in order to bypass the technobabble, this basically gives your 'audio' group permissions to access realtime functionality. You may notice that the commands look a little different, thats because of the nature of what they are doing. Linux beginners just need to know to use these commands with caution, and to copy/paste them. DO NOT go around using sudo su everywhere! you will regret it!! now lets keep moving...

3. ALSA sequencer module
sudo modprobe snd-seq

we are going to need this for alsa midi, the midi protocol currently used with wineasio. typically this is not a module that is loaded on boot up, but the above command loads it when entered. to have it persistently load across boot ups, we have to add it to the etc/modules file. Its actually very easy to do with a simple terminal command:

sudo su -c 'echo snd-seq >> /etc/modules'

and now we dont have to worry about that anymore!

4. Timer resolution

sudo sysctl -w dev.rtc.max-user-freq=1024
sudo su -c 'echo dev.rtc.max-user-freq=1024 >> /etc/sysctl.conf'

this ensures that the kernel has a proper timer resolution for midi. the default is 250 hz and these commands change it to 1024. (the second command gives you this resolution every time you boot)

5. Secondary USB keyboard/soundcard fix

sudo su -c 'echo options snd-usb-audio index=-2 >> /etc/modprobe.d/alsa-base'
this should help if linux confuses a usb keyboard or secondary audio device as he primary device. this usually happens when you leave the usb device plugged in and on while booting up.

addition (5.5 wineasio/jack simlink)

Im going to add this step in because im not sure if you have to do this still or if wineasio already looks. If it already does it it wont hurt to try this command. What it does is create a symlink between wineasio in jack so so jack is activated everytime wineasio in used:

sudo ln -s /usr/lib/libjack-0.100.0.so.0 /usr/lib/libjack.so.0

that should take care of that

6. setting up JACK

For setting up JACK, ymmv [Your mileage may vary] with a lot of things, but this guide should get you going. make sure you can launch jack control (the terminal command is "qjackctl" without quotes, or look in your program menu under multimedia for "jack control". hit the setup button and make sure realtime is checked, and softmode is checked. here is a picture of what mine looks like for my audiophile 2496 card.

Also refer to the guide previously mentioned for more info and troubleshooting. BEFORE CONTINUING, make sure from jack control that you can start the server with realtime and have no problems...if it times out shortly after starting, ten you have some troubleshooting to do. I will help here where i can, but again, this will very significantly between hardware. once you can verify that the JACk server can run in realtime with no problems, you can close JACK control and move on in the guide.

Alright! our studio preparation is done. lets move on to the wine stuff now.

In the terminal, type this command:


This is the command we use to setup wine. It should bring up a config dialog for wine.

Now to setup a few things.....under the 'applications' tab, with 'default settings' highlighted, you will see a drop down menu where you can pick the "windows" version. it defaults to windows 2000, but switch this to XP. now go to the 'audio' tab. It will give you some driver options here. what we want to pick is ALSA and only ALSA. make sure NOTHING else is checked, or midi will NOT work.

Do not worry about/mess with DirectSound settings.

Now under the 'graphics' tab, un-check 'allow the window manager to control the windows' ...this will give all wine windows the default windows look, versus using your linux window manager. this gives improved performance. Once you get your feet wet a little bit, you may play around with this to see what works best for you.

Last edited by w00t; 01-11-2008 at 10:52 AM.
w00t is offline   Reply With Quote
Old 01-09-2008, 05:03 PM   #5
Human being with feelings
Join Date: Oct 2007
Posts: 133

Okay now that we have done that, we are very close! now lets get WineAsio sorted m'kay?

Here is an alternative method mentiond by xtd, thanks! This is like installing via synaptic with a little twist because the Jakclab wineasio patches are RPM packages, designed natively for SUSE/REDHAT iirc. so If the link doesnt work try this method. Or if your comfortable with it. if not dont worry.

Originally Posted by xtd
Nice post.

Little addition for the wineasio part :

instead of d/l the .dll, you could have a nice .deb to (un)install using alien and the wineasio suse rpm.

This part would then looks like :

Install alien binary package converter using
sudo apt-get install alien
D/l the last wineasio rpm from the ftp using e.g.
wget ftp://ftp.gwdg.de/pub/linux/misc/jacklab/SUSE-10.2/RPMS/i586/wineasio-0.7.3-3.1.i586.rpm
Transform the package using alien :
sudo alien --to-deb wineasio-0.7.3-3.1.i586.rpm
Then install the package newly created :
dpkg -i wineasio-0.7.3-3.1.i586.deb

this links to the newest wineasio.dll.so (0.72) hand rolled by me on Xubuntu 7.10 this should work for everyone using newest Ubuntu versions. download this and put the file on your desktop (if its not already there)

(anyone who needs more info on how to roll your own (compile) wineasio, just drop a line....also if someone has a more permanent means of storing the file, please let me now...I'd appreciate it...)

Fire up the terminal again, and type this in

cd Desktop
This will take the terminal to your desktop path (cd afaik stands for 'change directory')

Once you've done that, type this command:

sudo cp wineasio.dll.so /usr/lib/wine
this will copy the wineasio dll to the win lbirary, and will take care of permissions for you. without some sort of admin access (aka 'sudo') you cannot modify system files.

now, once thats done, type this command:

regsvr32 wineasio.dll
You should see a return of something like "wineasio.dll successfully registered." once you see that....well, we can see that proverbial light at the end of the tunnel!
Now we get into some stuff your probably familiar with. head over to Reaper.fm and to downloads and grab a hot copy of the newest build, or whatever build you wish i guess. download the .exe to the Desktop.

Now, once again from the terminal navigate to the Desktop:

cd Desktop
Now enter this command to run the reaper installer

wine reaper2030-install.exe
* you might need to adjust the build number, respectively.

(alternatively you can usually right-click the file and "open with wine" , but this is a more precise method and stays uniform with the rest of the guide...also, it helps n00bs get used to the terminal a little bit more, and of course the terminal returns errors that may help in troubleshooting...DO NOT close the terminal while installer is running or whenever you run REAPER or jack from the terminal)

you should get the install dialog as you normally would under Windows. I usually uncheck rewire and cd burning, but i dont think it REALLY matters. then just install as you normally would. I bet you wanna know where this mysterious "C:" is for wine, huh? Well its simply in your home folder inside a folder called ".wine"

(the full path is /home/userName/.wine)

Once its all installed, do not run REAPER right away. We have some stuff we need to go over first. let's go ahead and navigate to the ".wine" directory in your home folder. If you don't see it, that means "hidden" folders are not in view. hit ctrl+H and that should solve that. Inside the .wine folder, you should see a folder called "drive_c". Think of this as the c drive in any normal windows install. Once in there, make a folder that sits along with the windows and Program Files folders called something like "vstPlugins" we will use this as our [primary] vst plugin folder. i would encourage you to go grab some freebie "dll-only" style vsts and plop them in there. we will use these to test out our wineasio reaper! (im going to be using {xoxos' "sounds of nature" }thunder module for this guide)

Okay, now that we have done that, lets fire up REAPER. if you put the icon on your desktop, double clicking it should open REAPER. I personally like to run from the terminal, becuase i can see any errors or "missing dlls" that give me trouble (more on this later).

To launch from terminal, use this command:

wine /home/YourUserName/.wine/drive_c/Program*Files/REAPER/reaper.exe

replace "your user name" with ...your user name

(hint: the terminal keeps a log of your previous commands. to run reaper at a later time, you can just use the "up" arrow to browse old commands used, and find the reaper one.)

Once in there lets do a little configuring. Ctrl+P to bring up preferences, and go on down to Audio->devices. change driver type to asio, and it should automatically bring up wineasio. it should basically look like this:

okay lets go down to "vst" preferences, and add our vstPlugin path we created (you did put a dll or wo in there..right?) click the "browse button, and go to the "my computer" and "c:" paths. You should see the folder we created, just select that. Also before you are done if you have a midi controller hooked to your soundcard, make sure to check it in the midi tab preferences. If you have a usb midi controller....well it's probably gonna be a little more difficult to get it working, but i cant go into that in this guide. sorry.

okay go ahead and scan the plugins, save/apply all changes, create a track and add some fx by hitting the fx button of course. pull up the vst you want to load.

then click it. If all goes well it should load the vst like it does in Windows. try using your midi. Its wonderful isnt it? you are NOW using REAPER in Linux with wineasio! check your latency in the upper right...pretty sweet eh?

Last edited by w00t; 01-24-2008 at 09:20 AM.
w00t is offline   Reply With Quote
Old 01-09-2008, 05:09 PM   #6
Human being with feelings
Join Date: Oct 2007
Posts: 133

section IV: FYI and closing statements

FYI: other things you should know

- When installing stuff to wine, its very important to to use the terminal for troubleshooting. a lot of times the terminal will tell you that a .dll is missing when an installer goes weirdo on you. try downloading the .dll mention in the terminal and putting them in your /.wine/drive_c/windows/system32/ folder (no need to register them like with wineasio.dll)...you'll find that after a few common dll are sorted, stuff works more often than not!

-there will always be an "overhead" when using wine when compared to running it natively. this is because the wine api is running OVER the linux, so while JACK may give you some crazy good latencies, dont expect to be able to function as smoothly as native Windows just yet....for most its just fine though. some of the major issues mostly have to do with the gui (being slower or slightly choppy at times). So on that note, turn off all 3d/compiz effects when using REAPER with wineasio, it keeps your cpu stress to a minimum. In fact, once you get your feet a little wet, I sugggest setting up an alternative lightweight linux desktop (fluxbox,blackbox.openbox etc) for use when you are making music. That way you know you resources aren't being ate up by the pretty desktops. This will be my next linux/REAPER guide...look for that soon

-vsts are not always going to work. whether its some weird library it needs or some copy protection, some just dont work. this has more to do with wine, but just be prepared to test and see what works. most free dll only plugs will work. If your having issues with a plug you think can work, let me know and we'll see if we can get you sorted.

-you do not need to run "jack control" whenever you want to use reaper. it [wineasio] will run the jack server without the control gui. you WILL need to use the gui to configure your settings, and make sure the server runs realtime without problems. Also wineasio apps show up in the jack control connections, so use that if you want to chain reaper with other JACK compatible apps, whether they are wineasio or not! Pretty friggin' sweet huh?

-There are tons of other audio apps to explore with linux. this guide really only focuses on what is need to run REAPER. I encourage you to sit in papa google's lap and ask what else is out there

( i may add more here)

Well we have come to the end of the road for my guide. It is very long it seems so, i will be scanning it thoroughly for errors and erroneous crap, I hope it can be functional for you guys. if you have problems, issues, complaints, praises whatever post them in this thread. I would like to thank first Cockos for the incredible REAPER, and their support for wine use, hope this can serve as a small token of my appreciation for what you guys are doing . without that this wouldnt be possible. Then next i would like to thank the Jacklab community, for forging the way of WineAsio. You guys rock so hard! and that means you: Edogawa, Drumfix, "Lump" and the lot of ya!!! see you guys in #jacklab as usual when im begging for help (lol)

now get going you linux musicians, and make me a "dont fear the reaper" cover song!!!! with even MORE cowbell!!!!!

peace yall,
w00t is offline   Reply With Quote
Old 09-25-2009, 05:59 PM   #7
Human being with feelings
dminoz's Avatar
Join Date: Sep 2006
Location: Castlemaine, Vic, Au
Posts: 186

Originally Posted by w00t View Post
Okay now that we have done that, we are very close! now lets get WineAsio sorted m'kay?
w00t, the download link for the wineasio dll is dead. Any chance of a new link? I'm following through this setup process and I'm stuck here...
dminoz is offline   Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 12:46 AM.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.