From 708360e58ba585d04bbd033d031b13ef986a4a7b Mon Sep 17 00:00:00 2001 From: tpoole Date: Mon, 31 Jul 2017 12:37:49 +0100 Subject: [PATCH] Replaced curly quotes with regular " characters in BREAKING-CHANGES.txt --- BREAKING-CHANGES.txt | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/BREAKING-CHANGES.txt b/BREAKING-CHANGES.txt index 1b0333d3d0..c6aea72e5b 100644 --- a/BREAKING-CHANGES.txt +++ b/BREAKING-CHANGES.txt @@ -204,7 +204,9 @@ multi-bus API (JUCE version 4.0.0 - 4.2.4). Change ------ -JUCE now generates the AAX plug-in bus layout configuration id independent from the position as it appears in the Projucer’s legacy “Channel layout configuration” field. +JUCE now generates the AAX plug-in bus layout configuration id independent from +the position as it appears in the Projucer’s legacy "Channel layout +configuration" field. Possible Issues --------------- @@ -223,17 +225,17 @@ Rationale -------- The new multi-bus API offers more features, flexibility and accuracy in specifying bus layouts which cannot be expressed by the Projucer’s legacy -“Channel layout configuration” field. The native plug-in format backends use +"Channel layout configuration" field. The native plug-in format backends use the new multi-bus callback APIs to negotiate channel layouts with the host - including the AAX plug-in ids assigned to specific bus layouts. With the callback API, there is no notion of an order in which the channel -configurations appear - as was the case with the legacy “Channel layout -configuration” field - and therefore cannot be used to generate the AAX plug-in +configurations appear - as was the case with the legacy "Channel layout +configuration" field - and therefore cannot be used to generate the AAX plug-in id. To remain backward compatible to pre JUCE 4.0.0 plug-ins, JUCE does -transparently convert the legacy “Channel layout configuration” field to the +transparently convert the legacy "Channel layout configuration" field to the new callback based multi-bus API, but this does not take the order into account -in which the channel configurations appear in the legacy “Channel layout -configuration” field. +in which the channel configurations appear in the legacy "Channel layout +configuration" field.