Mercurial > hg > match-vamp
comparison src/MatchFeatureFeeder.cpp @ 191:f415747b151b re-minimise
Normalised path costs should use a different type from un-normalised ones (because they are in a different range)
author | Chris Cannam |
---|---|
date | Thu, 26 Feb 2015 15:52:16 +0000 |
parents | 24ddab06aace |
children | f6be68852c1d |
comparison
equal
deleted
inserted
replaced
190:48f9c50587dc | 191:f415747b151b |
---|---|
56 { | 56 { |
57 if (m_pm1->getFrameCount() == 0 || m_pm2->getFrameCount() == 0) { | 57 if (m_pm1->getFrameCount() == 0 || m_pm2->getFrameCount() == 0) { |
58 return 0; | 58 return 0; |
59 } | 59 } |
60 int bestRow = 0; | 60 int bestRow = 0; |
61 pathcost_t bestCost = 0; | 61 normpathcost_t bestCost = 0; |
62 if (!m_finder.getBestColCost(m_pm2->getFrameCount()-1, bestRow, bestCost)) { | 62 if (!m_finder.getBestColCost(m_pm2->getFrameCount()-1, bestRow, bestCost)) { |
63 return -1; | 63 return -1; |
64 } else { | 64 } else { |
65 return bestRow; | 65 return bestRow; |
66 } | 66 } |