You will need to upgrade your monitoring setup too. If not Internally Atmos even in a 7.1.4 monitoring setup is always 9.1.6 as the beds are always 7.1.2
1 Like
Could you reword that please? I donât really understand what you mean.
1 Like
Atmos is basically 7.1.2 bed plus 118 mono Objects, Objectâs can be interpreted to 7.1.4, or even bigger space such as 9.1.6 monitoring setup or even larger spaces with even lager speaker layout. If you can afford it. Otherwise a 7.1.4 is minimum for a 14 by 16 foot studio space.
1 Like
[quote=âMattiasNYC, post:200, topic:876348â] Could you please tell us what bugs you are talking about? Iâm sure there are several people who havenât started on v13 yet and would like to know[/quote].
After 2 minutes of research (I havenât checked everything for validity), and there are more:
2 Likes
Youâre right. So, no 9.1.4? It jumps from 7.1.4 to 9.1.6 , Curious and disappointing. But 9.1.4 is well documented in Dolby Atmos.
1 Like
Yes, Iâll make a note. I wanted to add 2 widths in front, but Iâll also have to add 2 centers to the ceiling. I hesitate.
Thanks Rajiv.
1 Like
Well maybe you should have checked before asserting that the number is huge and what is huge are bugs. A lot of times when new versions come out people a) donât install correctly / fully, b) donât understand new features, c) donât realize old features have been moved or removed, d) unknowingly change settings leading to things not happening when they think they should⌠and so on. So itâs not all bugs.
First link: Undefined error. Could be a bug. Could be something else.
2nd: Not new issue in N13, existed in N12, and the issue as described works for user MAS.
3rd: Could be a bug. Could be something else. Surely if media and samples were missing due to a bug most would mention this.
4th: User error.
5th: Same as first link.
6th: Not a bug. Works as intended.
7th: Could be a bug. Could be something else. My hunch tells me this is an installation problem, not a bug.
8th: User error / resolved by user.
9th: Could be a bug.
10th: User error.
11th: Could be a bug.
12th: Bug.
13th: Bug, or so it seems.
14th: Could be a bug. Could be user error.
15th: Not a bug. Option removed.
So Iâd say itâs far from clear that weâre dealing with a âhuge numberâ.
2 Likes
I think itâs a language / translation problem.
1 Like
I donât work for SB and donât have the time to check. I think that the bugs cited (and confirmed by you), after a very short search, seem significant, enough to add a layer of hesitation about moving from N12 to N13, or at least waiting for the corrected versions. Especially in addition to the rest related to the too-quickly-made interface, which SB admits it needs to correct. Thatâs what I was saying, nothing more.
1 Like
Yes, itâs something to keep an eye on. Personally, I donât do it enough, in the hubbub of exchanges. But if I re-translate into French my texts already translated from French into English, itâs a circus, or at least some weirdness. It doesnât help to understand. Thatâs why I try to write in short sentences, without metaphors, but itâs not easy.
1 Like
1 Like
I think with every new major version like this, you should expect to be some issues. You install it, you test it on your projects/workflow. You only put it in production if youâre satisfied that it works for you. In the meantime you keep the previous/stable version around for current projects, until you know that the new version works.
But without trying the new version you wonât know if it will work on your specific workflows. Sometimes you can imply that from other usersâ experience. But thatâs of limited value, as they may have different systems, use different features, have different data, donât operate the software the same way.
Keep in mind that we have some ~50 people here noting various problems. How many hundreds of users have upgraded and not said anything here. For the most part people only post if they have problems, not when theyâre happy. You have to account for this bias.
Was it the smoothest new version of an app Iâve experienced? Definitely not. Is it worse than what usually happens? No, not at all. Is it frustrating? Well, itâs software. Nothing is ever non frustrating at some level with software. But such is the nature of very complex systems. We could be doing this all by hand on analog, and maybe it wouldnât be as frustrating, but you wouldnât be able to do the same things.
Such is life in the 21st century high tech world.
2 Likes
Good point.
I think cmbourget is a bit overreacting. Thatâs a lot of complaining already.
For me to be honest it works great, apart from some minor stuff that will be resolved in the first maintenance updates. I donât even use 12 anymore, and Iâm in the middle of a 12 episodes series. Seamless transition here!
The GUI in the other hand⌠it really is a disaster in my opinion. Designers all over the world are mourning for Cubendo right now.
4 Likes
I dunno, it seems to be the style of things these days. I havenât used it enough to really have a good opinion but the flat style is what is currently âinâ. Studio One is very flat, which some people say makes it look âmodernâ. Windows, Android, also very flat.
Some of it is just style, some of it is practical in that flat graphics are often easier to do as vector graphics, which means they can be scaled to arbitrary DPI better.
1 Like
Ok, but until you actually pay attention to what youâre posting itâs just FUD, and quite frankly we donât need more of that.
I disagree. The âmaybe itâs a bugâ items are really just âmaybe itâs a bugâ. The only two I saw that seemed to be confirmed to be bugs seem relatively minor. Regardless, two isnât a âhuge numberâ, which was my point.
1 Like
Of course you can. So itâs wise to wait for future updates, when the important thing is more work than experimentation. Iâm not saying that SB is problematic here, on this particular point. Iâm just saying that itâs wise to wait unless weâre prepared to suffer a littleâŚ
1 Like
This exchange is going nowhere. Iâll stop here.
1 Like
Great.
#11 turned out to be user error as well.
1 Like
I donât mind flat design. Itâs the new GUI that os bad, not flat design.
3 Likes
In principal I very much agree with your logic here, to put these issues in a lot more perspective to ground the conversation in reality and away from free wheeling emotions.
And youâre doing this as a public service to this forum, without digging into each of the issues in detail necessarily (understandably).
My only nit-pick is that not all of them may be actually âuser errorâ, which I think off as user made a mistake or forgot to do something. The pilot not lowering the landing gear is a user error.
Take #10 on the list (because itâs mine I have extra context).
I wouldnât classify it as user error, more like âworkaround exists, root cause unconfirmedâ. You could also use the âmay be a bugâ as you did with some others.
To cross my Ts, I tested the same use case in N12 (external renderer in native mode). In N12 it doesnât even show up as a choice. You can only use the external renderer in Rosetta mode. In N13 it is listed as choice in native mode but fails to function properly. So it could very much be that itâs intended to work, and SB thinks it is working, when it is in fact not. Which would make it a bug. I just solved my problem on my own by switching to Rosetta mode, thus working around whatever the problem is.
It could also have been (though itâs not based on my testing) that it used to work in N12, and now itâs not, which would make it a regression in the software. Which also makes it a bug. Some of the DOP issues appear to be a regression.
Given that a work-around exists (or in other cases is a minor annoyance having to select events differently with an extra click), it wouldnât stop anyone from adopting N13 as their DAW for current client work. Which is your (very valid) main point. But I think itâs worth tracking these issues, and keeping SBâs feet to the fire on them (if they own the fix).
Thanks for humoring me with making this distinction. As an ex-software guy, this detail does matter to me. And again, I do appreciate the time and effort that youâre putting into this forum and clarifying some of the issues.
PS: As weâre both NYC based, if you some day you would like to meet in person over a coffee that would be nice.
4 Likes