Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Release Candidate Firmware V1.24 RC12
#21
Still getting strange behavior with tables in RC4!

Check this video out. Notice how it hits the first row of the table twice - the first of these times it doubles the value (although only doubles the value on the first play).

Reply
#22
(02-09-2021, 12:44 AM)depaffect Wrote: Still getting strange behavior with tables in RC4!

Check this video out. Notice how it hits the first row of the table twice - the first of these times it doubles the value (although only doubles the value on the first play).


I can imagine that you could get problems with the resync and maybe also with the playing order.
The spfx is processed earlier than the table command. 
Try either being looped or maybe set the tables from the FX column before the spfx (like table on fx1 and the spfx on fx2.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#23
(02-09-2021, 06:15 AM)XORadmin Wrote:
(02-09-2021, 12:44 AM)depaffect Wrote: Still getting strange behavior with tables in RC4!

Check this video out. Notice how it hits the first row of the table twice - the first of these times it doubles the value (although only doubles the value on the first play).

I can imagine that you could get problems with the resync and maybe also with the playing order.
The spfx is processed earlier than the table command. 
Try either being looped or maybe set the tables from the FX column before the spfx (like table on fx1 and the spfx on fx2.

Oh taking it back, I didn't look well.
There was a problem with tables in general with this RC. I will upload a new version in a few minutes which fixes this issue and tables are working well again.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#24
UPDATE RC5:
- fixed that table issue introduced with the last RC's again
- updated ratch functions so they work also well if externally clocked

Files in the first post are updated.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#25
Awesome, tables now work great!!
Reply
#26
Wink 
(02-09-2021, 02:20 PM)XORadmin Wrote: UPDATE RC5:
- fixed that table issue introduced with the last RC's again
- updated ratch functions so they work also well if externally clocked

Files in the first post are updated.

Take a look at this. 

REGULAR ONESHOT 
PING PONG ONESHOT 

RC5 

Reply
#27
(02-10-2021, 03:20 PM)T3t_one Wrote:
(02-09-2021, 02:20 PM)XORadmin Wrote: UPDATE RC5:
- fixed that table issue introduced with the last RC's again
- updated ratch functions so they work also well if externally clocked

Files in the first post are updated.

Take a look at this. 

REGULAR ONESHOT 
PING PONG ONESHOT 

RC5 

Looks like it gets an additional retrigger point which makes it think it is finished. I guess this is like it always was, right?
What worries me more is that additional Dot with this font with a #  Big Grin
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#28
(02-10-2021, 03:48 PM)XORadmin Wrote:
(02-10-2021, 03:20 PM)T3t_one Wrote:
(02-09-2021, 02:20 PM)XORadmin Wrote: UPDATE RC5:
- fixed that table issue introduced with the last RC's again
- updated ratch functions so they work also well if externally clocked

Files in the first post are updated.

Take a look at this. 

REGULAR ONESHOT 
PING PONG ONESHOT 

RC5 

Looks like it gets an additional retrigger point which makes it think it is finished. I guess this is like it always was, right?
What worries me more is that additional Dot with this font with a #  Big Grin

Can you explain the logic behind this? Looks like the first line is playing twice and the last isn't playing at all. Extra dot appears on the Patch screen too, as 'TRIGGR PROB .  %'. Also in Setup under 'CONFIRM SEQ. STOP'.
Reply
#29
(02-10-2021, 04:16 PM)T3t_one Wrote:
(02-10-2021, 03:48 PM)XORadmin Wrote:
(02-10-2021, 03:20 PM)T3t_one Wrote:
(02-09-2021, 02:20 PM)XORadmin Wrote: UPDATE RC5:
- fixed that table issue introduced with the last RC's again
- updated ratch functions so they work also well if externally clocked

Files in the first post are updated.

Take a look at this. 

REGULAR ONESHOT 
PING PONG ONESHOT 

RC5 

Looks like it gets an additional retrigger point which makes it think it is finished. I guess this is like it always was, right?
What worries me more is that additional Dot with this font with a #  Big Grin

Can you explain the logic behind this? Looks like the first line is playing twice and the last isn't playing at all. Extra dot appears on the Patch screen too, as 'TRIGGR PROB .  %'. Also in Setup under 'CONFIRM SEQ. STOP'.

It does play the last line. 
And it plays the first line once. But the one time pingpong plays 0->15->0 and that are 31 steps. Step zero is the last one and the first one when the table is started again. Thats why it sounds like twice.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#30
(02-10-2021, 04:43 PM)XORadmin Wrote:
(02-10-2021, 04:16 PM)T3t_one Wrote:
(02-10-2021, 03:48 PM)XORadmin Wrote:
(02-10-2021, 03:20 PM)T3t_one Wrote:
(02-09-2021, 02:20 PM)XORadmin Wrote: UPDATE RC5:
- fixed that table issue introduced with the last RC's again
- updated ratch functions so they work also well if externally clocked

Files in the first post are updated.

Take a look at this. 

REGULAR ONESHOT 
PING PONG ONESHOT 

RC5 

[EDIT]
Looks like it gets an additional retrigger point which makes it think it is finished. I guess this is like it always was, right?
What worries me more is that additional Dot with this font with a #  Big Grin

Can you explain the logic behind this? Looks like the first line is playing twice and the last isn't playing at all. Extra dot appears on the Patch screen too, as 'TRIGGR PROB .  %'. Also in Setup under 'CONFIRM SEQ. STOP'.

It does play the last line. 
And it plays the first line once. But the one time pingpong plays 0->15->0 and that are 31 steps. Step zero is the last one and the first one when the table is started again. Thats why it sounds like twice.



It's definitely showing the penultimate line being played twice in this new, slowed down video for REGULAR ONESHOT.

(02-10-2021, 05:03 PM)T3t_one Wrote:
(02-10-2021, 04:43 PM)XORadmin Wrote:
(02-10-2021, 04:16 PM)T3t_one Wrote:
(02-10-2021, 03:48 PM)XORadmin Wrote:
(02-10-2021, 03:20 PM)T3t_one Wrote: Take a look at this. 

REGULAR ONESHOT 
PING PONG ONESHOT 

RC5 

[EDIT]
Looks like it gets an additional retrigger point which makes it think it is finished. I guess this is like it always was, right?
What worries me more is that additional Dot with this font with a #  Big Grin

Can you explain the logic behind this? Looks like the first line is playing twice and the last isn't playing at all. Extra dot appears on the Patch screen too, as 'TRIGGR PROB .  %'. Also in Setup under 'CONFIRM SEQ. STOP'.

It does play the last line. 
And it plays the first line once. But the one time pingpong plays 0->15->0 and that are 31 steps. Step zero is the last one and the first one when the table is started again. Thats why it sounds like twice.

[post can't have 2 videos]

It's definitely showing the penultimate line being played twice in this new, slowed down video for REGULAR ONESHOT.

 

Tried to save and NerdSEQ froze.


Attached Files
.nrd   TABLE.NRD (Size: 433,53 KB / Downloads: 2)
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)