Loading a previously made SGU file and using FL Studio 20.1, Windows 10 and the plugin. Highlighting all chords by holding left mouse button and dragging over all chords then pressing Ctrl+C on my keyboard crashes FL Studio 20.1.
I picked the feel, tempo, timesig, etc.. Then I selected a style, played it and decided to look at another style. The feel, tempo, timesig, etc. were gone. I had to redo this again. Can you please fix this so I don't have to refill the fields each time?
Also, the first style I selected, drums didn't generate. So, I selected a RealDrum. Generated it and it puts it in the list as pedal steel and nothing is generated. This was happening with the build 606. I tired this numerous times. Always the same.
And I'm using VST3.
I’m having similar issues. I tried to generate a new track in the plugin and it failed. So I opened the file in BiaB and tried, while I can generate the track I can’t drag and drop anymore it will drag, but not drop.
ahh, how sad, so the wait is on again? .... i'll try it with Cubase later, and report ... F
Geez be dragging and dropping the whole thing, if this aint fixed to a decent acceptable level.
Well maybe not L.O.L.
I look at it this way. His is a very big upgrade, and a really cool step forward. If it takes a few days and some patience I am willing to work with it. For a while. Yesterday’s patch fixed a couple issues. Hopefully the next will fix more. So far it works well enough to get some things done.
I look at it this way. His is a very big upgrade, and a really cool step forward. If it takes a few days and some patience I am willing to work with it. For a while. Yesterday’s patch fixed a couple issues. Hopefully the next will fix more. So far it works well enough to get some things done.
- This.
Matt, Did you just minus me
Hi I'm new here... First Post:
Running Sonar X3 Professional on Win 7 Pro with no apparent problems.
I bought the 2019 mainly for the VST DAW Plugin.
Although with latest patch: 607 So far it's still a NO GO
Now with the latest patch it does show up in the Cakewalk plugin manager as a VST3i
When I drag it into a track, it comes up with a screen saying: It is likely this plugin is incompatible with Sonar.
Any suggestions?
I doubt Matt minus'ed you, I'm sure he meant, as I DO ... "what he said!"
so a BIG +
Larry
Even if he did I would be happy cause a Matt minus is better than some folks plus. I’m just pullin his leg. Which on its own merit is a bit weird
Very funny! Yes, I meant I completely agree with your statement and positive attitude. Nicely done.
Very funny! Yes, I meant I completely agree with your statement and positive attitude. Nicely done.
I'm sure many of us would have a more positive attitude if we could ever get it working...lol
I've yet to see anyone bashing anything that is working for them.
I got really positive, trashed the plug-in, and got back to work.
VST3i won't even generate tracks in either Reaper or Studio One....some work to be done yet!
Hi I'm new here... First Post:
Running Sonar X3 Professional on Win 7 Pro with no apparent problems.
I bought the 2019 mainly for the VST DAW Plugin.
Although with latest patch: 607 So far it's still a NO GO
Now with the latest patch it does show up in the Cakewalk plugin manager as a VST3i
When I drag it into a track, it comes up with a screen saying: It is likely this plugin is incompatible with Sonar.
Any suggestions?
Just a thought, are you running a 64 bit version of Sonar?
Hi Charlie,
Highlighting all chords by holding left mouse button and dragging over all chords then pressing Ctrl+C ...
...Then I selected a style, played it and decided to look at another style. The feel, tempo, timesig, etc. were gone...
We will look into this. I'm running FL Studio here, and I'm not experiencing either of these problems, so there is something more to this. Verify that you have the latest version of the plugin. Check in the About dialog that it says 1.7.11. Note that in FL Studio, you might have to re-scan plugins.
Andrew, yes, the plugin is at v 1.7.11. Have you upgraded to FL Studio 20.1?
And I have rescanned. I'm using VST 3. Thanks.
Pleasantly surprised that the Reaper's transport now starts the VSTi3 plugin's transport.
However, it doesn't follow the Time Selection within Reaper nor can I auto repeat the song within the plugin when it comes to the end.
Is there a way?
BBMaestro: When I drag it into a track, it comes up with a screen saying: It is likely this plugin is incompatible with Sonar. Any suggestions?
We've tested the Vst3 with Cakewalk by BandLab 2018.11 build 25 , and that is working fine. We're making videos this week of using the VST3 with various DAWS. So far it works for all of them in our testing.
gwp99: Pleasantly surprised that the Reaper's transport now starts the VSTi3 plugin's transport.
However, it doesn't follow the Time Selection within Reaper nor can I auto repeat the song within the plugin when it comes to the end.
Glad the VST3 is working for you in Reaper. Its been working fine in our tests too.
Regarding your questions:
- Auto repeat within the plugin. That's not implemeneted yet, but is a good suggestion. We assumed that people would be dragging the tracks to the DAW, but being able to play them and loop them within the plugin sounds fine to me. We'll add that one to the list.
- To get the DAW and the plugin to be in sync, make sure the tempo in your DAW project is the same as the plugin. Assume the DAW tempo is 120. You open the plugin and then the plugin tempo would be 120. That's great, as the plugin uses the DAW tempo. Now you select a style in the plugin where the tempo is 85. That will set the plugin to tempo of 85, different from the DAW 120. So if you play that, it won't be in sync, and you should change the DAW tempo to 85, or change the plugin tempo to 120.
Marcus, there mucst be some other issue at play, because the plugin works fine for us and other users in both Reaper and PreSonus (and other DAWS). If the plugin shows up, that's a gppd sign, and if its not generating, perhaps the folders are not set correctly - check the settings (preferences) in the plugin. For example, have you selected a style, and does the stylepicker show up?
> charlieMcG: Loading a previously made SGU file and using FL Studio 20.1, Windows 10 and the plugin. Highlighting all chords by holding left mouse button and dragging over all chords then pressing Ctrl+C on my keyboard crashes FL Studio 20.1.
Glad to hear that you got it working in FL Studio. Not sure what that issue is you're having with Ctrl-C, but best to avoid that for now, and let us know if you have any other issues with FL-Studio.
Yes I can pick a style...it starts to generate...gets about a tenth the way done then the blue bar disappears (goes back to the beginning).
If I try to play it ...it says the tracks haven’t generated yet.
It works still in Sonar 8.5 64 bit
As the VSTi is not passing audio to the DAW, there is no way to control the output volume within the VSTi.
Would like to see an Output Knob(and Meter).
I can get the plug to generate tracks from a style in both studio one, and reaper. Then that’s where it all goes south. Nothing seems to work after that. No multiriff no swapping out tracks in the plugin.
On one test changed out a extra piano track for a vocal ahh/ooh and that actually worked. But one style failed to generate one of the instruments and I could not get it to regenerate the track.
I love the way this is going, but it is still buggy for me.
all of the above is happening here too - with the addition it also slows down the entire OS!
Yes I can pick a style...it starts to generate...gets about a tenth the way done then the blue bar disappears (goes back to the beginning).
If I try to play it ...it says the tracks haven’t generated yet.
That's exactly the issue that I'm having.
Comforting to know I'm not the only one, I've seen folk with various other issues, but you're the first I've seen to describe this same issue.
Marcus, there mucst be some other issue at play, because the plugin works fine for us and other users in both Reaper and PreSonus (and other DAWS).
Here's what I sent to support regarding the issue just so you know that you are not completely alone, and to perhaps identify some common element that maybe a cause. So it may work for other users but clearly not ALL of them.
Operating System: Windows 10
Other OS: build 17763.194
Computer: Asus Prime Z370 based Generic PC
Processor: Intel Core i5 8600k
Memory (RAM): 16Gb
Sound Card: Roland UA-55 Quad Capture
MIDI Synth: N/A
MIDI Interface: N/A
MIDI Input Driver: Impact LX25+ (Keyboard)
MIDI Output Driver (selected): loopMIDI
MIDI Output Drivers (all) Varies
DXi/VSTi synth: Yes
MME/ASIO: MME. Both WAS and ASIO cause issues.
Problem or Question:
Band-in-a-Box DAW VST Plugin does not generate any audio files.
I have loaded the VST into various DAW Hosts, Studio One 4, Reason 10, Sonar 8.5 and Savihost.
Whenever I try to generate files loaded into the plugin or created within the plugin and select any of the generate options the plugin starts the process, indeed it creates a folder in Drive:\bb\BBPlugin\SavedTracks, then after a few seconds the generate process stops without any error message and the newly created folder remains empty. Midi data gets saved as numbered midi file e.g; 5.mid but no Audio data.
Some (not inconsiderable) steps I've tried to rectify the issue include changing (then changing back) various folder and app permissions, uninstalling AV protection, enabling on board sound, instead of and as well as my Roland interface, re-installing WMP as I usually use MPC-BE as my default player, as well as various other tweaks all to no avail.
Any further help would be appreciated.
And before anyone gleefully points out the report applies to plugin version 1.5.8 it equally applies to 1.7.11.
I doubt Matt minus'ed you, I'm sure he meant, as I DO ... "what he said!"
so a BIG +
Larry
He was saying that he meant "This" not "his". Read the context,
Wendy
> Not sure what that issue is you're having with Ctrl-C, but best to avoid that for now.
Sorry, Peter but I can't resist. On Hee Haw a guy goes to the doctor and says, "Doc, it's hurts when I do this." The doctor looks at him and says, "Well, don't do that!"
I doubt Matt minus'ed you, I'm sure he meant, as I DO ... "what he said!"
so a BIG +
Larry
He was saying that he meant "This" not "his". Read the context,
Wendy
Thanks, but I wasn’t correcting the typo. I was saying I agree with THIS. I’will be clearer in the future.
Jonbouy, your info you sent to support includes "Midi synth N/A". You have to select a synth even if it's just the Coyote Wavetable otherwise no midi will be generated. And I'm not sure if "Loopmidi" is an output driver.
Bob
Jonbouy, your info you sent to support includes "Midi synth N/A". You have to select a synth even if it's just the Coyote Wavetable otherwise no midi will be generated. And I'm not sure if "Loopmidi" is an output driver.
Bob
loopMidi is a virtual cable setup, I can create ports on the fly, I've also got a couple of primal hardware midi ports via the Roland interface, so not applicable seemed the only honest reply.
Once or twice I've flipped the wrong switch but that's not what is happening here.
Thank you.
loopMidi
64 bit Yes... Kontakt runs fine but BIAB VST3i No go...
Thanks Peter,
Since the latest update 607, the Plugin does now show up in Sonar/Cakewalk plugin manager as a VST3i which it did not before the current patch.
You say you have it working in Cakewalk/Bandlab 2018.11 build 25
This does not help me since I have a fully functioning Sonar X3 Producer (X3e Build 352) - x64 running Win 7 Professional
Have you actually tested it on Sonar X3 Producer?
Perhaps you could suggest what settings I might need to make to run this plugin successfully?
Thanks Peter,
Perhaps you could suggest what settings I might need to make to run this plugin successfully?
I agree with this, a list of pre-requisites for the plugin to run successfully, it would help, as well as some plain reading error reporting (via exit codes on initiated actions maybe) to offer clues as to what might have gone wrong when things do go pear-shaped.
Who knows? It may even help narrow some issues down quicker at the same time.
I doubt Matt minus'ed you, I'm sure he meant, as I DO ... "what he said!"
so a BIG +
Larry
He was saying that he meant "This" not "his". Read the context,
Wendy
duh?
I wasn’t correcting anything that anybody wrote.
I was simply saying that I (AND MATT) agreed with the sentiment in the previous post. The purpose of the quotes around the PHRASE "what he said" was meant as a term of "agreement" (i.e., that we, Matt and myself, agree with… WHAT HE SAID, “he” being the previous poster.
I make so many typo’s I would/will never try to correct anyone else’s typing, grammer, spelling, ….
My left hand “one-finger” typing on a PC keyboard almost always beats my right hand “two-finger” typing a lot - so I get a lot of reversed letters and articles of speech, and small pronouns (he, it,) and verbs (is,be) OUT OF ORDER or dropped completely and I hit “post” too fast (I'm a SLOPPY internet poster and email sender) so that’s why I would never attempt to correct minor typos (unless total meaning is 180 out) – there’s probably some typos/mistakes here now -LOL
Boy did I drag this way off topic - sorry folsk
Larry
Boy did I drag this way off topic - sorry folsk
Larry
nOr Plobem
I been minused! I’m getting a Tshirt made “I been minused by Matt”
By the way what Y’all said!
Oh by the way I knew all along he didn’t minus me. If he did I would say “oh know you didunt”
My experiences with BiaB and the VSTi.
The good:
1-Both the 32 and 64 bit versions of BiaB work fine.
2-The VSTi now loads into my Studio One Pro 4 and does not crash it.
The not so good VSTi info (note this is with the 607 update - I just DLed 608 and will get to it at a later date - This info is based on the MIDI side of the VSTi with no RTs):
1-Not all tracks generate. Some are blank until the last chord.
2-The playback in the VSTi is scrambled. It is like the entire band had to much weed or alcohol. But the playback is fine once the tracks are dragged and dropped into the DAW. Note I have checked the usual suspects like sample rate and all is OK.
3-Why when working in MIDI does the VSTi generate wavs? There should be an option for that.
4-If the VSTi has to generate wavs for some reason why not put the purge button on the main GUI so a dummy like me doesn't forget and load my C:/ drive with stuff I'll never use.
5-Having to drop the MIDI files to my DAW one at a time. Why not a master like there is for the wavs?
Maybe 608 has fixed some of these problems, don't know yet.
Although I can't use the VSTi yet I do appreciate all of the work that the PGMusic team is putting into this.
Wow! I just downloaded Cakewalk Band Lab to upgrade my Sonar X3 Producer... The upgrade to CBL was seamlessly pain free!
I'm blown away with the fact that all my VSTs are working and the new BIAB VST for DAW appears to be working too!
This a fabulous addition to my upgraded DAW.
Thanks to everyone at PG Music for all the work ironing out the bugs in the new VST3i.
Cheers and Happy Holidays to all.
Mike
I have cakewalk bandlab and VSTi3 doesn’t work in it.
Replaced Sonar X3 with Cakewalk Bandlab on Win 7 Pro
Very happy... All appears to be running OK including the VST3i
However, if I try to edit a chord in the VST plugin, I am unable to insert more than two chords in a measure. i.e. C,D,E comes out as a Blank!
In the Stand alone 2019 BIAB, no problem, so I make all my song chords in the standalone then save the file for import to the VST... No problem.
Comments?
Mr. BBMaestro, how do you compare Sonar X3 and Cakewalk Bandlab I used Sonar X1 a while back and downloaded Bandlab recently. So far the plugin doesn’t work with it. I normally use Studio One I find Bandlab rather cluttered. I can clean it up but I wonder is it stable. I always found Sonar slightly shakey. I also don’t really understand the comping features in cakewalk. It’s so easy in Studio One.
Hi Rob,
I've used Cakewalk since DOS... Yea I'm that old! Never had a problem with Sonar X3 - X2 - X1 Always did the upgrades.
I can't help you with Studio 1 comparison since I've never used it.
I installed cakewalk Band lab leaving my Sonar X3 Pro. on my win 7 pro desktop. I was pleasantly surprised that all my channel effects and VSTs were working. It was as though my Sonar X3 Pro had been given an upgrade!
So far the only a minor problem I have discovered with the BIAB VSTi is with the inputting of chords as mentioned in my previous post.
I have to say I'm very happy with the BIAB VSTi... It has given a new lease on life to my DAW.
Well done PG Music!
Cheers,
Mike