Activity for Menno
-
Menno posted a comment on ticket #8
great stuff But some feedback: it may be on my system only (Linux Mint 19), but it is hard to see the loop lines under the sample. Please look at the attachment. Can these lines become more apparent somehow?
-
they certainly do :) already built and testing... On Thu, Jul 19, 2018 at 5:54 PM, Rui Nuno Capela rncbc@users.sourceforge.net wrote: things are getting better (hopefiully)... just check 0.9.1.21git.[667a81] and beyhond... ;) [tickets:#8] Start sample from another point in time Status: pending Milestone: git_head Created: Thu Jan 04, 2018 10:21 AM UTC by --- Last Updated: Tue Jul 17, 2018 09:32 AM UTC Owner: nobody Samples can currently only be played starting from the beginning. This is problematic...
-
Does that mean that the Settings window in Zyn do not show the values correctly? But the values of the commandline are actually active? i do not see a config file where those kind of values are stored. And it isn't stored in the .xmz file either....
-
i do not see an option to close the issue - can you close it please, Rui?
-
Now that Samplv1 has the 2 looping methods in place, we like to address the issue of the start locator again. It is non-intuitive to go to Audacity, cut the sample, go back to Samplv1, load that sample and find out that after all that sample start is not what we are looking for, so going back to Audacity, cut, load, not good, back to Audacity etc. etc... Having a start locator should not be too difficult on the level of math. In pseudo-code: start sample = start sample + locator_start_sample
-
We have tested the Xfade with pitched and non-pitched sounds. Both with success! We found that with pitched samples the Zero looping method is to be preferred, and with non-pitched the Xfade method. I will write my findings in the Samplv1 User manual: https://github.com/rncbc/samplv1/wiki/User-Manual i will close the issue - thanks!!
-
i do believe this is working now - i have sent you (WeTransfer) the result of my tests to rncbc at rncbc dot org. Clearly the Xfade method is winning now. It's great to have both methods available! perfect.wav has 5 segments: 1. the key C4 as reference 2. C2 without Zero or Xfade. plops at for example: 8.833 seconds 3. C2 with Zero method. Still audible plops at for example 21.244 4. C2 with Xfade method. No more plops at all with fade setting of (for example)150 samples 5. C2 with both Zero and...
-
Does that mean that the Settings window in Zyn do not show the values correctly? But the values of the commandline are actually active?
-
i have attached a screenshot. I assume -b and -o can be set from the commandline and Settings of Zyn should reflect those numbers, am i right?
-
Okay, i'll let you know when i send you files via WeTransfer - and you can pich them up from your junk mail. The sample 'plopsmono' is imported at key C4. This is the first key to be heard in the wav file. Then i go to C2. I choose the 2 octaves down so that there is plenty of time to hear the clicks produced with the different looping methods. Of course, the clicks are on every key but i have chosen C2 to be the reference for my comparison Zero method <--> Xfade metheod. I notice a dip of only 2...
-
Right, attacked the issue right away.... I have made a comparison between the Zero and the Xfade method. using the same sample. I had a settings the highest fadetime possible = 2000 samples - a setting that should ensure the smoothest fade ever...alas it does not as there is stille a DC issue in this looping method. It is my opinion that because of this DC jump there will never be a smooth transition. That is why, right now, the zero method is still the winnerrrr... I will send to you via WeTransfer...
-
Thanks Rui, for the advice to look at the github for the latest xfade branch. I hope i have some time one of these days to test it all and provide you with a detailed report and all possible files i have used for this test :) As a side note, a week ago i did sent you a rendered audio mp3 file via WeTransfer but you did not download it. WeTransfer reported that to me. I did sent it to you using WeTransfer because the file was rather large and i don t think SourceForge accepts the size of it. At the...
-
--oscil-size remains 1024
-
sure. I'll give you 1. the sample plopmono (sorry as i thought i had already send it) 2. the plopjes .samplv1 file 3. 3. the wav and times of ticks you have already: sunday_version.mp3 What does YMMV mean? My gues is Your then something...
-
sure. I'll give you 1. the sample plopmono (sorry as i thought i had already send it) 2. the plopjes .samplv1 file 3. 3. the wav and times of ticks you have already: sunday_version.mp3 What does YMMV mean? My gues is Your then something...
-
i have tested and will tell: yesterday and today when recoding the loops in Audacity, i notice 3 samples out-of-line. They spil all the fun. They are not in line with the rest of the fades and i do not have a clue why this is happening. When the sample is loaded at its original place C4 and played at C4, all goes well - perfect fades. Playing lower ánd higher notes reveales those 3 samples that wish not to be tamed! Please have a look at the attachment. when played lower than C4: - 4.72840 - 8.72514...
-
i have done some new tests with the sample file you already have, 'plopmono.wav'. I have recorded the result in Audacity. First, i have set a loop in the sample and play it. When i play the sample lower, you can hear and see in Audacity that there are sudden changes in the sound caused by the loop - for example as second 7.828. The fade out/in are possibly long long enough to smooth this out? Attached are the .samplv1 file and the AUdacity mp3
-
i have done some new tests with the sample file you already have, 'plopmono.wav'. I have recorded the result in Audacity. First, i have set a loop in the sample and play it. When i play the sample lower, you can hear and see in Audacity that there are sudden changes in the sound caused by the loop - for example as second 7.828. The fade out/in are possibly long long enough to smooth this out? Attached are the .samplv1 file and the AUdacity mp3
-
No problem, i am used to smoking speakers....i am doing some betatesting for other programs as well... Because i am not a programmer but a user, i feel betatesting is the one thing i can do in return. I'm a betatester for another program as well and the goal is always to make things better :) And, of course, in this case, i want Samplv1 to work fantastically because it is the only Linux sampler that i know of. and the basic functionality is nearly complete. (At one point, i want to write a manual...
-
Yes, DCoffset is the result of Samplv1 i recorded in AUdacity. I have made a video and will wetransfer it to you, along with the loop i use. Perhaps you can replicate it. I think it has to do with the end of the loop when this is set at the very end of the sample. I tries to find the beginning of the loop (which is in this case the very beginning of the sample also) . Please have a good look at the sample counter, when i change to one sample shorter, it loops all right, but one sample longer the...
-
This time i get some ticks in the loop, probably some DC offset - see attachments How many samples are the fade outs/ins at the moment?
-
This time i get some ticks in the loop, probably some DC offset - see attachments How many samples are the fade outs/ins at the moment?
-
wow...didn't realize you were still at it :) I'll be happy to do the betatesting tonight and report back!
-
That is disappointing :( I asked the Csound forum http://csound.1045644.n5.nabble.com/Csnd-how-to-floop-td5762234.html#a5762254 and someone came up with the math how to do it: http://www.csounds.com/udo/displayOpcode.php?opcode_id=55 Also, in the code from the looping opcodes from Csound i see some crossfading done around line 600: https://github.com/csound/csound/blob/develop/Opcodes/sndloop.c but that's all abracadabra to me.... that's all about xfading i could find on the internet.
-
i couldn't wait until Monday and had some time on my hands, so.... for testing i changed the value of xtime =2400, recompiled AND made another one with xtime = 4800, then recompiled. Every time i deleted the version and installed it anew. What i notice are the holes - see attachment. The sawwave above has xtime = 4800, while the second one has xtime = 2400 Clearly one can see the difference in the holes. This means that the xfade is not working as i expected. The fade out of the end of the sampleloop...
-
Hi Rui, we (Harry and me who both attended LAC2018) are very happy you are willing to look into this! Next Monday and Tuesday we will have our musical sessions and it is then that we will write to you in detail about this issue. We will make some examples as well, because on Monday we will have one machine with one looping method at zero crossings and a second machine with the xfade branch. Luckily I was able to build and install samplov1 from the xfade branch without probs. And noticed that you...
-
i was reading up on why the decision came to be to drop the small fade in and out to make a seemless loop. I do understand why the decision was made to look for the zero-crossing method only, as you mention in that Github issue #12. Quote from this issue: 'good news are micro-fade-in/outs on loop points are now gone ( c226562 ) bad news are that other, more atonal but looped samples may now click harder than before :( ' We on the other hand work with ambient sounds, that falls into the catagory 'more...
-
i was reading up on why the decision came to be to drop the small fade in and out to make a seemless loop. I do understand why the decision made to look for the zero-crossing method only, as you mention in that Github issue #12. Quote from this issue: 'good news are micro-fade-in/outs on loop points are now gone ( c226562 ) bad news are that other, more atonal but looped samples may now click harder than before :( ' We on the other hand work with ambient sounds, that falls into the catagory 'more...
-
i was reading up on why the decision came to be to drop the small fade in and out to make a seemless loop. I do understand why the decision made to look for the zero-crossing method only, as you mention in that Sourcefroge issue #12. Quote from this issue: 'good news are micro-fade-in/outs on loop points are now gone ( c226562 ) bad news are that other, more atonal but looped samples may now click harder than before :( ' We on the other hand work with ambient sounds, that falls into the catagory...
-
it appears that Samplv1 was recently implemented with a different looping system and the choice was made for that one. This means this Ticket can be closed.
-
we do not ask for an audio sample editor. We are asking for a locater that represents the start of the sample playback on that location. i have attached a screenshot of the sampler (Grace) that we are working with now. It has 4 locators: the blue ones are for the loop, the green one is the Playback start locator. This is the one i am talking about. This start locator makes it easy to, on-the-fly, find a start of our liking without going several times back to Audacity before finding the right playback...
-
we do not ask for an audio sample editor. We are asking for a locater that represents the start of the sample playback on that location.
-
set loop time for fade in and out
-
Thanks, libtool did the trick - i could build QMidiArp without further problems....
-
perhaps i need another program. I get an error in line 29: possibly undefined macro:...
-
yes i think i get it :) Being able to assign a CC would be a good start for what...
-
thanks Frank, for your reply. I know Csound can do it, PD as well, and at the moment...
-
thanks Frank, for your reply. I know Csound can do it, PD as well, and at the moment...
-
i am starting to think that this request should be a QMidiRout request - not a QMidiArp....
-
Hi Frank, yes, i know about the channel output setting. But i am looking for a way...
-
option to change midi channel output
-
i understand, thank very much for wanting to help at a later time. Michael Gogins...
-
i do not know how to do that. I wish i could, but my talents lay elsewhere. Can you...
-
Loris & Csound 6
1