[UPDATES FROM MARK] Where is the sound output setup?

[Woland]

@bonemap said:

it will be helpful to get the release notes for Isadora 3.

 I'm going as fast as I can 

[bonemap]

@woland

Crickey! 45 pages of release notes! You should release them in stages...

[mark_m]

@bonemap said:

@woland
Crickey! 45 pages of release notes! You should release them in stages...

 Real stages or virtual ones?

[Woland]

The Release Notes for Isadora 3 are now live: https://support.troikatronix.com/support/solutions/articles/13000064496-isadora-3-release-notes

We apologize for the delay (Mark added a LOT of cool new things so there was a lot to cover! )

[Juriaan]

I really hate to say this, but removing / releasing without the basic audio features is a slap in the face of users that rely on Isadora for there installations that incorportate sound. No sound input is especially a pain and is something that I used quite heavly and makes it painfull to update my 2.6.1 patches to Isadora 3. I would really like an ETA on this.

Other then that please talk with us about the features that we need, if you are re-working the audio library currently with the suggestions and features that we need to make amazing audio installations with Isadora.

[Woland]

@juriaan said:

I really hate to say this, but removing / releasing without the basic audio features is a slap in the face of users that rely on Isadora for there installations that incorportate sound. No sound input is especially a pain and is something that I used quite heavly and makes it painfull to update my 2.6.1 patches to Isadora 3. I would really like an ETA on this.
Other then that please talk with us about the features that we need, if you are re-working the audio library currently with the suggestions and features that we need to make amazing audio installations with Isadora.

Dear Juriaan,

I totally understand your frustration but please keep in mind that as one of our most prolific Windows-based power-users your definition of “basic audio features” is much different than the definition used by the vast majority of our users (who happen to be Mac users, where sound input in live capture is still present). I would define “basic audio features” as “audio playback”, which Isadora 3 has, and which covers the use cases of audio for the vast majority of our users. As the release notes say, Mark needed to completely gut the old sound library and put in a new one and, since the main focus of Isadora is video, we had to prioritize that over recreating advanced audio support for the initial release. We absolutely could not afford to delay the release for the significant amount of time it would have taken to recreate and thoroughly test the advanced audio features that were present in the 32-bit audio library that was removed. 

That being said, a workaround for your specific use-case, albeit not an ideal one, would be to use one Windows computer running 2.6.1 for the advanced audio features and then sending the data you need over OSC to a second computer running Isadora 3 via LAN, so you are not completely without recourse.

I will speak to Mark about a time frame today, but I can tell you that the entire staff of TroikaTronix is running low on energy and we’re going to need a little bit of time to recover from the frenzy leading up to the launch of Isadora 3, meaning that you should not expect the advanced audio support features to return for at least a few weeks. The good news is that once we dive back into this issue, we are unquestionably going to involve you directly in the redevelopment of advanced audio features for Isadora 3 because of your impressive skill set and experience in that specific field.

Thank you for your patience and understanding,

The TroikaTronix Team

[jhoepffner]

@woland

Dear Woland,

I really not agree with you concerning sound. First because I use, since long time, extensively sound in my work, from synced and unsynced source to spatialized output, second because many people I teach in different places, including Werkstatt 2017, are concerned about sound and frustrated with the way Isadora manage it. Unfortunately there is no progress with version 3 and I am not appeased with the soLoud library choice. I looked at their website and I am not impressed about the possibilities. Their goal is to make a sound library for games, not for professional audio-visual software.

I invested in Dante system on my computer, Via on my main Windows one, SVC on the other ones and for me its necessary to check if the possibilities of Dante with Isadora, who is now the de facto standard for sound on network, its necessary to check what would be the possibilities of routing, not only stereo tracks but separate mono tracks, to have the minimum of sound treatment: limiter/compressor/equalizer, to be able to reroute the sound coming from video, to be able to play aiff, wave, mp3 sound in 44.1 and 48 kHz and in 16 and 24 bits.

All the concurrency, Millumin, QLab, TouchDesigner and others have now a serious sound system because the creators need it, Isadora must be serious in this field also!

I am impressed by the work you have done until now but its not finished.

Thank you for your commitment, All the best,

Jacques

[mark]

@juriaan said:

I really hate to say this, but removing / releasing without the basic audio features is a slap in the face of users that rely on Isadora for there installations that incorportate sound. No sound input is especially a pain and is something that I used quite heavly and makes it painfull to update my 2.6.1 patches to Isadora 3. I would really like an ETA on this.

Responding to  your points:

SOUND INPUT

First of all, let's be clear: no sound input features  were removed on MacOS or Windows. You can still set up live sound input using the Live Capture Settings that feeds to the Sound Level Watcher and, optionally, to the Sound Frequency Watcher or Sound Frequency Bands (only if you check the box that sounds "Sound Frequency Analysis." That's the same as it always was.

On Windows, the"Sound Input" button on the Live Capture Settings that is being discussed duplicated the function of the popup menus that are already there.

Here's the sound settings area of the Live Capture Window

and here's what you saw when you pressed the Sound Settings button

As you can see, they offer exactly the same parameters. Not only was nothing lost, if you did something in the Audio Input Settings in 2.6.1 it would screw up the Live Capture settings part so you couldn't select anything. In other words there was no purpose for this in 2.6.1.

On MacOS, the "Sound Settings" button still opens the Audio Midi Setup application as it it in 2.6.1.

MOVIE SOUND OUTPUT

As it was in 2.6.1, if you have multi-channel audio movies and you assign the channels when you render the, this will be respected and the audio from those movies will play out of the proper channels on your multi channel audio interface.

AUDIO UNITS SOUND INPUT AND OUTPUT (MACOS ONLY)

All of the AU features that were in 2.6.1 remain in 3. Let me throw in here that everything you could do with multi-channel sound playback in 2.6.1 -- and a whole lot more -- can be accomplished if you use the AUAudioFilePlayer and other audio unit plugins to route the sound.

SOUND PLAYER SOUND OUTPUT

The only place the Sound Output Settings had an impact was on the Sound Player. In Windows 2.6.1 if you selected the Sound Output Settings item from the menu you saw this

So you most certainly didn't lose anything there.

But it is true that you lost something on MacOS in terms of the Sound Output Setup. In anticipation of getting a universally improved sound output in Isadora, I felt it was important to go to a cross-platform sound library that would be the same on MacOS and Windows. While Jacques may not thing that SoLoud is very good, in terms of the core functionality of getting sound out of the program, it does the job well. It's lightweight, low-latency and works exactly the same on MacOS and Windows. Having SoLoud in place paves the road for somethig I desperately wanted to get into this release: VST support for both MacOS and Windows. Unfortunately, to do VST fully is a massive task of its own, that we just couldn't do it without more months of delay.

I won't promise VST for the first point release, but I will promise multi-channel output from the Sound Player again. The main task here is to write a decent sounding sample-rate converter; the actual multi-channel output is fairly easy once that's done.

But what is possible in the short term: if this is an urgent issue for people, I can look into reinstating the sound playback code on MacOS that was in 2.6.1. I will invesitgate this over the next few days an report back on the feasibility of this. There's a few other things that are going to bring about a 3.0.2 version relatively soon, and this could be one of the things that is in there. We just have to make sure it doesn't introduce bugs of its own.

I always take it quite personally when you guys all get upset or feel let down. I wish it we could have satisfied you all, but at a certain point we just had to say "no" to certain things and get this version out there, because it was essential that we start selling some programs. That said, I am listening to what you're saying and you can help define what's essential for the impending updates.

Sincerely,
Mark

[barneybroomer]

I agree the absence of the sound output on the player is something that is not possible. What I don't understand is why we can select different outputs in the program very easy with the Audi Device Output actors, but not with a movie player. For multichannel it is really a pity that QT is ditched. Back in the days you could make with QT5 one movie file with text, timecode, midi, 16 channel multichannel audio and video! That was really awesome. Now it is almost 2020 and were back to ehhh, how to assign a stereo audio output.....

[mark]

Everyone: I have revised my post above as I was initially under the impression that this was about Windows. Please take the time to read again.

Best Wishes,
Mark

[mark]

@mark

I have just created an experimental build that would reinstate the previous functionality on MacOS. It works as it did (I never throw code away) but now we'll have to investigate if it could lead to crashes with the threaded engine, etc. But a revision that goes back to using MacOS specific features for the MacOS version seems possible.

I will keep you updated.

Best Wishes, Mark

[Woland]

@woland said:

you should not expect the advanced audio support features to return for at least a few weeks

 @Juriaan 

Well Mark's on the scent so it shouldn't be that long now I guess. Keep your eyes peeled for an experimental build.

[jhoepffner]

@Juriaan @mark 

I made some extensive try with sound between Mac, Windows, Dante etc. here my momental results:

– Its possible to play multi tracks sound (with or without video) on V3 on MacOs. The technic is to make a multitrack wave file with "SoundFilesMerger" (free, only macos), then make a .mov file with quicktime and to play it as movie in Isadora. With a multitrack output in sound and midi config (I tried with Dante VSC and with real Motu sound card), each track go to a discrete output, as in 2.6.1

- Its not possible on Windows. I tried all the combinations between wave, .mov, M-Audio souncard, Dante, at best I have a stereo output, at worst no output at all.

I think on windows its necessary to look at ASIO implementation, it is the de facto standard on Windows, not so cool as coreAudio on macOs concerning mixed frenquecy, bit deepness and sharing of output but when you are careful, it work well and with Dante Via (unfortunately paying application) its really easy to route everything. If you play in theater equipped with Dante sound mixer its really easy to manage.

Concerning SoLoud, I made only a quick research so I cannot be so affirmative but I doesn't read anything concerning multitrack management. One of the main demand from people around me concerning Isadora is around sound routing and I think that for many situations its important to be able to route each single track to single output, be real output or software input in Ableton or Max for filtering or analyzing.

Sincerely,

Jacques

[mark]

@jhoepffner said:

Its not possible on Windows. I tried all the combinations between wave, .mov, M-Audio souncard, Dante, at best I have a stereo output, at worst no output at all.

This goes in opposition to findings by @Fred that he posted some time ago -- though it was for Isadora 2.6.1. Did you try the techniques he described in that post? If the movies don't do multi channel output on Windows, it's a bug and we'll fix it.

Now, with regard to AIFF and WAVE audio files played by the movie player -- the experimental build solves the problem for Mac. I will have to see if it's possible to add a way to route the audio with SoLoud under Windows. I will research that in over the next few days as well.

Best Wishes,

Mark

[Fred]

@mark and @jhoepffner I will re-check this media with the 7.1 audio today and let you know if it still works. I cannot imagine anything changed.

[mark]

@fred

Did you discover anything you want to report?

Thanks,
Mark

[mark]

Dear All,

Here's a further update: I've reinstated the old MacOS sound behavior in the 3.0.2b1 verison which all beta testers will have right now. If you urgently need this feature, contact us by opening a ticket and we can get it to you.

But in the long run, I have a much better solution: by making a small modification in the SoLoud source code, I can route the sound to any channel on the multisound output device. ( @jhoepffner -- this is another advantage of SoLoud: I have all the source code and can improve/change it.)

So what I propose to do is to add a field to the Sound Player to allow you to specify the channel routing in the actor itself. This would be a text field so that you could enter things like

1-3, 5, 9

to route the sound to channels 1, 2, 3, 5 and 9.

You could then use this input change the routing interactively if you wanted.

I have tested this and it works well for stereo sounds. What I have not yet tested is, for example, a four channel sound and a routing like the above, though I think it will work OK. I'll do that teest in the coming week.

This would give us a very flexible, cross-platform solution to routing sound.

Comments?

Best Wishes,
Mark

[Fred]

@mark of course things got out of hand and I can actually test tomorrow. I have a few other tests I want to do with video playback as well. The proposed changes to soloud giving routable audio sound pretty great (but I'm assuming this is only for audio files not for the audio from a movie player?).

Sorry things are getting pushed before the summer break. I have a little list for Isadora for checking to reproduce some errors I found (unless they are just for me).

[mark]

@fred said:

(but I'm assuming this is only for audio files not for the audio from a movie player?).

This should also be possible under Windows; I saw some stuff in the API for Media Foundation that seemed to allow this with relative ease, but I have to find that again and refresh my memory. In AVFoundation, it is a much bigger job: Apple engineers told me some time ago that "we will never support the sound routing capabilities of QuickTime in AVFoundation." (Thanks Apple!) What's required is to build an entire Audio Units graph that intercepts the sound coming from the movie and then routes it to the proper channels using an AUMatrixMixer. Not a small task I'm afraid.

Still, I'm listening to all of you about the importance of audio. Let's keep talking and we can see what's possible to get on the roadmap for the 3.1 release we plan for the August Werkstatt.

Best Wishes,
Mark

[Fred]

@mark ok thats tough. I'll get some tests done tomorrow.