MOTUnation.com

If anyone can remind me of things to try in order to to alleviate this maddening problem, please tell me. Thank you, brothers.

Movie:

http://www.rfjmusic.com/publicmusic/bundlesproblem.mov" onclick="window.open(this.href);return false;

I don't know how to prevent it, but I seem to remember something about doing a short bounce, like just one measure, and the bundles will snap back to where they belong. Since it's not a fix but a workaround, I'll only take half a million if it works.

Dan Worley wrote:I don't know how to prevent it, but I seem to remember something about doing a short bounce, like just one measure, and the bundles will snap back to where they belong. Since it's not a fix but a workaround, I'll only take half a million if it works.

Ahh, yes, Dan W, I do remember that one...

Alas, no go in this instance after trying it. So close to $500K for you, eh?

I have a similar issue (perhaps the same issue?) and it is a huge time waster.

First of all, I like how in the Bundles window, you can do some kind of macro wiring. They way it works with audio i/o seems to work for my rig. I can almost always make some change in there that prevents me from having to reassign tracks one by one.

With the INSTRUMENTS tab, it would be nice if you could create an instrument there such that if I open the file on another computer, or whatever makes it forget-- at least DP can look for an instrument with the same name, and/or load another into that spot so I don't have to go and reassign every damn track.

I still have bundles issues. 7.24 didn't fix them for me. I wonder if they're VE Pro related for me?? Do any of you guys use VE Pro?

I can tell you, that even without VIs, creating a project and opening it on another machine will
generate lost bundles

DP 7.24

best

Klaus

I don't know what to say.. 7.24 fixed it instantly for me, never looked back. Anywhere from 3 to 10 instances of VE Pro here, on the slave machines. Huge templates on some of my projects, zillions of Kontakts, Play, Omnisphere, Korg.



If I got the bundles mess again, my suffering would be legendary..

cbergm7210 wrote:

Dan Worley wrote:I don't know how to prevent it, but I seem to remember something about doing a short bounce, like just one measure, and the bundles will snap back to where they belong. Since it's not a fix but a workaround, I'll only take half a million if it works.

Ahh, yes, Dan W, I do remember that one...

Alas, no go in this instance after trying it. So close to $500K for you, eh?

I'm so sorry to hear about this, cbergm7210... I know how frustrating and maddening this can become.

You've probably tried this already, but have you tried enabling/disabling the stubborn VIs? This seemed to fix their bundles when the bouncing trick didn't work for me. This sort of reloads the VI and it fixed it most times.

Hey FM Man, thanks for the reply. Sounds like something like that would perhaps shake things up a bit. I'll monkey around with it today and see if anything happens.

It is just odd as it (in this particular project) only happens with one of the two VE Pro instances. The other one is always correct. And, this does not happen on every project. And sometimes, it starts happening after a project gets fairly big. It is hit or miss, in other words.

You know, what I could try is loading a third instance of VE Pro and sub my #1 instance out for this new #3 instance. Then, if #1 continues to do this,

it won't matter because I will not be using it, I'll only be using #2 and #3.

I haven't had this issue since I stopped renaming the VEPro instances and outputs. The long names are clunky in the tracks overview, but the bundles problem has (knock on wood) gone away.

DS

sinkd wrote:I haven't had this issue since I stopped renaming the VEPro instances and outputs. The long names are clunky in the tracks overview, but the bundles problem has (knock on wood) gone away.

DS

Now that's interesting. Sometimes I do and sometimes I do not.

Just FYI my making a "dummy" VE Pro instance worked. My VE Pro instance #3 remains intact while the unused #1 is being changed. At least I don't have to redo everything now when opening the project.