groakat / AudioTagger

5 stars 2 forks source link

Frequency axes bug #81

Open tristankleyn opened 7 years ago

tristankleyn commented 7 years ago

Frequency (kHz) axes need fixing. Some recordings are showing pipistrell calls at 300 kHz, others at 450 kHz, etc. Scales of spectrograms are different and messed up for each recording.

macaodha commented 7 years ago

Are the recordings you are using time expanded? If so you need to set the playback speed appropriately (e.g. to 0.1 if time expanded by 10).

tristankleyn commented 7 years ago

Hmm it's possible it was time expanded. I will try that next time I'm in. Thanks.

macaodha commented 7 years ago

If it doesn't work, post a link to an audio file that's causing the problem and I can take a look.

Good luck

tristankleyn commented 7 years ago

Yes it was that! Thanks

macaodha commented 7 years ago

Great. Will add a note in the documentation about this.

On 26 Oct 2016 02:29, "tristankleyn" notifications@github.com wrote:

Yes it was that! Thanks

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/groakat/AudioTagger/issues/81#issuecomment-256295924, or mute the thread https://github.com/notifications/unsubscribe-auth/AGWhq7Yw9K2I5S7i7AeY3yesMIA0fRrLks5q3x2CgaJpZM4Kf0Lj .

groakat commented 7 years ago

Thanks Oisin, for taking care of this. If I can do anything, let me know.

On 25 Oct 2016, at 17:30, Oisin Mac Aodha notifications@github.com wrote:

If it doesn't work, post a link to an audio file that's causing the problem and I can take a look.

Good luck

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/groakat/AudioTagger/issues/81#issuecomment-256087274, or mute the thread https://github.com/notifications/unsubscribe-auth/ADQuNsLZ03qBiti4tcVd5T_NW3YAj_KUks5q3i6JgaJpZM4Kf0Lj.

ali-fairbrass commented 7 years ago

Hi Oisin,

They are not time expanded recordings. Just ultrasonic wav files from an SM2 detector.

On Tuesday, 25 October 2016, Oisin Mac Aodha notifications@github.com wrote:

If it doesn't work, post a link to an audio file that's causing the problem and I can take a look.

Good luck

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/groakat/AudioTagger/issues/81#issuecomment-256087274, or mute the thread https://github.com/notifications/unsubscribe-auth/AF77aIWpKu3DMf6zIOygWDuvoQGwxxWHks5q3i6JgaJpZM4Kf0Lj .

Alison


Alison Fairbrass Engineering Doctorate University College London Civil, Environmental and Geomatic Engineering +447912616367

Twitter: @AlisonFairbrass

Webpage: https://www.ucl.ac.uk/cber/people/alison-fairbrass

alison.fairbrass.10@ucl.ac.uk alison.fairbrass@gmail.com

macaodha commented 7 years ago

@tristankleyn Have you tried any time expanded files to check if it works for those too.

tristankleyn commented 7 years ago

If you let me know where some time expanded files are I can try them and check.

ali-fairbrass commented 7 years ago

@tristankleyn The attached files are time-expanded for you to test them on audioTagger.

iBatsBulgaria_Batishnitsa_03072009_chop2.zip

macaodha commented 7 years ago

Hey @tristankleyn and @ali-fairbrass, has this issue be solved for you?