Anyone else having this problem? I'm running 64 bit plug ins successfully on windows 7(64). Each time I try and drag biab
into a track, studio one just freezes?

First thing I would try is making sure I'm running both Studio One and BIAB as Administrator. I know this worked for me a least a couple of times. I'll try it again with the new 602 patch build, just to make sure nothing is broken.


BTW, I'm running Studio One v4, so don't know if it's an issue with Studio One v3.

Thanks John,I'm running V4 as well and the new patch.Havent tried running as Admn although my computer was originally configured to run only as admin.

I just tested in with my Studio One v4 and the tracks generated and imported nicely, I made sure tempo and key matched first. I dragged the blue box (all tracks) in and they all got created and play back nicely. Took just a couple of minutes. No lockup.

I had the same thing happen. I found if I added a track first then drag the plugin onto that track it seemed to work.
(note: in the video demo he just drags the plugin onto the edit window without adding a track which it is supposed to do)

Brian

FWIW, I already had an audio track created.

Thanks again.Still no luck for me.Im running the 64 bit plug in Studio one and running on 48Khz(as im using the Studiolive series 3 mixer as my interface).Are you all running the 32 bit vst in your daw's or the 64bit? By the way ive installed last update today also.My daw just totally freezes and have to go to task manager to end task.
Ive tried adding with tracks and without same result(and ive run as admin)?

Many Thanks aLL

Mine crashed too. But I was able to make progress by Rt clicking on the BIAB VST in the Instrument list and refreshing.

In my case, this allows the VST to open correctly. I haven't got it to work beyond opening but I'm sure there are some other Studio One settings I haven't yet found to adjust and get things going. It's just a matter of time, trial and error...

I am 64bit 24/44khz. Under normal operation if you drag a VST over it will create a track and set it up. However it will crash my system if I do that with the BIAB VST. If I create a audio track first and drag it on over to the track it does work. It will automatically set the tempo of the BIAB VST to the host tempo.

Brian

I always have had an audio track created first (I never tried dragging the VST over to a blank slate). Maybe that's why it worke for me. I am also set at 16-bit, 44,100 kbps, since that's what all the RealTrack generated audio is (as I understand it).

Thanks Charlie.Tried refreshing also still couldnt get to work,however!!!,I tried some of my NI Instruments in and presonus impact,quickly followed by a drag ove from biab to a blank track and it actually opened!

It did then crash my Edititors keyboard which meant i couldnt type the chords in.

The joys of an upgrade hey.

Thanks a lot John and Brian.I have tried running 16 bit down from 24 and then it worked even using 48khz.Only problem now is,as it crashes my editors keys(configured for studio one) i can't write some of the chords in,although i did manage to get a few major chords in eventually so i generated and it dragged over splitting tracks as it should.

Funny though went out of s1 and back in and in the same boat!!! The joys of an upgrade!!!

I did find that typing in chords was sporadic when using it with Studio One. It's like the focus of the keyboard kept jumping from the VST back to the Studio One main screen interface. So, I'd enter a chord and press ENTER or TAB and find myself back on the Studio One screen. Clicking in the cell with the mouse and then typing the chord did work.

I did not have this problem in Cakewalk/Sonar.

Thanks a lot John.Im going to give it a go in Sonar 2.

I managed to succesfully load a song that i created in biab outside the daw and then inported into studio one (via the biab vst) and then dragged all tracks onto blank space and it created all tracks perfectly.So as they all say keep trying im sure pg music will get it right soon.

There is a 32 bit VST? I thought the VST was only 64.

Bob

There is only a 64-bit VST (although I haven't tried it in bridged mode in a 32-bit DAW; it may be possible).

As John has said.I havent tried bridging either as Im using the 64 bit.Still a few bugs,especially in entering chords etc and sometimes ive found if you try adding several soloists it can freeze when generating.

I have tried the plugin in Reaper, reason 10 and in Cubase Elements 6.1...it does not load properly in any of them. I reported it to the Tech support group and they have verified that it is a known problem. How about that?

Lol your a star.Thank you.

We'll have to wait as for me i wasn't able to test it properly in Cubase 9. PG support said they're working on an updated version ... in my case it loaded a file alright but synced/slaved playback didn't quit work as i expected. But no crash. With windows you might test your graphics card drivers and settings (f.i. try running without hardware acceleration). Check VCbasics and DotNet in case of GUI related crashes.- F

Good point.Will do.Thank you.

I did try bridging it and Jbrige says it created the bridge file but no file is evident. More reason to believe that there is something terribly wrong with the VST.

I just ran JBridger; loaded Sonar Home Studio 32-bit (one of the few 32-bit DAWs I have left on my PC - I load it just to get the 32-bit TTS-1 synth); rescanned my VSTs and it picked up the bridged version of the 64-bit plugin; loaded the bridged version of the DLL in Sonar Home Studio 32-bit. It launched the VST; I created a quick arrangement; selected a style; generated the arrangement; and dragged the files into Sonar Home Studio 32-bit. It all worked.