JACK as a Plugin

Development
96

In your opinion, should I remove JACK support from Core and recommend users to download SkJack? Or should I keep it (and still recommend users to download SkJack)?

97

You should definitely keep it, many new users will be wanting to get going simply and Audio is fine for that. You shouldn’t need to use a 3rd party plugin to output to jack.

5 Likes
98

Sounds good :+1:

1 Like
99

+1 to keep the jack support (and perhaps improve it) in the Core

2 Likes
100

You shouldn’t, no. It wasn’t even supported outside of a patched build when I wrote this.

101

this topic is confused to me

I never used a patched build (I always compiled by myself) and I have jack at least from the 0.5 without building jack, I like SKjack because it is titled as "First-class JACK support for VCV Rack " which mean all the jack features (midi, transport, clock, etc) I use Skjack but today the only difference that I can see is the capability to add mayor number of input and outputs.

I dont not know when you wrote the code , but when you announced the SKjack I already have jack connections in the core and RCM audio16. (without patched)

question: when I select Jack in the core module , is that jack or what ?

2 Likes
102

When I was building 0.6 from source, I turned Jack support on for RtAudio. When I selected it I remember it only partially working with two ports in the flow graph even though Audio had four. Maybe the version I built was broken and it worked in the officials :woman_shrugging:

103

ahhh, I see
to make it work correctly you must open a jack I/O as dummie, for instance I open renoise with 8 imputs enabled and it is enough to connect the core audio.

yes, you are right now we can skip that step and connect the vcv rack directly.

but in other hand the ladish session can’t remember the connections (that is possible with the core audio) and we must reconnect it every time.

1 Like
104

you know what should be nice?

a 2HP jack connector with a couple of knobs, think about it

1 Like
105

attenuverters and unnamed ports?

2 Likes
106

exactly

1 Like
107

So is this not going to be available any more? It was very useful.

108

Existing functionality ought to work since I migrated it to the compatibility headers. Those should be on github under a v1 branch, but nobody has done builds and posted them. Fixing the deprecations and dealing with the paperwork will probably happen in time.

1 Like
109

Hello @Skrylar just to be clear, are you maintaining (and will you maintain) this plugin?

1 Like
110

I m not sure what it mean, the plugin will not be available via plugin manager? any news about the paperwork or the support campaign?

1 Like
111

v1 sent off to the plugin team

6 Likes
112

awesome, thanks!

whats about the support campaign?

1 Like
113

My laptop has died, so, there isn’t much of one.

114

…and considering that your are answering a 3 months ago comment, I not expect much of it

2 Likes
115

Thanks for all the work you did on this, having got sick of the rtaudio implementation not meeting my needs, I have got this to the point of partially working with Rack 2, Currently the audio paths work but the naming doesn’t. This atleast meets my needs far better then the internal Rack module and plugin naming would be useful so i’m planning to spend some time getting the module up to speed again. If you would like I am happy to contribute the fixes back to you once they are working properly or otherwise I’ll rebrand it and atleast publish the linux plugin file to github.

6 Likes