Vivek Prasanna

Vivek Prasanna is an Indian actor who appears in Tamil language films, mostly in supporting roles.[1] In 2017, he won the Vijay Award for Best Supporting Actor for his performance in the film Meyaadha Maan. His brother Karthik Netha is working as a lyricist.

Vivek Prasanna
Born (1986-09-22) 22 September 1986
Salem, Tamil Nadu, India
OccupationActor
Years active2016 – present
RelativesKarthik Netha (brother)

Career

After several appearances in short and telefilms, he made his acting debut alongside Vijay Sethupathi in Arun Kumar's police drama Sethupathi (2016). A critic from Indiaglitz.com noted that Vivek Prasanna as "the main henchman fits the role to the T".[2]

In 2017, Vivek Prasanna made a breakthrough and appeared in supporting roles in a series of successful Tamil films. His role as the drug lord Ravi in Vikram Vedha and as a politician in Peechankai, also won Vivek acclaim.[3][4][5] He then appeared as the second lead in the romantic comedy, Meyaadha Maan, winning rave reviews for his portrayal of the character of Vinoth.[6][7] First He denied the role of Vinoth in Meeyaadha Maan Movie, But Director (Rathana Kumar) Convinced him to do that role. He Trused Vivek Prasanna can be noted on his role on Meeyaadha Maan Film for his acting.[8]

Filmography

YearFilmRoleNotes
2015Bench Talkies - The First BenchVinoth
2016SethupathiMadhivaanan
IraiviDirector
2017MaanagaramSundeep's friend
PeechankaiNallathambi
Vikram VedhaRavi
Podhuvaga Emmanasu ThangamMurugesan
Meyaadha MaanVinoth
VelaikkaranBabu
2018Irumbu ThiraiLoan collection agent
Maniyaar KudumbamNarthanga Saamy's nephew
2019PettaCollege professor
Charlie Chaplin 2Dubai Raja
Nenjamundu Nermaiyundu Odu RajaLocal goon
SindhubaadhPassenger
GorillaVenkat
AadaiGowri
2020Soorarai Pottru
gollark: Tape Shuffler would be okay with it, Tape Jockey doesn't have the same old-format parsing fallbacks and its JSON handling likely won't like trailing nuls, no idea what tako's program thinks.
gollark: Although I think some parsers might *technically* be okay with you reserving 8190 bytes for metadata but then ending it with a null byte early, and handle the offsets accordingly, I would not rely on it.
gollark: Probably. The main issue I can see is that you would have to rewrite the entire metadata block on changes, because start/end in XTMF are offsets from the metadata region's end.
gollark: I thought about that, but:- strings in a binary format will be about the same length- integers will have some space saving, but I don't think it's very significant- it would, in a custom one, be harder to represent complex objects and stuff, which some extensions may be use- you could get some savings by removing strings like "title" which XTMF repeats a lot, but at the cost of it no longer being self-describing, making extensions harder and making debugging more annoying- I am not convinced that metadata size is a significant issue
gollark: I mean, "XTMF with CBOR/msgpack and compression" was being considered as a hypothetical "XTMF2", but I'd definitely want something, well, self-describing.

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.