64bit plugs/vsts on 32bit daw?

[vejichan]

Does amplitube 3 come in 32bit? i couldnt find it in ikmultimedia site. The installer only had 64bit

i just bought amplitube 3 and it was 64bit.
is it ok to run 64bit on 32bit reaper? my computer is 64bit windows 7.

thanks

 

[Ericlingus]

amplitube 3 comes in 32 bit as well. I remember during the installation it gave the option to install both 32 and 64 bit. I'm using 64 bit though.

 

[bryan_kilco]

In Reaper, while in the FX list, right-click on any plugins that aren't the same as your DAW and chose "Run as .... Embed bridged GUI" or something like that. This will get rid of the annoying extra floating window that pops up with the GUI of the plugin.

I run 32 bit Reaper in Win 64 because Reaper 64 bit had a ton of bugs. It does seem slightly slower than the 64 bit version on my machine though.

 

[vejichan]

i checked and there were no options for 32bit amplitube. I originally was going to download 64bit reaper but reading about the bugs .. i went with 32bit reaper instead.
Are there any problems with running 64bit plugins/vsts in a 32 bit reaper?
pros/cons?

 

[septic]

In Reaper, while in the FX list, right-click on any plugins that aren't the same as your DAW and chose "Run as .... Embed bridged GUI" or something like that. This will get rid of the annoying extra floating window that pops up with the GUI of the plugin.

I run 32 bit Reaper in Win 64 because Reaper 64 bit had a ton of bugs. It does seem slightly slower than the 64 bit version on my machine though.

Sorry but, plz proof it with examples!!!!!
i switch to 64 bit long time ago, never hab any probs with reaper 64.

@vejichan: amplitube 32 bit (and other 32 bit plug ins) runs stable an good in 64 bit reaper

 

[bryan_kilco]

I don't have proof, but here's what happened:

I got 64 bit Reaper. Installed, started downloading all my free plugins that I always use. Messed around on a quick "dummy" session, and for some reason I opened ReaPitch. This plugin would cause Reaper to crash every time I used it.

ReaEQ also had a bug where the little graphic analyzer was missing and none of the bands could be altered. I know there were a few others, but I can't recall now. But that was enough to make me not want to use it.

I did try uninstalling and reinstalling that version with no luck. Then my HDD failed when it was only 1.5 months old. Got a new one along with an SSD. Installed 64 Reaper again. Same exact bugs happened. Ditched it and went 32 bit and never looked back.

I've also heard other guys on this forum ran 64 and never had problems. *shrug*

 

[FarBeyondMetal]

I don't have proof, but here's what happened:

I got 64 bit Reaper. Installed, started downloading all my free plugins that I always use. Messed around on a quick "dummy" session, and for some reason I opened ReaPitch. This plugin would cause Reaper to crash every time I used it.

ReaEQ also had a bug where the little graphic analyzer was missing and none of the bands could be altered. I know there were a few others, but I can't recall now. But that was enough to make me not want to use it.

I did try uninstalling and reinstalling that version with no luck. Then my HDD failed when it was only 1.5 months old. Got a new one along with an SSD. Installed 64 Reaper again. Same exact bugs happened. Ditched it and went 32 bit and never looked back.

I've also heard other guys on this forum ran 64 and never had problems. *shrug*

I'm surprised to hear that man. I've been using 64bit REAPER for the past 2 months with no issues at all. I use mostly 64bit plugins but I have bridged 32bit a few times successfully. ReaPlugs also works as expected.

You should try to get REAPER to crash from ReaPitch and post a crash log on the REAPER forum, they usually pretty helpful over there.

EDIT: Here's a paste of the instructions for seeing the crash log. I figured I should find them since I I didn't know how to do it myself

[XP]
Go 'Start Menu->Run' and type EVENTVWR <Enter>. In Event Viewer, open the 'Applications' branch and look for the latest "Error" entries.

[Vista and Windows 7]
Go 'Control Panel'=>'Administrative Tools'=>'Event Viewer'. The Vista Event Viewer has more branches, go 'Windows Logs'=>'Application'. Since Vista doesn't have a "details" button on its crash notification windows, Event Viewer is the only way to get the needed data here.

Jotting down the time of the crash or creating a fresh crash may help you finding the right error entry. The most important informations there are the faulting module and the fault offset. Post them, please.