Tag Archives: miscommunication

Madhuri Dixit’s Canada show organisers clarify delay caused by miscommunication from her team: “This delay was entirely beyond the control of True Sound Live Ltd”

A day after Madhuri Dixit faced backlash for allegedly arriving three hours late to a live event in Canada, the organisers of the show, True Sound Live Ltd., issued a statement clarifying the reason behind the delay.

The event, titled *Madhuri Dixit: The Golden Girl of Bollywood*, took place on November 2 at Toronto’s Great Canadian Casino Resort.

**Madhuri Dixit’s Canada Show Organisers Clarify Delay Caused by Miscommunication from Her Team**
According to the organisers, the delay was caused due to miscommunication from the actress’s own management team. The company stated that Madhuri was “misinformed” about her call time, leading to confusion and frustration among attendees who had been waiting for her performance.

The clarification came after social media users criticised both the organisers and Madhuri for the delay and lack of transparency about the event format.

Labeling the controversy as “misleading social media commentary,” the organisers issued the following statement:

> “We at True Sound Live Ltd. would like to clarify the facts regarding the recent *Madhuri Dixit: The Golden Girl of Bollywood* show held in Toronto, following misleading social media commentary. The event commenced on time with a high-energy opening act featuring exceptional singers from Indian Idol, exactly as scheduled.”

They further explained:

> “The show’s format, as communicated to Madhuri Dixit’s management, included a Q&A session at 8:30 PM followed by Madhuri’s 60-minute performance segment. However, despite our production team’s readiness and continuous communication throughout the evening, Madhuri Dixit’s own management team misinformed her about the call time, resulting in her late arrival around 10 PM. This delay was entirely beyond the control of True Sound Live Ltd.”

The organisers also blamed “certain backstage individuals” for creating further confusion during the event.

> “We also want to clarify that certain backstage individuals, including Shreya Gupta, were preoccupied with personal video recordings instead of supporting the artist’s timely coordination, which further added to the confusion. Attached videos clearly show Madhuri Dixit’s on-stage presence and performance, and we invite the public to view the footage and judge objectively,” the statement added.

A video shared by a user named Parwaiz Dhanani showed Madhuri dancing to her popular number *Mera Piya Ghar Aaya* from the 1995 film *Yaraana*.

However, criticism continued online as several attendees accused the organisers of poor communication.

One person wrote:

> “Everyone please report the organizers to Consumer Protection Ontario. I just got off the phone, and this falls under ‘Misrepresentation.’ It’s illegal for a business or individual to give you false information about themselves or the product or service they offer.”

Another attendee expressed disappointment:

> “I am glad I saw her, but I left at 11:05 PM as I had work the next day. I honestly don’t know if it was the organizers or her who decided she would come at 10 PM. On my ticket, it said the start time was 7:30 PM. It did not mention any pre-shows. I expected it to be a chat with some singing and dancing. It just started way too late and disrespected the audience’s time.”

**Also Read:**
*Truth behind Tezaab: How Boney Kapoor and N. Chandra built the Anil Kapoor-Madhuri Dixit classic*

*BOLLYWOOD NEWS LIVE UPDATES*
https://www.bollywoodhungama.com/news/bollywood/madhuri-dixits-canada-show-organisers-clarify-delay-caused-miscommunication-team-delay-entirely-beyond-control-true-sound-live-ltd/

AMD Promises Continued Driver Support For RDNA 1 “RX 5000” & RDNA 2 “RX 6000” GPUs

**AMD Confirms Continued Driver Support for RDNA 1 & RDNA 2 Radeon GPUs**

AMD has addressed recent concerns regarding driver support for its older Radeon GPUs based on the RDNA 1 and RDNA 2 architectures. In a new statement, the company has clarified that Radeon RX 5000 and RX 6000 series cards will continue to receive driver updates, including new game support, optimizations, and security fixes.

### Background: Confusion Around Adrenalin 25.10.2 Driver Release

The release of the AMD Adrenalin 25.10.2 driver update sparked confusion among Radeon users. The update changelog noted that RDNA 1 and RDNA 2 GPUs would be moved to a separate driver branch and labeled as entering “Maintenance Mode.” Additional changes included the temporary removal of USB-C power charging support on the RX 7900 series (which was later reverted) and an increase in the overall driver package size to over 1 GB.

The primary concern, however, was the uncertainty around future driver support for older GPUs. Initial AMD statements hinted that game support for these older GPUs would continue “as per market needs,” but the vague wording failed to clarify exactly what that entailed.

### AMD’s Clarification: Continued Support with Dedicated Driver Branches

Today, AMD has provided a clear explanation on Radeon GPU driver support moving forward. According to the company, RDNA 1 (RX 5000 series) and RDNA 2 (RX 6000 series) GPUs will continue to receive:

– Support for the latest game releases
– Stability and game optimizations
– Security patches and bug fixes

These updates will arrive similarly to those provided for their latest RDNA 3 (RX 7000 series) and upcoming RDNA 4 (RX 9000 series) GPUs.

The key difference is that older GPUs will benefit from a dedicated, stable driver branch. This branch is built on years of tuning and optimizations, ensuring stability and consistent performance for current and future games. Meanwhile, newer GPUs on the RDNA 3 and RDNA 4 architectures will receive drivers that can integrate new features faster through a separate development path.

### What This Means for Radeon Users

AMD summarized the situation as follows:

> “This is not the end of support for RDNA 1 and RDNA 2. Your Radeon RX 5000 and RX 6000 series GPUs will continue to receive game support for new releases, stability and game optimizations, as well as security and bug fixes.
>
> The difference is that these products now benefit from a dedicated, stable driver branch, one built on years of tuning and optimization. This approach helps deliver a smoother, more consistent experience for your games while insulating previous generation GPUs from rapid changes designed for newer architectures.”

### Why AMD Is Taking This Approach

AMD explained the rationale behind splitting the driver codebase:

> “Our goal is simple: to give every Radeon gamer the best experience possible. By separating the code paths, our engineers can move faster with new features for RDNA 3 and RDNA 4, while keeping RDNA 1 and RDNA 2 stable and optimized for current and future games.”

### AMD’s Commitment to Radeon Gamers

The company reinforced its commitment to supporting all Radeon users:

> “We’ve supported Radeon gamers for generations and that commitment isn’t changing. Whether you’re gaming on an RX 5000, RX 6000, or the latest RX 9000, you’ll continue to get the reliability, performance, and care you expect from AMD. Because we’re all part of the same gaming community and every Radeon gamer matters.”

### Looking Ahead

It will be interesting to monitor how AMD delivers on this promise in upcoming driver releases. Currently, the Adrenalin 25.10.2 driver stands as the latest update available for RDNA series GPUs.

For Radeon users, this clarification should bring reassurance that their older GPUs will continue to receive essential support while allowing AMD to innovate rapidly on its newest architectures.
https://wccftech.com/amd-promises-continued-driver-support-for-rdna-1-rx-5000-rdna-2-rx-6000-gpus/

Liam Lawson under fire after latest claim by Mexico’s motorsport authority

**Visa Cash App RB Driver Liam Lawson Has Close Call with Marshals at 2025 Mexico City GP**

Liam Lawson, the Visa Cash App Red Bull driver, experienced a frightening near-miss with track marshals shortly after exiting the pit lane during the 2025 Mexico City Grand Prix at the Autódromo Hermanos Rodríguez.

The race started with fierce action as Lawson had a strong launch off the line and was battling Carlos Sainz into Turn 1. However, the Spaniard failed to leave sufficient space and collided with Lawson’s car, causing significant damage to the Kiwi driver’s vehicle. This forced Lawson to pit for repairs early in the race.

The collision between Sainz and Lawson, combined with other incidents in Turn 1, left considerable debris scattered across the Turn 1, 2, and 3 section of the circuit. Consequently, the FIA stewards deployed double-waved yellow flags in this area to ensure the marshals could safely clear the track.

Despite these safety measures, a tense situation unfolded when Lawson rejoined the track at the end of Lap 2. As he approached Turn 1, he encountered several marshals still on track collecting debris. The Kiwi driver narrowly avoided a serious incident, but the close call led to an angry radio message from Lawson expressing his frustration about marshals being on the racing line.

Following the incident, Mexico’s motorsport federation OMDAI Sport Mexico issued a public statement sharply criticizing Lawson. The release stated:
“The images clearly show that driver Liam Lawson maintains the steering wheel angle of his car when taking Turn 1, without changing his trajectory, even though the track marshals were crossing the track to return to their post. This action occurs while personnel were still working in the area, which shows that the driver did not interrupt his line despite the obvious presence of marshals on the track.”

The FIA also commented publicly after the race, noting that the instructions to dispatch marshals had been rescinded once Lawson pitted. They confirmed that an investigation into the incident is still ongoing.

**Liam Lawson Speaks Out About the Incident**

After the race, Lawson spoke to the media about the dangerous situation, calling it unacceptable. During the race, he had already voiced his concerns over team radio, pointing out the severe risk of injury.

“I honestly couldn’t believe what I was seeing. I got to Turn 1 and there were two dudes just running across the track. And I nearly hit one of them. Honestly, it was so dangerous. Obviously, there’s been a miscommunication somewhere, but I’ve never experienced that before, I’ve only seen that in the past. It’s pretty unacceptable,” said Lawson.

Unfortunately, the damage sustained in the Lap 1 collision ultimately forced Lawson to retire from the race.

This incident has raised serious questions about track safety protocols and communication between race control and marshals during high-intensity moments on the circuit. The ongoing FIA investigation will likely provide further clarity on how such a dangerous situation unfolded and how it can be prevented in future events.
https://www.sportskeeda.com/f1/news-liam-lawson-fire-latest-claim-mexico-s-motorsport-authority