MOTUnation.com

raromatix wrote: i agree to a certain point that my dear ol´ german Logic is somewhat quirky and maybe even ”illogic” In fact realized that long time ago ever since i helped some logicguys, logicgals and logigcats oiling up some hinges, knobs & bolts during the years and even producing a record using Windows and Logic!

Always wonder about this. I don't find Logic to be that illogical. Mostly Emagic left the guts exposed, and asked the end user to go in there every once in a while, i.e. attaching arpeggiators etc. But when it comes to features of the Arrange page like looping and cycling I would even say that Logic is less illogical than DP. I haven't used LogicX though, left it at version 8.

DP trounces other programs with it's editing features for the most part though.

Dear mr. kinnylandrum
Well, well...Brendan of Motu have no answer and consequently no solution to this particular problem but suspect (or at least gave a hint) that the pre-gen (as i myself suspeced in the first place) causing the problem while using external drives. (Since my internal ssd only got some poor 256 gb, i had to rely heavily on external drives - i my case a Thunderbolt drive) The problem is particularly interesting and annoying since it appears after several success bounce procedures - i.e. the project gradually ”rots” or get ”infected” especially while working on huge files like mine in the environment of 9.13 (but not 9.02!). The pre-gen thing is so far i understand intended for internal drives only and i sensed that nor Brendan or Motu regarded that special problem as a bug or shortcoming and therefore it never will be fixed.
Peter

raromatix wrote: The pre-gen thing is so far i understand intended for internal drives only and i sensed that nor Brendan or Motu regarded that special problem as a bug or shortcoming and therefore it never will be fixed.
Peter

That definitely would be a shortcoming if not a bug. I use an external FW800 for audio, and haven't had any of the pre-gen problems cited here with 9.13. But a pre-gen only works with internal drives its a problem if Apple continues with the modular approach.

Hi Raromatix,

When it comes to sample based VIs, it is simply not true that pre-gen works only when the audio samples are stored on internal drives. Remember that pre-gen isn't just for sample based VIs. Pre-gen will render any audio file, plug-in, soft synth or sample based VI pre-real time. I'm wondering where you are getting this information from? Your issue is likely related to a drive problem or the VI.

I suspect the meaning of "uses internal drives" is that it renders the temporary freeze track to the boot drive and if your boot drive is almost full performance suffers or pregen doesn't work right.

raromatix wrote:Dear mr. kinnylandrum
Well, well...Brendan of Motu have no answer and consequently no solution to this particular problem but suspect (or at least gave a hint) that the pre-gen (as i myself suspeced in the first place) causing the problem while using external drives. (Since my internal ssd only got some poor 256 gb, i had to rely heavily on external drives - i my case a Thunderbolt drive) The problem is particularly interesting and annoying since it appears after several success bounce procedures - i.e. the project gradually ”rots” or get ”infected” especially while working on huge files like mine in the environment of 9.13 (but not 9.02!). The pre-gen thing is so far i understand intended for internal drives only and i sensed that nor Brendan or Motu regarded that special problem as a bug or shortcoming and therefore it never will be fixed.
Peter

Well Peter, it is true that, for whatever reason, my problems have been with simple files, not complex. But if it's a problem with external drive, that could present problems for me down the line.

Right now, all the drives I'm using are internal, but I'm on a 6 year old Mac Pro with 4 internal spinners, and when I update to something with SSDs, I will absolutely have to use external drives, and I hope that doesn't present more problems.

I don't believe MOTU has any kind of handle on this at all. I just hope it's not ongoing.

Kurt Cowling wrote:I suspect the meaning of "uses internal drives" is that it renders the temporary freeze track to the boot drive and if your boot drive is almost full performance suffers or pregen doesn't work right.

To the drive? Not to RAM?

kinnylandrum wrote:To the drive? Not to RAM?

Well, I haven't been able to find an answer to that question either way in any of the DP documentation. I assumed it writes invisible files to the boot drive rather than using RAM since it comes into play for heavy VI use and that also needs lots of RAM.

I solved the problem following MOTU instructions (https://motu.com/techsupport/technotes/ ... 20Glitches).

I'm using DP 9.52. A really easy project.. a Omnisphere Keyscape Piano track, a mono click track and a stereo wav track. Ok, with several tempo change, but a really easy project.

I was not able to bounce... I temporary solved freezing the track.

I opened the project in safe mode, and I tried to use a DP plugin for my piano track, but same problem... the bounce started really slow (like always) but after some minutes bounced, increased the speed... and I understood that this meaning that DP was bouncing an empty track.

But reading the link in the MOTU website, I solved making a new empty project, and with File->Load I loaded my bugged project... and... surprise!

Everything back working great!