-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Midi import: Tempo from MIDI file is overwritten by default tempo II #230
Comments
can you attach the MIDI file and the exact steps to reproduce the issue? |
My test-file to see things are up and performing well: It has to be renamed back to *.mid |
The exact steps are:
The initial tempo should be 59 bpm |
thanks i could reproduce your findings and found some more: it all seems to work as it should iif you drop the file anywhere but the very first bar or measure of the timeline (bar > 1) whatever current or default tempo is ; iow. the first tempo change in the MIDI file seems to be ignored and overriden by the current default tempo iif the file is dropped to start within the very first bar or measure (1 < bar < 2) which includes the absolute beginning (time = 0) of course. will look into it and try to fix this idiosyncriticality (just made up the term;)) |
a standard MIDI file (as reported on issue #230).
maybe fixed on cb72c22 . |
Tested:
-> Idiosyncriticality is gone or does not cause trouble any more :) Thanks for fast (as usual) solution |
More details at [1] [1] rncbc/qtractor#230 (comment) Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Hi
When importing a MIDI file, the (initial) tempo at tick 0 is ignored.
Interesting: Did set a breakpoint on qtractorMidiFileTempo::addNodeTempo to analyse. My file is setting tempo at tick 0 and changes tempo at later ticks. Later ticks do change tempo properly but first one is ignored: When I play the file to first tempo change, stop and go backward to start tempo is set wrongly to default tempo (120 on fresh system).
Tests were done on latest master
The text was updated successfully, but these errors were encountered: