Open GoogleCodeExporter opened 9 years ago
Which LV2 host program are you using?
Did you install amsynth from source code or a binary package?
The MIDI event handling changed in amsynth 1.5.0 to make it sample accurate -
as a result if the sample offsets in the MIDI input stream
(LV2_Atom_Event.time.frames) are wrong, or the events are not sorted in order,
it would cause problems.
Original comment by nixxpep...@gmail.com
on 5 Feb 2015 at 7:04
I wrote my own, but I lifted the atom code from jalv. I'm building amsynth from
source every time.
this is great info, will double check my calculations before concluding that
it's a problem with amsynth
Original comment by fenlonor...@gmail.com
on 5 Feb 2015 at 8:43
Any luck finding the cause of the problem?
If it's a bug with amsynth, please let me know!
Original comment by nickdowell
on 13 Feb 2015 at 7:24
hi! not yet. It would be helpful to know exactly the difference between how
amsynth handles the atom data (how it handles the atom data differently after
1.4.2)...or at least exactly how it is expecting the atoms in order to
calculate the necessary deltas...
Is it it just LV2_Atom_Event.time.frames that's calculated in a different way?
Original comment by peppersc...@gmail.com
on 13 Feb 2015 at 7:39
Please try with the latest amsynth code from git, I have made a change so that
the order of midi events passed in should no longer matter.
Original comment by nickdowell
on 14 Feb 2015 at 9:02
Thanks a lot for putting in some effort regarding this...unfortunately I'm
still not getting audio back from amsynth, I've tried dssi and lv2, it's
definitely something with the atom. I'll take a look at the git log and see if
I can track it down. Thanks again
Original comment by peppersc...@gmail.com
on 15 Feb 2015 at 9:05
Original issue reported on code.google.com by
peppersc...@gmail.com
on 4 Feb 2015 at 2:50