![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
![]()
Hello Everyone,
It's late, and this is an incomplete report. 1) It appears that importing tracks now brings along much data that wasn't actually in the tracks of the source session. It's acting like "Save Session Copy" now. I have to manually remove unused files from the new session B after importing tracks from session A. 2) It appears that consolidating those files on import is also broken, it seems that it just copies them regardless of how large you specify the handles to be. 3) It appears that panner linking, even on single stereo tracks, is now weird. Sometimes it works, sometimes it doesn't. Often it will grab the other panner half way through a touch update, and it will snap to the new position. Sometimes, it just follows in a gimpy semi-coherent way, with a sort of offset or something. I'm describing a single stereo track, with the main panner link enabled. 4) Fade bug is still here. Two tracks, one on top of the other. Bottom track muted. Make a cut and move. Do a crossfade. Bottom crossfade (the muted track) now has unmuted. Must now manually mute this. Anybody else seeing these things? HD2 Accel G5 Dual 2.3 6.5 GB RAM 10.4.6 PT 7.2 Thanks, S.
__________________
IMDB |
#2
|
|||
|
|||
![]() Stu, seeing the fade-issue. haven't bumped on the other ones yet (then again, not been counting disc-space on imports, so will check this this morning). Panner not linking for me at all when doing snaps. -cd |
#3
|
|||
|
|||
![]()
With respect to the panner linking, there are now two modes: absolute and relative. These are set by a preference near the top of the mixing prefs.
If it is set relative, then the "snap" thing won't work as before, and it will at times appear to have an offset as that possibility is part of the point of relative panning. If it is set to absolute then it is the same as previously. The pref is: "use absolute pan linking" Please also check out whether there are any key command changes in the manual pertaining to the snap thing.... I know that some things had to change modifiers due to the improvements to automation that use the apple key.
__________________
Jonathan Wales Sonic Magic Studios Culver City CA |
#4
|
|||
|
|||
![]()
__________________
Tim vdB Avid Audio "There's a fine line between stupid and clever." |
#5
|
|||
|
|||
![]()
Hey Stuart,
I am seeing all the bugs you are mentioning... With regards to the fades, I think the idea they had was good, but the implementation is wrong... If you do a crossfade that is ten frames long, essentially you are getting a 10 frame fade out and a 10 trame fade in that are overlapping. But, if you move one of the regions to another track, and your cut was in the middle of the fade, you then get a 5 frame fade out and a 5 frame fade in - no overlapping - so you are 5 frames short on the out and 5 short on the in - that could potentially be a lot of missing info. I have spotted and additional 5-6 bugs in the first few days of operation - but overall it is a good build. I think they need to have more post guys in their beta testing program - we seem to be hitting on all the same topics everytime. TOM
__________________
Thomas C. Brewer |
#6
|
|||
|
|||
![]() Quote:
However, the absolute vs. relative panning mentioned does not however apply to all of the things I observed. Sometimes the automation simply was not playing properly on one pass, and then would on the next. This needs to be examined, I believe. Of course, like many, I upgraded just as quick as I could once the update appeared, and in the middle of an extensive project (luckily I'm the only who ever does things like that) . Thanks again, S.
__________________
IMDB |
#7
|
|||
|
|||
![]()
All I have to say is ... STUART... you should know better then that!!
(We all do - but we all ignore our brain!) T
__________________
Thomas C. Brewer |
#9
|
|||
|
|||
![]()
Just looked at the thread hierarchy. Hey Tom, WHADDUP! Didn't mean to sound dissmissive to your reply.
Hope you're good, man. (I already know you're busy). Talk to you soon, S.
__________________
IMDB |
#10
|
||||
|
||||
![]() Quote:
Regarding #4 - I'm not sure which 'fade bug' you're referring to and the steps you've given don't give me enough info to link it to a known issue. Can you clarify the steps? When you say 'make a cut and move' - are you cutting on one track? Both? Are you seperating the regions or cutting out a section? What are you moving - one track? Both? Where are you putting the fade, exactly? |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Having issues linking Cntrl 24 | tim carter | ICON & C|24 | 2 | 10-16-2012 02:54 PM |
Stereo panner linking | mattyharm | Pro Tools 9 | 2 | 01-25-2012 05:41 AM |
Audio Import Linking Problems | bloozerd | macOS | 2 | 09-09-2011 11:28 AM |
Import Session Data - Fades not Linking - HELP- 7.4.2 + Leopard | left coast | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 12 | 08-24-2008 11:12 PM |
Linking MIDI tracks to Audio Tracks | Mixchump | Pro Tools TDM Systems (Mac) | 0 | 11-10-2003 02:33 PM |