Bundles not working, what else is new...

[jmca]

I still can't believe it. More clicks and whistles being added to DP for every version, yet me & others are still having the old crappy Bundles bug since 2006. I've had it with this junk. With these kind of price tags I'm totally flabbergasted by the thought of this bug not being fixed 4 years later. This is the bug where every time you switch from "Sound File" or disengage/re-engage a virtual instrument track (specifically ToonTrack stuff), all multiple output assignments in the Bundles go haywire. It's a craps shoot at which outputs DP will assign. I'm going to start organizing betting pools to see which coordinate the little black squares will land on. This issue makes DP completely unusable, completely killing my work flow and my time. Forget the snazzy new features, FIX THE BUGS!!!

[doodles]

Hmmm. First post.

Can only imagine it's really annoying, but is this a rant or do you want help?

[HCMarkus]

I use VIs all the time (but not Toon Tracks) and have never experienced the problem you describe, or anything remotely resembling it for that matter.

Could there be an issue with your system, possibly?

Which reminds me... what IS your system. You might want to set up a signature. Here's what I'm using at present:

[Frodo]

Take ToonTrack out of the equation-- create a new project without ToonTrack and see if the problem persists.

At that point, it only takes a minute to rebuild one's Bundles.

If that doesn't do it, it's time to talk to someone at ToonTrack. You might find that adjusting your Work Priority, Prime Seconds, or Work Quanta or even Max Work Percent might be of some benefit if used wisely.

If we're dealing with any version beyond DP 5.13, then there must be an implicit understanding of what pre-rendering is all about.... and that VI pre-rendering is different than audio pre-rendering, the capability for which were implemented in different versions of DP.

All that to say this: it might not be Bundles or a "bug" at all.

[fsheinfeld]

I've had a similar issue with a few others VIs. One thing I noticed is that when this happens I see a lot of inputs assigned to rewire MIDI instruments -even if I'm not using Rewire. Maybe it's Rewire related? You could turn the Rewire driver of and see what happens (although I'm not sure if you are still trying to troubleshot this).

I used to have that problem with Drumcore in DP5 and Model12 in DP6, but I still have it now with Battery 3, on one old session I just opened from DP6 with DP7.1.
I haven't really troubleshot this because I just switched the inputs manually very quickly, so it wasn't a big deal for me.

Are you opening an old session? If so, I would try to create a new template from scratch with DP7.1. Many of my problems went away that way. Bundles and Device Groups can act like a bad virus if you keep dragging them with all your DP versions....

[superjeezus]

I have been dealing with this since version 6. It happens with lots of different VI combinations, so I don't think any particular instrument is to blame. It may be rewire related, though I don't see how it could be anything other than a DP bug. The problem appears to be DP's bundles, and I have had no similar problems with other apps and rewire.

To fix it, I will usually just delete and recreate the VI bundles. Yeah it's a pain, but for me it's worth it to keep using DP. I have tried what Frodo suggested, but no love.

I suspect this has something to do with the seemingly random crashes I have experienced in DP ever since version 6.

[newrigel]

WOW... I use TT and NO issues whatsoever!

[crduval]

I just went through some problems this morning where I had lost work due to crashes and twice used autosave copies to recover (most) of what I had done. I was very happy about that...

Relative to Toontrack though, both times, when I launched the autosaved version of the project, I could no longer hear the EZ drummer multitrack outputs.

When I opened the Bundles window and looked at the "Instruments" tab, I saw that the multitrack instrument outputs of EZ drummer had vanished. Reentering them in the Bundles window and then re-assigning the tracks in the Tracks window fixed the problem both times.

One of the two times, the instrument outputs were shown in the tracks window in italics (cluing me in on what had happened). The other time though, they were not italicized, but still did not sound. Turns out that while they had vanished from the Instruments tab on the Bundles window, they showed up as valid inputs on the "input" tab of the Bundles window, assigned to the channels of my ultralite!

Weird...

[MIDI Life Crisis]

What a great first post. And after years of problems no less - no questions to ask, no "I can't find this on the forum, can you help" and no "hi - I don't have a clue what I'm taking about, but here's the problem: the stuff I've been doing for years hasn't worked and I'm just getting around to bitch about it."

Reminds me of the guy who was seen running along his bicycle down the street and someone asked: "Why are you running along side your bike?" He replied: "I'm late for work and I don't have time to get on."

I wonder which year he registered the copy with MOTU...?

[newrigel]

I just went through some problems this morning where I had lost work due to crashes and twice used autosave copies to recover (most) of what I had done. I was very happy about that...

Relative to Toontrack though, both times, when I launched the autosaved version of the project, I could no longer hear the EZ drummer multitrack outputs.

When I opened the Bundles window and looked at the "Instruments" tab, I saw that the multitrack instrument outputs of EZ drummer had vanished. Reentering them in the Bundles window and then re-assigning the tracks in the Tracks window fixed the problem both times.

One of the two times, the instrument outputs were shown in the tracks window in italics (cluing me in on what had happened). The other time though, they were not italicized, but still did not sound. Turns out that while they had vanished from the Instruments tab on the Bundles window, they showed up as valid inputs on the "input" tab of the Bundles window, assigned to the channels of my ultralite!

Weird...

Try saving your custom board settings within EZD! Once you get everything assigned the way you want, save it as a custom mixer template in EZD and you shouldn't have any problem (hopefully).
But... I keep it simple. I just use multiple instances of EZD or SD and only send to each the data I want to send to them. Forget all that bussing mojo... too much BS. Like a stereo pair of the total kit and then I have one with only a snare and then one with only a kick and just mix the stereo kit within EZD or SD's mixer. But the snare and kicks get the SSL and UAD treatments because SD have some decent plugs in them for EQ's and dynamics (SD2 has Sonalksis plugs) so...I have 3 instances of the TT plugs, one of an entire kit and the other ones with kicks only and snare only to send to whatever I want in DP and it KILLS! I like what SD does for the toms right within it's own mixer because sending them out causes them to loose the live feel that the combined rooms samples give... but everyones different.

[Kurt Cowling]

Unfortunately saved mixer presets (user) do not save output assignments, only volume/pan/mute type data. I would love it if TT would change that and I've suggested it to them.

Yes, bundles get messed up and duplicated in weird ways whenever something goes on- or off-line. I have to switch to mLan when printing audio from my S90-ES and bundles are all messed up when I go back to MAS.

[Shooshie]

I still can't believe it. More clicks and whistles being added to DP for every version, yet me & others are still having the old crappy Bundles bug since 2006. I've had it with this junk. With these kind of price tags I'm totally flabbergasted by the thought of this bug not being fixed 4 years later. This is the bug where every time you switch from "Sound File" or disengage/re-engage a virtual instrument track (specifically ToonTrack stuff), all multiple output assignments in the Bundles go haywire. It's a craps shoot at which outputs DP will assign. I'm going to start organizing betting pools to see which coordinate the little black squares will land on. This issue makes DP completely unusable, completely killing my work flow and my time. Forget the snazzy new features, FIX THE BUGS!!!

Maybe if you updated to the current version, upgraded to Snow Leopard, and quit trying to run it on a G3 iMac, then Read the Manual, you'd find out what the rest of us know: DP is running great these days.

Shoosh

[superjeezus]

Maybe if you updated to the current version, upgraded to Snow Leopard, and quit trying to run it on a G3 iMac, then Read the Manual, you'd find out what the rest of us know: DP is running great these days.

May I respectfully point out - it doesn't look like the OP has listed whether he is running on an old machine, or whether he has read the manual. But as a mod you may be privy to some additional information, or maybe you are making a point so the OP will post his setup.

Nevertheless, as has been pointed out in this thread, at least a couple of us are experiencing similar problems on current/updated systems. If there is something in the manual that explains how to prevent this Bundles problem, please post the page number or section. I will be very thankful and will promptly look it up in my DP7 manual, which I have in fact read quite thoroughly.

Granted, the tone of the OP's post is not the most productive. But some of the rest of us might benefit from some constructive discussion of the issue. It sure seems like a real problem to me, and I think I have troubleshot the issue quite thoroughly without finding a solution.

[michkhol]

you'd find out what the rest of us know: DP is running great these days.

Except when it crashes.

I have a project with VE Pro with exactly the same problem. After I open it or disable/enable the VE Pro plugin all outputs would shift to rewire instruments in random order. As a workaround I created another VI with the same VE Pro and output assignments and made sure it came after the first one in the bundles window. The new VE Pro outputs were stable. What makes it even more interesting, I also had a second (now third) multichannel VE Pro instance in the same sequence but it never behaved improperly. For me it is an obvious DP bug but I never brought it up here because I knew what kind of discussion it might cause (see above).

YMMV

[Shooshie]

May I respectfully point out - it doesn't look like the OP has listed whether he is running on an old machine, or whether he has read the manual. But as a mod you may be privy to some additional information, or maybe you are making a point so the OP will post his setup.

Nevertheless, as has been pointed out in this thread, at least a couple of us are experiencing similar problems on current/updated systems. If there is something in the manual that explains how to prevent this Bundles problem, please post the page number or section. I will be very thankful and will promptly look it up in my DP7 manual, which I have in fact read quite thoroughly.

Granted, the tone of the OP's post is not the most productive. But some of the rest of us might benefit from some constructive discussion of the issue. It sure seems like a real problem to me, and I think I have troubleshot the issue quite thoroughly without finding a solution.

You nailed it: he needs to post his setup and change his tone. If you're experiencing a real problem, start a thread on it that deals with it in a constructive manner. I don't have time or inclination to help jerks who come in here and lambast DP in their 1 and only post, with ZERO clues as to how we might help him, and with no apparent desire for help, just a bunch of trash talk. I wouldn't want to interrupt his betting pool with something that might stop the problem.

For those of you who have legitimate problems and need to discuss it, for my 2-cents it's not going to happen in this thread. And in case anyone is actually wondering at this point, my response was not based on any sort of fact or opinion. It was simply "in-kind." Granted, it would have been more mature of me simply not to respond at all, or to politely ask that he post his info and zero in a little more thoroughly on the problem, but really I'm not here to do his testing for him, or to guess what circumstances may be causing it.

I've seen something like the problem he described, and I've even posted my own experience with it, and how I dealt with it. But I won't be posting any more about it in this thread. This is a rant and belongs in the Rants and Off-Topics forum. Let's face it guys; none of us is paid to do this. We come here for reasons of our own, but mostly for camaraderie and shared problem solving. When some jerk comes in here and lays down a first post like that, it's disrespectful to every single one of us. Which of us is going to be able to add meaningful information until the poster explains very carefully what is going on, what events may have precipitated this result, and all the hardware/software that may be involved? I'm not a wizard with a crystal ball, and I rather resent being put on the spot like that. The tone is basically " DP sucks. It screwed up my bundles. We're betting that nobody here has an answer, so basically DP sucks."

I use a LOT of my spare time in here giving what I can to people whose work might benefit from my past and present experience. I don't ask for anything back. But when someone pizzes me off like this, disrespecting the forum and everyone in it, I reserve the right to tell him what I think about that. If he wants to repost in another thread and try again -- this time displaying an actual desire to get to the bottom of it and figure out what can be done about it -- then I'll be glad to behave and work with him.

Or he can leave his post like this and get lost, for all I care.

Shooshie