Bundles Mess Fixed in 7.24!
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
-
- Posts: 2232
- Joined: Thu Jan 13, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: USA
Bundles Mess Fixed in 7.24!
EDIT:
I renamed this thread, rather than posting a whole new one. See bottom for the news!
Here's some of the history for those who don't know about it:
http://www.motunation.com/forum/viewtop ... ndles+mess" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;
http://www.motunation.com/forum/viewtop ... ss#p373161" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;
I'm still on 7.21, my system didn't do so well on 7.22 for some reason. I'm thinking of trying 7.23 out today.. so is this problem fixed yet, or better? The workarounds (like bouncing the empty bar, using a blank project as a template, etc.) don't always work for me.
I really want to be able to create a new project from a template and have it all come up as it should- this problem getting old.
One thing I have noticed is that the more MIDI I write into the tracks, the better the problem gets, and at some point towards the end of composing a piece, the bundles become solid and come up correctly every time the project is launched.
Anybody have anything new on this?
I renamed this thread, rather than posting a whole new one. See bottom for the news!
Here's some of the history for those who don't know about it:
http://www.motunation.com/forum/viewtop ... ndles+mess" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;
http://www.motunation.com/forum/viewtop ... ss#p373161" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;
I'm still on 7.21, my system didn't do so well on 7.22 for some reason. I'm thinking of trying 7.23 out today.. so is this problem fixed yet, or better? The workarounds (like bouncing the empty bar, using a blank project as a template, etc.) don't always work for me.
I really want to be able to create a new project from a template and have it all come up as it should- this problem getting old.
One thing I have noticed is that the more MIDI I write into the tracks, the better the problem gets, and at some point towards the end of composing a piece, the bundles become solid and come up correctly every time the project is launched.
Anybody have anything new on this?
Last edited by Killahurts on Wed Jul 27, 2011 9:34 am, edited 3 times in total.
DP11, 2019 16-Core Mac Pro, OS 14 Sonoma , 64GB RAM. RME HDSPe MADI FX to SSL Alphalink to SSL Matrix console, and multiple digital sub consoles. UAD Quad PCIe. Outboard stuff.
Re: More thoughts about the bundles problem..
Sorry Killahurts,
but i'm on 7.23 and running into the same problem. It's a little inconsistent in the sense that sometimes it works but i still find it an issue. Mostly or only for me with VE Pro busses. Really want this to be fixed in the next update. I believe i remember James saying that MOTU were working on it so... here's hoping.
haydn.
anyone else?
but i'm on 7.23 and running into the same problem. It's a little inconsistent in the sense that sometimes it works but i still find it an issue. Mostly or only for me with VE Pro busses. Really want this to be fixed in the next update. I believe i remember James saying that MOTU were working on it so... here's hoping.
haydn.
anyone else?
Computer/s: OSX 10.8.3
2 x 2.66 GHz Mac Pro Quad-Core Intel Xeon w/ 16GB RAM,
DAW:DP8.05
Hardware: Apogee Duet
VI's/Plug-ins:
Kontakt 5.1, EW PLAY Libraries and a
million others.
2 x 2.66 GHz Mac Pro Quad-Core Intel Xeon w/ 16GB RAM,
DAW:DP8.05
Hardware: Apogee Duet
VI's/Plug-ins:
Kontakt 5.1, EW PLAY Libraries and a
million others.
- James Steele
- Site Administrator
- Posts: 22792
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: San Diego, CA - U.S.A.
- Contact:
Re: More thoughts about the bundles problem..
I don't know if that was the issue or not. I don't have VE Pro. I just heard something like some things they were working on in connection with it, but I have no idea about specifics.hrw wrote:Sorry Killahurts,
but i'm on 7.23 and running into the same problem. It's a little inconsistent in the sense that sometimes it works but i still find it an issue. Mostly or only for me with VE Pro busses. Really want this to be fixed in the next update. I believe i remember James saying that MOTU were working on it so... here's hoping.
haydn.
anyone else?
JamesSteeleProject.com | Facebook | Instagram | Twitter
Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
Re: More thoughts about the bundles problem..
Thanks James, well, here's hoping anyway.James Steele wrote:I don't know if that was the issue or not. I don't have VE Pro. I just heard something like some things they were working on in connection with it, but I have no idea about specifics.hrw wrote:Sorry Killahurts,
but i'm on 7.23 and running into the same problem. It's a little inconsistent in the sense that sometimes it works but i still find it an issue. Mostly or only for me with VE Pro busses. Really want this to be fixed in the next update. I believe i remember James saying that MOTU were working on it so... here's hoping.
haydn.
anyone else?
Computer/s: OSX 10.8.3
2 x 2.66 GHz Mac Pro Quad-Core Intel Xeon w/ 16GB RAM,
DAW:DP8.05
Hardware: Apogee Duet
VI's/Plug-ins:
Kontakt 5.1, EW PLAY Libraries and a
million others.
2 x 2.66 GHz Mac Pro Quad-Core Intel Xeon w/ 16GB RAM,
DAW:DP8.05
Hardware: Apogee Duet
VI's/Plug-ins:
Kontakt 5.1, EW PLAY Libraries and a
million others.
-
- Posts: 2232
- Joined: Thu Jan 13, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: USA
Re: More thoughts about the bundles problem..
Yeah, thanks guys. It is definitely a problem with VE Pro, although I don't know if it's exclusive to that. Seems like it mostly has to do with using aux channels to receive multiple inputs from VI's.
I thought about putting everything in a V Rack to see if that helps, but it would take me the rest of my life to set that up, so I haven't tried it yet.
I thought about putting everything in a V Rack to see if that helps, but it would take me the rest of my life to set that up, so I haven't tried it yet.

DP11, 2019 16-Core Mac Pro, OS 14 Sonoma , 64GB RAM. RME HDSPe MADI FX to SSL Alphalink to SSL Matrix console, and multiple digital sub consoles. UAD Quad PCIe. Outboard stuff.
Re: More thoughts about the bundles problem..
Yes my friend. This is exactly my experience. Glad in one way that i'm not alone and crazy! Would love it to be fixed.Killahurts wrote:Yeah, thanks guys. It is definitely a problem with VE Pro, although I don't know if it's exclusive to that. Seems like it mostly has to do with using aux channels to receive multiple inputs from VI's.
Computer/s: OSX 10.8.3
2 x 2.66 GHz Mac Pro Quad-Core Intel Xeon w/ 16GB RAM,
DAW:DP8.05
Hardware: Apogee Duet
VI's/Plug-ins:
Kontakt 5.1, EW PLAY Libraries and a
million others.
2 x 2.66 GHz Mac Pro Quad-Core Intel Xeon w/ 16GB RAM,
DAW:DP8.05
Hardware: Apogee Duet
VI's/Plug-ins:
Kontakt 5.1, EW PLAY Libraries and a
million others.
Re: More thoughts about the bundles problem..
I have the problem with other VI bus outs too.
The other day I had set up a 3-4 output in Kontakt4, and an Auxiliary channel to route it, so I could apply a plugin to one patch in a Multi. When the project was closed and reopened, the Kontakt 3-4 bus was no longer assigned in the Bundles window (usually assigned to a Bidule/Rewire output which I'm not even using in the project).
So, I deleted all the Kontakt assignments in the Bundles window Instruments section then manually reassigned them. After getting the Aux setup and working again, I closed the project and reopened it again. The 3-4 Kontakt were 'forgotten' again!
So, I deleted all the Kontakt assigns again, but instead of manually assigning new ones, I used the Add Multiple button, choosing around 60 or so. Guess what? Some were left out, like Kontakt 3 through 8... nothing assigned to them! So I assigned the patch, and Aux channel to Kontakt 9-10... Closed/reopened the project... still assigned.
The other day I had set up a 3-4 output in Kontakt4, and an Auxiliary channel to route it, so I could apply a plugin to one patch in a Multi. When the project was closed and reopened, the Kontakt 3-4 bus was no longer assigned in the Bundles window (usually assigned to a Bidule/Rewire output which I'm not even using in the project).
So, I deleted all the Kontakt assignments in the Bundles window Instruments section then manually reassigned them. After getting the Aux setup and working again, I closed the project and reopened it again. The 3-4 Kontakt were 'forgotten' again!
So, I deleted all the Kontakt assigns again, but instead of manually assigning new ones, I used the Add Multiple button, choosing around 60 or so. Guess what? Some were left out, like Kontakt 3 through 8... nothing assigned to them! So I assigned the patch, and Aux channel to Kontakt 9-10... Closed/reopened the project... still assigned.
-
- Posts: 2232
- Joined: Thu Jan 13, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: USA
Re: More thoughts about the bundles problem..FIXED?




Installed 7.24, created a new project from (existing) template, set the VI bundles straight (none were working), saved. Quit. Loaded the project again, the bundles were perfect. Started composing a theme, did 3 or 4 MIDI tracks, Saved. Quit. Loaded again, the bundles were perfect. Quit, loaded again, the bundles were.. perfect.
Made another project. Repeated everything above, same result.
Before I pee in my pants, I need for you guys to check this out and see what it does on your machines. We may have a fix here! I have not had that kind of luck that many times in a row since this problem was recognized.
Haydn, Tim, Gabe, Armando, FMiguelez, anyone who this has been a problem for, needs to try this out and report. I had to re-set up all the bundles in the first one, but once it's saved, it's saved!
DP11, 2019 16-Core Mac Pro, OS 14 Sonoma , 64GB RAM. RME HDSPe MADI FX to SSL Alphalink to SSL Matrix console, and multiple digital sub consoles. UAD Quad PCIe. Outboard stuff.
Re: More thoughts about the bundles problem..
Haydn here.That's great news Killahurts. Not in the studio today but will check it out asap and report back. Sounds exciting!
Computer/s: OSX 10.8.3
2 x 2.66 GHz Mac Pro Quad-Core Intel Xeon w/ 16GB RAM,
DAW:DP8.05
Hardware: Apogee Duet
VI's/Plug-ins:
Kontakt 5.1, EW PLAY Libraries and a
million others.
2 x 2.66 GHz Mac Pro Quad-Core Intel Xeon w/ 16GB RAM,
DAW:DP8.05
Hardware: Apogee Duet
VI's/Plug-ins:
Kontakt 5.1, EW PLAY Libraries and a
million others.
-
- Posts: 2232
- Joined: Thu Jan 13, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: USA
Re: More thoughts about the bundles problem..7.24 FIXED?
I took one of my successful projects above and did a "Save as Template".
Made a new project from that new template and the bundles came up perfectly. Hallelujah!
Way to go MOTU, thank you thank you thank you!

Made a new project from that new template and the bundles came up perfectly. Hallelujah!
Way to go MOTU, thank you thank you thank you!

DP11, 2019 16-Core Mac Pro, OS 14 Sonoma , 64GB RAM. RME HDSPe MADI FX to SSL Alphalink to SSL Matrix console, and multiple digital sub consoles. UAD Quad PCIe. Outboard stuff.
-
- Posts: 223
- Joined: Sun Aug 18, 2013 7:04 am
- Primary DAW OS: Windows
- Location: New York, NY
- Contact:
Re: Bundles Mess Fixed in 7.24!
I'm still seeing this problem in 8.05 on Windows. Anyone else have this one come back?
DP 10 - Win 10 - Ultralite AVB
- FMiguelez
- Posts: 8266
- Joined: Sun Oct 24, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Body: Narco-México Soul/Heart: NYC
Re: Bundles Mess Fixed in 7.24!
What is your problem exactly? Do bundles disappear, remain inactive, misconnected...?
Are you using VE Pro?
Are you using VE Pro?
Mac Mini Server i7 2.66 GHs/16 GB RAM / OSX 10.14 / DP 9.52
Tascam DM-24, MOTU Track 16, all Spectrasonics' stuff,
Vienna Instruments SUPER PACKAGE, Waves Mercury, slaved iMac and Mac Minis running VEP 7, etc.
---------------------------
"In physics the truth is rarely perfectly clear, and that is certainly universally the case in human affairs. Hence, what is not surrounded by uncertainty cannot be the truth." ― Richard Feynman
Tascam DM-24, MOTU Track 16, all Spectrasonics' stuff,
Vienna Instruments SUPER PACKAGE, Waves Mercury, slaved iMac and Mac Minis running VEP 7, etc.
---------------------------
"In physics the truth is rarely perfectly clear, and that is certainly universally the case in human affairs. Hence, what is not surrounded by uncertainty cannot be the truth." ― Richard Feynman
-
- Posts: 223
- Joined: Sun Aug 18, 2013 7:04 am
- Primary DAW OS: Windows
- Location: New York, NY
- Contact:
Re: Bundles Mess Fixed in 7.24!
Sorry for the long delay - didn't realize you'd replied.
As some users describe above, I was having a weird issue when using anything but the main outs of multi-out plugins (especially Kontakt). As soon as I reloaded a project, any aux tracks or bundles assigned to those outputs would forget their assignments and go back to the first available bus or bundle, and I'd have to reassign them. For example, if I created an aux track to handle the output of Kontakt 3-4, it would work fine until I closed & opened the project again, at which point the input of the aux track would change to REAPER (through rewire), and I'd have to reassign it. The master out (Kontakt 1-2), was remembered correctly.
I ended up starting a TechLink for this, and the friendly folks at MOTU confirmed that there is an issue on Windows. It is supposed to be fixed in 8.06, which I understand is just around the corner.
However, I also found that the issue only occurs when I use one of the "smaller" Kontakt DLL's (8-out or 16-out), and does not occur when I use the regular 32-out DLL. I also tested it out with at least one other multi-out plug, and did not have the problem there. I simply disabled the 8-out and 16-out versions of Kontakt, and am only using the 32-out, so I no longer have a problem.
Thanks for the response!
Mike
As some users describe above, I was having a weird issue when using anything but the main outs of multi-out plugins (especially Kontakt). As soon as I reloaded a project, any aux tracks or bundles assigned to those outputs would forget their assignments and go back to the first available bus or bundle, and I'd have to reassign them. For example, if I created an aux track to handle the output of Kontakt 3-4, it would work fine until I closed & opened the project again, at which point the input of the aux track would change to REAPER (through rewire), and I'd have to reassign it. The master out (Kontakt 1-2), was remembered correctly.
I ended up starting a TechLink for this, and the friendly folks at MOTU confirmed that there is an issue on Windows. It is supposed to be fixed in 8.06, which I understand is just around the corner.
However, I also found that the issue only occurs when I use one of the "smaller" Kontakt DLL's (8-out or 16-out), and does not occur when I use the regular 32-out DLL. I also tested it out with at least one other multi-out plug, and did not have the problem there. I simply disabled the 8-out and 16-out versions of Kontakt, and am only using the 32-out, so I no longer have a problem.
Thanks for the response!
Mike
DP 10 - Win 10 - Ultralite AVB