![]() ![]() Somebody in the development team should know what happened going to PT9. The D-Command Main Unit features an easily accessible, central control section with straight-forward. Similar to D-Control, ICON D-Command employs an intuitive console layout. I don't know what changed in PT9, but it would be great to have the reaction time of PT7 & 8 again on the D-Control. The ICON D-Command will support mixes up to 24-bit/192 kHz in up to 5.1 surround and directly integrates with industry-standard Pro Tools recording and editing software. I also have posted some time ago about the Control24 being slower to respond with PT9 then during the PT7 days. In PT9 and 10 it's slow, so something changed in the D-Control protocol from PT9 onwards. I thought at some point that (since PT8) the ethernet protocol had to deal with 5 extra sends and inserts and thus became slower to communicate everything to the channels.īut to my surprise the same session was instant in globally switching to EQ in PT7 AND PT8 (when the extra sends and inserts were introduced). ![]() It reminds me of configuring a Neve DFC as it builds the channel's DSP. I was very curious to quickly test this, because I hoped that PT10 made the D-Control quicker again as it used to be in PT7.įrom PT9 onwards (and I wasn't sure anymore if it was the same under PT8) the D-Control takes more time to change the channels globally from sends to EQ: if you globally switch to EQ, the channels will switch from left to right (depending on configuration of fader units) and take about 2 seconds to switch 32 channels. Ive gotten it from my supplier of esp modules. What DID change with the PT10 D-Control firmware: the EQ LED on all channels remains lit at all times (even selecting insert, send.) This made me wonder something was wrong in my first observation. It all seemed to work (I did not mix or make it work hard however). Now I have PT10 firmware in the D-Control and I have started a quick test session with about 35 tracks with EQ7 on PT10.0, 9.0.3, 8.0.4cs2 and 7.4.2cs2 without changing firmware. I did some further experiments and came to the conclusion that probably D-Control with firmware from PT9 was not happily working together with PT10. ![]() (We always had to do this with various demo systems, etc). Also - in my experience, usually you can ignore doing the firmware upgrade when switching cpu's and versions with no real problem. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |