Exporting stems is super duper slow

DJ Hellfire wrote:

DaizM wrote:

DJ Hellfire wrote:
3. You can't export audio from the tracks because audio does not flow through the tracks anymore. Audio flows through the program. It's mathematically impossible for the software to render multiple stems out of the same audio path at the same time.

Given that it's been explained that tracks sending data to the same program will have to have new programs (duplicates) created in order for the tracks to be represented as separate audio stems when exported, is there any chance of a feature in the software in the near future that provides an option to automatically duplicate the program (or create a smaller new program for each sound) when exploding a track?

For instance, you have a drum sequence you have created on Track 1 that includes all the sounds of he kit on one track. You then explode the track to have all the pieces of the kit on separate tracks, but since they all route to the same program they would have to be rendered as stems in multiple passes (as you explained earlier). Instead of having to manually go and duplicate the programs, the software would have an option on the explode screen that lets you choose wether to create separate programs for the track elements. It would then create a new program for each sound of the kit-- which would then allow the user to export the stems in the single pass as is desired. Creating a separate program for each sound I know sounds crazy, but since we are going to have to duplicate entire programs to get separate stems anyway, I think at least minimizing the amount of sample duplication and making it an automatic option would be helpful and help folks forget about the awkwardness of the new mixer implementation when it comes to exporting stems (and maybe even song mode). Just a thought...

Remember, when you duplicate a program you aren't duplicating the samples. A program is just data that references the samples assigned to it. So when you duplicate a program, you are only duplicating the pad's parameters, not the actual samples. Seems like good idea though to have the option to duplicate on explode.

OHhhhhh yeah....that's right!! Completely forgot that was corrected a few rev's ago right? Thanks for clarifying that one. So it's not duplicating the sample but each new program gets its own audio path?? I know that was highlighted in 1.7 release, but I guess it's significance just never really truly sunk for me until now... That's actually pretty slick when I think about it....knowing that, now having multiple progs to get separate stems doesn't sound like such a problem after-all to me....if it were automatically done at track explode it would be completely a non-factor for me at that point. Hopefully that gets added in the future! Good info HF

DJ Hellfire wrote:

jigdagod wrote:Thanks for breaking it down. Well explained....I still don't like it.

Explode tracks only works in Main Mode and not Song mode. I'm running into the problem if I have different tempo changes it only takes the first tempo. So now I'm stuck with doing it the other way.

In this case I would track to a DAW in plugin mode.

Good point! I still need to get into doing this. Keep pushing for more virtual outs for us. 128 is more than enough.

DaizM wrote:

DJ Hellfire wrote:Remember, when you duplicate a program you aren't duplicating the samples. A program is just data that references the samples assigned to it. So when you duplicate a program, you are only duplicating the pad's parameters, not the actual samples. Seems like good idea though to have the option to duplicate on explode.

OHhhhhh yeah....that's right!! Completely forgot that was corrected a few rev's ago right? Thanks for clarifying that one. So it's not duplicating the sample but each new program gets its own audio path?? I know that was highlighted in 1.7 release, but I guess it's significance just never really truly sunk for me until now... That's actually pretty slick when I think about it....knowing that, now having multiple progs to get separate stems doesn't sound like such a problem after-all to me....if it were automatically done at track explode it would be completely a non-factor for me at that point. Hopefully that gets added in the future! Good info HF

Nah, this isn't something new. I have always used this technique on all of my MPCs for adding filtered versions of my chops. 1.7 just has the added advantage of getting a dedicated audio channel as well. But as far as duplicating programs, MPC's have always done this without duplicating samples.

Finally had a chance to try it out. Worked so much better than exporting one stem at a time but still doesn't quite seem to be the speed of 1.6. It's fast enough for my needs though. I also like the idea of being able to explode a program to multiple programs as well so we wont have to do this manually since programs are basically the new tracks. Hopefully this can happen in the future.

Eyalc wrote:

DJ Hellfire wrote:Already did very long ago. I suggested to just max it out at 128. Don't know if it will happen.

However, one option you have is not tracking everything in stereo. If a sound is mono, you're better off panning it hard and tracking it to a mono track in your daw instead of burning a pair of outs. This could potentially give you up to 32 channels depending on how many actual stereo samples/instruments you're using.

I remember you talking about 128. Too bad they won't do it. Doesn't make sense to me why they wouldn't. Hopefully they will see this conversation and consider it again.

As far as not tracking everything in stereo, agree. Typically my drum sounds I track in mono, everything else in stereo, so I still often run out with 16 stereo. But could find other ways to reduce the stereo track count.

But dang, if they would just double it once more, no issues then. It's a simple request - but must be a difficult change. Or allow multiple instances in a DAW. But I'd prefer more virtual outs.

Well, I'm not saying they definitely aren't going to do it. I just don't think it's as high on the priority list as more requested features.

DJ Hellfire wrote:

DaizM wrote:

DJ Hellfire wrote:Remember, when you duplicate a program you aren't duplicating the samples. A program is just data that references the samples assigned to it. So when you duplicate a program, you are only duplicating the pad's parameters, not the actual samples. Seems like good idea though to have the option to duplicate on explode.

OHhhhhh yeah....that's right!! Completely forgot that was corrected a few rev's ago right? Thanks for clarifying that one. So it's not duplicating the sample but each new program gets its own audio path?? I know that was highlighted in 1.7 release, but I guess it's significance just never really truly sunk for me until now... That's actually pretty slick when I think about it....knowing that, now having multiple progs to get separate stems doesn't sound like such a problem after-all to me....if it were automatically done at track explode it would be completely a non-factor for me at that point. Hopefully that gets added in the future! Good info HF

Nah, this isn't something new. I have always used this technique on all of my MPCs for adding filtered versions of my chops. 1.7 just has the added advantage of getting a dedicated audio channel as well. But as far as duplicating programs, MPC's have always done this without duplicating samples.

no, you're right. I used to have a 2k a 2500 and still have a 3k and know the hardware MPC just had pointers to the files, but I thought I recalled one of the earlier releases of the MPC software was duplicating samples if the program was duplicated....I must be having a memory lapse then, but still a slick implementation for the software though