![]() ![]() They promised and delivered the next version which fixed the issue, but they said it meant they had to go through the entire program and basically rewrite the entire application to fix the "one track" issue. ![]() I was part of a discussion with Pro Tools (not yet an Avid company) and we asked them about it and they said bascially it was part of the very first version written by one person on his own (the inventor of Pro Tools as it were) and it was completely integrated in every version since. ![]() If you moved a clip from one track to another and wiped out some edits you could not undo it, but it if it was on the same track you could. I remember (eons ago) Pro Tools could only undo on the same track. But that's unrealistic, technology progresses, new video formats show up, new titles must be made! etc. But don't get me wrong –– I often fantasize about Avid just stopping all progress and ONLY fixing bugs. Are you going to go the city and ask for a variance to relocate Bambi's drinking spring!!!? So you walk up the hill to see if the water can be stopped somewhere else and you find a nature preserve with a pring where Bambi hyrdates whilst reminiscing about his murdered mother. So a french drain maybe? But that will cost a lot of money and will have to go through the oak tree you love and part of the retaining wall holding back potential mudslides. I then get a window when I reopen chrome to restore tabs. Why is the patio tilted, because water coming down the hill is getting under it. Google Chrome crashes every day since I received my new MacBook Air with M1 Chip Hi, Is anyone experiencing Google Chrome crashing on their new 2020 mac book air with m1 chip I would be in the middle of working and the program just shuts down. Well it's coming from the back patio, but the back patio which is slightly tilted. You replace the door and it holds back the water a bit, but then the water creeps in again, so you investigate the source of the water. Like a house with a leaky back door where water gets in, let's say. I can only assume the issues are baked deep in the code so it is not as simple as you might think to fix. Again let me know if Avid is being ignored by Apple and I will write and call. I am used to a high level of stability with Avid that is missing in my new Mac studio set up. Is Apple not playing nice with Avid ? Let me know and I will send lettters to and call Apple. I managed to get through theshow I am on but am a little scared to instal the update from 2022.4. Why do they still exist ? What do I know. Also some of the error messages I get seem to date back 15-20 years in these forums. a couple times a week and this temporarily speeds things up. Lag can be up to 2 -3 seconds.I trash MC stae etc. Overall slugish functionalty when working in timeline ie waiting on simple stuff like go to next edit. Also as noted in other posts Titler + causing slow jumpy playback and crashing other Avids in teams when sharing around sequences. I have started to quit MC when using other apps or taking a break. When you come back to Media Composer say 5 minutes or so later MC crashes. If you hide or leave Media Composer to say use another app. Absolutely same behaviour on my new Mac Studio as well. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |