PreSonus Forums

jazzundso wrote

j0001s wroteI do wonder if Presonus's "it may look like MIDI, but it's not..." decision for instrument tracks is causing some heartburn for them now.

Why should it?

Probably should have stayed away from conjecture, but I'm in it now, so...

Quoting from the S1 manual, "The Musical Instrument Digital Interface (MIDI) specification was created in 1983. While it has served musicians well for more than 25 years, it has some limitations in terms of resolution and speed. We circumvent many of those limitations within Studio One by substituting our own high performance control system in place of MIDI when controlling certain vital internal parameters.

As an example, fine-grained parameter automation is provided within virtual instrument parts, rather than much lower-resolution (128 steps) MIDI control-data automation. The Control Link system is also made possible by abstracting MIDI from Studio One's internal processes."

So, for every new feature added to MIDI, they have to translate it to their internal model. And the structure of their internal model has to be able to accommodate these new commands. Then it has to be able to reconstruct their internal structure back to MIDI in order to control external sound generators and devices.

Other DAWs simply have to store the MIDI as is, and shove it out at the right time. Since MIDI is stored as is, creating editors for it (such as the list editor) is easy to do in other systems, and it becomes easy to add the new functions to their existing editors.

What tends to get forgotten is that Presonus did what they did for valid reasons - better instrument timing and finer parameter control over other DAWs. And this advantage isn't really promoted.

PreAl wroteRemove or add the plugin file paths. It's weird. Sometimes I have to point to the waves plugin folders and rescan, and then remove all the file paths and rescan. Restarting and clearing blacklists inbetween. Anyway there are loads of threads covering this.

Thanks, I tried changing the paths, etc. based on a thread you had been involved in. What's weird is everything was working fine until the Studio One update...

I got them to show up by doing the following:
1. Xfered all my licenses up to the cloud, then back again to my PC. (Why not?)
2. I ran Waves Central and Updated whatever it wanted to update
3. THEN, I found this, and went with "Mix of v9 and v10 licenses". On this page, there is the "V9-V10 Organizer" which I ran, it did some cleaning up, and it seemed to work.

j0001s wroteWhat tends to get forgotten is that Presonus did what they did for valid reasons - better instrument timing and finer parameter control over other DAWs. And this advantage isn't really promoted.

Exactly. No need to worry for anybody. All we have to do is being patient enough to wait for them to focus on a specific feature like Poly Pressure or SysEx...

the release notes say Import Song Data into a song template is a new feature,but its been there since v4.0. Am i misunderstanding what this new feature is? Have Presonus now added Bus import to 4.1 as that was not possible in 4.0

Daw Stew wrotethe release notes say Import Song Data into a song template is a new feature,but its been there since v4.0. Am i misunderstanding what this new feature is? Have Presonus now added Bus import to 4.1 as that was not possible in 4.0

You're now able to import song data from a template which wasn't possible before 4.1. You were able to import session data from another session file but not a template file.

Daw Stew wrotethe release notes say Import Song Data into a song template is a new feature, but its been there since v4.0. Am i misunderstanding what this new feature is? Have Presonus now added Bus import to 4.1 as that was not possible in 4.0

No, they have not added buses (without the workaround).
You can now pull song data from a .songtemplate file as opposed to just a .song file.
Have now figure out what this brings to the party with regards to using it as a "track template" functionality.

Please post further discussion about ISD track inputs in the original thread on that topic at viewtopic.php?f=151&t=30727

Related posts from this thread have been moved there

Thanks

Hey guys, I'm on the boat returning to Studio One after a period of time.
I like very much the additions on v4 and v4.1, however I'm trying to make a set up for my headphones mixes and I realise
that the Cue mix doesn't appear anymore under BUS or FX tracks (it did in v3).
This is a problem because I want to send a reverb to the studio room (headphones) while tracking.
What happened? Is there any workaround?

**EDIT
I just saw that when you engage "Cue mix mute follows channel" in preferences, we have back the cue mix on both BUS and FX tracks.
But from the other hand, we loose the goodies of the new implementation for solos, mutes etc to not affect the cue mixes.
It's a little bit confusing... Why this new feature cancels the cue mixes on bus and fx?

nikolaospitloglou wroteHey guys, I'm on the boat returning to Studio One after a period of time.
I like very much the additions on v4 and v4.1, however I'm trying to make a set up for my headphones mixes and I realise
that the Cue mix doesn't appear anymore under BUS or FX tracks (it did in v3).
This is a problem because I want to send a reverb to the studio room (headphones) while tracking.
What happened? Is there any workaround?

**EDIT
I just saw that when you engage "Cue mix mute follows channel" in preferences, we have back the cue mix on both BUS and FX tracks.
But from the other hand, we loose the goodies of the new implementation for solos, mutes etc to not affect the cue mixes.
It's a little bit confusing... Why this new feature cancels the cue mixes on bus and fx?

It's has been brought up to the developers, is currently a constraint and they will improve over time.

jpettit wroteIt's has been brought up to the developers, is currently a constraint and they will improve over time.

I hope so! It's a "must" for studio recording operations.
Thank you jpettit!

If they would only now ad a pipeline system for external synths it would be great....
So fed up needing to ad multiple tracks to record my external synths....
Just for that I went back to cubase and Ableton...


https://answers.presonus.com/22832/stud ... ent-plugin

Waves PRS Super Models aren't scaling correctly for me (150%) on a 4k monitor.
Bunch of dead space at the top of the window... and about half the Super Model GUI (in the lower half of the window).

Jim Roseberry wroteWaves PRS Super Models aren't scaling correctly for me (150%) on a 4k monitor.
Bunch of dead space at the top of the window... and about half the Super Model GUI (in the lower half of the window).

Hey Jim -

The scaling feature is dependent on Win library code the individual plugs are built with. So first contact should be with Waves.

elizeubezerra wrote Hi, the same thing happened to me. Studio One 4.0.1.48247 runs seamlessly with the Brazilian bank program. After I made the upgrade to version 4.1.0.40427 it did not run, presenting the white screen problem. After viewing the information in this forum, I removed the security module from the bank program, so Studio One 4.1.0.40427 worked normally. But now I can not use the bank program. I tried to reinstall the security module of the bank but it returns the problem in Studio One. How to do to run the two programs? Thank You

I chose to remain with a bigger cause performing on my computer which is S1. I can use the bank app on my phone. I guess this is a programming issue with the bank program itself, that maybe the bank developers can help out if you reach them out. Since that might be too hard I rather avoid using the bank program on my computer.
BTW!! if you are based in São Paulo, DM if you want to collaborate!

BobF wrote

Jim Roseberry wroteWaves PRS Super Models aren't scaling correctly for me (150%) on a 4k monitor.
Bunch of dead space at the top of the window... and about half the Super Model GUI (in the lower half of the window).

Hey Jim -

The scaling feature is dependent on Win library code the individual plugs are built with. So first contact should be with Waves.

Hi Bob,

Yeah, I realize...but wanted to share.
The GUI is *tiny*

Is there a bug in "merge to stereo file" command in browser, when you select two mono audio files and right click. Crashes here on S1 4.1 mac OS X 10.13.6

tommikujala wroteIs there a bug in "merge to stereo file" command in browser, when you select two mono audio files and right click. Crashes here on S1 4.1 mac OS X 10.13.6

I just replicated this in Win10. Studio One vanishes after a brief delay.

I'll submit a report on it.

UVI Falcon V1.61 does not work with S1 V4.1 (gets black listet)
But it does work in S1 V3.56

Who is to blame now? UVI or Presonus?

lfo2k wroteUVI Falcon V1.61 does not work with S1 V4.1 (gets black listet)
But it does work in S1 V3.56

Who is to blame now? UVI or Presonus?

This is the latest version?
Try removing the plugin folders, restarting S1 and then putting the plugin folders back... Doing the usual scans.

Traditionally you report plugin issues to the plugin developer. If they find there is an issue with Studio One they should contact Presonus.