c4dd0b30a4
Mention the new CMake requirement in the changelog
2020-12-07 18:28:16 +01:00
7f7da50282
Log processing cycles on verbosity level 2
2020-12-07 02:08:03 +01:00
23d5567e72
Add a time info caching compatibility option #62
...
This is needed to get good performance out of SWAM Cello until this
issue is fixed by the plugin.
2020-11-30 14:49:02 +01:00
cbf276b7dc
Hide all symbols by default
...
As mentioned by @abique. Could prevent issues caused by symbol clashes,
and it also greatly reduces the size of all binaries.
2020-11-27 20:40:59 +01:00
f0b4232239
Add more debug printing for audioMasterGetTime()
2020-11-23 16:38:46 +01:00
cea5459eef
Fix wording in changelog
2020-11-20 14:37:51 +01:00
f79e2465e8
Bump to version 2.1.0
2020-11-20 14:24:42 +01:00
ef98ff3d64
Reword parts of the changelog
2020-11-20 14:24:42 +01:00
1c2418d4d8
Clean up the installation instructions
...
Most references to symlinks have been removed since this only caused
confusion and yabridge 2.1.0 will no longer require manual PATH setup i
most cases.
2020-11-20 14:24:42 +01:00
18f15014e6
Mention the new plain yabridgectl AUR package
...
Since having only a VCS version does make making breaking changes a bit
harder.
2020-11-20 14:24:42 +01:00
c69037b649
Always search for host in ~/.local/share/yabridge
2020-11-20 14:24:42 +01:00
ed5f0c42d9
Fix off-by-one error in speaker arrangement read
...
This is why you don't do pointer arithmetic. Fixes an error message in
Renoise when trying to load a plugin as an effect.
2020-11-14 19:37:04 +01:00
f40f031bb0
Reword changelog
2020-11-14 19:31:33 +01:00
d52268b53e
Update changelog
2020-11-14 18:15:10 +01:00
ad71016c9a
Bump to version 2.0.2
2020-11-14 18:13:18 +01:00
ff021d0581
Work around editor opening bug in Ardour 6.3
2020-11-13 17:08:41 +01:00
b93f0ddb8b
Don't depend on the parallel STL
...
We were not linking with TBB, and it's a bit of a waste to require it
just for this one unused function.
2020-11-13 13:42:06 +01:00
5f1fbcb905
Bump to version 2.0.1
2020-11-08 21:53:55 +01:00
b04e1da0d9
Terminate the Wine host after the sockets close
...
The Wine host application would not close properly if the VST host would
suddenly crash or terminate without closing all plugins.
2020-11-08 21:49:52 +01:00
97d1055063
Bump to version 2.0.0
2020-11-08 13:47:33 +01:00
91604f41b5
Change wording in changelog
2020-11-08 13:47:08 +01:00
f2d4d78c49
Remove removed items from the the readme
...
In preparation for yabridge 2.0.0.
2020-11-08 13:32:19 +01:00
7931f38066
Remove the deprecated use-* compilation options
2020-11-08 12:36:47 +01:00
889d9d81c4
Fix wording in the changelog
2020-11-08 10:54:45 +01:00
5bcae68d77
Add an example for using a single plugin group
...
Now that plugin groups are 100% stable this can be a valid approach.
2020-11-08 00:28:34 +01:00
acdbcaca6a
Fix plugin host fallover behaviour
...
GroupHost::running() would sometimes cause plugins to get terminated
prematurely when connecting to another plugin's group host process since
the plugin's own group host process has exited.
2020-11-07 23:11:49 +01:00
d2500ff31d
Get rid of message loop skipping and EditorOpening
...
This special behaviour is no longer needed now that event handling is
fully concurrent and the Win32 message loop no longer blocks
`dispatch()` calls.
2020-11-07 22:06:58 +01:00
822985e140
Mention new socket location in changelog
2020-11-07 18:35:11 +01:00
42032c5c2d
Fix the old accumulative process() function
2020-11-07 18:17:21 +01:00
23cd2dd193
Bump the event loop handling rate up to 60 Hz
...
This will also cause plugins to update their editors at 60 FPS. This was
kept at a lower value for performance reasons, but since the message
loop now no longer blocks event handling we can safely increase this.
This will double the amount of resources spent on drawing, but since
audio processing in a real world scenario almost never utilizes all
cores anyways this should not be an issue.
2020-11-07 00:30:12 +01:00
c18e4be039
Add more improvements to socket rework changelog
2020-10-30 01:30:49 +01:00
9633a70745
Use 'concurrent' instead of 'asynchronous'
...
While asynchronous is technically also correct, this makes it a bit
clearer what's going on.
2020-10-29 20:49:46 +01:00
66976ddfff
Clarify the plugin group changelog entry better
2020-10-28 21:32:48 +01:00
264f6ab8b5
Mention that all plugin group crashes are fixed
2020-10-28 21:19:50 +01:00
f39ee82bd4
Update socket rework changelog entry
2020-10-28 01:21:56 +01:00
59b57f48da
Add a changelog entry for the thread rework
2020-10-27 17:30:18 +01:00
dc72dd97a5
Reword the socket rework changelog entry
2020-10-27 11:13:39 +01:00
e51c7f7ae3
Get rid of hack_reaper_update_display
...
It is now no longer necessary.
2020-10-27 11:13:39 +01:00
4c490808c0
Add a changelog entry for the socket rework
2020-10-26 18:00:10 +01:00
532bfb4e5e
Change wording in changelog
2020-10-23 15:56:44 +02:00
cbc55aa16f
Bump to version 1.7.1
2020-10-23 14:10:11 +02:00
9e7888a78e
Reword part of changelog
2020-10-23 14:09:49 +02:00
c2ec1ce994
[yabridgectl] Fix removing non-existent directory
...
As mentioned in #46 .
2020-10-23 01:49:46 +02:00
db02fa1c43
Fix issue with closing sockets in plugin groups
...
As per Boost.Asio's manual, an explicit `socket.shutdown()` is needed
before calling `close()`. For some reason this worked fine in almost
every situation, but when hosting both a plugin hosted within a group
host process and a normal individually hosted plugin within a single
process, and then removing those two plugins in order, the
`host_vst_dispatch` socket of the first plugin never got closed. This
would hang the entire shutdown sequence to hang on the
`dispatch_handler` jthread.
First discovered in #45
2020-10-22 14:05:59 +02:00
3facdf532a
Fix fake dropdown menus in TDR plugins
...
These would close immediately when hovering over them with the new focus
grabbing method.
2020-10-19 14:34:52 +02:00
e6af947fe1
[yabridgectl] Only recreate files when necessary
...
As suggested in #42 . This also adds a `--force` flag to reenable the old
behaviour and always recreate files even when not necessary.
2020-10-17 18:21:53 +02:00
150845a301
Fix editor_double_embed causing X11 errors
...
Since the error codes were not before version 1.7.0 we just didn't
notice this, even though everything still appeared to work fine.
2020-10-14 16:36:48 +02:00
21c1f53b40
Update version in changelog
2020-10-13 15:41:24 +02:00
0602a6e3d4
Reword parts of the changelog
2020-10-13 15:38:10 +02:00
a1162c2256
Print invalid and unknown options on startup
2020-10-13 15:04:33 +02:00
Robbert van der Helm