![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#111
|
|||
|
|||
![]()
The question is - was this change a deliberate act ? or something went wrong ?
If it was a deliberate act, then simply put it back to how it was - there's nothing to compute. Nobody likes this change. |
#112
|
||||
|
||||
![]()
Yes x 1,000. This should be the easiest bug fix ever. Just give it to us as 2024.10.3. AVID?
__________________
Desktop build: Pro Tools Studio 2024.6 / Win 11 / i9-11900K @ 5.1GHz / 64GB / 4TB NVMe PCIe 4 / Gigabyte Z590 Vision D / PreSonus 2626 Laptop: Pro Tools Studio 2024.6 / Win 11 / i5-12500H / 16GB / 1TB NVMe / Lenovo IdeaPad 5i Pro / U-PHORIA UMC1820 Ancient/Legacy (still works!): Pro Tools 5 & 6 / OS9 & OSX / Mac G4 / DIGI 001 Click for audio/video demo Click for resume |
#113
|
|||
|
|||
![]() Quote:
__________________
~Will |
#114
|
||||
|
||||
![]() Quote:
Wish we could get a 2024.3 out but as Tope said in an earlier post in this thread: Fix is expected to be part of the next major release this year. We expect it to be out by mid year. no exact dates on this but it will be out soon :) So bug # PT-334697 has been squashed. You just have to wait a bit. Marianna
__________________
Marianna Montague Sr. Dir. CX and Community | Customer Advocate [email protected] cell +1 (813) 493-6800 AOL IM avidmarianna Twitter Avidmarianna We're Avid. Learn more at www.avid.com |
#115
|
|||
|
|||
![]()
So essentially, everyone's going to have to pay $500 for a "bug fix" on a "feature" that should never have been introduced in the first place. Common sense would tell any Pro Tools user that this playlist change was absolutely ridiculous, and a workflow killer.
This "operational change/feature/bug" tactic could be used ad infinitum to get users to cough up another $500 every time there's a lull in the renewals statistic. Customers should not be forced into paying for something that was deliberately broken. We should be paying willingly for fantastic new features that everyone is excited to start using - such as a "Drum Edit Window" . . . you know, like Cubase had back in the 80's on an Atari computer. |
#116
|
|||
|
|||
![]()
Avid should really give Perpetual License users the 2025.6 update for free then, as people would have to pay just to get it fixed.
Otherwise, people would've paid for a year of updates... which they can't use... right?! |
#117
|
||||
|
||||
![]()
Well the way I see it the playlist bug should have never happened. Why was it ok to release 2024.10 that way and move on? Someone made that decision. There's no way that was not caught in the beta trials. What was Avid's goal here? "We've already fallen behind the release schedule, no big deal, we'll fix that later" What's the priority here?
![]()
__________________
Logic Pro 11.1.2 | Studio One 7.1.1 | Pro Tools 2024.10.2 | Dolby Atmos Render 5.3 & Album Assembler 1.4 | UA Apollo Twin X Gen 2 | UA Native Plugins & Sphere LX | UAD Ultimate 13+ Bundle | SSL UC1 | 2023 Mac Studio M2 Max 12 Core CPU 38 Core GPU | MacOs Sequoia 15.4 | Genelec 8020D & Yamaha MSP10 | Korg Kronos LS | Sonarworks Sound ID | Beyerdynamic DT 1990 Pro | DT 880 PRO | DT 770 Pro | etc. |
#118
|
||||
|
||||
![]()
My Perpetual Ultimate Support Plan expires in 6 days.
Not happy!! ![]()
__________________
Retro 176 (pair), Pultec EQP-1A (pair), Germanium Comps (pair), BAE 10DC (pair), Distressor (pair), Manley Vari-Mu, Sta-Level, Zener, SSL Fusion, SSL FX G384, API 2500, LA2A, 1176, Bricasti, Massive Passive, Anamod ATS-1, Eventide H3500, TC 2290, Yamaha D5000, PCM92, PCM70... Amps, Amps & More Amps. |
#119
|
|||
|
|||
![]() Quote:
I wish I could say I was surprised. I love PT but Avid....come on now. You broke it, you fix it. And no matter how scummy Avid acts, I'll still reinstate my Ultimate when I upgrade to an M4 Mac. You'll get my money no matter what. And that's why you do the things you do. Bah.
__________________
MacMini M1 (2020) / macOS 13.7.4 / PTU 2023.12.1 / Avid S1 |
#120
|
||||
|
||||
![]()
This would be a fair solution.
__________________
Desktop build: Pro Tools Studio 2024.6 / Win 11 / i9-11900K @ 5.1GHz / 64GB / 4TB NVMe PCIe 4 / Gigabyte Z590 Vision D / PreSonus 2626 Laptop: Pro Tools Studio 2024.6 / Win 11 / i5-12500H / 16GB / 1TB NVMe / Lenovo IdeaPad 5i Pro / U-PHORIA UMC1820 Ancient/Legacy (still works!): Pro Tools 5 & 6 / OS9 & OSX / Mac G4 / DIGI 001 Click for audio/video demo Click for resume |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
2024.10 Playlist 'Solo' now changed to 'Audition' changing some workflows | diamondschwin | Post - Surround - Video | 19 | 11-19-2024 06:49 PM |
Export Pro Tools "Playlist" tracks as a new session or Split Playlist into new Tracks | AMIEL | Pro Tools 12 | 1 | 12-08-2016 01:48 PM |
Move midi behaviour changed | tamasdragon | Pro Tools 11 | 2 | 08-16-2013 11:56 AM |
A way to create a new playlist when re-recording over playlist section? | jschmidtiii | macOS | 2 | 08-13-2013 02:28 AM |
back & play behaviour changed? (d-control) | tomlowd | Pro Tools 9 | 0 | 01-31-2011 07:58 PM |