@thcilnnahoj wrote:
OK, testing done, but it seems the problem I have might be different from yours after all. 🙁
The strange problem I remembered (and now confirmed) is that I have trouble getting the first input note recorded at all if it is played close to the start of a bar.
This happens only when a new sequence is created by the recording – NOT when I record with a sequence already present on the track and the recorded notes get added to it. (Frits, if you need any more info, just tell me once you get back!)Other than that, I didn’t notice any timing-related problems… If and when the first played note was recorded, it was on time. 😕
Does it happen regardless of whether you ‘overdub’ an already existing MIDI sequence or let Podium create one while recording?
did various ways of recording ( but allways with LOOP ON if that matters ) :
did a redording on the first run of the looped region – let the loop pass one time ( to create a clip ) before recording into the existing clip – a mix of both
sometimes it happens sometimes not – i can’t track it down to a certain preference setting ( time stamp from driver on / off ) / plug in / input device
on a side note : sometimes while recording in loop mode a second clip is created when i don’t input midi notes for a short time
EDIT : this happens only while recording midi input from a physical device – this does not happen when i record the midi output of a plug in !!!
EDIT2 : switching LOOP ON or OFF does NOT matter – recording a new clip or overdubbing an existing clip does NOT matter – piece of crap this is!!!
did some further testing : happens with Podium Free too …
is this only me???
does nobody else suffer from this issue???
other hosts do work fine with these settings / drivers / setups … 😯
@Zynewave wrote:
So the problem you reported in that other topic, is the exact same problem you still have today?
yes, some hardware has changed ( soundcard / MIDI input devices ) but the issue is still the same …
first time i had this issue was at about 2.20 i guess
it does NOT change anything if i check use time stamp or uncheck it
it happens with every MIDI input
way too early is about 1/16 at bpm range 100-130
the way of recording does not matter ( loop switched on / off – punch in / out enabled / disabled )
edit : maybe you can remember : http://www.zynewave.com/forum/viewtopic.php?p=12630&highlight=#12630
obviously it was before 2.20 ( tempus fugit ! )
just changed version of Podium – drivers ( M-Audio 2496 ) are up to date – drivers of MPD18 too ( which i used when i faced the issue recently ) – happened in earlier versions too – it’s hard to replicate – issue comes and goes – NB the note IS recorded but way too early so i have to quantize it in order to get it into the loop …
i see, so we can only keep posting requests and keep our fingers crossed, can’t we? i thought keeping in touch with existing customers and listening closely was a great chance for small companies to stay in business?
nevermind
you may call my nosey but i’d really like to get an idea of what to expect in the next releases – something like a roadmap or a list divided into a) high priority b) normal c) when i’ve finished a) and b) !
or maybe hold a poll where every licensee can vote for his / her top 3 features out of a list of your 50 topics ?!?
Thanks for joning Frits, i read about the MCU ( only ) support -this was ment to be a call for users sharing their experience – Behringer BCF supports MCU and so does the Korg NanoKontrol2 – does anybody use any of these 2?
@Zynewave wrote:
@michi_mak wrote:
update – after a second install of rc3 i can’t reproduce this issue ( i kept preferences again ) …
Could it be the timeline zoom that tricked you the first time?
i don’t think so, notes entered with the mouse were 1/32 or 1/16 …
update – after a second install of rc3 i can’t reproduce this issue ( i kept preferences again ) …
@Zynewave wrote:
@michi_mak wrote:
@Zynewave wrote:
@michi_mak wrote:
had a quick run with rc3 : it got an issue with midi note lengths : when recording with my mpd18 i can NOT alter the note lengths to say 1/32 – they stay at about 2 bars length ( does not happen with 2.42 ) – xp 32bit sp3 with respective rc3
I can’t reproduce this problem (Vista 32bit). Can you provide more details please? What do you mean with “stay at about 2 bars length”; Did you record them at 2 bars length, or can’t you resize them smaller than 2 bars?
rc3 recorded the notes with a length of around 2 bars ( not precisely 2 bars btw ) and i was not able to resize them ( smaller ) later on. in 2.42 these notes get recorded with a length of around 1/32 to 1/16…
And if you uninstall 3.0, and reinstall 2.42, (and not change your device setup/project), then you are able to record lengths below 2 bars?
Is the realtime plugin playback ok, when you record?
Have you tried the various ways you can resize note events, e.g. alt+clicking the note value buttons in the note editor? Still not able to resize the note events? If not, please provide a screenshot or mail me the project file.
yes, 2.42 didn’t show this issue ( keeping preferences ), playback was ok ( i triggered drum samples so this was not an issue as the sample were much shorter than 2bars 🙂 ) – alt clicking did NOT work – will try to provide a screen shot asap.
@Zynewave wrote:
@michi_mak wrote:
had a quick run with rc3 : it got an issue with midi note lengths : when recording with my mpd18 i can NOT alter the note lengths to say 1/32 – they stay at about 2 bars length ( does not happen with 2.42 ) – xp 32bit sp3 with respective rc3
I can’t reproduce this problem (Vista 32bit). Can you provide more details please? What do you mean with “stay at about 2 bars length”; Did you record them at 2 bars length, or can’t you resize them smaller than 2 bars?
rc3 recorded the notes with a length of around 2 bars ( not precisely 2 bars btw ) and i was not able to resize them ( smaller ) later on. in 2.42 these notes get recorded with a length of around 1/32 to 1/16…