Did you get a chance to look at DFH 2.0 ?twistedtom wrote: bjornln I just got EZD and love it.
/B
Moderator: James Steele
Did you get a chance to look at DFH 2.0 ?twistedtom wrote: bjornln I just got EZD and love it.
I'll be going from 4.61 to 6 soo I missed 5...Phil Jeffers wrote:I don't agree - the DP 5 manual skims over a lot of sections that I think it could pay far more attention to... and the Help drop down is somewhat of a joke.DP has some of the best documentation.
This is just an opinion! Please don't crucify me for saying anything bad about Digital Performer!!!!
I'm sure the upgrade cost will be the same... (at least here in Oz)Talcott wrote:I'll be going from 4.61 to 6 soo I missed 5...Phil Jeffers wrote:I don't agree - the DP 5 manual skims over a lot of sections that I think it could pay far more attention to... and the Help drop down is somewhat of a joke.DP has some of the best documentation.
This is just an opinion! Please don't crucify me for saying anything bad about Digital Performer!!!!
LOL! What key stirs up the biggest mob mentality???Shooshie wrote:I've got the pitchforks, guys; you get the lanterns and ropes! AFTER HIM!Phil Jeffers wrote:I don't agree - the DP 5 manual skims over a lot of sections that I think it could pay far more attention to... and the Help drop down is somewhat of a joke.DP has some of the best documentation.
This is just an opinion! Please don't crucify me for saying anything bad about Digital Performer!!!!
Shooshie
PS: which pitchforks does an angry music mob use, anyway? I've got "A's" and "Bb's". Will those do?
paulhurt wrote:Maybe someone has already picked up on this••¦Plug-in management.
I doubt these have changed. I think command-arrows are pretty sensible already, no?paulhurt wrote:Hope they've chosen sensible keyboard modifiers for zoom in/out••¦
Yes, me too. You don't want to open up a project which uses a disabled plugin, have to reactiveate it, and then quit and relaunch DP in order to use it again within that project. I would assume that it will NOT work like this... which does suggest some significant code rewriting, because it means that DP is no longer going to launch the plugins BEFORE a project is selected, but will wait, instead, and load them with a project.blue wrote:I hope it works on a project level, rather than globally.
I hear you Paul, I love DP and look forward to 6, but man could I navigate fast in Vision. My choice of Digital Performer was because it was the most Vision-like.paulhurt wrote:
might get my efficiency with DP back up to Opcode Vision levels! Even after six years with DP, I still miss how fast I used to be able to get around Vision.
Thank you MOTU. I'm very excited about DP6.
I wonder about this..frankymax wrote:oh, I forgot a biggie (at least for me)- you will be able to burn a CD directly from DP without having to use another app; and it will create tracks based on markers or soundbites- very nice!
The markers are the track indexes and the name of the markers/tracks get embedded as track names in the CD text feature on the audio CD.toodamnhip wrote:I wonder about this..frankymax wrote:oh, I forgot a biggie (at least for me)- you will be able to burn a CD directly from DP without having to use another app; and it will create tracks based on markers or soundbites- very nice!
Does anyone know if you will be able to differentiate between markers for personal file use and markers that get written to the cd ?
I see a need for both.
I will need to make both markers for IN SESSION usage and markers for CD tracks...
They said that it is still being worked out exactly how it will work, but in theory, they were looking at there being a global preference that DP will use to launch the program and look for a certain set of plug-ins every time. This could be to look for everything...or nothing, etc....zed wrote:Yes, me too. You don't want to open up a project which uses a disabled plugin, have to reactivate it, and then quit and relaunch DP in order to use it again within that project. I would assume that it will NOT work like this... which does suggest some significant code rewriting, because it means that DP is no longer going to launch the plugins BEFORE a project is selected, but will wait, instead, and load them with a project.blue wrote:I hope it works on a project level, rather than globally.
It would be easier to have two kinds of markers, one that shows in a cd, one that doesnt, or, be able to ear mark which of one's markers get embedded in the cdbralston wrote:The markers are the track indexes and the name of the markers/tracks get embedded as track names in the CD text feature on the audio CD.toodamnhip wrote:I wonder about this..frankymax wrote:oh, I forgot a biggie (at least for me)- you will be able to burn a CD directly from DP without having to use another app; and it will create tracks based on markers or soundbites- very nice!
Does anyone know if you will be able to differentiate between markers for personal file use and markers that get written to the cd ?
I see a need for both.
I will need to make both markers for IN SESSION usage and markers for CD tracks...
just open a new sequence, copy all the audio files onto one stereo track in order...with the proper space between them and burn/bounce that to CD.
It is really a feature to use DP as a mastering tool in separate mastering sequences.
If DP did indeed re write basic code for more efficiency, lets hope no 3rd party stuff breaks as did waves...blue wrote:Some of the new features seem to address CPU consumption, at least for some users. If VI pre-rendering works as advertised, I would be a happy camper. That, in conjunction with effect pre-rendering, could make DP pretty light on its heels.bradswan wrote:••¦now I'm wondering how much CPU it's gonna take to power all these new features.
Also, I have to wonder if the redesigned interface is a sign that MOTU has undergone a code overhaul. I haven't seen it yet ••“ the changes could be superficial ••“ but it sounds unlikely they could redo the GUI without getting their hands seriously dirty.
Then there is support for native formats other than SD2, non-realtime VI bouncing and AU side-chaining. All this leads me to believe MAS has undergone some serious surgery.