Saajan Ki Baahon Mein
Saajan Ki Baahon Mein is a 1995 Indian Bollywood film directed by Jay Prakash and produced by Dinesh B. Patel. It stars Rishi Kapoor, Sumeet Saigal, Raveena Tandon and Tabu in pivotal roles.
| Saajan Ki Baahon Mein | |
|---|---|
| Directed by | Jay Prakash |
| Produced by | Dinesh B. Patel |
| Screenplay by | Sachin Bhowmick |
| Story by | Jay Prakash |
| Starring | Rishi Kapoor Sumeet Saigal Raveena Tandon Tabu |
| Music by | Nadeem-Shravan |
| Cinematography | Kabir Lal |
| Edited by | Jawahar Razdan |
Release date |
|
| Country | India |
| Language | Hindi |
Cast
- Rishi Kapoor... Sagar
- Sumeet Saigal... Rakesh Singh
- Raveena Tandon... Sapna Narang
- Tabu... Kavita
- Prem Chopra... Pyarelal
- Deven Verma... Dr. Rastogi
- Laxmikant Berde... Anand
- Pran... Mr. Narang (Sapna's Father)
- Saeed Jaffrey... Ranvir Singh
Soundtrack
| # | Title | Singer(s) |
|---|---|---|
| 1 | "Koi Kya Pehchane" | Kumar Sanu |
| 2 | "Kitna Sukun Kitna Aaram" | Kumar Sanu |
| 3 | "Pilaya Hai" | Kumar Sanu |
| 4 | "Aap Ke Karieb Hum Rehte" | Kumar Sanu, Sadhana Sargam |
| 5 | "Purab Se Chali" | Kumar Sanu, Asha Bhosle |
| 6 | "Saachi Kaho Hum Se" | Kumar Sanu, Sadhana Sargam |
gollark: XTMF was not really designed for this use case, so it'll be quite hacky. What you can do is leave a space at the start of the tape of a fixed size, and stick the metadata at the start of that fixed-size region; the main problem is that start/end locations are relative to the end of the metadata, not the start of the tape, so you'll have to recalculate the offsets each time the metadata changes size. Unfortunately, I just realized now that the size of the metadata can be affected by what the offset is.
gollark: The advantage of XTMF is that your tapes would be playable by any compliant program for playback, and your thing would be able to read tapes from another program.
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.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.