MOTUnation.com

waxman wrote:

crescentoon55 wrote:Plugins with problems... soundlib- G Player.... and Reaktor 5 & 6 ...but only one or two presets from them... strange. G player plays gigasampler sounds and I have been having sync problems with it...

Plugs operating under their own players are not working well. Vienna, Stylus and others that use their own engine within the DAW. G Player and Reactor have the same issues right?

By "operating under their own players," do you mean as opposed to MOTU's own plug-ins, or as opposed to Kontakt-based libraries, or...?

According to the tech at MOTU certain VI's like stylus have their own engines. Older versions of Vienna. In the dp insert those vi's are not built to take advantage of pre-gen and have issues. MOTU and the companies are working on it...

9.1.2 still buggy here

lost audio connection with ssl madi card synchro (9.02 was fine)
and it seems that it bypass the MIDI mute note suddenly ,... really weird ,....
force to restart soft and it works again until,..... it happened agin,..........same with 9.1
and its not systematical .....
back to that good old 9.02!!


also a bug with steven slate vmr and VTM and with empty room reverb they all go to bypass mode as you reopen a project, it forces you to leave them open if you don't want them to be bypass,.... really annoying behavior on fat session !

chunk are still buggy after a chunk change the views are messed up in between views and chunk name or you get frooze view, forces you to recall chunk back and forth to get the right window ,... but this is happening since eeeeeeeeeever dp 5-6-7-8-9....

otherwise this software is great !

and cheers to all !

gman wrote:9.1.2 still buggy here

lost audio connection with ssl madi card synchro (9.02 was fine)
and it seems that it bypass the MIDI mute note suddenly ,... really weird ,....
force to restart soft and it works again until,..... it happened agin,..........same with 9.1
and its not systematical .....
back to that good old 9.02!!


also a bug with steven slate vmr and VTM and with empty room reverb they all go to bypass mode as you reopen a project, it forces you to leave them open if you don't want them to be bypass,.... really annoying behavior on fat session !

chunk are still buggy after a chunk change the views are messed up in between views and chunk name or you get frooze view, forces you to recall chunk back and forth to get the right window ,... but this is happening since eeeeeeeeeever dp 5-6-7-8-9....

otherwise this software is great !

and cheers to all !

Have you repaired permissions since the install? Might help.

MIDI Life Crisis wrote: Have you repaired permissions since the install? Might help.

It hasn't helped the last 200 times you suggested it, what's different this time?

stratology wrote:

MIDI Life Crisis wrote: Have you repaired permissions since the install? Might help.

It hasn't helped the last 200 times you suggested it, what's different this time?

Okay... I'm done with this guy. I don't need the aggravation. He's booted off the board.

It's a well known fact that the 201st time you repair permissions does the trick...

gman wrote:also a bug with steven slate vmr

FYI, Slate sent out a message today with news that there is an update to VMR.

Whats the bug with Slate Virtual Mix Rack?

In experiencing the new next gen pre gen, I am starting to grow a bit uncomfortable with one aspect of all of this.
I am no programmer of course, and I wish I were so as to understand this better, but it seems to me that the new “design” of DP could require several 3rd party companies to update their software to “work right" with DP. I am a bit concerned that this is a scenario in which DP has a great idea, but if no other companies wish to play along and update their software to “work well" with DP, we all might be waiting on a variety of companies to update things. That can be a very long road that never goes anywhere. When I hear users having to keep Slate products windows open so they work right, well? Where's the “bug”? Slate or DP? If it’s “Slate’s bug”, then what other 3rd party companies will also have issues, and will we all be waiting for 3rd party updates and for how long?Thsfar, only one company I know of has gone out of it’s way for MOTU, that being Vienna, who made a special edition for MAS. In the past, many companies made MAS versions, but not anymore as far as I know.
I hope I am wrong here and I hope that all software adjustments can be made on MOTU’s end. But if not, and MOTU forges ahead with “next gen pre gen”, then I hope MOTU will at least PUBLISH a list of INCOMPATIBLE 3rd party software so none of us get burned or buys software that does not work well with DP. Seems like a lot of cooperation may be needed between companies, and such cooperation is not always simple or easy.
Does anyone else see my point here? DP can have the greatest idea in the word....but if other companies have to adjust to make this great idea work, who’s to say these companies will cooperate and when they will do so? From my laymen software development viewpoint, next gen pre gen requires a lot of synch and cooperation between DAW and plug in. A lot!
For those that say I worry about nothing, well, why are so many users going back to 9.02? Something is complex here. Complex is fine and expected. 3rd party companies altering their software to work better with DP? I’,m not confident of such. Let’s hope MOTU can fix this on their end without need for 3rd party updates.

toodamnhip wrote:Thsfar, only one company I know of has gone out of it’s way for MOTU, that being Vienna, who made a special edition for MAS. In the past, many companies made MAS versions, but not anymore as far as I know.

In that scenario, I think Vienna really had a compelling reason to as so many film/TV composers use DP. DP sort of has a BIG footprint in that area.

James Steele wrote:

toodamnhip wrote:Thsfar, only one company I know of has gone out of it’s way for MOTU, that being Vienna, who made a special edition for MAS. In the past, many companies made MAS versions, but not anymore as far as I know.

In that scenario, I think Vienna really had a compelling reason to as so many film/TV composers use DP. DP sort of has a BIG footprint in that area.

I was very impressed with Vienna for doing this, and I let them all know my appreciation through their forums, through which many of their developers can be accessed. I hope other members let Vienna know their MAS version was appreciated. It is very nice to see all those MIDI channels become available in the MAS versions. Latency comp was also fixed for awhile, but now seems broken again in the latest versions of DP. They are looking into it but as of now, I have to run VE’s buffers at “none”=0 again to keep parts, especially drums, from being late. I guess, by now, it should be understood that we are in a rotating scenario where one thing or another will always be broken, fixed, broken, fixed. It would be nice to “park” at one version where everything works perfectly. But this is tough to do, as time moves forward and users can only stay back so long. I just updated the Play engine and was told by tech support, after the fact, that the latest update no longer supports my “free" string library they gave out years ago. So I have to either buy the silver orchestra or have a broken “free” VI. There was zero warning in the updates page.
And so it goes....
I am actually starting to rethink my work strategy as, up to now, I have left all VIS ON throughout the months, until “finished”, at which point, I bounce to audio. But this is starting to feel like a house of cards where any one developer can screw up a song. I hate committing to audio until absolutely 100% finished with production work. But this may very well be a strategy that is NOT supported by the realty of todays’ software.
For example, last month, I lost my drums when there was a bug with EZ drummer and VE Pro. EZ drummer changed it’s naming protocol, VE Pro didn’t recognize it..poof, no drums. I had to get special instruction to go back to earlier EZ drummer versions and it was a real pain and gave me a few grey hairs.
I will recommend this to all viewers of this thread- SAVE your VIs and Plugs as presets!!!!!
That way, if something goes screwy, you can re load the preset.
Seems like lately, there’s a variety of 3rd party manufacturers breaking things...err..”improving” things....

toodamnhip wrote:...I hope I am wrong here and I hope that all software adjustments can be made on MOTU’s end...

My gut tells me that MOTU is working on it. I think that the .12 update shortly after 9.1's release was to address pressing issues that could quickly be fixed and the pre-gen bugs are probably now the priority. Of course this is pure speculation on my part and you should pay absolutely no attention to my mindless babbling, but I'm hoping my optimism gives others comfort.

toodamnhip wrote: I hope other members let Vienna know their MAS version was appreciated.

I for one sure did, and will continue to do so. It is so stinking elegant!

Phil O wrote:

toodamnhip wrote:...I hope I am wrong here and I hope that all software adjustments can be made on MOTU’s end...

My gut tells me that MOTU is working on it. I think that the .12 update shortly after 9.1's release was to address pressing issues that could quickly be fixed and the pre-gen bugs are probably now the priority. Of course this is pure speculation on my part and you should pay absolutely no attention to my mindless babbling, but I'm hoping my optimism gives others comfort.

This is definitely the case, and MOTU has said so publicly elsewhere. (wish I could find the thread, but it's there on Gearslutz somewhere).