From b04c0b2c65b32d53504c86040aea00380f60266b Mon Sep 17 00:00:00 2001 From: Robbert van der Helm Date: Sun, 18 Apr 2021 14:24:03 +0200 Subject: [PATCH] Update links to the VST3 documentation Those were broken after Steinberg restructured the docs with the VST 3.7.2 SDK release. --- README.md | 2 +- .../vst3/plugin/xml-representation-controller.h | 2 +- tools/migration/migrate-bitwig.py | 2 +- tools/yabridgectl/README.md | 2 +- tools/yabridgectl/src/actions.rs | 6 +++--- tools/yabridgectl/src/files.rs | 2 +- 6 files changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 932af008..0f03227d 100644 --- a/README.md +++ b/README.md @@ -138,7 +138,7 @@ to be repeated for all of your installed plugins whenever you download a new version of yabridge. Doing the same thing for VST3 plugins involves creating a [merged VST3 -bundle](https://steinbergmedia.github.io/vst3_doc/vstinterfaces/vst3loc.html#mergedbundles) +bundle](https://developer.steinberg.help/display/VST/Plug-in+Format+Structure#PluginFormatStructure-MergedBundle) by hand with the Windows VST3 plugin symlinked in. Doing this without yabridgectl is not supported since the process is very error prone. diff --git a/src/common/serialization/vst3/plugin/xml-representation-controller.h b/src/common/serialization/vst3/plugin/xml-representation-controller.h index 13ebf766..5af86c54 100644 --- a/src/common/serialization/vst3/plugin/xml-representation-controller.h +++ b/src/common/serialization/vst3/plugin/xml-representation-controller.h @@ -33,7 +33,7 @@ * plugins actually use these representations, do they place them in the * standard locations, and do hosts use them? If so we should be symlinking * them in yabridgectl. See - * https://steinbergmedia.github.io/vst3_doc/vstinterfaces/representation.html + * https://developer.steinberg.help/display/VST/%5B3.5.0%5D+Remote+Representation+of+Parameters+Support */ class YaXmlRepresentationController : public Steinberg::Vst::IXmlRepresentationController { diff --git a/tools/migration/migrate-bitwig.py b/tools/migration/migrate-bitwig.py index 7432b805..deb4b0fb 100755 --- a/tools/migration/migrate-bitwig.py +++ b/tools/migration/migrate-bitwig.py @@ -183,7 +183,7 @@ for preset_filename in glob.glob( with open(preset_filename, "r+b") as f: # Luckily this format is clearly defined, so this is much easier than # trying to parse the .bwproject files - # https://steinbergmedia.github.io/vst3_doc/vstinterfaces/vst3loc.html#presetformat + # https://developer.steinberg.help/display/VST/Preset+Format f.seek(8) uid_bytes = f.read(32) if uid_bytes in uid_bytes_replacements: diff --git a/tools/yabridgectl/README.md b/tools/yabridgectl/README.md index 69d77965..e31cae8a 100644 --- a/tools/yabridgectl/README.md +++ b/tools/yabridgectl/README.md @@ -91,7 +91,7 @@ yabridge for VST2 plugins. This approach is slightly less robust and does not perform any problem detection or status reporting, but it will get you started. Doing the same thing for VST3 plugins is much more complicated and it involves [merged -bundle](https://steinbergmedia.github.io/vst3_doc/vstinterfaces/vst3loc.html#mergedbundles) +bundle](https://developer.steinberg.help/display/VST/Plug-in+Format+Structure#PluginFormatStructure-MergedBundle) with the Windows VST3 module symlinked in, so it's recommended to have yabridgectl do that for you. diff --git a/tools/yabridgectl/src/actions.rs b/tools/yabridgectl/src/actions.rs index 7698a7bb..9de6128d 100644 --- a/tools/yabridgectl/src/actions.rs +++ b/tools/yabridgectl/src/actions.rs @@ -269,7 +269,7 @@ pub fn do_sync(config: &mut Config, options: &SyncOptions) -> Result<()> { plugin_path.clone() } // And then create merged bundles for the VST3 plugins: - // https://steinbergmedia.github.io/vst3_doc/vstinterfaces/vst3loc.html#mergedbundles + // https://developer.steinberg.help/display/VST/Plug-in+Format+Structure#PluginFormatStructure-MergedBundle Plugin::Vst3(module) => { // Only set up VST3 plugins when yabridge has been compiled with VST3 support if libyabridge_vst3_hash.is_none() { @@ -312,7 +312,7 @@ pub fn do_sync(config: &mut Config, options: &SyncOptions) -> Result<()> { } // We'll then symlink the Windows VST3 module to that bundle to create a merged - // bundle: https://steinbergmedia.github.io/vst3_doc/vstinterfaces/vst3loc.html#mergedbundles + // bundle: https://developer.steinberg.help/display/VST/Plug-in+Format+Structure#PluginFormatStructure-MergedBundle let windows_module_path = module.target_windows_module_path(); utils::create_dir_all(windows_module_path.parent().unwrap())?; install_file( @@ -326,7 +326,7 @@ pub fn do_sync(config: &mut Config, options: &SyncOptions) -> Result<()> { // If `module` is a bundle, then it may contain a `Resources` directory with // screenshots and documentation // TODO: Also symlink presets, but this is a bit more involved. See - // https://steinbergmedia.github.io/vst3_doc/vstinterfaces/vst3loc.html#win7preset + // https://developer.steinberg.help/display/VST/Preset+Locations if let Some(original_resources_dir) = module.original_resources_dir() { install_file( false, diff --git a/tools/yabridgectl/src/files.rs b/tools/yabridgectl/src/files.rs index 8ebc48a4..58d74109 100644 --- a/tools/yabridgectl/src/files.rs +++ b/tools/yabridgectl/src/files.rs @@ -255,7 +255,7 @@ impl Display for LibArchitecture { impl LibArchitecture { /// Get the corresponding VST3 architecture directory name. See - /// https://steinbergmedia.github.io/vst3_doc/vstinterfaces/vst3loc.html. + /// https://developer.steinberg.help/display/VST/Plug-in+Format+Structure#PluginFormatStructure-FortheWindowsplatform. pub fn vst_arch(&self) -> &str { match &self { LibArchitecture::Dll32 => "x86-win",