oh, i had put this in the serato help, not video help because i thought the analyze/overview functionality fell within the bounds of the ssl software... didnt realize the video guys had anything to do with it, especially now that mp4 reading is native to ssl and does NOT require installation of the SV/VSL plugin.
we are only talking about building and scanning files in... not actually using them.

but what ever way it gets addressed, ;-)

Hi Joshua Carl,


Thanks for the detailed information here ( linked thread also ). Sorry I didn't get to the thread earlier as we have been really busy recently.

This is an analyzing and overview issue but falls within Serato Video support as you use video files and this inherently adds more variables to the issue.

Reading your Daily Journal discussion it seems you came full circle and resolved most of your issues along the way. There is certainly a lot of useful workflow tips for users in your diary account of the upgrade.

Generally speaking most of the crashing and analyzing issues seemed to be related to corrupt files. Non standard containers and incompatible video codecs.

As phatbob mentioned because of the changes from 1.9.2 to 2.3.3 the tag lib has gone through extensive updates including MP4 Tag Lib specifically in Scratch Live 2.3.3 which resolved the corruption issues that were apparent in Scratch Live 2.3.1.

I'm not to sure where you want to go from here as you seem to have resolved the issues with crashing on analysis.

Are you still having issues with the MIDI in Scratch Live 2.3.3 ?

If you can let me know how I can be of assistance and which issues you want me to look into I will be happy to oblige.

Anthony

I'm inmy phone...

But yeah.. Still getting the midi issue.
Even after making sure everything is up to date... When I look at the cue button; on the screen the cue 1 play button sometimes stays illuminated.
As if I am holding the cue button down...but I'm not... It's on absolute in the midi settings

Im going to try my dicers and nano pad this week to try to R/O whether its in fact a midi issue
or an X1 issue...

but in 192, it was fine.

Hi Joshua Carl,

I ran some tests here with Scratch Live 2.3.3 and 2.4.1 and the Knontrol X1. Also tested with Serato Video and MP4 files.

"I had did the NI update maybe around Xmas, but I don't run any extra software WHILE runnin the x-1 . No midi pipe, or anything like that.
It certainly worked, but it's almost as the button strikes were being buffered...
Example: X = midi button key strike 0: how it played
X...X....X . X.X.X
0...0....0 . 0.....00"

I was unable to reproduce the same response that you mention above. On occasion the first instance of the key strike seems to be delayed in video but not audio. This would be due to video buffering.

I haven't seen any anomalies in the software like the CUE button staying illuminated.

Have you monitored the values being sent from the Kontrol X1 in MIDI Monitor ?

Let me know what you find with the Korg NANO and the Dicers attached. If you find that you are getting the same response with other devices then we will look at other options.

so I have been noticing some tag writting on ejecting...
mostly on tracks Ive never played before (since the switch)

tracks Ive been playing every week for the last 3 weeks dont seem to get re-writes.
but they are quick, maybe 3-4 seconds tops.


I also used my dicers this week and saw ZERO...and im MEAN ZERO lag on cue points.
I was hammering on those things like Neil Pert.

Im going to try to get that Nanopad hooked up and whats going on there....

so, its certainly gotta be a Midi issue.
I also had the strangest midi issue ...
on my x1 I have CC __ mapped to start loop.
with out pressing ANYTHING, hands in my pockets... it would just start looping.
I shot a video...
note I am not touching ANYTHING, NOTHING.
I have the mouse over the loop cancel button, you can see me click it off with the mouse and seconds later it fires again on its own.
the remedy was un-midi mapping the "in" button on the x1

The only other little headache Ive run into is auto Gain.
I used this feature in 1.9.2 and it worked great, I only had to make miniscule adjustments on
the Trim.... now I find my self constantly adjusting the gains.

other than that Performance has been solid in 2.3.3(18)

Thanks Anthony.

video of ghost midi:
Watchwww.youtube.com
(sorry forgot to flip phone sideways, its 720p though)

if you notice when the midi in depresses, its a static signal.
as if someone is holding down the button.... not just tapping it.

Hi Joshua Carl,

Thanks for the info here, that is odd...

Are you using the Native Instruments MIDI Editor ?

I have noticed some strange behavior with the Kontrol X1 it seems to cycle through some of the controls on it's own. While not touching the controls at all as you have mentioned.

I don't have a definitive answer as to what is going on here but it seems to be a bug with the Control Editor software.

Have you tried assigning the loop IN and OUT to another button ? Do you get the same result ?

I did test with the Control Editor>Preferences>Touch Select OFF and MIDI assigned the buttons manually and didn't have the same anomalies.



There hasn't been any changes in the Auto gain functionality but we did make a change to the Output Gain signal to make it constant across all Rane devices.

Hey Anthony, thanks for the reply.

yeah, I used the Midi Control editor software.
I was going to change the CC# thatI had assigned to the loop-in button on the x1
see if that makes a difference.

there is certainly buggy behavior in the x1.
I love it as a standalone controller, but it certainly has its glitches
Ill mess with the touch select, see if that helps.
I mad made my own midi layout from scratch in the midi editor...
but Im relieved that the question I had been asking for 2 years is now answered
if in fact a 7200 or 5400 rpm FW800 drive is to blame for delayed/missed key strikes
on a midi device.
going back to the dicers + the x1 has proven in the dicers post 2.0 HID mode that you can
fire cue points as fast as you fingers can do them....
where as in 1.9.2, when the dicers were midi you could not.


Ill mess with the autogain... maybe its just a placebo effect on my brain from the upgrade.
it just seemed like I am tweeking the 57 gains more often than I used to in 1.9.2 to gain
a balanced input from channel 1 & 2.

thanks again.
I do see that 2.4.2 has mp4 re-writting issue fixes...
but its really not an option for me to upgrade past 2.3.3 at this moment.

There was in issue once that the Midi events were tied to the GUI refreshing. I remember that the slower the GUI refreshed the worse the MIDI events reacted. Not sure whether this is still the case.


It has not been fully fixed yet.

Hi Joshua Carl,

I haven't managed to test any further on this one.

I found these videos on youtube from Konix that may be of use although they are two years old.

Watchwww.youtube.com

Watchwww.youtube.com

yeah, i watched those when i first got the x1

for the last year+ i thought the external HD was to blame for the delayed midi performance.
even in 192 i could not really drum fast with any midi controller...

but now with the dicers in hid mode they are very very responsive,
so Im leaning to it being just way too much info for midi, too fast.
im not talking about just tapping along at a 128 1/1 kick.
i mean trying to do a 1/16th fill with cue points....
i can do it now with the dicers.... not the x1.
I could not do it with the dicers in midi mode (192)

its not the end of the world though, of course i would RATHER use only the x1.
but breaking the dicers out has opening up some performance windows
(Ie using the loop roll + cue points at the same time... no page changing)

I am, like i said still getting re-writes... but you guys are well aware of that.
but performance wise 2.3.3 18 has been pretty solid.

Hi Joshua Carl,

Thanks for the info mate, the Novation Dicers are a nice piece of kit.

Could you attach a couple of the files that are still re-writing tags for me to have at look here.

I'm glad 2.3.3 is working well for you now.