(here I have manually change two "58" to "455".) (BTW, I would expect that there is some way to have iRed to generate that file.)
This can be imported in IrScrutinizer (Import -> IrTrans). Then, I probably made a mistake with Import (it tries to identify as Dish_Network, which appears wrong)), instead select "Import/raw". Then export the raw signals (Export -> Export raw remote), and you have

Barf,
Since the codes appear to have no lead out, I think it is necessary to specify that only one frame should be transmitted. Your hex codes may send multiple frames. Also, the IRTrans documentation says that while timing values are specified in microseconds, the resolution is only 8us. So I chose to average the 24, 32, and 32 us intervals. I doubt that this would matter.

foufouner,
Barfs hex codes have the frequency set to 460KHz, which is as close as Pronto hex can get to 455KHz. I'm not sure how you're coming up with 243KHz. Anyway, as I said to Barf just above, it may be worth trying Barf's codes with the 4 starting numbers changed from 0000 0009 0000 0015 to 0000 0009 0015 0000.

foufouner,
Barfs hex codes have the frequency set to 460KHz, which is as close as Pronto hex can get to 455KHz. I'm not sure how you're coming up with 243KHz. Anyway, as I said to Barf just above, it may be worth trying Barf's codes with the 4 starting numbers changed from 0000 0009 0000 0015 to 0000 0009 0015 0000.

(here I have manually change two "58" to "455".) (BTW, I would expect that there is some way to have iRed to generate that file.)
This can be imported in IrScrutinizer (Import -> IrTrans). Then, I probably made a mistake with Import (it tries to identify as Dish_Network, which appears wrong)), instead select "Import/raw". Then export the raw signals (Export -> Export raw remote), and you have