perhaps future sound systems will be able to somehow scan the room for shape and density, position of listeners ears…taking advantage of these things to create immersive spatial audio experience…or even if there are many listeners, scanning for position of ears in combination with many small, laser-pointer-like directed audio speakers so that no matter where you are in a concert hall, for example, or inside a car, all the concert goers or passengers will always be in the sweet spot…the future of audio is a crazy mesmerizing thing to think about, what will be possible, not only for spatial audio effects but also more and more complexity in the field of physical modelling sysnthesis - eventually with enough processing power to account for the resonance of every atom, and build impossible physical instruments such as ‘blue whale’ or ‘mountain earthquake’…such things
Automated panning and cancellation question
In sliding bars or in automation the range is from 50L to 0L, Center, 0R to 50L. That’s 51 + 1 + 51 values, 103 values in total (instead of 103 they could have been 129 values). It is still an odd number. The values 0L or 0R is not the same as the Center value. I guess it’s a way to add more values and follow in a rounded format, 51 and 51.
Thus, the Left (or Right) side is also odd, being able to easily locate a right center, 25L:
- 50L to 26L (25 values)
- 25L (1 value) equals 50% to the L
- 24L to 0L (25 values)
If you use the panorama parameter to the note, it has a range from 0x00 to 0x80, that is 129 values, from 0 to 128 values, which is odd, with its center at 0x40, the same range as the volume, when 0x80 is the same as empty.
Renoise has adjusted these values in a convenient way.
Dolby Atmos can use up to 64 audio channels in the most complex cinema systems and 128 audio tracks. Nor would I call it an “intelligent system”, but more appropriate to distribute the sound, compared to Dolby Digital to DTS. The sound engineers will have to configure the audio tracks for this system, that is, there is a very wide work behind to correctly distribute all the sounds to cover all the space, the three dimensions. It is not something that the Dolby Atmos system does alone.
To avoid strange things when playing with the panorama, if you use a stereo sample, it is advisable to convert that stereo sample into mono. That is, use samples in mono. So no portion of negative phase.
Otherwise, you can do what @OopsIFly, use the Stereo Expander with the Expand value in “mono”. In I do not know what forum I read that in “mono” does not really act as a mono, but as something that approaches.
O.K, sorry for the misunderstanding. I assumed the panning slider had 256 values without checking it properly.
103 values is great, as an odd number, no problem to find perfect centre, centre right, centre left as you said.
Is this the standard? Why was the decision to have 103 points in the track panning, but 129 points in the panning effect command made?
Also, I think the autopan command doesnt work properly…doesnt cycle in time (same as vibrato), am I wrong? Maybe Im missing something.
I was looking at the panning guide by someone on the forums, I believe it is wrong, although still quite useful, should be updated. Didnt take into account that there are 129 points in total including 0x00 as a point?:
https://forum.renoise.com/t/pxx-panning-command-guide/48824
https://forum.renoise.com/t/some-panning-column-techniques/48784
These are great tips here, thankyou.
One last question, should I use tracks main panning, or add a gainer and use the panning in that for my panning automations? I guess that way I will be able to offset afterwards if desired?
If you use the Pxx parameter, the range is 0x00 left, 0x80 center, 0xFF rigth. Generally, the value 0 is also a valid value for everything in Renoise, and in mathematics.
Better use the panning in the pre-mixer, and do not use anything else in the chain unless it influences the panorama.
So you have two approaches here. If you use effects in the chain that modify the sound and play with the panorama, a profit at the end will allow you to correct what has been modified before in the chain of that panorama, not afterwards. Although to correct the whole chain you have the panning of the post-mixer, which you can not automate.
If you do not add effects in the chain that influence the scenario, it does not seem reasonable to use a profit to correct the chain. For that it uses the panning of the pre-mixer or post-mixer.
As a general rule, the fewer things you add in the chain, the better.
awesome, thanks. these are great tips…this should be interesting. pulsating, swelling panning stuff…movements in the panning. very cool
I think with the Pxx commmand there is still the problem of panning being handled in 256 values/points, an even number.
80 cannot be true centre…maybe it is both 0L and 0R at the same time?
but with panning sliders and panning column you can still do true centre, because they use an uneven number of values/points.
maybe this is a compatibility feature, so that panning commands from .xm and so on can still be imported.
also, reportedly the J and K panning slide commands work properly only at 8 tick per line.
same problem with vibrato, tremelo and autopan?
maybe these were done very early in renoise development and somehow there was a mistake about basing those commands behaviour on 8 ticks per line instead of 12 ticks per line
This is true. The range should be 0 to 256, that is, 257 values, odd range. The problem is that the decimal value 256 is equivalent to 0x100, the first 3-digit value. To respect the 2-digit value, it is necessary not to leave the range 0 to 255, that is, from 00 to FF.
Renoise is full of details of this type.
The MIDI input only accepts a range of 0 to 127, which is 128 values, from 0x00 to 0x7F. That is, the velocity can not return 0x80, only up to 0x7F. Therefore, 0x80 is like not putting anything in the maximum value of note volume.
A similar case occurs with the panorama of note. The MIDI input only accepts a range of 0 to 127, which is 128 values, from 0x00 to 0x7F, which is an even range. The value 0x80 has been added to complete it, just as in the volume.
They are extreme cases. With the delay of the note the 00 is empty, and the FF is the maximum delay, with an effective range of 0x01 to 0xFF, which is 255 values.
Perhaps in the Pxx effect, the value of 0x00 should be canceled, using a range of only 255 values, odd range, with 128 (0x80) as the center.
That is a little confusing about the volume column, in that the maximum is actually 0x80=127, not 0x80=128.
So, do you think with the Pxx command, if I enter 0x80, its actually setting two panning points, 0L and 0R, rather than true center??
Otherwise, what is the meaning of 0L and 0R? Ive never seen ‘one point away from center’ described in this way before…it must be a fasttracker2/milkytracker compatibility thing I guess?
What do you think about the broken panning slide, autopan, vibrato and tremelo commands?
When I tried them real slow at 32BPM and listened close I think its true that these commands have behaviour based on 8TPL for some reason. Needs to be changed to cycle properly at 12TPL. That is regular panning, volume or pitch variation in time with the song settings, looping perfectly when a pattern loops or is played more than once consecutively in the song.
So this is why all my old modules are lopsided towards one side? Doing stereodetunes by panning 40/C0 like a total No0b!
Maybe it’s dealt with by a multiplication factor on one of the sides? I’m assuming that 00 and FF are truly hardpanned. Gonna check the pattern command ranges with a phase cancellation test in Mxxx later.
If anyone has time, please check on the behaviour of the vibrato, tremelo, autopan, panning slide left and panning slide right commands…
seems like the effect column commands are looping their internal LFO based on cycles of 8 ticks, rather than 12 ticks…for the panning slide left and right commands in the panning column, seems like they will reach hard left or right from centre in time, on the beat only if ‘ticks per line’ is set to 8, not the standard, 12.
Its a shame because this kind of error just seems like it was a simple a ‘typo’ from years ago that hasnt ever been found. Like someone was thinking of ‘Lines Per Beat’ instead of ‘ticks per line’ and somehow entered 8 instead of 12…
vibrato and tremelo commands are nice and expressive, same with autopan…its such a shame not to use them, or to use them but to notice that they are weird…its just a small thing but it would be seriously nice to fix them so they work properly. for example, one vibrato cycle per line, two per line etc…or slow ones, one cycle per 4 lines and so on
Effect command column:
0Vxy - vibrato
0Txy - tremelo
0Nxy - autopan
Panning column:
Jx - Panning slide left with step x (0 - F)
Kx - Panning slide right with step x (0 - F)
Notice this quote from It-alien, from 9 years ago…
"admittedly, vibrato did not get the right attention when we decided, with the release of Renoise 2.0, to redefine the behaviour of tracking commands.
the backward compatibility problem pointed out by dblue is a false problem in my opinion, since we can base the behaviour of vibrato on the version number of the loaded song. Of course, the user should be aware of the fact that saving a song with the new version will break the vibrato behaviour."
Please fix vibrato, autopan, tremelo, panning slide right, panning slide left …
come on yo! it a small typo-like error
Not forget the most important difference:
When you use the panning column, you pan the instrument “per note”. So you can have multiple notes running in different positions in the panorama.
If you use gain slider somewhere in the mixing context, just the audio stream will be panned.
This is for me the main criterion for choosing which function to use for panning. Like the per note column if I want to do effects like a cloud of notes in the panorama. And the sliders for static panning, or automation of the whole track’s audio.
it is awesome that you can set panning, volume and delay separately for each note in a chord all within one track. the word cloud describes that kind of chord with spatial characteristics perfectly. I just wish the panning slide left and right commands would work out to pan things rythmically in time, so that each note in the cloud can also be moving, same goes for autopan (if each note in the chord was in a separate track). I havent tried it but presumably you can set a panning point with the panning column then add movement around that point with autopan. I think its exactly the same kind of time-error in tremelo and vibrato too. it can all be done with LFOs as a workaround but better, more efficient to fix those few pattern effect commands
for example, with autopan, vibrato and tremelo it is not possible to finish their cycles exactly on a line
with panning column commands it is not possible to pan hard left to hard right and have the whole movement end at a line boundary…it all seems to be based on 8TPL, instead of 12TPL.
Would be cool to have each note in a chord do stuff like head from right and left to center, crossover each other, then hang around a while ‘wobbling’ with an autopan, then head back to their start point and stuff like that…or to have them ‘bursting out’ from central confines to dissolve in the periphery
If you think that vibrato, tremolo and autopan have some problem, you should report it in the forum of bugs.
It is necessary to detail the problem so that it is understood.
https://forum.renoise.com/c/help-support-bugs
There someone will listen. Here probably not…
I will do that, just tested it again…
to see what im describing, just takes two minutes to check it out:
set LPB to 8
pattern length to 16
BPM to 32
add a note
put V all down the pattern effect command column
put 0V1F in the first line’s V command
you can hear as the pattern loops the vibrato cycles out of time.
Try it with 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E and F.
They are all out of time cycles which you can notice as the pattern loops (although 0V7F and 0VEF are almost in time, still not quite).
Try it with T (tremelo), also out of time
try it with N (autopan), you can watch it cycling out of time in the VU meter at the top
Try the panning column, like J1 and K1…no matter what I do I dont think that its reaching hard left or right from center, exactly by the start of line 8.
When you see the error with those commands youll know what I mean. I would definitely want those cycling in time to be able to use them properly and without those annoying pops when the pattern loops.
I will put it into bug reports
I know there is a problem with Vibrato V, Tremelo T and Autopan N…but if Im just being dumb about the J (slide panning left with step x) and K (slide panning right with step x) please give me some tips. Im guessing that a J1 slides by one panning value per tick, so I gues the way to do these things would be to start with a Pxx command to set the place to pan from, then use a panning column J or K command on the following line, (or can it be done from the same line?), counting out the ticks and panning points to the desired position.
its like you said though, the Pxx panning and panning column panning have different scales (panning column has 129 points, Pxx has 256 points)…but I think it should be possible to just set a position with Pxx and start a slide with J or K on the same line, but it may be I can only do it from the following line.
Have you tried changing the “Ticks Per Line” value in “Renoise: Song Options / Playback Options”?
Does this change anything?
O.k, I tried V, T and N, all speeds, maximum depth at 3TPL, 4TPL, 6TPL, 8TPL, 12TPL and 16TPL…cycle is out of time for all of them.
I thought maybe it could be triplet cycles instead of straight cycles, so I tried with pattern length 12. Same out of time cycles.
I tried it with LPB at 12, still all out of time cycles.
Is it a problem somehow cause by the inclusion of a 0 value, or none, for these commands?
There are only 15 values left if the ‘zero speed cycle’ is included, where there could have been 16 values total if ‘0’ was used as ‘1’…(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F)
For example:
–V0F - no vibrato / speed zero vibrato at maximum depth
–T0F - no tremelo / speed zero tremelo at maximum depth
–N0F - no autopan / speed zero autopan at maximum depth
Seems like there is no need to enter vibrato, tremelo or autopan commands for no vibrato, tremelo or autopan, yet the ‘0 depth’ takes up one of the values
It went pretty crazy at 3TPL, sounds a bit like yingwie malmsteen guitar arps
I 100% agree with Garrett Wang