Previous Thread
Index
Next Thread
Print Thread
Go To
RealBand
Joined: Dec 2011
Posts: 457
Journeyman
OP Offline
Journeyman
Joined: Dec 2011
Posts: 457
Well, I'm finally starting to use RB. I have the latest version that came with BiaB 2017. Received wisdom is that, once you've gotten a tune worked up to a sufficient point in BiaB then it's time to bring it in to RB and do the fine tuning/tweaking to the mix there. So, right off, I see that none of my VXTs and DXs have gotten carried along in the switchover. Or at least so far. I've only tried a few tunes yet, so it's still early.

But anyway, I have sorta-kinda figured out how to set up a VST in RB, but what happens is every MIDI device gets the changes, not just the one I want it for. For example, say I'd like to add the DX for reverb to my melody track. So I click on the little "fx" button on the track panel and up pops the DirectX/VST window. I've selected Coyote because I'm just using one of the MIDI voices for now, and then in one of the lower slots I select Reverb. Suddenly everything is Reverby. And I check the fx's on all the other MIDI tracks and they also all have Reverb set up on them. And it is set up identically to the track I originally set it up for. It gets worse if I want to select a VXT. Suddenly every MIDI instrument has this same VST selected.

I don't want this. And even if I did, I'd want to be able to control them independently from each other.

Why is it that something that appears to be so logical and straightforward is anything but? BiaB's been putting me through the ringer and now it's RB's turn. This is getting really old really fast.

Oh, and before composing this note, I looked through all the available help videos here at PG Music on RB, hoping to find at least one that deals with setting up DXs and VXTs. Couldn't find any.


Last edited by cooltouch; 11/14/17 08:28 PM.
RealBand
Joined: May 2000
Posts: 21,609
Veteran
Offline
Veteran
Joined: May 2000
Posts: 21,609
Here's what is catching you.
When you use the BiaB tracks you are using a single synth that is shared by all the BiaB tracks.

First step;
Use the right-click Track menu to make all the BB tracks regular tracks. This is so they now behave more like RB tracks than BB tracks .. generating and other features will then behave differently.
When you open a BiaB file in RB this is necessary to make the tracks behave more like a DAW.

The second step is to go to the desired track. Select it, then go to the right-click menu and select Port.
Assign it to a separate VSTi Port (softsynth), then assign another instance of the synth to that track using a different Port (and using the top slot in the resulting options). Now you have 2 separate instances of the same synth being used.
All the BB tracks will be assigned to the Default Synth Port, so applying effects to that synth affects all the tracks using that instance of the synth, doing the above step separates them to different instances (and thus different paths).

It all makes sense once you think about it, but this has caught many of us before.

The key is to assign the desired track to it's own instance of a synth so it doesn't affect all the other tracks trying to use the same synth.

Each track goes to a Port
That Port can be any hardware or softsynth (16 of each available)
The Port assignment sends the track info to the desired path (Port or Output path)
In RB the audio FX can be assigned on that path (only if it is a softsynth Port) that affect the audio output of the selected softsynth/Port. If you apply the effect to a synth all tracks are sharing, well they all get to share it. This is sometimes a good thing.
If you want it to affect only one track, you can't share that unique path with other tracks.
You have to give it its own instance of that synth so it doesn't affect all the other tracks.

Attached Files (Click to download or enlarge) (Only available when you are logged in)
RBPorts.jpg (100.66 KB, 135 downloads)
Last edited by rharv; 11/15/17 02:34 PM.

Make your sound your own!
.. I do not work here, but the benefits are still awesome
RealBand
Joined: Dec 2011
Posts: 457
Journeyman
OP Offline
Journeyman
Joined: Dec 2011
Posts: 457
Hi rharv and thanks very much for your reply. I'm sorry to report that, at this point, it isn't making much sense to me at all. And I have a DAW background -- Cakewalk Pro Audio and Sonar and more recently PreSonus's Studio One 3. Now, I'll admit that I frequently get confused with Sonar because of its complexity, so I'm not unused to being stumped.

Okay, I made all BB tracks regular tracks. But where you lost me was at the Ports part. I called up a song that I had saved as a .seq file since I was planning on doing a fair amount of work to it in RB. Clicked on the Melody track, which is the first one I'd like to associate with a synth. Did the right click thing and found Port:17>>CoyoteWT<< in the menu bar. Ran my mouse over that and a dropdown appears with 16 Microsoft GS Wavetable Synths, then the >>CoyoteWT<<, which is indicated with a dot, then 16 DXi/VSTi Synths followed by another >>CoyoteWT (Default)<< that has not been indicated. Below that are two more menu choices, which open up their own dropdowns: Load DXi/Vsti Synth into unused Slot, and Load DXi/VSTi Synth into specific Slot. CoyoteWT is selected in both cases.

So what I did was click on one of the DXi/VSTi tracks, which generated a DirectX/VST Window -- a familiar sight at least. So I plugged in what I wanted as far as DX's go, and I was gratified to hear that only the melody instrument was being "affected" by these effects. I went ahead and configured another VST for the melody, but I am using Coyote as a synth for two other instruments, assigning it to a separate track number with each and each is being affected by its effects separately. This is what I was trying to do at the outset. So that's mission accomplished for me. But I don't understand what you have going on by assigning another instance of the synth to that same track. Why?

This may make sense to you, but right now to me, it's about as clear as mud. So I reckon I'll be doing stuff by rote for a while in RB. Till I get a feel for it -- hopefully.

RealBand
Joined: Dec 2000
Posts: 12,580
Veteran
Offline
Veteran
Joined: Dec 2000
Posts: 12,580
It all depends upon the synth you select. Some synths allow you to connect multiple tracks to them and the instrument played is determined by the channel the track is sending it. Coyote is like this, so you only need to have one instance of it. Cakewalk Dimensions Pro can support of to 4 channels, but is really used for layering up to four sounds. In that case, you would put a separate instance of Dimension on each track (when you do this, you will see Dimension listed on multiple ports). If you selected just one instance of Dimensions on multiple tracks, and changed the instrument assignment, it would apply to all the tracks.

So again, you have to understand the synth you are using and what it expects from the DAW.

For what it's worth, TTS-1, Coyote WT, Coyote Forte, Synthfont, and a handful of others only require a single instance to play up to 16 channels of MIDI data.

Others may and do require separate instances.


John

Laptop-HP Omen I7 Win11Pro 32GB 2x2TB, 1x4TB SSD
Desktop-ASUS-I7 Win10Pro 32GB 2x1.5TB, 2x2TB, 1x4TB SATA

BB2024/UMC404HD/Casios/Cakewalk/Reaper/Studio One/MixBus/Notion/Finale/Dorico/Noteworthy/NI/Halion/IK

http://www.sus4chord.com
RealBand
Joined: May 2000
Posts: 21,609
Veteran
Offline
Veteran
Joined: May 2000
Posts: 21,609
John,
I think you are missing this part;
Yes the synth can play 16 channels with different instruments on each .. BUT if all of those 16 channels are assigned to the Default Synth, and you have an Audio Reverb plugin after it (due to the instance of the synth), all of them will have reverb.

The OP wants different effects for different 'Tracks', so these separate Tracks may need separate synth instances.

RB uses 'Ports' to send the signal to a certain Synth/Effect path.
If you want different effects for a given track it needs it's own 'Port' assignment (new instance of the synth with different AUDIO FX after it) so the FX only affect that Track.

Example:
If Tracks 1-8 are all assigned to a given Port (say the Default synth Port), then putting an Audio Reverb effect after the synth, say in slot 2-4, will affect all the other Tracks using that default Port. This can either save resources or be a hindrance.

To make a given track different, it needs to have its own Port (or path) so the Audio FX that follow that synth instance (or Port) are handled differently.

I suppose a drawing would help (and I think I've posted this before), but the flow is:

Track goes to Port (1 thru 32)
Port assigns synth (hardware or software) if MIDI.
Or it can select the Audio Out Port, if an Audio Track.

Audio FX follow the synth assigned to the selected Port (if a softsynth/MIDI track).

So selecting a different Port, then assigning a new instance of the desired synth to the new Port creates a new 'path' .. and then you can assign different Audio FX to that path (after that instance of the synth of course) to make them different.

I'll see if I can clarify with images if needed.


Make your sound your own!
.. I do not work here, but the benefits are still awesome
RealBand
Joined: Dec 2011
Posts: 457
Journeyman
OP Offline
Journeyman
Joined: Dec 2011
Posts: 457
Yes, rharv, that's what I discovered. The Coyote "default" selection results in all tracks getting the same DX sounds. If I assign Coyote to a track then only that track is affected. And that was what I was after, so I'm good now.

John, I'm familiar with Cakewalk's TTS-1 and it behaves sort of similarly in Sonar. It has to be assigned to a specific track. Only difference with it is, if it isn't assigned to a specific track, it doesn't do anything but just sit there.

RealBand
Joined: Jun 2005
Posts: 7,687
Veteran
Offline
Veteran
Joined: Jun 2005
Posts: 7,687
There's different ways to handle this. I use Sampletank 3. It has a full effects suite so there's none of this going on, if I have a guitar on track 4, channel 4 (I try to keep them the same) ST has it's own guitar cabinet sims and other effects and it only goes on that channel.

The other possibility is to not bother with any effects until you render your midi tracks to audio. Now your audio effects plugins are used. You set up different ones for each track. I know it's fun to keep it all in midi and mess around with stuff but as you're finding out it gets confusing.

You're experienced enough I suspect you've done a few studio sessions over the years. They usually record you dry and feed some effects into your headphones if you need that but the actual recording is dry and unaffected. Adding effects is for the mixdown. The exception was lead guitars, they have their amps and pedals and want that sound on the recording.

But over the last few years I've read that guitarists and bass players use so many sims it changes how recordings are done. Some will not have an amp on stage, they go direct through the PA and/or recording console using an amp sim and they can just push a button and get an entirely different sound without screwing around with amp controls or pedals. The stage or monitor sound is effected but the recording is dry because the engineer and/or the player can mess with all the different sims later. This is exactly why many guitarists on the forum requested DI guitar Real Tracks so now you see lots of them, adding these different amp sims can drastically change the original dry recording.

Of course none of this is written in stone, it's called whatever works for you. But I find it fun to occasionally read some recording forums to get an idea of what's going on lately.

Anyway, after I render my dry tracks to audio I do a Save As so as not to change the original midi or SEQ file in case I want to go back to it.

Bob


Biab/RB latest build, Win 11 Pro, Ryzen 5 5600 G, 512 Gig SSD, 16 Gigs Ram, Steinberg UR22 MkII, Roland Sonic Cell, Kurzweil PC3, Hammond SK1, Korg PA3XPro, Garritan JABB, Hypercanvas, Sampletank 3, more.
RealBand
Joined: Dec 2000
Posts: 12,580
Veteran
Offline
Veteran
Joined: Dec 2000
Posts: 12,580
Quote:
If Tracks 1-8 are all assigned to a given Port (say the Default synth Port), then putting an Audio Reverb effect after the synth, say in slot 2-4, will affect all the other Tracks using that default Port. This can either save resources or be a hindrance.


Okay, I'm going to have to play with this some. I don't understand why, if the effect comes after the synth sound is generated and is specific to just that track (versus a bus effect) it should effect the synth sounds on the other tracks, just because they are sharing a multi-timbral synth. How is the generated sound from the other tracks getting routed to that effect?

Just trying to understand.


John

Laptop-HP Omen I7 Win11Pro 32GB 2x2TB, 1x4TB SSD
Desktop-ASUS-I7 Win10Pro 32GB 2x1.5TB, 2x2TB, 1x4TB SATA

BB2024/UMC404HD/Casios/Cakewalk/Reaper/Studio One/MixBus/Notion/Finale/Dorico/Noteworthy/NI/Halion/IK

http://www.sus4chord.com
RealBand
Joined: May 2000
Posts: 21,609
Veteran
Offline
Veteran
Joined: May 2000
Posts: 21,609
You misunderstood my post I think .. what I was trying to say is, if you add an audio effect to any MIDI track using the default synth, all the default synth tracks inherit this .. as the audio going out of the (shared) synth is effected after the synth. So it can't be on one MIDI channel, because that channel comes out of a synth using many channels, and that output is what gets the next effect. Can't separate a MIDI channel after it is converted to a stereo Audio signal.


Make your sound your own!
.. I do not work here, but the benefits are still awesome
RealBand
Joined: Dec 2000
Posts: 12,580
Veteran
Offline
Veteran
Joined: Dec 2000
Posts: 12,580
Got it. I see what's happening now. But just need to load the same multitimbral synth on different ports and you can use individual effects on each track (just verified it using TTS-1).


John

Laptop-HP Omen I7 Win11Pro 32GB 2x2TB, 1x4TB SSD
Desktop-ASUS-I7 Win10Pro 32GB 2x1.5TB, 2x2TB, 1x4TB SATA

BB2024/UMC404HD/Casios/Cakewalk/Reaper/Studio One/MixBus/Notion/Finale/Dorico/Noteworthy/NI/Halion/IK

http://www.sus4chord.com
RealBand
Joined: May 2000
Posts: 21,609
Veteran
Offline
Veteran
Joined: May 2000
Posts: 21,609
Exactly.


Make your sound your own!
.. I do not work here, but the benefits are still awesome
RealBand
Joined: Dec 2000
Posts: 12,580
Veteran
Offline
Veteran
Joined: Dec 2000
Posts: 12,580
Thanks, I appreciate the explanation. Like I said, I just wanted to understand and sometimes it takes a time or two. Hard heads and all.


John

Laptop-HP Omen I7 Win11Pro 32GB 2x2TB, 1x4TB SSD
Desktop-ASUS-I7 Win10Pro 32GB 2x1.5TB, 2x2TB, 1x4TB SATA

BB2024/UMC404HD/Casios/Cakewalk/Reaper/Studio One/MixBus/Notion/Finale/Dorico/Noteworthy/NI/Halion/IK

http://www.sus4chord.com
Previous Thread
Next Thread
Go To

Link Copied to Clipboard
ChatPG

Ask sales and support questions about Band-in-a-Box using natural language.

ChatPG's knowledge base includes the full Band-in-a-Box User Manual and sales information from the website.

PG Music News
Convenient Ways to Listen to Band-in-a-Box® Songs Created by Program Users!

The User Showcase Forum is an excellent place to share your Band-in-a-Box® songs and listen to songs other program users are creating!

There are other places you can listen to these songs too! Visit our User Showcase page to sort by genre, artist (forum name), song title, and date - each listing will direct you to the forum post for that song.

If you'd rather listen to these songs in one place, head to our Band-in-a-Box® Radio, where you'll have the option to select the genre playlist for your listening pleasure. This page has SoundCloud built in, so it won't redirect you. We've also added the link to the Artists SoundCloud page here, and a link to their forum post.

We hope you find some inspiration from this amazing collection of User Showcase Songs!

Congratulations to the 2023 User Showcase Award Winners!

We've just announced the 2023 User Showcase Award Winners!

There are 45 winners, each receiving a Band-in-a-Box 2024 UltraPAK! Read the official announcement to see if you've won.

Our User Showcase Forum receives more than 50 posts per day, with people sharing their Band-in-a-Box songs and providing feedback for other songs posted.

Thank you to everyone who has contributed!

Video: Volume Automation in Band-in-a-Box® 2024 for Windows®

We've created a video to help you learn more about the Volume Automation options in Band-in-a-Box® 2024 for Windows.

Band-in-a-Box® 2024: Volume Automation

www.pgmusic.com/manuals/bbw2024full/chapter11.htm#volume-automation

Video: Audio Input Monitoring with Band-in-a-Box® 2024 for Windows®

We've created this short video to explain Audio Input Monitoring within Band-in-a-Box® 2024, and included some tips & troubleshooting details too!

Band-in-a-Box® 2024: Audio Input Monitoring

3:17: Tips
5:10: Troubleshooting

www.pgmusic.com/manuals/bbw2024full/chapter11.htm#audio-input-monitoring

Video: Enhanced Melodists in Band-in-a-Box® 2024 for Windows®!

We've enhanced the Melodists feature included in Band-in-a-Box® 2024 for Windows!

Access the Melodist feature by pressing F7 in the program to open the new MultiPicker Library and locate the [Melodist] tab.

You can now generate a melody on any track in the program - very handy! Plus, you select how much of the melody you want generated - specify a range, or apply it to the whole track.

See the Melodist in action with our video, Band-in-a-Box® 2024: The Melodist Window.

Learn even more about the enhancements to the Melodist feature in Band-in-a-Box® 2024 for Windows at www.pgmusic.com/manuals/bbw2024upgrade/chapter3.htm#enhanced-melodist

Band-in-a-Box® 2024 DAW Plugin Version 6: New Features Specifically for Reaper®

New with the DAW Plugin Version 6.0, released with Band-in-a-Box® 2024 for Windows: the Reaper® Panel!

This new panel offers built-in specific support for the Reaper® DAW API allowing direct transfer of Band-in-a-Box® files to/from Reaper® tracks!

When you run the Plugin from Reaper®, there is a panel to set the following options:
-BB Track(s) to send: This allows you to select the Plugin tracks that will be sent Reaper.
-Destination Reaper Track: This lets you select the destination Reaper track to receive media content from the Plugin.
-At Bar: You can select a bar in Reaper where the Plugin tracks should be placed.
-Start Below Selected Track: This allows you to place the Plugin tracks below the destination Reaper track.
-Overwrite Reaper Track: You can overwrite previous content on the destination Reaper track.
-Move to Project Folder: With this option, you can move the Plugin tracks to the Reaper project folder.
-Send Reaper Instructions Enable this option to send the Reaper Instructions instead of rendering audio tracks, which is faster.
-Render Audio & Instructions: Enable this option to generate audio files and the Reaper instructions.
-Send Tracks After Generating: This allows the Plugin to automatically send tracks to Reaper after generating.
-Send Audio for MIDI Track: Enable this option to send rendered audio for MIDI tracks.
-Send RealCharts with Audio: If this option is enabled, Enable this option to send RealCharts with audio.

Check out this video highlighting the new Reaper®-specific features: Band-in-a-Box® DAW Plugin Version 6: New Features Specifically for Reaper®

Band-in-a-Box® 2024 DAW Plugin Version 6: New Features Video

The new Band-in-a-Box VST DAW Plugin Verion 6 adds over 20 new features!

Watch the new features video to learn more: Video: Band-in-a-Box® 2024 - DAW Plugin Version 6 New Features

We also list these new features at www.pgmusic.com/bbwin.plugin.htm.

Forum Statistics
Forums66
Topics81,392
Posts732,471
Members38,440
Most Online2,537
Jan 19th, 2020
Newest Members
zagrajbarke, Ernest J, Izzy, BenChaz, Csofi
38,440 Registered Users
Top Posters(30 Days)
MarioD 195
Al-David 124
DC Ron 113
dcuny 87
rsdean 83
Today's Birthdays
CeeDee, SethMould
Powered by UBB.threads™ PHP Forum Software 7.7.5