This ensures you edit in CD frame timing. ![]() Remember to edit (cut) in Logic Pro with divisions (Snap: Division) and with a tempo of 281,25 BPM 44.1 kHz. Not because it's "crap" to use per se, but because it can cause problems such as clicks and (at one time at least) 15 bit audio.ĭo you really want to risk these kinds of errors with a project you've likely spent many hours on? Get yourself Sonoris DDP Creator and do the editing in Logic Pro.ĭSP-Quattro is not very intuitive and has some bugs as well, I agree.ĭDP Creator is a breeze, but you need to do the editing in Logic Pro first, then export files to DDP Creator. I'm merging previous comments into this thread for clarity.I really can't recommend using WaveBurner. Let's discuss the new DDP plug-in and potential consequent features :) Unfortunately there seams to be no free DDP import tool. ![]() However, I used 30-day trial version of Sonoris DDP Creator to test the files.Ĭurrently there is no import, maybe it will be somewhere in the future. The DDP export is a brilliant new feature. However, it's unnecessarily complex for the user imo. Is it possible to have a "DDP edit/setup" window that allows the user to actually set up the DDP markers etc. Ī list-view like the Sonoris, that when edited would shift the audio on a given track around and create the necessary markers for us would be very very useful :) I don't know how complex it would be to create it, but if DDP output is already available, it doesn't seem to me that it would be very difficult to package up the guts of it into a better interface than creating lots of markers with specific names that are easy to screw up. It is a little harder to make edit screen without interference with the default marker usage. For some, creating markers is easier and more intuitive, as this is in the time domain, others prefer the list. However, a feature could be at least to display the (readonly) list of tracks with INDEX positions and meta data. But if the list is editable, it can make the conflict with the markers, if the markers are moved after the track list is edited. Yes, to fully use the markers, it can be a little complex. ![]() But if you don't need INDEX0, ISRC, EAN, you can just use # markers, as for CUE/BIN export. Would it really be difficult to have an editable list that was itself updated by the manual moving of markers? They would both update each other - maybe I'm not understanding the issue with this?Īlso very useful (arguably essential) would be RedBook compliance checking of the DDP set that would result from the current marker set. and burning straight to CD from the DDP render window as well. ![]() What about sws including it in their marker window (that's unless the new region window in reaper gets some love) ) Maybe a dedicated DDP discussion thread is a good idea? I'm asking a lot, I know, but such a feature begs for additional functionality in order to be reliable and useful for the majority of users. To make the both-way editable list markers, it would need a little more integration into the REAPER, and more programming time :) Redbook compliance is ensured by automatically correcting the tracks to conform the specification. Possible, yes, but now only theoretically. It is not recommended, that some export plugin is changing the markers. The export plugin should only change the output file, but leave the session intact. What I see as an option, is editable list, which is always filled automatically by reading the markers.
0 Comments
Leave a Reply. |